Deploying the testing and simulation archive

You deploy the testing and simulation archive on Rule Execution Server to enable testing and simulation features in Decision Center.

About this task

Before deploying the testing and simulation archive, make sure that the database is already created (see Mandatory: Create the databases).

The Decision Runner module is used to run tests and simulations in the Business console.

Note: The testing and simulation archive must be installed on the same server and port as the Rule Execution Server console. If the Rule Execution Server console is not deployed on the same server and port, set the RES_URL init parameter on the Decision Runner web application (Decision Runner) to the Rule Execution Server console that uses the Decision Runner.

Procedure

To deploy the testing and simulation archive:

  1. In the WebSphere Integrated Solutions Console, open Applications > New Application and click New Enterprise Application.
  2. Select Local file system, then click Browse, navigate to the following file, and click Next:

    <ODM_InstallDir>/executionserver/applicationservers/WebSphere/jrules-ssp-WAS.ear

    The EAR file contains the WAR files for the Decision Runner.

  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.
  6. In the step Initialize parameters for servlets, set the RES_URL init parameter for the Decision Runner to the corresponding Rule Execution Server consoles.

    For example:

    http://<host>:<port>/res

    You can leave the field blank if the application is deployed on the same sever and port as the Rule Execution Server console.

  7. In the step Map resource references to resources, select the work manager that you want for the Decision Runner.

    To run test suites and simulations in managed threads, you select the default work manager (wm/default) or use a dedicated work manager. Make sure that each work manager that you select exists on the application server. If necessary, create the matching work manager on the application server. In the Service Names section of the work manager properties page, make sure Security is selected.

    For more information about WebSphere® Application Server, see the WebSphere Application Server documentation.

  8. In the step Map security roles to users or groups, if you activated security, select resAdministrators and click Map groups.
  9. Click Search.
  10. Click the resAdministrators group under Available, and then click an arrow to move the group to the Selected column.
  11. Click OK to return to the Map security roles to users or groups page.
  12. Repeat these steps for the resDeployers group, and select resDeployers in the Available list.
  13. Continue to the last step, and then click Finish.
  14. After the installation is completed, click Save directly to the master configuration.
  15. Open Applications  > Application Types > WebSphere enterprise applications, and click Testing and Simulation.
  16. Click Class loading and update detection.
  17. Select Classes loaded with local class loader first (parent last), click OK, and then save to the master configuration.
  18. Click Testing & Simulation, and then click Manage Modules.
  19. Click Decision Runner. Select Classes loaded with local class loader first (parent last), and click OK.
  20. Click OK again, and then Save to save to the master configuration.
  21. Open Applications  > Application Types > WebSphere enterprise applications.
  22. Select Testing and Simulation and click Start.

Results

You can check the availability of the Decision Runner by entering http://<host>:<port>/DecisionRunner.