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:
- From the WebSphere Integrated Solutions Console,
open and click on your server.
- Under Web Container Settings, click Web
container transport chains.
- Click HttpQueueInboundDefault, then HTTP
inbound channel (HTTP 2), and then Custom properties.
- Click New, and then add the property:
- Name:
AllowGetRequestWithContentEncodingAndNoBody
- Value:
false
- Do steps 3 and 4 for HTTP inbound channel (HTTP 4).
- Click OK, and then Save.
Restart the server before deploying the EAR.
Procedure
- From the WebSphere Integrated Solutions Console,
open and click New Enterprise
Application.
- Under Local file system browse and
select the following archive file, and click Next: <ODM_InstallDir>/executionserver/applicationservers/WebSphere/jrules-res-management-WAS.ear
- Select Detailed - Show all installation options
and parameters.
- Expand Choose to generate default bindings and
mappings, select Generate Default Bindings,
and click Next.
- Click Continue to accept the security
warning.
The "Select installation options" page
opens.
- In Step 1, click Next to
accept the default settings.
- 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.
- 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.
- In Step 3 to Step
5, click Next to accept the default
settings.
- In Step 6, select the check box
for the
eis/XUConnectionFactory
resource reference.
- Click Browse, select the entry
named xu_cf, and click Apply.
- For the
jdbc/resdatasource
reference,
click Browse, and select the entry named resdatasource.
- Click Apply, and then click Next.
- At the bottom of the Application Resource Warnings page,
click Continue.
- In Step
9: Map security roles to users or groups, proceed as follows:
- Select the check box next to the resAdministrators role.
- Click Map Groups and click Search.
- Click the resAdministrators role
in the Available column and click the arrow to move it to the Selected
column.
- Click OK to return
to the "Mapping security roles to users or groups" page.
- Repeat the steps to map the roles resDeployers and resMonitors to
their equivalent group.
- Click Next. In steps 10, 11, and
12, click Next to accept the default settings.
Step 13 provides a summary.
- Click Finish.
- When the installation is complete, click Save.
Then, click Manage Applications at the bottom
of the page.
- Click Rule Execution Server.
- In the Configuration tab, click Manage Modules.
- Click Rule Execution Server Console.
- Under General Properties, for Class loader order,
select Classes loaded with local class loader first (parent
last).
- Click OK, and in the next panel,
click Save to save directly to the main configuration.
- In the side panel, open .
- In the Enterprise Applications page,
select the check box next to Rule Execution Server and
click Start to start the application.