Deploying the Rule Execution Server management EAR

After you have activated the security and deployed the XU RAR, you deploy the Rule Execution Server EAR to WebSphere® Application Server.

Before you begin

Before deploying the Rule Execution Server EAR, specify a custom property on the HTTP transport channel:
  1. From the WebSphere Integrated Solutions Console, open Servers >  Server Types > WebSphere application servers and click on your server.
  2. Under Web Container Settings, click Web container transport chains.
  3. Click HttpQueueInboundDefault, then HTTP inbound channel (HTTP 2), and then Custom properties.
  4. Click New, and then add the property:
    • Name: AllowGetRequestWithContentEncodingAndNoBody
    • Value: false
  5. Do steps 3 and 4 for HTTP inbound channel (HTTP 4).
  6. Click OK, and then Save. Restart the server before deploying the EAR.

Procedure

  1. From the WebSphere Integrated Solutions Console, open Applications > New Application and click New Enterprise Application.
  2. Under Local file system browse and select the following archive file, and click Next: <ODM_InstallDir>/executionserver/applicationservers/WebSphere/jrules-res-management-WAS.ear
  3. Select Detailed - Show all installation options and parameters.
  4. Expand Choose to generate default bindings and mappings, select Generate Default Bindings, and click Next.
  5. Click Continue to accept the security warning.

    The "Select installation options" page opens.

  6. In Step 1, click Next to accept the default settings.
  7. In Step 2, proceed as follows:
    • If you have only one server, click Next to skip Step 2.
    • If you have more than one server, select the server to which you want to deploy the application. Then select the check box for the Rule Execution Server Console and click Next.
  8. Proceed as follows:
    • If you are working on WebSphere Application Server for distributed platforms, in Step 3 through Step 8 of the wizard, click Next to accept the default settings.
    • If you are working on WebSphere Application Server for Linux® on z Systems®, in Step 6, you map the resource references to JNDI resources.
    1. In Step 3 to Step 5, click Next to accept the default settings.
    2. In Step 6, select the check box for the eis/XUConnectionFactory resource reference.
    3. Click Browse, select the entry named xu_cf, and click Apply.
    4. For the jdbc/resdatasource reference, click Browse, and select the entry named resdatasource.
    5. Click Apply, and then click Next.
  9. At the bottom of the Application Resource Warnings page, click Continue.
  10. In Step 9: Map security roles to users or groups, proceed as follows:
    1. Select the check box next to the resAdministrators role.
    2. Click Map Groups and click Search.
    3. Click the resAdministrators role in the Available column and click the arrow to move it to the Selected column.
    4. Click OK to return to the "Mapping security roles to users or groups" page.
    5. Repeat the steps to map the roles resDeployers and resMonitors to their equivalent group.
  11. Click Next. In steps 10, 11, and 12, click Next to accept the default settings.

    Step 13 provides a summary.

  12. Click Finish.
  13. When the installation is complete, click Save. Then, click Manage Applications at the bottom of the page.
  14. Click Rule Execution Server.
  15. In the Configuration tab, click Manage Modules.
  16. Click Rule Execution Server Console.
  17. Under General Properties, for Class loader order, select Classes loaded with local class loader first (parent last).
  18. Click OK, and in the next panel, click Save to save directly to the main configuration.
  19. In the side panel, open Applications  > Application Types > WebSphere enterprise applications.
  20. In the Enterprise Applications page, select the check box next to Rule Execution Server and click Start to start the application.