Deploying the Decision Center EAR file

You map roles to their equivalent groups and deploy the Decision Center EAR.

Before you begin

Before deploying the Decision Center EAR, specify Java parameters for heap size and UTF encoding as follows:
  1. Open Servers >  Server Types > WebSphere application servers and click on your server.
  2. Expand Java and Process Management under Server Infrastructure.
  3. Click Process definition, then click Java Virtual Machine, and then:
    • Under General Properties modify:
      • Initial heap size: 4096 MB
      • Maximum heap size: 8192 MB or up to 16 GB for 64-bit systems.
      • Under Generic JVM Arguments, add: -Dclient.encoding.override=UTF-8
    • Under Additional Properties, click Custom Properties and add the following properties:
      • com.ibm.ws.cdi.enableImplicitBeanArchives=false
      • com.ibm.ws.cdi.enableCDI=false
  4. Depending on our operating system:
    • Windows: Save your changes and restart the server before deploying the EAR.
    • Linux
      1. Save your changes and stop the server.
      2. Increase the open file limit of the operating system by using the command ulimt -n 8192.
      3. Restart the server, and then deploy the EAR.

About this task

When you deploy the Decision Center EAR file, the process sets the persistence locale. After you have saved a rule to the database, you are no longer allowed to change the persistence locale. If you want to install Decision Center in a language other than English, take note of the instructions in Setting the persistence locale.

If you redeploy the Decision Center EAR file, all users lose their role and the module properties are lost.WebSphere® Application Server reverts to the default parent first setting.

Procedure

To deploy the EAR file:

  1. In the WebSphere Integrated Solutions Console, click Applications > New Application and then New Enterprise Application.
  2. Click Browse and navigate to the Decision Center EAR file for your version of WebSphere Application Server, and then click Next.
    • WebSphere Application Server for distributed environments: <ODM_InstallDir>/teamserver/applicationservers/WebSphere85/jrules-teamserver-WAS85.ear
    • WebSphere Application Server for Linux on z Systems®: <++JRULESHOME++>jrules-teamserver-WAS85.ear. <++JRULESHOME++> is your z/OS® zFS Operational Decision Manager installation directory.
  3. Select Detailed - Show all installation options and parameters.
  4. Expand Choose to generate default bindings and mappings, select the Generate Default Bindings check box, and then click Next.
  5. If a security warning is displayed, click Continue.
  6. On the Install New Application page, in Step 1, click Next to accept the default settings.
  7. In Step 2, select the target server and the three WAR files and click Next.
  8. For Step 3 to Step 8, click Next to accept the default settings.
  9. In Step 9, map the security roles that are defined in the deployment descriptors.

    You map these roles to your users or groups of users, as follows:

    1. Select the check box next to the rtsAdministrator role and click Map groups.
    2. Click Search to display the groups.
    3. Select the AdminGroup that you created in the previous step, and move it to the Selected column.
    4. Click OK and repeat for the rtsInstaller role.
    5. Finally, select the check box next to the rtsUser role, and click Map Special Subjects > All Authenticated in Application's Realm. All authenticated security realm.
  10. Click Next for steps 10, 11, and 12 to accept the default settings.

    Step 13 displays a summary.

  11. Click Finish.
  12. Click Save to save your workspace changes to the master configuration.
  13. When the installation is complete, click Applications >  Application Types > WebSphere enterprise applications.
  14. Click the name of the Decision Center application (ODM Decision Center).
  15. Under Modules, click Manage Modules.
  16. Click teamserver, which corresponds to the Decision Center Enterprise console.
  17. In the Class loader order menu, select Classes loaded with local class loader first (parent last), and then click Apply.
  18. In Additional Properties click Session Management, then select Override session management, and then click OK.
  19. Click Save to save the changes directly to the master configuration.
  20. Click decisioncenter, which corresponds to the Decision Center Business console, and repeat the same actions.
  21. Click decisioncenter-api, which corresponds to the REST API, and repeat the same actions.
  22. Click Save and restart the server.
  23. In the side panel, open Applications >  Application Types > WebSphere enterprise applications.
  24. Select the check box next to ODM Decision Center and click Start.

What to do next

Before completing the configuration, specify Java parameters for:
  • Heap size
  • UTF encoding
To do so:
  1. Open Servers >  Server Types > WebSphere application servers and click on your server.
  2. Expand Java and Process Management under Server Infrastructure.
  3. Click Process definition and then click Java Virtual Machine and then:
    • Under Additional Properties modify:
      • Initial heap size: 4096 MB
      • Maximum heap size: 8192 MB or up to 16 GB for 64-bit systems.
    • Under Generic Java Arguments, add: -Dclient.encoding.override=UTF-8
  4. Save and restart the server.

At this point you are able to open the Decision Center consoles. See Completing the configuration of Decision Center for information on how to open the consoles, and what tasks remain to complete.

Parent topic: Manual equivalents of configuring Decision Center
Related concepts:
Preventing session and authentication errors in WebSphere Application Server