Decision Management & Intelligence (ODM, DI)

Decision Management & Intelligence (ODM, DI)

Connect with experts and peers to elevate technical expertise, solve problems and share insights


#Data
#Data
#Businessautomation
 View Only
Expand all | Collapse all

Go into migrations from Dev, Test, UAT and Prod. How is that done? A normal Java ear gets moved?

  • 1.  Go into migrations from Dev, Test, UAT and Prod. How is that done? A normal Java ear gets moved?

    Posted Mon February 20, 2012 04:20 PM
    This is a question that was asked during the February 15 Lab Chat on WODM:

    Go into migrations from Dev, Test, UAT and Prod. How is that done? A normal Java ear gets moved?



  • 2.  Go into migrations from Dev, Test, UAT and Prod. How is that done? A normal Java ear gets moved?

    Posted Fri March 09, 2012 06:23 PM
    First, let me describe the concept of the Decision Center repository.  IBM Decision Center (a module of Operational Decision Management V7.5) is a design-time, central repository for all decision artifacts and when ready, these artifacts are deployed from Decision Center to a Decision Server runtime.  One Decision Center can be used to deploy rulesets to multiple Decision Servers, so generally there is a single Decision Center for all environments and a Decision Server in each environment (Dev, Test, UAT, Prod, etc.).

    For business rules, the artifact that is deployed to the Decision Server is a JAR file containing resource and rule files in a language interpreted by the Rule Execution Server, so they are not Java nor are they WAR or EAR files.  Once deployed, business rules can be immediately invoked using POJO and EJB rule sessions and Web Services, among other options.  For business events, the artifact that is deployed to the Decision Server is an XML file representing the various filters and rules in a language interpreted by the Event Runtime, so again it is not Java nor WAR or EAR files.