Configuring Rule Execution Server and XU Adapter

The XU (Execution Unit) Adapter is a resource adapter packaged with IBM® Operational Decision Manager.

About this task

The Operational Decision Manager ships different XU Adapters for different application servers. The default Rule Engine implementation of Master Data Management (JRulesXUEngine) uses XU Adapter to invoke the Operational Decision Manager rules that are deployed in the Rule Execution Server. The rules are created using Operational Decision Manager Rule Designer tool and is deployed in Rule Execution Server.

1. Open WebSphere® Application Server Administrative Console.
2. Go to Security > Global Security > Java Authentication and Authorization Service > J2C authentication data.
3. Create a new user identity for Rule App Database by specifying the alias name (for example, resDB2user) and the database credentials (Issue MDM Database credentials if MDM DB is used for creating Rule App tales).
4. Open Go to Resources > JDBC > Data Sources and create a data source by specifying the data source name (for example, jdbc/resdatasource) and the database details.
5. While creating the datasource, clear the check box for the option Use this data source in container managed persistence (CMP) and set the user you just created (resDB2user) for Container managed authentication, and Component managed authentication aliases.
6. Populate the Rule App database tables by executing the appropriate scripts. The Rule App table generation scripts can be found in the IBM Operational Decision Manager installation directory (WODM\executionserver\databases). For DB2®, run the SQL files repository_db2.sql, trace_db2sql, and xomrepository_db2.sql.

To install the XU Resource Adapter:

7. Go to Resources > Resource Adapters.
   1. Click on Install RAR.
   2. Locate the XU RAR from the Operational Decision Manager installation directory (WODM\executionserveapplicationservers\<app-server-naem>\jrules-res-xu-<app-server-name>.rar) and install the same.
   3. Save changes to configuration.
   4. Click on the XU Adapter that you just installed, and click J2C connection factories under Additional Properties.
   5. Click New and create a connection factory by specifying the correct JNDI Name (eis/XUConnectionFactory).
   6. Save changes to configuration and restart the application server.

Installing the Rule Execution Server Management EAR:

8. Go toApplications > WebSphere Enterprise Applications.
   1. Click Install.
   2. Locate the RES Management EAR from the Operational Decision Manager installation directory (WODM\executionserver\applicationservers\<app-server-name>\jrules-res-management<app-server-name>.ear), and click Next.
   3. Select Detailed path for installation. Click Next and Continue.
   4. In Map resource references to resources, select the previously configured XU Connection factory (eis/XUConnectionFactory) and the datasource (jdbc/resdatasource).
   5. In Map virtual hosts for Web modules, map the host.
   6. In Map security roles to users or groups, map the required user access to the security roles resAdministrators, resDeployers, and resMonitors. (Select All Authenticated in Application’s Realm to give access to all authenticated users.)
   7. Continue to install the EAR and save changes to configuration.
   8. Click the newly installed RES application (do not start it).
   9. Go to the Manage Modules page and click the ILOG® Rule Execution Server Console module.
   10. Change the Class loader order to Classes loaded with local class loader first (parent last).
   11. Save the changes to configuration, and start the application.

   Rule Execution Server and XU Adapter are ready to use. The Operational Decision Manager rule sets can be deployed to the Rule Execution Server and then become accessible to InfoSphere® MDM via the XU Adapter.