Step 3: Deploying the testing and simulation archive

After you create the database resources, you can deploy the testing and simulation archive.

About this task

Use this procedure to deploy the default testing and simulation archive that is packaged with the installer or for any subsequent deployment of a repackaged archive. You can also deploy the default file and use it to test your rules if you have an XML XOM. An XML XOM is included in the ruleset archive of each RuleApp, so you do not have to repackage the default file to include the XOM.

You must deploy the archive to the same server as the execution unit (XU). Moreover, for the testing and simulation services to work, the Scenario Service Provider (SSP) and Decision Runner WARs in the archive must be installed on the same server and port as the Rule Execution Server console.

If a Rule Execution Server console instance is not deployed on the same server and port, you must implement the IlrSSPResolver interface for SSP. In the resolver, you can use the server name to return a specific server URL.

For the Decision Runner, if a Rule Execution Server console instance is not deployed on the same server and port, you must set the RES_URL init parameter on the Decision Runner web application to the Rule Execution Server console that uses the Decision Runner.

If you are installing the testing and simulation features on z/OS®, you can do the task by using customizable installation scripts (see Configuring Rule Execution Server on WebSphere® Application Server for z/OS using wsadmin scripts).

Procedure

To deploy the testing and simulation archive:

  1. In the side pane of the WebSphere Integrated Solutions Console, open Applications > Application Types > WebSphere enterprise applications.
  2. Click Install.
  3. Select Local file system if it is not selected.
  4. Click Browse, navigate to the following file, and click Next:

    <ODM_InstallDir>/executionserver/applicationservers/WebSphere85/jrules-ssp-WAS85.ear

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

  5. Select Detailed - Show all installation options and parameters.
  6. Expand Choose to generate default bindings and mappings, select Generate Default Bindings, and click Next.
  7. Click Continue to accept the security warning.
  8. In steps 1 - 6, click Next to accept the default settings.
  9. Required: In step 7, Map resource references to resources, select the work managers that you want for SSP and 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 in step 7 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 configuring a work manager by using the WebSphere Application Server administration console, see the topic Configuring work managers in the WebSphere Application Server documentation.

  10. Click Next.
  11. In steps 8 and 9, click Next to accept the default settings.
  12. In step 10, Map security roles to users or groups, if you activated security, select resAdministrators and click Map groups.
  13. Click Search. Modify the maximum number of displayed results if you do not see resAdministrators in the Available list, and then click Search again.
  14. Click the resAdministrators group under Available, and then click an arrow to move the group to the Selected column.
  15. Click OK to return to the Map security roles to users or groups page.
  16. Repeat steps 12 - 15 for the resDeployers group, and select resDeployers in the Available list.
  17. Click Next repeatedly until you reach step 13, and then click Finish.
  18. After the installation is completed, click Save directly to the master configuration.
  19. In the side pane, open Applications  > Application Types > WebSphere enterprise applications, and click Testing and Simulation.
  20. Click Class loading and update detection.
  21. Select Classes loaded with local class loader first (parent last) and click OK.
  22. Click Manage Modules.
  23. Click Scenario Service Provider.
  24. In General Properties, under Class loader order, select Classes loaded with local class loader first (parent last) and click OK.
  25. Click Decision Runner. Under General Properties, for Class loader order, select Classes loaded with local class loader first (parent last) and click OK.
  26. Click OK again, and then click Save to save directly to the master configuration.
  27. In the side pane, open Applications  > Application Types > WebSphere enterprise applications.
  28. In the Enterprise Applications page, select Testing and Simulation and click Start to start the application.
Parent topic: Additional steps to configure testing and simulation