Abstract
Target audience Application architect, developer, business analyst In this chapter you will learn Technology and deployment issues to consider when planning your integration, like transaction support, scalability, data access, ruleset deployment How to manage the ruleset life cycle How to implement rule execution as a decision service using web service, SCA and JMS Key points Access to the data model used by the rules can impact performance and should be part of the decision service implementation not the ruleset. Data model definitions are different: there is one for messaging and service contract level; one for the rule execution, and one for persistence in the database. Parallel processing of rule execution is a common implementation in business application to support scalability and hot deployment. Ruleset parameters should not be exposed as generic service, but behind a service interface which specify the business intent of the different decision service operations.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
A is for ATOMICITY, C for CONSISTENCY, I for ISOLATION, and finally D for DURABILITY.
- 2.
See the apache project at http://commons.apache.org/pool/.
- 3.
See Java Thread API at http://download-llnw.oracle.com/javase/6/docs/api/packagejava.lang.
- 4.
See specification at Java Persistence API: http://www.jcp.org/en/jsr/detail?id=317.
- 5.
See SDO specification at http://www.osoa.org/display/main/service+data+objects+home.
- 6.
- 7.
See SDO Apache project in http://tuscany.apache.org/sdo-overview.html.
- 8.
Java Archive: based on the zip compression format a Java archive groups all the java artifacts needed to a java application. At start-up, a java application load a set of jars files so it can execute.
- 9.
http://www.smartenoughsystems.com/ and the book from James Taylor and Neil Raden, “Smart Enough Systems: How to Deliver Competitive Advantage by Automating Hidden Decisions.”
- 10.
- 11.
See Chap. 6 for detail on those concepts.
- 12.
See Sun Core J2EE Patterns – Data Access Object at http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html.
- 13.
The JSR 94 specification can be found at http://jcp.org/aboutJava/communityprocess/review/jsr094/index.html" \t "_blank.
- 14.
POJO is an acronym for Plain Old Java Object and is used to emphasize that a given object is an ordinary Java Object, not a special object like an Enterprise JavaBean.
- 15.
Event Driven Architecture.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Boyer, J., Mili, H. (2011). Issues in Deploying Rules. In: Agile Business Rule Development. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-19041-4_12
Download citation
DOI: https://doi.org/10.1007/978-3-642-19041-4_12
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-19040-7
Online ISBN: 978-3-642-19041-4
eBook Packages: Business and EconomicsBusiness and Management (R0)