You can optionally deploy the WAR file for hosted transparent
decision services.
About this task
On a Liberty profile
server, you use the execution unit (XU) as a Java™ SE component. Use the following procedure
to deploy the hosted transparent decision service WAR on the Liberty profile
server:
Procedure
- Copy <InstallDir>/executionserver/applicationservers/WLP855/DecisionService.war to <WLP_HOME>/usr/servers/<SERVER_NAME>/apps.
- In <WLP_HOME>/usr/servers/<SERVER_NAME>/server.xml,
add the following code in the application section:
<!-- HTDS -->
<application type="war" id="DecisionService" name="DecisionService"
location="${server.config.dir}/apps/DecisionService.war">
</application>
- Save the file.
- If you want to change the context root for HTDS, which
is set to /DecisionService by default, you must change
the ilog.rules.res.HTDS_CONTEXT parameter. In the WEB-INF/web.xml of
the Rule Execution Server console,
change the <param-value>/DecisionService</param-value> in
the following <context-param> section:
<context-param>
<description>Hosted Transparent Decision Services context-root. Can be modified.</description>
<param-name>ilog.rules.res.HTDS_CONTEXT</param-name>
<param-value>/DecisionService</param-value>
</context-param>
For example, you could change <param-value>/DecisionService</param-value> to <param-value>/myservice</param-value>.
Also,
you must adapt the application section of the server.xml accordingly,
by adding a context-root attribute that specifies
the new context root.
- Restart the Rule Execution Server console
for the hosted transparent decision service to function correctly.
- Set the ruleset.xmlDocumentDriverPool.maxSize ruleset
property to the appropriate value.
See Setting the ruleset.xmlDocumentDriverPool.maxSize
property.
What to do next
For information about checking whether you have deployed
the hosted transparent decision service successfully, refer to the Rule Execution Server console
online help.