Build operational Decision Manager cluster

The operational Decision Manager (ODM) cluster contains the full functionality of Decision Server and Decision Center for enterprise testing, simulation, and Operation http://www.aliyun.com/ Zixun/aggregation/13784.html "> Business decisions.

As shown in the following illustration, two clusters are defined in the ODM unit for organizing Decision Server instances and Decision Center instances. Each instance member in the same cluster has the same configuration to achieve load balancing and failover.

Figure 1. ODM cluster topology

Before you start

Before starting to build the ODM cluster, you need to install the following software to:

IBM WebSphere Creator Server Receptacle deployment 8.5 IBM Operational Decision Management 8.5 DB2 (Oracle can be selected as appropriate, MSSQL, this paper takes DB2 as an example)

Since this article will use components such as IBM Http Server and WebSphere customization Tool (hereinafter referred to WCT) to complete the related configuration, install IBM WebSphere creator Server Receptacle Deployment, you will also need to install the related components listed in the following figure.

Figure 2. Install was ND and related components

For detailed steps on ODM installation, you can read the product Help documentation (reference 3).

Create was deployment Manager and Node

You can create deployment Manager and Node in the following two ways:

profile Management Tool is command line tool

Profile Management Tool provides a graphical interface, but there are more steps, so this article takes command line tools as an example. Open the command line and enter the following command to create Deployment Manager (hereinafter referred to as Dmgr), where <WAS_HOME> is the installation directory for your was ND.

Listing 1. Create Dmgr

&lt;was_home&gt;\bin\manageprofiles.bat-create-templatepath &lt;was_home&gt;\profiletemplates\management- Cellname odmcell-nodename odmdmgrnode-enableadminsecurity true-adminusername Websphere-adminpassword WebSphere- ProfileName Odmdmgr-profilepath &lt;was_home&gt;\profiles\odmdmgr-defaultports

Next, create the Node1, and the command looks like this:

Listing 2. Create Node1

&lt;was_home&gt;\bin\manageprofiles.bat-create-templatepath &lt;was_home&gt;\profiletemplates\managed- Cellname custcell-nodename rulesnode01-profilename Rulesnode01-profilepath &lt;was_home&gt;\profiles\rulesnode01- Defaultports

Replace the RulesNode1 in Listing 2 as RulesNode2 and execute again to create the Node2.

After the nodes have been created, the nodes are then combined into Dmgr to make them Dmgr managed nodes. When you perform a federated operation, you need to start the Dmgr, which you can do by using the following command:

Listing 3. Start Dmgr

&lt;was_home&gt;\bin\startmanager.bat-profilename Odmdmgr

The following command is used to combine Node1 into Dmgr, where 8879 is the Dmgr default SOAP communication port that you can use in <was_home>\profiles\odmdmgr\logs\aboutthisprofile.txt Gets the information in the

Listing 4. United Node1

&lt;was_home&gt;\bin\addnode.bat localhost 8879-username websphere-password websphere-quiet-profilename RULESNODE01

Similarly, replace the RulesNode1 in the above command with RulesNode2 and execute again to combine Node2 into Dmgr.

Now that you have completed the topology preparation, you can view these nodes in the Dmgr management console.

Figure 3. Node Agent List