Configuring
On a distributed system, you deploy and configure the provided archives on a supported application server to test and run your applications in the environment that you use in production. When you use the WebSphere® Application Server profile templates, deploy these archives by using scripts.
Important: While deploying the archives, enable IBM® License Metric Tool, and make
sure that you have the correct license type. You must deploy Decision
Center, Rule Execution Server, and
the Decision Server Events runtime
as an exploded archive to activate the tool. For more information,
see Modifying the product license type.
Note: To configure Decision Server
Insights, follow
the instructions under Configuring Insight servers.
- Configuring on Liberty profile 8.5.5.6
- You must configure the Operational Decision Manager components manually.
- Configuring on WebSphere Application Server 8.5 and 8.5.5
- You can use a cluster on WebSphere Application Server to achieve high availability and scalability. Profile templates are provided for cluster configuration with the manageprofiles command. You can also configure the Operational Decision Manager components manually.
- Configuring on Tomcat 7
- To use Operational Decision Manager on a new instance of Tomcat, you must establish your databases, deploy the provided archives for the server, and set configuration properties.
- Configuring on JBoss 6.1 and 6.3
- To use Operational Decision Manager on a new instance of JBoss, you must establish your databases, deploy the provided archives for the server, and set configuration properties.
- Configuring on Oracle WebLogic Server 11g, 10.3.6, and 12c
- To use Operational Decision Manager on a new instance of WebLogic Server, you must establish your databases, deploy the provided archives for the server, and set configuration properties.
- Configuring on Java™ SE 7
- 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.