Search Tips   |   Advanced Search

Configure ODM v8.5 Decision Center

  1. Create and augment dmgr profile
  2. Create managed node profiles
  3. Federate nodes
  4. Create cluster and add first member
  5. Add second member to cluster
  6. Tune JVMs
  7. Map users and groups
  8. Backup profiles
  9. LDAP Integration
  10. Configure IHS Plugin
  11. Web Server Configuration
  12. Tune Decision Center
  13. Installation options

  1. Create and augment dmgr profile
    1. Install ODM on the dmgr host

    2. Create dmgr profile...

        cd ODM_HOME/AppServer/bin/
        ./manageprofiles.sh -create \
                          -templatePath ODM_HOME/AppServer/profiles/profileTemplates/management \
                          -serverType DEPLOYMENT_MANAGER \
                          -profileName odmDmgr \
                          -profilePath ODM_HOME/profiles/dmgr \
                          -enableAdminSecurity true \
                          -adminUserName odmAdmin \
                          -adminPassword odmAdmin \
                          -cellName odmCell \
                          -startingPort 49000 

    3. Augment dmgr profile

        cd ODM_HOME/AppServer/bin/
        ./manageprofiles.sh -augment \
                            -profileName odmDmgr \
                            -templatePath ODM_HOME/AppServer/profiles/profileTemplates/rules/management/dc 

  2. Create managed node profiles
    1. Install ODM on each node host

    2. On dmgr host, start the deployment manager

    3. On node1 run...

        cd ODM_HOME/bin/
        ./manageprofiles.sh -create \
                            -templatePath ODM_HOME/profiles/profileTemplates/managed \
                            -profileName node01 \
                            -profilePath ODM_HOME/profiles/node01 \
                            -nodeName node01 \
                            -cellName Node01Cell \
                            -federateLater true \
                            -dmgrHost dmgrhost.mydomain.com \
                            -dmgrPort 49003 

    4. On node2 run...

        cd ODM_HOME/bin/
        ./manageprofiles.sh -create \
                            -templatePath ODM_HOME/profiles/profileTemplates/managed \
                            -profileName node02 \
                            -profilePath ODM_HOME/profiles/node02 \
                            -nodeName node02 \
                            -cellName Node02Cell \
                            -federateLater true \
                            -dmgrHost dmgrhost.mydomain.com \
                            -dmgrPort 49003

  3. Federate nodes
    1. On node1 run...

      cd ODM_HOME/profiles/node01/bin/
      ./addNode dmgrhost.mydomain.com 49003 \
                -conntype SOAP \
                -username odmAdmin \
                -password odmAdmin 

    2. On node2 run...

      cd ODM_HOME/profiles/node02/bin/
      ./addNode dmgrhost.mydomain.com 49003 \
                -conntype SOAP \
                -username odmAdmin \
                -password odmAdmin 

  4. Create cluster and add first member
    1. On dmgr server, set...

        export ODM_HOME=ODM_HOME/ODM

    2. Edit...

      ...and set...


    3. Copy rulesTemplateResource.jar from...




      Copy rulesTemplateResource.jar from...




    4. On both nodes...

        mkdir ODM_HOME/executionserver/applicationservers/WebSphere85
        mkdir ODM_HOME/shared/profiles/profileTemplates/rules/lib

    5. Copy all files under...




    6. Copy all files under...




    7. On dmgr, set default server name in...

      For example...

        deployClusterTools.createCluster(cellName, clusterName, clusterNodeName, clusterNodeName + "-myDCServer")

    8. Set MaxPermGen heap size in...


        <jvmarg value="-XX:MaxPermSize=256m"/>
        <jvmarg value="-Xmx2G"/>

    9. Create cluster and first cluster member...
      cd ODM_HOME/profiles/dmgr/bin/
      ./configureDCCluster.sh -dmgrAdminUsername odmAdmin \
                              -dmgrAdminPassword odmAdmin \
                              -clusterPropertiesFile ODM_HOME/profiles/dmgr/bin/rules/configureDCCluster.properties \
                              -targetNodeName node01 \
                              -dmgrHostName dmgrhost.mydomain.com \
                              -dmgrPort 49003 

    10. To verify cluster create success, log in to admin console and go to...

        Servers | Clusters | Websphere application server clusters

      Verify the first DC cluster member was created on node01...

        Cluster name | Cluster members

    Note that configureDCCluster.sh is used to create decision center cluster and the first cluster member only. It cannot be used to add a node or cluster members to an existing cluster.

  5. Add second node to cluster
    1. Set clusterNodeName in...

    2. Set "MaxPermGen" heap size in...


        <jvmarg value="-XX:MaxPermSize=256m"/>
        <jvmarg value="-Xmx2G"/>

    3. Add node...

      cd ODM_HOME/profiles/dmgr/bin/bin/
      ./addNodeToDCCluster.sh -dmgrAdminUsername odmAdmin \
                              -dmgrAdminPassword odmAdmin \
                              -clusterPropertiesFile ODM_HOME/profiles/dmgr/bin/rules/configureDCCluster.properties \
                              -targetNodeName node02 \
                              -dmgrHostName dmgrhost.mydomain.com \
                              -dmgrPort 49003 

    On successful execution, second cluster member is created with all resources configured. To verify it, logon to admin console and go to...

      Servers | Clusters | Websphere application cluster | odmDCCluster | Additional Properties | Members | Details

  6. Tune JVMs
  7. Initial Heap Size

    4096 MB

    Maximum Heap Size

    4096 MB

    Generic JVM Argument


    To perform, JVM tuning...

      Servers | Websphere application servers | server name | Process Definitions | Java and Process Management | Java Virtual Machine

    Save and synchronize the changes. Perform the same for all JVMs (cluster members and deployment manager).

  8. Create required groups and map users for decision center
    1. From Integrated Solutions Console, go to...

        Security > Global security

    2. Configure the repository security as follows.

      • If Federated repositories is already selected under Current realm definition, verify that Enable application security is selected. Apply and Save to save the changes to the master configuration.

      • If Federated repositories is not already selected, click Security Configuration Wizard and configure...

        1. In Step 1 of wizard, to specify the level of protection, select...

            Enable application security

          ...and click Next.

        2. In Step 2 of wizard, select Federated repositories and click Next.

        3. In Step 3 of wizard, type a name in the primary administrative user name field and password in the password field, and click Next.

        4. In Step 4 of wizard, review the security configuration summary and click Finish.

        5. Click Save to save the changes to the master configuration.

        6. Restart the server.

    3. In the side panel, open...

        Users and Groups | Manage Groups

    4. Click Create and enter "rtsUser" as the group name. Click Create.

    5. Click Create Like and create another group named "rtsAdministrator". Click Create.

    6. Click Create Like and create another group named "rtsConfigManager". Click Create.

    7. Click Create Like and create another group named "rtsInstaller". Click Create. Click Close.

    8. In the side panel, open...

        Users and Groups | Manage Users

    9. Click Create.

    10. Enter rtsUser1 as the User ID and assign this new user to a group. To do so:

    11. Click Group Membership. The page that enables you to select a group opens.

    12. Click Search. The list of existing groups is displayed.

    13. Select the rtsUser group and click Add. Click Close.

    14. Enter a given name and surname for rtsUser1, then enter the rtsUser1 password, and click Create.

    15. Click Close.

    16. Create another user named rtsAdmin with password rtsAdmin, and assign this user to the rtsAdministrator and rtsInstaller groups.

    17. Create another user named rtsConfig with password rtsConfig, and assign this user to the rtsConfigManager group.

    18. Restart the application server.

  9. Backup profiles
    • tar -cvf ODM_node01_010614.tar ODM

  10. LDAP Integration
    1. Logon to deployment manager admin console and go to...

        Security | Global Security | Federated Repository | Configure | Add repositories

      ...and fill in following details.

      For New Repository value, select "LDAP repository" from available options. Click on Apply

      Repository Name LDAP1_ODM
      Repository Type LDAP Repository
      Unique Distinguished name of the base  o=mybaseDN,st=mn,c=us

    2. On next page, fill in details. Keep rest as default and click on Ok. Save the changes.

      Primary Host Name cls004.mydomain.com
      Port 389
      Bind distinguished name uid=was1bind,cn=ieewasadmins,o=mybaseDN,st=mn,c=us
      Bind Password password for bind id

    3. Added registry will be shown under federated repositories

    4.   Verify integration. 


        Users and Groups | Manage Users | Search

      It will list users from Repository

      Click on...

        Users and Groups | Manage Groups | Search

      It will list groups from Repository

  11. Configure IHS Plugin
  12. After installing IHS and Plugin on both node servers, on each node server, edit...



    • Change Listen 80 to Listen 8181
    • Change ServerName nodename:80 to ServerName fully_qualified_nodename:8181

  13. Plugin Configuration
  14. Use the WCT toolbox manages to configure plugins.

    To move WCT repository to non- shared location.

    1. Make repository data directory at non-shared location on each node server.

        cd /IBM/toolbox85/ODM/WCT/
        mkdir WCT85data

    2. Edit the WCT configuration file (config.ini) to point to new repository location.


    3. Make changes in conf.ini file


    4. Save the changes in conf.ini file.

  15. Customize response file to configure plugin
    1. Make a copy of the old response file.

        cd /IBM/toolbox85/ODM/WCT
        cp pct_responsefile.txt ODM_node0[1|2]_responsefile.txt

    2. Edit ODM_node0[1|2]_responsefile.txt response file and make the property changes...




      Comment out (#) ihsAdminPort, ihsAdminUserID, ihsAdminUserGroup


      Comment out (#) ihsAdminUnixUserID, ihsAdminUnixUserGroup, ihsAdminPassword


    3. To create new definition location using customize response file...

      ./wctcmd.sh -tool pct \
                  -createDefinition \
                  -defLocName odmWebServer[1|2]Location \
                  -defLocPathname /IBM/plugins/ODM \
                  -response pctenv_responsefile_node0[1|2].txt

  16. Configure web server definition in dmgr
  17. Successful execution of above steps creates script...



      Web server name Node Script
      odmWebServer1 1 configureodmWebServer1.sh
      odmWebServer2 2 configureodmWebServer2.sh

    To complete the web server configuration...

    1. Edit configureodmWebServer[1|2].sh and verify path to .jacl file is correct ...

        ./wsadmin.sh $PROFILE_NAME_PARAMETER \
                     $WSADMIN_USERID_PARAMETER \
                     $WSADMIN_PASSWORD_PARAMETER \
                     -f 'ODM_HOME/AppServer/bin/configureWebserverDefinition.jacl' \
                     odmWebServer[1|2]  \
                     IHS \
                     '/IBM/ihs85/ODM' \
                     '/IBM/ihs85/ODM/conf/httpd.conf' \
                     8181 \
                     MAP_ALL '/IBM/plugins/ODM' \
                     managed node0[1|2] 

    2. Copy scripts to dmgr host, then run...
      cd ODM_HOME/profiles/dmgr/bin 
      cp /home/waslwadm/ODMInstall/ihs85/configureodmWebServer[1|2].sh  
      ./confugreodmWebServer[1|2].sh -profileName <dmgr_pofile_name> -user <wasadmin_user_id> -password <wasadminpassword> 

    3. To set custom HTTP ports, from WAS console, navigate to...

        Environment | Virtual hosts

      ...and, for both nodes, change...

        * 80
        hostname 80

      ...to, for example...

        * 8181
        hostname 8181

      On each node, add entry for nodehost.mydomain.com on port 49019. Used by /teamserver and /decisioncenter.

      Remove definitions for ports you do not need.

      Save changes

    4. Run...

        Environment | Update global Web server plug-in configuration | OK

    5. Generate plug-in for both servers...

        Servers | Server Types | Web servers | servers | Generate Plug-in

    6. Propagate plug-in for both servers...

        Servers | Server Types | Web servers | servers | Propogate Plug-in

    7. Restart the web servers.

    8. Navigate to...

        Servers| Clusters| WebSphere application clusters

    9. Restart the cluster.

  18. Tuning of Decision Center
  19. The tuning of Decision Center is accessible in the enterprise console of Decision Center.

  20. Installation Options
  21. The installation manager of the enterprise console provides access to the main options of Decision Center...

    Modifying the build storage option limits the memory usage and stores on disk the cache of compiled business rules so this cache is persistent. To get those results, navigate to the installation manager and set the configuration parameter "teamserver.build.archive.storage" to file instead of memory...

  22. Project Options
  23. The options of a project are configurable in the Project tab of the enterprise console...

    Tuning of the rule project limits memory consumption and CPU usage at rule edition and compilation time. Use the following steps to tune the rule project build:

    1. Disable the Archive parsing flag option. This can be accessed by selecting Project -> Edit project options -> Check the ruleset archive

    2. Use Automatic build to avoid a huge ruleset generation cost at first ruleset generation

    3. Disable Rule analysis checks.



ODM - Web Servers


ODM Install and Configuration Related Links:

  1. ODM 8.5.1 Infocenter
  2. Manual creation of WBE DB
  3. Configure WBE credentials from LDPA
  4. Enable WBE trace for debugging