Configuring Operational Decision Manager

You must configure Rule Execution Server and Decision Center on a supported application server.

After installing Operational Decision Manager on your machine (see Installing Operational Decision Manager), you must configure Rule Execution Server and Decision Center on a supported application server.

When you deploy the archives, enable IBM® License Metric Tool, and make sure that you have the correct license type (see ILMT Tagging).

• List of supported languages

  Operational Decision Manager interfaces and rule editors are translated into many languages.

• Configuring Rule Designer

  Rule Designer is an Eclipse-based development environment. You can open the designer in a supported language, change your Rule Designer Java™ (JVM), and set up the product documentation to consult locally.

• Setting up Ant to automate processes

  You must have Apache Ant installed on your computer to deploy RuleApps to Rule Execution Server, automate managerial tasks within Decision Center, and run many of the samples.

• Securing Operational Decision Manager

  To use Operational Decision Manager provides servers and components for use in IT environments for software development, testing, and production. Securing these applications and their data is important to meeting your organization's compliance and security requirements.

• Mandatory: Create the databases

  Before you configure an application server, you must create or establish the databases for Rule Execution Server and Decision Center.

• Configuring on Liberty profile

  To use Operational Decision Manager on WebSphere Liberty, created your databases and deploy the provided archives.

• Configuring on Tomcat

  To use Operational Decision Manager on Tomcat, establish your databases and deploy the provided archives.

• Configuring on JBoss®

  To use Operational Decision Manager on JBoss, establish your databases and deploy the provided archives.

• Configuring on Java SE

  To use Operational Decision Manager on Java SE, you must deploy a simple Java Standard Edition JAR file. This deployment implements a lightweight J2C container, which uses a pooling infrastructure. The resource is scoped to a client application.