Step 2: Deploying the Decision Validation Services archive for the first time

After you have Decision Warehouse database resources available, you deploy the Decision Validation Services archive.

Before you begin

To deploy a Decision Validation Services archive, you work in the WebSphere Integrated Solutions Console. Log in to the console as explained in Before you start: Opening the administration console.

About this task

You can follow this procedure to deploy the default Scenario Service Provider (SSP) archive that is packaged with the installer or for any subsequent deployment of a repackaged archive. Deploy the default SSP EAR file if you want to check the availability of the feature. You can also deploy the default SSP EAR file and use it to test your rules if you have an XML XOM. An XML XOM is included in the ruleset archive inside a RuleApp. Therefore, you do not have to repackage the SSP EAR file to include the XOM.
Important: You must deploy the Decision Validation Services archive on the same server as the XU. Moreover, for the testing and simulation services to work, by default the SSP application is expected to be collocated with the Rule Execution Server console. If a Rule Execution Server console instance is not also deployed on the same server as the SSP, you must implement the IlrSSPResolver interface as explained in Distributing Decision Validation Services tests to multiple servers.

If you are installing Decision Validation Services on z/OS®, you can use customizable installation scripts to perform this task. For more information, refer to Configuring Rule Execution Server on WebSphere Application Server for z/OS using wsadmin scripts.

Procedure

To deploy an SSP archive:

  1. In the side panel of the WebSphere Integrated Solutions Console, open Applications and click Websphere Enterprise Applications.
  2. Click Install.
  3. Make sure that Local file system is selected, click Browse and navigate to one of the following files, and then click Next.
    • For WebSphere Application Server 8.0: <ODM_InstallDir>/executionserver/applicationservers/WebSphere8/jrules-ssp-WAS8.ear
    • For WebSphere Application Server 8.5 or 8.5.5: <ODM_InstallDir>/executionserver/applicationservers/WebSphere85/jrules-ssp-WAS85.ear
  4. Select the check box Detailed - Show all installation options and parameters.
  5. Expand Choose to generate default bindings and mappings, elect the check box Generate Default Bindings, and click Next.
  6. Click Continue to accept the security warning.
  7. In Step 1 through Step 8 click Next to accept the default settings.
  8. In Step 9, if you have activated security, select resAdministrators and click Map groups.
  9. Click Search.
  10. Click the resAdministrators group under Available and then click the arrows to move it to the Selected column.
  11. Click OK to return to the Map security roles to users or groups page.
  12. Repeat steps 8 to 11 for the resDeployers group, selecting resDeployers.
  13. Click Next and then click Finish.
  14. After the installation has completed click Save directly to the master configuration.
  15. In the side panel, open Applications  > Application Types > WebSphere enterprise applications, and click jrules-ssp-WAS8 or jrules-ssp-WAS85.
  16. Click Manage Modules.
  17. Click Scenario Service Provider.
  18. Under General Properties, for Class loader order select Classes loaded with local class loader first (parent last) and click OK.
  19. Click OK again and then click Save to save directly to the master configuration.
  20. In the side panel, open Applications  > Application Types > WebSphere enterprise applications.
  21. In the Enterprise Applications page, select the check box next to jrules-ssp-WAS8 or jrules-ssp-WAS85 and click Start to start the application.