IDEAS home Printed from https://ideas.repec.org/h/spr/sprchp/978-3-642-19041-4_13.html
   My bibliography  Save this book chapter

Deploying with JRules

In: Agile Business Rule Development

Author

Listed:
  • Jérôme Boyer

    (IBM)

  • Hafedh Mili

    (Université du Québec, Montréal)

Abstract

Target audience Application architect, software architect, developer In this chapter you will learn How rulesets are packaged as part of a RuleApp What are the ruleset versioning capabilities How to manage a RuleApp in Rule Team Server and in Rule Execution Server How to use the Rule Engine API, the JSR 94 or the Rule Execution Server rule session API to integrate rule engine processing into your application How to use a rule engine using JMS deployment The concept of Transparent Decision Service How to identify which rules executed using the Decision Warehouse capability How to develop queries to select the rules you want to have in your ruleset Key points The main deployment unit when using the rule execution server is the RuleApp, which can be created and managed by a business user within rule team server. JRules offers a very flexible API to integrate the rule engine into the business application leveraging JEE or J2SE deployment model. Rule execution server is simple to use and delivers the rich set of features to manage a ruleset in production and scale vertically. Business users use Rule Team Server to author but also deploy rules to the different RES. Rulesets can be exposed as services, but for most business application deployed in SOA a decision service is part of reusable business services therefore better deigned with a meaningful interface and implemented using Java using the RES API.1

Suggested Citation

  • Jérôme Boyer & Hafedh Mili, 2011. "Deploying with JRules," Springer Books, in: Agile Business Rule Development, chapter 0, pages 419-444, Springer.
    • Handle: RePEc:spr:sprchp:978-3-642-19041-4_13
    DOI: 10.1007/978-3-642-19041-4_13
    as

    Download full text from publisher

    To our knowledge, this item is not available for download. To find whether it is available, there are three options:
    1. Check below whether another version of this item is available online.
    2. Check on the provider's web page whether it is in fact available.
    3. Perform a search for a similarly titled item that would be available.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:sprchp:978-3-642-19041-4_13. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.