IBMWebSphere Operational Decision Management Version 8 … · 2018-06-11 · Using a remote Solr...

IBM WebSphere Operational Decision ManagementVersion 8 Release 0

Configuring Decision Center

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 171.

This edition applies to version 8, release 0, modification 0 of WebSphere Operational Decision Management and toall subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2008, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Configuring Decision Center . . . . . . 1Configuring the Decision Center consoles onWebSphere Application Server . . . . . . . . 1

Configuring the Decision Center consoles onWebSphere Application Server . . . . . . . 1

Before you start . . . . . . . . . . . 1Step 1: Enforcing database user permissions . . 2Step 2: Creating a data source and connectionpool . . . . . . . . . . . . . . . 3

Creating a JDBC provider . . . . . . . 3Creating a data source and connection pool 4Creating J2C authentication data. . . . . 5Changing the custom properties of yourdata source . . . . . . . . . . . . 6Connecting to the database . . . . . . 7

Step 3: Configuring security . . . . . . . 7User registries . . . . . . . . . . . 7Creating users and groups . . . . . . . 8Security policies for the Decision Centerconsole . . . . . . . . . . . . . 10

Step 4: Deploying the Decision Centermanagement EAR . . . . . . . . . . 11

Declaring custom groups . . . . . . . 11Changing the class loading sequence . . . 11Deploying the EAR . . . . . . . . . 12

Step 5: Verifying the deployment of theDecision Center Enterprise console . . . . 14Step 6: Completing the configuration of theDecision Center consoles . . . . . . . . 15

Completing the configuration from theDecision Center Enterprise console . . . 15Completing the configuration using Anttasks. . . . . . . . . . . . . . 20

Additional steps to configure the DecisionCenter Business console . . . . . . . . 29

Using a remote Solr search engine . . . . 29Setting parameters for the Solr searchengine . . . . . . . . . . . . . 29

Additional steps to configure DecisionValidation Services . . . . . . . . . . 31

Before you start . . . . . . . . . . 31Step 1: Creating Decision Warehousedatabase resources . . . . . . . . . 32Step 2: Deploying the Decision ValidationServices archive . . . . . . . . . . 33Step 3: Checking the availability ofDecision Validation Services . . . . . . 34Step 4: Packaging Decision ValidationServices using Ant . . . . . . . . . 36Step 5: Redeploying the Decision ValidationServices archive . . . . . . . . . . 36

Troubleshooting . . . . . . . . . . . 37Providing more memory for applications 37

Configuring the Decision Center consoles onWebSphere Application Server for Linux onSystem z . . . . . . . . . . . . . . 38

Before you start . . . . . . . . . . . 38Step 1: Enforcing database user permissions 40Step 2: Setting up Java 2 connection security 41Step 3: Configuring security on WebSphereApplication Server . . . . . . . . . . 41

Defining a user registry . . . . . . . 41Creating users and groups . . . . . . 42Security policies for the Decision CenterConsole. . . . . . . . . . . . . 44

Step 4: Creating the DB2 database . . . . . 44Step 5: Creating a JDBC provider . . . . . 44Step 6: Creating a data source and connectionpool . . . . . . . . . . . . . . . 45

Creating a data source and connection pool 45Testing the connection to the database . . 46

Step 7: Deploying the Decision Center EAR onWebSphere Application Server . . . . . . 47

Declaring custom groups . . . . . . . 47Changing the class loading sequence . . . 48Deploying the EAR . . . . . . . . . 48Verifying the deployment of the DecisionCenter Enterprise console. . . . . . . 50

Step 8: Completing the configuration . . . . 50Completing the configuration from theDecision Center Enterprise console . . . 50Completing the configuration using Anttasks. . . . . . . . . . . . . . 55

Additional steps to configure the DecisionCenter Business console . . . . . . . . 64

Using a remote Solr search engine . . . . 64Setting parameters for the Solr searchengine . . . . . . . . . . . . . 65


Before you start . . . . . . . . . . 66Step 1: Creating Decision Warehousedatabase resources . . . . . . . . . 67Step 2: Deploying the Decision ValidationServices archive . . . . . . . . . . 68Step 3: Checking the availability ofDecision Validation Services . . . . . . 70Step 4: Packaging Decision ValidationServices using Ant . . . . . . . . . 71Step 5: Redeploying the Decision ValidationServices archive . . . . . . . . . . 71

Configuring the Decision Center consoles usingprofile templates. . . . . . . . . . . . 72

Decision Center profile templates . . . . . 72Configuring Decision Center on a new profile 73Augmenting an existing profile with DecisionCenter . . . . . . . . . . . . . . 75Configuring the Decision Center consoles forhigh availability and scalability . . . . . . 78

Augmenting a deployment manager profilewith Decision Center . . . . . . . . 78

© Copyright IBM Corp. 2008, 2012 iii

Running the configureDCCluster script tocreate a cluster . . . . . . . . . . 79Unaugmenting Decision Center from anexisting cluster . . . . . . . . . . 81Uninstalling Decision Center from a cluster 82

Configuring the Decision widget for BusinessSpace . . . . . . . . . . . . . . . 83

Configuring the Decision widget using awsadmin script . . . . . . . . . . . 83Enabling single sign-on for the Decisionwidget . . . . . . . . . . . . . . 84

Configuring the Decision Center Enterprise consoleon Tomcat 7.0 . . . . . . . . . . . . . 84

Before you start . . . . . . . . . . . . 85Step 1: Enforcing database user permissions . . 86Step 2: Creating a data source and connectionpool . . . . . . . . . . . . . . . . 87Step 3: Configuring security . . . . . . . . 88

Groups and permissions . . . . . . . . 88Declaring custom groups . . . . . . . . 89

Step 4: Deploying the Decision Center WAR . . 91Step 5: Verifying the deployment of the DecisionCenter Enterprise console. . . . . . . . . 91Step 6: Completing Decision Center configuration 92

Completing the configuration from theDecision Center Enterprise console . . . . 92

Installation Settings wizard overview . . . 92Step 1: Configure the database . . . . . 93Step 2: Set up message files . . . . . . 93Step 3: Set up groups . . . . . . . . 94Step 4: Set the persistence locale . . . . 95Step 5: Set configuration parameters . . . 95

Completing the configuration using Ant tasks 97Setting up the Ant tasks environment. . . 97Creating the database schema . . . . . 98Defining and uploading message files . . 102Setting the persistence locale . . . . . 103Adding or removing configurationparameters . . . . . . . . . . . 103Repackaging the Decision Center archive 105


Before you start . . . . . . . . . . 105Step 1: Creating Decision Warehousedatabase resources. . . . . . . . . . 106Step 2: Deploying the Decision ValidationServices archive . . . . . . . . . . 108Step 3: Checking the availability of DecisionValidation Services . . . . . . . . . 109Step 4: Packaging Decision ValidationServices using Ant. . . . . . . . . . 110

Providing more memory for applications . . . 110Configuring the Decision Center Enterprise consoleon JBoss 5 and 6.1 . . . . . . . . . . . . 111

Before you start. . . . . . . . . . . . 111Step 1: Enforcing database user permissions . . 112Step 2: Creating a data source and connectionpool . . . . . . . . . . . . . . . 113Step 3: Configuring security on JBoss . . . . 115

Groups and permissions . . . . . . . . 115Declaring custom groups . . . . . . . 116

Step 4: Deploying the Decision Center EAR onJBoss . . . . . . . . . . . . . . . 117Step 5: Verifying the deployment of the DecisionCenter Enterprise console . . . . . . . . 117Step 6: Completing your Decision Centerconfiguration . . . . . . . . . . . . 118


Installation Settings wizard overview . . 118Step 1: Configure the database. . . . . 119Step 2: Set up message files . . . . . 120Step 3: Set up groups. . . . . . . . 120Step 4: Set the persistence locale . . . . 121Step 5: Set configuration parameters . . . 121

Completing the configuration using Ant tasks 123Setting up the Ant tasks environment . . 123Creating the database schema . . . . . 124Defining and uploading message files . . 128Setting the persistence locale . . . . . 129Adding or removing configurationparameters . . . . . . . . . . . 129Repackaging the Decision Center archive 131


Before you start . . . . . . . . . . 132Step 1: Creating Decision Warehousedatabase resources. . . . . . . . . . 132Step 2: Deploying the Decision ValidationServices archive for the first time . . . . . 134Step 3: Checking the availability of DecisionValidation Services . . . . . . . . . 134Step 4: Packaging Decision ValidationServices using Ant. . . . . . . . . . 136

Troubleshooting . . . . . . . . . . . 136Providing more memory for applications . . 136

Configuring the Decision Center Enterprise consoleon WebLogic Server 10.3.2 . . . . . . . . . 137

Before you start . . . . . . . . . . . 137Step 1: Enforcing database user permissions . . 138Step 2: Creating a data source and connectionpool . . . . . . . . . . . . . . . 139Step 3: Configuring security . . . . . . . 140

Groups and permissions. . . . . . . . 140Creating groups in WebLogic Server. . . . 141

Overview. . . . . . . . . . . . 141Adding all groups to the security realm 141Declaring global roles . . . . . . . 142

Creating users in WebLogic Server . . . . 143Adding users to groups in WebLogic Server 144

Step 4: Deploying the Decision Center EAR . . 144Step 5: Verifying the deployment of the DecisionCenter Enterprise console . . . . . . . . 145Step 6: Completing Decision Centerconfiguration . . . . . . . . . . . . 146


Installation Settings wizard overview . . 146Step 1: Configure the database . . . . 147Step 2: Set up message files . . . . . 148Step 3: Set up groups. . . . . . . . 148Step 4: Set the persistence locale . . . . 149

iv IBM WebSphere Operational Decision Management: Configuring Decision Center

Step 5: Set configuration parameters . . . 149Completing the configuration using Ant tasks 151

Setting up the Ant tasks environment . . 151Creating the database schema . . . . . 152Defining and uploading message files . . 156Setting the persistence locale . . . . . 157Adding or removing configurationparameters . . . . . . . . . . . 157Repackaging the Decision Center archive 159


Before you start . . . . . . . . . . 159Step 1: Creating Decision Warehousedatabase resources. . . . . . . . . . 160Step 2: Deploying the Decision ValidationServices archive for the first time . . . . . 162Step 3: Checking the availability of DecisionValidation Services . . . . . . . . . 163

Step 4: Packaging Decision ValidationServices using Ant. . . . . . . . . . 164

Troubleshooting . . . . . . . . . . . 165Providing more memory for applications . . 165

Verifying your configuration of Decision Center 165Publishing a project . . . . . . . . . . 165Publishing the projects for the Decision Centertutorials to Decision Center. . . . . . . . 166Opening the Decision Center Enterprise console 167Running the Decision Center Enterprise consolediagnostics . . . . . . . . . . . . . 168Opening the Decision Center Business console 168

Notices . . . . . . . . . . . . . . 171Trademarks . . . . . . . . . . . . . . 173

Index . . . . . . . . . . . . . . . 175

Contents v

vi IBM WebSphere Operational Decision Management: Configuring Decision Center

Configuring Decision Center

To use Decision Center on any instance of an application server other than theSample Server, you must deploy and configure the provided archives.

Configuring the Decision Center consoles on WebSphere ApplicationServer

To be able to use the Decision Center consoles on an instance of WebSphere®

Application Server, you deploy the provided archives and go through a series ofconfiguration steps. To configure a cluster, you can use a profile template.

Configuring the Decision Center consoles on WebSphereApplication Server

To be able to use the Decision Center consoles on a new instance of WebSphereApplication Server, you deploy the provided archives for this server and perform aseries of configuration tasks.

Before you startTo configure the Decision Center consoles on WebSphere Application Server, youmust follow specific steps. Some are mandatory, while others are optional.

Decision Center includes two consoles: Enterprise and Business. Only theEnterprise console works on WebSphere Application Server V7.0, while bothconsoles – Enterprise and Business – work on WebSphere Application Server V8.0.

The table below summarizes the steps for configuring Decision Center onWebSphere Application Server. You must have WebSphere Application Serverinstalled and running to do this configuration.

A specific integration extension for the IBM® Process Server platform is available.For more information, see WebSphere Operation Decision Management IntegrationSupportPacs.

After configuring your application server, you complete the task by following thesteps in Completing the configuration using the Decision Center console orCompleting the configuration using Ant tasks. After finishing your configuration,you can use Decision Center (see Opening Decision Center).

Note:

v If you have rule projects created with a previous product version, refer to theMigrating topics on how to upgrade the Rule Team Server database schema.

v This guide assumes that you use a profile with administrative security enabled.

What steps to follow

The following table summarizes the steps that you follow to configure DecisionCenter on WebSphere Application Server.

© Copyright IBM Corp. 2008, 2012 1

http://www.ibm.com/support/docview.wss?uid=swg27017588


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_completing.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_completing_ant.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_opening.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.family.migrating/topics/wodm_family_migrating.htm

Step Required

Step 1: Enforcing database user permissions

“Step 2: Creating a datasource and connection pool”on page 3

Creating a JDBC provider

“Creating a data source andconnection pool” on page 4

“Changing the customproperties of your datasource” on page 6

Optional

“Connecting to the database”on page 7

“Step 3: Configuringsecurity” on page 7

“User registries” on page 7 Optional

“Creating users and groups”on page 8

Optional

“Security policies for theDecision Center console” onpage 10

“Step 4: Deploying theDecision Center managementEAR” on page 11

“Declaring custom groups”on page 11

Optional

“Deploying the EAR” onpage 12

“Changing the class loadingsequence” on page 11

“Step 5: Verifying the deployment of the Decision CenterEnterprise console” on page 14

“Step 6: Completing theconfiguration of the DecisionCenter consoles” on page 15

Completing the configurationusing the Console

Select one of the twomethods to complete theinstallation. Required fordistributed platforms only.

Completing the configurationusing Ant tasks

Step 1: Enforcing database user permissionsDecision Center data is stored in a database. You restrict the type of operationsthat a user can perform on a database by defining access privileges.

The data source that contains the Decision Center data is always mapped to adatabase user.

Note:

The database privilege types differ across the supported databases. A databaseadministrator must define the privileges.

2 IBM WebSphere Operational Decision Management: Configuring Decision Center

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_db_permissions.htm





Any privilege listed in the table as “Not required” denotes that it is not requiredby the Decision Center data source.

The following table highlights the database permissions that you must enforce forthe database users, with attention given to the type of operation that you want theusers to perform:

Databasepermission

Operation

Browse and editrules (rtsUser)

Create thedatabase schemathrough theDecision Centerconsole or Anttasks(rtsInstaller)

Modify thedatabase schemathrough theDecision Centerconsole or Anttasks(rtsInstaller)

Migrate thedatabase schema(rtsInstaller)

CREATE ANYINDEX

Not required Required Required Required

DROP ANYINDEX

Not required Not required Required Required

CREATE ANYROLE

Not required Not required Not required Required

CREATE ANYSEQUENCE


DROP ANYSEQUENCE


SELECT ANYSEQUENCE

Required Required Required Required

ALTER ANYTABLE


CREATE ANYTABLE


DROP ANYTABLE


INSERT ANYTABLE


SELECT ANYTABLE


UPDATE ANYTABLE


CREATE ANYVIEW


DROP ANYVIEW


Step 2: Creating a data source and connection poolWhen your database is already running, you can create a JDBC provider, a datasource, and a connection pool. You can change the data source properties ifnecessary. Then you establish the connection.

Creating a JDBC provider:

Configuring Decision Center 3

Before you can create a data source and connection for Decision Center, you firstcreate a JDBC provider in WebSphere Application Server.

About this task

The first step in creating a data source is to create a JDBC provider.

Procedure

1. Log in to the Integrated Solutions Console.2. In the side menu, open Resources > JDBC, and click JDBC Providers.3. In Scope, select Node=x, Server=y, where x is the name of your node and y the

name of your server, and click New.4. In Step 1, Select the database type, provider type, and a non-XA

implementation type. For example, Derby, Derby JDBC Provider, andConnection pool data source.

5. Click Next. A summary opens.6. Click Finish.7. Click Save to save the changes directly to the master configuration.

Creating a data source and connection pool:

You must create a connection pool and a data source in WebSphere ApplicationServer V8.0 to enable Decision Center.

About this task

After creating your JDBC provider, you create a data source and connection pool.

Note:

If WebSphere Application Server is used in cluster mode, you must define the datasource at node level in the cluster (as opposed to cluster level). See Rule ExecutionServer deployment on cluster environments.

Procedure

To create a data source and a connection pool:1. In the Integrated Solutions Console, open Resources > JDBC, and click Data

sources.2. In the Scope side panel, select the scope that you selected for the JDBC

provider in “Creating a JDBC provider” on page 3, and then click New.3. In Step 1, enter a name for the data source in the Data source name field and

jdbc/<your_data_source_name> in the JNDI name field, and click Next.

Important: The name of the data source is not important here, but in the JNDIname, you must reuse the data source name that you entered. For example, ifyou entered ilogDataSource as the data source name, set the JNDI name tojdbc/ilogDataSource. Otherwise, Decision Center cannot use the data source.

4. In Step 2, select Select an existing JDBC provider, and then select the non-XAJDBC provider that you created in “Creating a JDBC provider” on page 3, andclick Next.

5. In Step 3, enter database properties specific to the data source and click Next.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/shared_config_websphere_topics/tpc_was_deploy_in_clusters.htm


The following table shows the minimum set of properties required to define thesupported databases. If the table does not include your driver, check theWebSphere Application Server documentation for more information.

Database Properties

DB2® Universal JDBCDriver

Properties include:

v databaseName: Database name if driverType is set to 4, or alocally catalogued database name if driverType is set to 2

v driverType: 2 or 4

The following properties are required if driverType is 4:

v serverName: TCP/IP address or host name

v portNumber: TCP/IP port number

DB2 legacy CLI-basedType 2

databaseName: for example, Sample.

Oracle JDBC Driver URL: for example, jdbc:oracle:oci:@sample

Derby v databaseName: path to the location of the database files. Thisdirectory must not exist already. For example, c:\derbydata.

v Clear the option Use this data source in container managedpersistence (CMP).

For more information, refer to the Derby documentation.

6. In Step 4, click Next to accept the default values.Step 5 displays a summary of your settings.

7. Click Finish.The connection pool is created and associated with the data source.

8. Click Save to save the changes directly to the master configuration.Related information:“Opening the Decision Center Enterprise console” on page 167You open the Decision Center console in a web browser.“Completing the configuration from the Decision Center Enterprise console” onpage 15You can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.“Completing the configuration using Ant tasks” on page 20Ant tasks provide an alternative method for completing or modifying theconfiguration. These tasks perform the same configuration steps as the InstallationSettings wizard in the Decision Center console.

Creating J2C authentication data:

In WebSphere Application Server, you can secure your enterprise informationsystem by creating J2C authentication data.

About this task

After you have created your data source and connection pool, you create the J2Cauthentication data. J2C is a secure mechanism for integrating enterpriseinformation systems to an application server and enterprise applications.


This step uses rtsAdmin as the user ID and rtsAdmin as the password. Your user IDand password might be different, depending on the user or schema that is used toexecute the Rule Execution Server SQL script. If you perform the step as described,tables are created under the rtsAdmin schema.

In the case of a Derby database, if the connect command does not contain the userID, then the user ID and password use the default values APP and APP. If youcreate the tables under the APP schema, you do not need to perform this step.

Procedure

1. In the Integrated Solutions Console, open Resources > JDBC and Datasources.

2. Click ilogDataSource.3. Under Related Items, click JAAS - J2C authentication data.4. Click New and set the fields Alias, User ID, and Password. For example, this

procedure uses the following values:v Alias: RtsDerbyUserv User ID: rtsAdminv Password: rtsAdmin

5. Click Apply and Save to save directly to the master configuration.6. Open Resources > JDBC and Data sources and click ilogDataSource.7. In the Security settings section, for Component-managed authentication alias,

select the <NodeName>/RtsDerbyUser alias, where <NodeName> is the name of theWebSphere Application Server node on which you are configuringRuleExecution Server.

8. For Container-managed authentication alias, select <node name>/RtsDerbyUser.9. Click Apply and Save to save directly to the master configuration.

Changing the custom properties of your data source:

Before you create the connection to the database, you can change the customproperties of your data source.

About this task

You can change many custom properties of the data source from the GeneralProperties page of the Integrated Solutions Console.

Procedure

To change the custom properties of your data source:1. In the Integrated Solutions Console, open Resources > JDBC, and click Data

sources.2. Click the name of the data source that you want to customize.3. Under Additional Properties, click Custom properties.

From here, you can make custom changes to the data source.

Example

For example, for a Derby data source, if you have not created the database, youcan set the createDatabase property to create. The first database connectioncreates the database.


To create the database:1. Click createDatabase. The General Properties page opens.2. Type create in the Value field.3. Click OK, and then click Save to save the changes to the master configuration.

Connecting to the database:

Test the connection to your database.

About this task

After you have created a data source and connection pool, you connect to the datasource to test the connection to the database.

Procedure

To test the connection to your database:1. In the Integrated Solutions Console, open Resources > JDBC, and click Data

sources.2. Select the check box next to the data source that you want to test, and click

Test connection.The status of the connection is indicated at the top in a message such as thefollowing one:The test connection operation for data source Decision Center Data Source on server <server_name> at node <node_name> was successful.

Step 3: Configuring securityAccess to Decision Center is managed by the application server security. To accessDecision Center in WebSphere Application Server, you must define a user registry.You can also manage the security policies.

User registries:

The user registries store information about users and user groups. Every user mustbelong to a group. You create and define the groups in the application server.

Information about users and groups resides in a user registry. In WebSphereApplication Server, a user registry authenticates a user and retrieves informationabout users and groups to perform security-related functions, includingauthentication and authorization. WebSphere Application Server supports thefollowing types of user registries:v Federated repositoryv Local operating systemv Standalone Lightweight Directory Access Protocol (LDAP) registryv Standalone custom registry

A federated user repository serves as the active user registry.v If you do not have groups or users defined or if you want define new groups or

users, go through the steps described in “Creating users and groups” on page 8.The following rules apply:– Every user of Decision Center must belong to at least one of the mandatory

groups rtsAdministrator, rtsConfigManager, rtsInstaller, or rtsUser.Adherence to these groups determines the parts of Decision Center that a usercan access.


– You must create all these groups in the application server.– For testing purposes, also create a default user and password for each of

these groups.– In addition, if you want to perform the Decision Center permissions tutorial

in your own installation, you must create the two custom groups Validatorand Eligibility.

v If you already have groups or users defined that can match the expected role,you will proceed to connect them to the roles during the applicationdeployment.

The following table summarizes groups, their uses, and their default users andpasswords.

Group Use Default user and password

rtsAdministrator Mandatory, gives the useradministrator access.

rtsAdmin, rtsAdmin

rtsConfigManager Mandatory, gives the userconfiguration manageraccess.

rtsConfig, rtsConfig

rtsUser Mandatory, gives a userstandard access.

rtsUser1, rtsUser1

rtsInstaller Mandatory, gives the useraccess to the InstallationManager.

rtsAdmin, rtsAdmin

Validator Optional custom group, usedin the Decision Centerpermissions tutorial.

Val, Val

Eligibility Optional custom group, usedin the Decision Centerpermissions tutorial.

Eli, Eli

Creating users and groups:

Security relies on users and user groups. You define the groups to which the usersbelong in the application server. For this purpose, you configure a federatedrepository as a user registry.

Before you begin

At this stage of the configuration, creating users and groups is optional:v If you already have suitable groups and users defined, skip this procedure and

connect users to their appropriate roles when you deploy your applications.v If you do not have groups and users defined or if you want to define new

groups and users, proceed with the following steps.

About this task

You configure a federated user repository as the active user registry in theWebSphere Application Server Integrated Solutions Console.


Procedure

To configure a federated repository:1. In the side panel, open Security > Global security.2. Configure the repository security as follows:

v If Federated repositories is already selected under Current realmdefinition, make sure that Enable application security is selected. If youselect Enable application security, you must click Apply and Save to savethe changes to the master configuration.

v If Federated repositories is not already selected, click SecurityConfiguration Wizard. Complete the wizard as follows:

a. In Step 1, to specify the level of protection, select Enable applicationsecurity and click Next.

b. In Step 2, select Federated repositories and click Next.c. In Step 3, type the name in the Primary administrative user name field

and enter websphere in the Password field, and then click Next.d. In Step 4, review the security configuration summary and click Finish.e. Click Save to save the changes to the master configuration.f. Restart WebSphere Application Server. Then you must log in to the

Integrated Solutions Console as the primary administrative user.3. In the side panel, open Users and Groups > Manage Groups.4. Click Create and enter rtsUser as the group name. Click Create.5. Click Create Like and create another group named rtsAdministrator. Click

Create.6. Click Create Like and create another group named rtsConfigManager. Click

Create.7. Click Create Like again and enter another group named rtsInstaller. Click

Create. Click Close.8. If you want to perform the Decision Center permissions tutorial in your own

installation, create two additional groups: Validator and Eligibility.9. In the side panel, open Users and Groups > Manage Users.

10. Click Create.11. Enter rtsUser1 as the User ID and assign this new user to a group. To do so:

a. Click Group Membership. The page that enables you to select a groupopens.

b. Click Search. The list of existing groups is displayed.c. Select the rtsUser group and click Add.d. Click Close.

12. Enter a given name and surname for rtsUser1, then enter the rtsUser1password.

13. Click Close.14. Repeat 10 to 13 to create another user named rtsAdmin with password

rtsAdmin.Assign this new user to the rtsAdministrator and rtsInstaller groups.

15. Repeat 10 to 13 to create another user named rtsConfig with passwordrtsConfig.Assign this new user to the rtsConfigManager group.


16. Optional: Create a user named Val with password Val and add the user to thertsUser, Validator, and Eligibility groups.Skip this step if you do not intend to perform the Decision Center permissionstutorial.

17. Optional: Create another user named Eli with password Eli and add the userto the rtsUser and Eligibility groups.Skip this step if you do not intend to perform the Decision Center permissionstutorial.

18. Restart your application server.Related information:“Opening the Decision Center Enterprise console” on page 167You open the Decision Center console in a web browser.“Completing the configuration from the Decision Center Enterprise console” onpage 15You can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.“Completing the configuration using Ant tasks” on page 20Ant tasks provide an alternative method for completing or modifying theconfiguration. These tasks perform the same configuration steps as the InstallationSettings wizard in the Decision Center console.

Security policies for the Decision Center console:

To enable the deployed application to access the MBean server, you must overridethe global security policies of the application server for Decision Center.

After you activate the global security of WebSphere Application Server, thedeployed application cannot access the MBean server.

You must override these security policies for the Decision Center console to allowthe console to record and manage a set of MBeans. Decision Center comes with apolicy file–was.policy–that overrides the server policies.

You can find was.policy in the META-INF directory of the jrules-teamserver-WAS<version_number>.ear file located at <InstallDir>/teamserver/applicationservers/WebSphere<version_number>.

Note: The EAR file is a compressed file. You must open it to extract the files thatmust be changed, and then replace the files in the EAR. You can use Antcommands to repackage the EAR file, as explained in “Repackaging the DecisionCenter archive” on page 28.

When you enable Java 2 Security on WebSphere Application Server, you mustupdate the was.policy file to give read and write permissions on each directorycontaining published RuleDocs. For example:

permission java.io.FilePermission "<path to my ruledoc folder>${/}-","read, write, delete";

If you do not update the was.policy file, users cannot synchronize RuleDoc to thefile system.


Step 4: Deploying the Decision Center management EARTo deploy the Decision Center EAR file for user-to-role mappings on WebSphereApplication Server, you must declare custom groups, deploy the archive file, andchange the class loader sequence.

Declaring custom groups:

Before you deploy the EAR file, you must declare your custom groups in thedeployment descriptor.

About this task

The Decision Center EAR file references the basic groups rtsUser,rtsConfigManager, rtsAdministrator, and rtsInstaller.

However, you must add any custom groups that you have declared, as describedin “Step 3: Configuring security” on page 7. This includes the Validator andEligibility groups created for the Decision Center tutorials.

Before deploying the EAR file, you add custom groups by editing the deploymentdescriptor files in <InstallDir>/teamserver/applicationservers/WebSphere<version_number>/jrules-teamserver-WAS<version_number>.ear.

Note:

v The EAR file is compressed. You must open it to extract the files that must bechanged, and then replace the files in the EAR. You can use Ant commands torepackage the EAR file, as explained in “Repackaging the Decision Centerarchive” on page 28.

v You might want to make a copy of the EAR file before modifying it.v To use the Decision Center permissions mechanism, you must upload groups to

the database. For more information, see Completing the configuration using theDecision Center console.

Procedure

To add your custom groups to the Decision Center deployment descriptor:1. Add your custom group as a role in the SECURITY - ROLE section of the

teamserver.war/WEB-INF/web.xml file in jrules-teamserver-WAS<version_number>.ear .<security-role>

<role-name>my_custom_group</role-name></security-role>

Using Validator as an example:<security-role>

<role-name>Validator</role-name></security-role>

2. If you are configuring Decision Center for WebSphere Application Server V8.0,repeat the same action in the decisioncenter.war/WEB-INF/web.xml file.

3. Add your custom group to META-INF/application.xml in the EAR file.<security-role>


Changing the class loading sequence:




After deploying the EAR file, you must set the class loading sequence to parentlast.

About this task

After you have deployed the Decision Center EAR file, set the class loadingsequence. The Decision Center application does not support the default parentfirst configuration.

Procedure

To change the class loading sequence:1. In the side panel of the Integrated Solutions Console, open Applications >

Application Types > WebSphere enterprise applications.2. Click ILOG Rule Team Server or the name you specified for the Decision

Center application.3. In the Modules section, click Manage Modules.4. Click teamserver.5. From the Class loader order menu, select Classes loaded with local class

loader first (parent last), and then click OK.6. If you are configuring WebSphere Application Server V8.0, click decisioncenter

and repeat the same action.7. Click Save to save the changes directly to the master configuration.8. In the side panel, open Applications > Application Types > WebSphere

enterprise applications.9. Select the check box next to ILOG Rule Team Server and click Start to start the

application.

What to do next

You can now verify the deployment of Decision Center (see Step 5: Verifying thedeployment of the Decision Center console).Related information:“Opening the Decision Center Enterprise console” on page 167You open the Decision Center console in a web browser.“Completing the configuration from the Decision Center Enterprise console” onpage 15You can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.“Completing the configuration using Ant tasks” on page 20Ant tasks provide an alternative method for completing or modifying theconfiguration. These tasks perform the same configuration steps as the InstallationSettings wizard in the Decision Center console.

Deploying the EAR:

After you have added custom groups, you deploy the Decision Center EAR file onWebSphere Application Server.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tsk_rts_verify.htm


About this task

After you have added your custom groups to the deployment descriptors in theDecision Center EAR, you deploy the EAR file on WebSphere Application Server tobe able to map security roles to users and groups.

Important:

v When you deploy the Decision Center EAR file, the process sets the persistencelocale. After you have saved a rule to the database, you are no longer allowed tochange the persistence locale. If you want to install Decision Center in alanguage other than English, take note of the instructions provided in Set thepersistence locale.

v If you redeploy the Decision Center EAR file, the redeployment has thefollowing consequences:– The class loading sequence is lost. See “Changing the class loading sequence”

on page 11. WebSphere Application Server reverts to the default parent firstsetting.

– All users, such as rtsUser1, rtsAdmin, lose their role, even though they belongto the correct group. When you sign in to the Decision Center console, amessage is displayeds, such as rtsUser1 does not have the correct role.

Procedure

To deploy the EAR file:1. In the side panel of the Integrated Solutions Console, click Applications >

New Application and then New Enterprise Application.2. Click Browse and navigate to the Decision Center EAR file that corresponds

to your version of WebSphere Application Server:v Version 7.0: <InstallDir>/teamserver/applicationservers/WebSphere7/

jrules-teamserver-WAS7.ear

v Version 8.0: <InstallDir>/teamserver/applicationservers/WebSphere8/jrules-teamserver-WAS8.ear

3. Click Next.4. Select the Detailed - Show all installation options and parameters check box.5. Expand Choose to generate default bindings and mappings and select the

Generate Default Bindings check box, then click Next.6. Click Continue to accept the security warning.7. In Step 1, click Next to accept the default settings.8. In Step 2, select the target server and click Next.

Keep the default setting if you only have one server.9. For Step 3 to Step 8, click Next to accept the default settings.

10. In Step 9, map security roles to users and groups.The application server uses the roles that are defined in the deploymentdescriptors. You must map these roles to the groups found in the securitysettings.a. Select a check box next to a role in the table and click Map groups.b. Click Search in the middle of the page to display the groups.c. Map the group to the role that you are editing by moving that role to the

Selected column.d. Click OK and repeat 10a to 10d for all the roles.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_set_db_locale.htm


e. In addition, if you want to follow the Decision Center permissions tutorialin your own installation, create two custom groups: Validator andEligibility.

After you have completed the assignments, they are shown as in the followingtable. If you have groups or users, you can map those to the existing roleinstead.

Table 1. Mapping user groups to roles

Role Mapped groups

rtsUser rtsUser

rtsAdministrator rtsAdministrator

rtsConfigManager rtsConfigManager

rtsInstaller rtsInstaller

Validator Validator

Eligibility Eligibility

11. If your application server is WebSphere Application Server V8.0, click Next forStep 10 and Step 11 to accept the default settings.A summary is displayed.

Note: If WebSphere eXtreme Scale is also installed, additional settings aredisplayed as Step 12 in the side panel of the Integrated Solutions Console. Seethe WebSphere eXtreme Scale Information Center for more information onadministering WebSphere eXtreme Scale with WebSphere Application Server.

12. Click Finish.13. After the installation has completed, click Save to save your workspace

changes to the master configuration.Related information:“Opening the Decision Center Enterprise console” on page 167You open the Decision Center console in a web browser.“Completing the configuration from the Decision Center Enterprise console” onpage 15You can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.“Completing the configuration using Ant tasks” on page 20Ant tasks provide an alternative method for completing or modifying theconfiguration. These tasks perform the same configuration steps as the InstallationSettings wizard in the Decision Center console.

Step 5: Verifying the deployment of the Decision CenterEnterprise consoleAfter you have finished configuring Decision Center for your application server,verify that you have deployed the archive successfully.

About this task

You start your application server, and then use your web browser to opentheDecision Center Enterprise console.


Procedure

To verify the deployment of the Decision Center console:1. Start your application server.2. Find the port number for the Decision Center console in the server log files.3. Enter the default URL to access Decision Center in a web browser:

http://localhost:<PORT_NUMBER>/teamserver.Set <PORT_NUMBER> to the port number of your web application. If yourbrowser is not running on the same host as the application server, replace thelocalhost with the address of the host.

4. Click Enter.The Decision Center sign in page opens in your browser.

Step 6: Completing the configuration of the Decision CenterconsolesAfter you have set database user permissions, created a data source, and deployedthe Decision Center EAR file, you complete the configuration either from theDecision Center console or by running Ant tasks.

Completing the configuration from the Decision Center Enterprise console:

You can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.

Installation Settings wizard overview:

You use the Installation Settings wizard in the Decision Center console to create ormodify the database schema, set up message files or groups, or change thepersistence locale or configuration parameters.

The Installation Settings wizard opens automatically when you launch the DecisionCenter console to complete an installation.

You can also open the Installation Settings wizard by clicking Configure >Installation Settings Wizard in the Decision Center console after you have

completed your initial installation. If you open Decision Center after following thesteps to install the module (see “Opening the Decision Center Enterprise console”on page 167), only the Install tab is available.

Note:

To access the Installation Settings wizard, you must have both administratorprivileges and the rtsInstaller role when you sign in.

You use the Installation Settings wizard to perform the actions in the followingtable.

Table 2. Actions in the Installation Settings wizard

Action Description

Configure thedatabase

This step is mandatory when you complete the configuration with adatabase on a distributed platform. For more information, see “Step 1:Configure the database” on page 16.


Table 2. Actions in the Installation Settings wizard (continued)

Action Description

Set up messagefiles

This step is mandatory during the installation only if you have somecustom rule model extension files. For more information, see “Step 2:Set up message files” on page 17.

Set up groups You must set up the same groups declared in the application server ifyou want to use the Decision Center security and permissionsmechanisms. For more information, see “Step 3: Set up groups” onpage 17.

Change thepersistence locale

You must perform this step if the persistence locale is different fromthe locale en_US. For more information, see “Step 4: Set the persistencelocale” on page 18.

Changeconfigurationparameters

This step is optional. You will change some configuration parameterswhen customizing Decision Center. For more information, see “Step 5:Set configuration parameters” on page 18.

After you have completed the installation, Decision Center is ready to use but doesnot contain rule projects. If you open Decision Center at this point, a message inthe Configure tab informs you that no project has been found and that you shouldeither publish a rule project using Rule Designer or contact the administrator.

If you see this message, you have to publish a rule project from Rule Designer. Formore information, see “Publishing a project” on page 165.

More information about using the Installation Settings wizard is available from theDecision Center console online help. To access the online help, click Help in thetop banner after you have signed in to Decision Center.

Note:

If you have rule projects created with a previous product version, refer to theMigrating topics on how to upgrade the Rule Team Server database schema.

Step 1: Configure the database:

You use the Installation Settings wizard to configure the database.

About this task

You store the extensions to the Decision Center rule model in two XML files:v Model description: This file usually has the filename extension .brmx.v Initialize enumerations and hierarchies: This file usually has filename extension

.brdx.

See the customization topics for more information about defining common modelextensions.

Procedure

To configure the database from the Installation Settings wizard:1. When the Installation Settings wizard opens in Decision Center, click Next.2. Select one of the extension files: Default extensions (already selected), Custom

extensions (brmx/brdx), or Custom extensions (Zip).



3. Click Generate SQL to generate the script that creates the database tablesbased on the contents of your rule model files.

4. After generating the script, select the Execute the SQL script check box, andthen click Next.

What to do next

After you have completed these steps, you can publish rule projects to yourdatabase.

Step 2: Set up message files:

Message files contain the display text that is associated with the extensions to therule model contained in the .brmx and .brdx files.

For example:status=StatuseffectiveDate=Effective DateexpirationDate=Expiration Datenew=Newdefined=Defined

Note: The contents of the message files must respect the ISO-LATIN-1 standard.

You can find the default message file in <WODM_InstallDir>/teamserver/bin/defaultextensionmessages_<LOCALE>.properties.

If you use the default rule model when creating your database, the defaultmessage file is automatically sent to the database. To upload your own messagefiles, use the Installation Settings wizard as explained below.

You must have a message file for each locale that you use. Message files areidentified by their locale.

To declare a message file in the Installation Settings wizard:

1. Click New.2. Enter a locale.3. Browse to the location of the message file for this locale.4. Click Apply.

If Decision Center supports this locale, the Installation Settings wizard assigns alocale code so that you can identify it.

When you click Next, the page “Step 3: Set up groups” opens.

Step 3: Set up groups:

In addition to creating groups in your application server when you set up securityaccess, you must use the Setup Groups page in the Installation Settings wizard toupload groups to the database.

You do this step only if you want to use the Decision Center project access andpermission mechanisms. You have to have added all the groups that you want to


see in the available list when enforcing project security or setting permissions inDecision Center. For more information, refer to the topics on Groups andPermissions in the Decision Center help.

Note: In Decision Center, the groups are the roles in the application server, not thegroups defined in the user registry. Decision Center uses the group information toverify whether a user belongs to a role in the application server.

To set up groups:

Using the Setup Groups page in the Installation Settings wizard, you upload yourcustom groups and create the default groups for rtsUser and rtsConfigManager asfollows:1. Click New.2. Type the group name.3. Click Apply.4. When you have added all the groups, proceed in one of the following ways:

v Click Next if you want to set a different persistence locale, or configurationparameters.

v Click Finish if you do not want to change these settings.

You do not have to upload the rtsAdministrator or rtsInstaller group. Theadministrator group has access to everything, and an installer user must belong toanother group.

Step 4: Set the persistence locale:

The persistence locale determines the language in which you store rules in theDecision Center database.

You set the locale when you deploy the Decision Center EAR file to yourapplication server. As a consequence, you store the rules in the database in thelocale of the Decision Center application.

Changing the persistence locale does not change the language in which DecisionCenter displays rules. Changing it in Decision Center is necessary only to matchthe locale of Rule Designer when synchronizing your rule projects, and to accessthe tutorials in your locale.

Important: You must not change the persistence locale after you have saved arule to the database.

To set the persistence locale:

1. Enter a locale in the Locale field.2. Click Apply.3. Do one of the following actions:

v Click Next if you want to set the configuration parameters.v Click Finish if you do not want to change these settings.

Step 5: Set configuration parameters:

Many tasks related to customizing Decision Center require you to add or removeconfiguration parameters.


Decision Center uses the following configuration parameters to generate completeURLs in permalinks:v teamserver.server.port: the port numberv teamserver.server.isSecure: true if the connection is securev teamserver.server.hostname: the name of the host.

You generate these parameters when you sign in to the Decision Center console forthe first time after configuring the database. You can use the Installation Settingswizard to change these parameters at any time.

The following table gives a description of the main configuration parametersavailable in teamserver.war/WEB-INF/lib/teamserver-model-XXX.jar/ilog/rules/teamserver/preferences.properties.

Parameter Used to

teamserver.<extractorValidator>.class Specify a ruleset extractor validator class touse for the given extractorValidator name.The class must implement theIlrExtractorValidator interface. After youdefine this class, specify this name as theextractor validator to use when defining aruleset extractor.

teamserver.build.path Define the location of the IRL cache in thefile system. Compute the path as follows:

v Use this property with the name of theuser who launched the server as the rootfor the cache (<build.path>_<username>).

v If it is not defined, use the systemproperty java.io.tmpdir and addrtscache (for example, <tempdir>/rtscache_<username>).

v If the system property is not defined, usethe server directory and add rtscache (forexample, <server dir>/rtscache_<username>).

teamserver.brl.verbalizers Specify the list of locales for which a BALverbalizer is defined.

teamserver.brl.verbalizer.<locale> Specify the verbalizer class for the givenlocale. The class must implement theilog.rules.vocabulary.verbalization.IlrVerbalizer interface.

Note:

The parameters in the table include the teamserver prefix, which is not in thepreferences.properties file. You must include the prefix when settingconfiguration parameters in the Installation Settings wizard.

To set configuration parameters:

Use the Set configuration parameters page in the Installation Manager wizard tocreate, modify, or delete configuration parameters.1. Do one of the following actions:

v To create a new parameter, click New.


v To change an existing parameter:a. Select the check box next to the parameter.b. Click Modify to change the parameter, or click Delete to remove the

parameter.2. Click Apply to implement your changes.3. Do one of the following actions:

v Click Previous if you want to make changes to previous settings.v Click Finish. The Installation log opens with a summary of the operations

that you performed in the Installation Settings wizard.4. Click OK to finish.

You now have to sign in to the Decision Center console. Continue with the section“Publishing a project” on page 165.

Completing the configuration using Ant tasks:

Ant tasks provide an alternative method for completing or modifying theconfiguration. These tasks perform the same configuration steps as the InstallationSettings wizard in the Decision Center console.

Setting up the Ant tasks environment:

To run Decision Center Ant tasks, you must first set up the appropriateenvironment variables.

Before you begin

When preparing to run Ant tasks, make sure that the following conditions are met:v You must have version 1.7.1 (or later) of Ant set up on your system. If Ant is not

installed or your version is older than version 1.7.1, you must set up yourenvironment to use the correct version of Ant.To test your current version of Ant, type the following command in a WindowsCommand Prompt or UNIX shell: ant -version

You can download Ant from the Apache web site, or you can use the Ant 1.7.1distribution packaged at <WODM_InstallDir>/shared/tools/ant, where<WODM_InstallDir> is your WebSphere Operational Decision Managementinstallation directory.

v Make sure that any environment variables required by WebSphere ApplicationServer are correctly set up. To do so, use the setupCmdLine.bat orsetupCmdLine.sh script in the <WAS_Install_Dir>/profiles/<profile_name>/bindirectory. This script sets up a full WebSphere Application Server environment,including the WAS_HOME, WAS_LOGGING, and WAS_CLASSPATH variables.For more information:– WebSphere Application Server 7.0 InfoCenter– WebSphere Application Server 8.0 InfoCenter

About this task

Communication between the Ant tasks and Decision Center supports the HTTP orHTTPS communication protocols. See Ant task communication protocol for moreinformation.


http://ant.apache.org/

http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.admin/topics/tpc_dc_admin_ant.htm

Procedure

To set up your environment to use Ant:1. Set the ANT_HOME environment variable to <WODM_InstallDir>/shared/tools/

ant.2. Add the directory <WODM_InstallDir>/shared/tools/ant/bin to your PATH

environment variable.

Results

The Decision Center Ant tasks are defined in <WODM_InstallDir>/teamserver/bin/build.xml and executed by commands of the form:

ant <taskName> <parameters list>

Note: To execute these Ant tasks, you must use the same Java Virtual Machineversion and vendor as the one used by the application server.

Ant task parameters start with -D. Use them to set values such as the followingones:v -Dserver.url=<server url>: Specifies the URL of the target application server.v -DdatasourceName=<data source name>: Specifies the JNDI name of the data

source to use for the task. The default value is jdbc/ilogDataSource).

Exampleant execute-schema -Dserver.url=<protocol://host:port>/teamserver/ -DdatasourceName=jdbc/ilogDataSource -Dfile=my_sql_file.sql

The <protocol://host:port> URL is defined in the file <installDir>/teamserver/bin/teamserver-anttasks.properties. If your browser is not running on the same hostas the application server, replace localhost with the address of the machine. If yourweb application is mapped to a host on a port that is different from the portnumber shown, change the port number to your host port number.

The file <WODM_InstallDir>/teamserver/bin/teamserver-anttasks.propertiesdefines the value of some common parameters and others that depend on theapplication server used. You do not have to include these parameters in your Anttask command if they are properly defined in this file. The content of theteamserver-anttasks.properties file is as follows:# Default properties# ------------------------------------rtsAdmin.login=rtsAdminrtsAdmin.password=rtsAdmin

protocol=httpserver.host=localhostserver.port=8080server.url=${protocol}://${server.host}:${server.port}/teamserver

datasourceName=jdbc/ilogDataSource

outputFile=output.sql

languagePackPath = .languagePackOutputPath = ./generated


persistenceLocale =selector =branch =override = false

Creating the database schema:

You can create the database schema in a single operation using the set-extensionsAnt task or choose to create it step by step.

Creating the schema using the set-extensions Ant task:

For convenience, you can create the database schema using the set-extensionsAnt task.

Extensions to the Decision Center rule model are stored in two XML files. One ofthe files contains the model description itself (usually, the .brmx extension is used),and the second one contains data to initialize enumerations and hierarchies(usually, the .brdx extension is used). You can use Ant tasks to load the rule modelfrom the two XML files and build the SQL script required to get the properdatabase schema.

For convenience, you can run the set-extensions Ant task, which runsgen-create-schema + execute-schema + upload-extensions + upload-roles, withthese parameters:v -Dserver.url=<server url>

v -DdatasourceName=<data source name>

v -DextensionModel=<model file>

The model description (.brmx extension).v -DextensionData=<data file>

The model data description (.brdx extension).v [-DdbSchemaName=<database schema name>]

An optional parameter that can be used to specify the database schema name.Decision Center uses the database user name as the schema name if thisparameter is not specified. However, some databases allow for a given user toaccess several schemas, and the default schema is not always named as the user.

v [-Droles=<role list>]

An optional parameter that uploads the list of roles to Decision Center. This listis specified as "role1 role2". For example:ant upload-roles -Droles="rtsUser rtsConfigManager EligibilityValidator".

Alternatively, you can create the database schema step by step, which is useful ifyou want to look at the generated SQL schema. See “Creating the schema using astep-by-step sequence.”

Note:

To execute these Ant tasks, you must use the same Java Virtual Machine versionand vendor as the one used by the application server.

Creating the schema using a step-by-step sequence:

If you want to look at the generated SQL schema, you can create it step-by-step.


Creating the database schema script:

You can create the database schema script using the gen-create-schema Ant task.

To create the SQL script required to create or update the database schema, run thegen-create-schema Ant task with these parameters:v -Dserver.url=<server url>





An optional parameter that can be used to specify the database schema name inwhich the Decision Center tables are stored. Decision Center uses the databaseuser name as the schema name if this parameter is not specified. However, somedatabases allow for a given user to access several schemas, and the defaultschema is not always named the same as the user.

v [-DoutputFile=<SQL file>]

The name of the file that stores the generated SQL script. If this parameter is notgiven, the task creates a file named output.sql in the directory defined asbasedir in build.xml.

For example:

ant gen-create-schema -DextensionModel=my_model_file.brmx-DextensionData=my_data_file.brdx -DoutputFile=my_sql_file.sql

The task connects to the given data source from the application server. The taskchecks if this data source points to an existing Decision Center database. If adatabase does not exist, the task builds the SQL script to create a fresh databaseschema to store the model. If a database does exist, the task builds the SQL scriptrequired to update the existing database schema.

Executing the database schema script:

You execute the database schema script.

To execute the SQL script that you created, run the execute-schema Ant task withthese parameters:v -Dserver.url=<server url>


v [-Dfile=<SQL file>]

The name of the file to execute, which corresponds to the script you created. Ifthis parameter is not given, the task attempts to execute a file named output.sqlin the directory defined as basedir in build.xml.

For example:

ant execute-schema -Dfile=my_sql_file.sql

Uploading the database schema extension:


You upload the database schema extension.

To store the rule model description in the database schema, run theupload-extensions Ant task with these parameters:v -Dserver.url=<server url>




The model data description (.brdx extension).

ant upload-extensions -DextensionModel=my_model_file.brmx-DextensionData=my_data_file.brdx

The description is stored in the database so that Decision Center applications canload it when they start. It is also used by gen-create-schema to get the currentmodel description to run a diff with the new schema.

In a cluster, you must restart the servers and close all current sessions.

Uploading a list of roles or groups to the database:

You can upload a list of roles or groups to the database if you use Ant tasks tocomplete or configure your installation.

In addition to creating groups in your application server when you set up securityaccess, you must upload groups to the database.

Note:

You must perform this task only if you want to use the Decision Center projectaccess and permissions mechanisms. For more information, see the topics onGroups and Permissions in the Decision Center online help.

Add all the groups that you want to see in the available list when enforcing projectsecurity or setting permissions in Decision Center. Create the default groups forrtsUser and rtsConfigManager, and upload your custom groups.

You do not have to upload the rtsAdministrator group or the rtsInstallergroup. The Administrator group has access to everything and an Installer usermust belong to another group.

To store in the database the list of roles or groups to be used by the application,run the upload-roles Ant task with the following parameters:v -Dserver.url=<server url>


v -Droles=<role list>

where <role list> is the list of roles or groups to upload to Decision Center,specified as "group1 group2".

ant upload-roles -Droles="rtsUser rtsConfigManager Eligibility Validator"



Removing a database schema:

You can create an SQL script to remove (drop) a database schema by using thegen-drop-schema Ant task.

To remove a database schema, you proceed in two steps:1. Create the SQL script required to remove the database schema.2. Execute the SQL script that you created.

Create the SQL script

To create the SQL script required to delete a database schema, run thegen-drop-schema Ant task with the following parameters:v -Dserver.url=<server url>


v -DextensionModel=<model file>: The description of the database schema toremove.

v [-DdbSchemaName=<database schema name>]

You can use an optional parameter to specify the database schema name. If youdo not specify this parameter, Decision Center uses the database user name asthe schema name. However, in some databases, users can access several schemasand the default schema is not always named as the user.


The name of the file that stores the generated SQL script. If you do not specifythis parameter, the task creates a file named output.sql in the directory definedas basedir in build.xml.

ant gen-drop-schema -DextensionModel=my_model_file.brmx-DoutputFile=my_sql_file.sql

Running the SQL script

The task connects to the given data source from the application server. It reads themodel description given in the parameters, and generates the SQL script requiredto remove the existing schema. Because many database tables are linked throughforeign keys, these tables must be removed in a specific order and the scriptgeneration handles these constraints.




The name of the file to execute, which corresponds to the script that you created.If you do not specify this parameter, the task attempts to execute a file namedoutput.sql in the directory defined as basedir in build.xml.


Defining and uploading message files:

You can define and upload message files to Decision Center using theupload-messages Ant task.


Message files contain the display text associated with the extensions to the rulemodel contained in the .brmx and .brdx files. For example:status=StatuseffectiveDate=Effective DateexpirationDate=Expiration Datenew=Newdefined=Defined

The default messages file is provided in: <WODM_InstallDir>/teamserver/bin/defaultextensionmessages_<LOCALE>.properties

Note: The contents of the messages files must conform to the ISO-LATIN-1standard.

You must have a messages file for each locale that you use. Upload the messagesfile to Decision Center by running the upload-messages Ant task with theseparameters:v -Dserver.url=<server url>


v -Dlocale=<locale>

v -DmessageFile=<message file>

ant upload-messages -Dlocale=en_US -DmessageFile=mymessages.properties

Setting the persistence locale:

The persistence locale is used to determine the language in which rules are storedin the Decision Center database.

The persistence locale is set when you deploy the Decision Center archive to yourapplication server, which means that the rules in the database are stored in thelocale of the Decision Center application.

Changing the persistence locale does not change the language in which rulesdisplay in Decision Center. Changing the persistence locale in Decision Center isnecessary only to match the locale of Rule Designer when synchronizing your ruleprojects, and to access the tutorials in your locale.

Note:

You must not change the persistence locale after you have saved a rule to thedatabase.

To set the persistence locale by running an Ant task:1. Open the <InstallDir>/teamserver/bin/teamserver-anttasks.properties file,

which defines the value of some common parameters.2. Add your locale to the persistenceLocale property and save the

teamserver-anttasks.properties file.For example: persistenceLocale = fr_FR

3. Run the Ant task using the form: ant taskName parameters_list

Alternatively, you can add the parameter to the command line. For example:ant taskName -DpersistenceLocale=fr_FR

Adding or removing configuration parameters:


You can add or remove configuration parameters of Decision Center using Anttasks.

Many tasks related to customizing Decision Center require configurationparameters to be added or removed.

The following configuration parameters, used to generate complete URLs inpermalinks, are generated the first time you sign in to Decision Center afterconfiguring the database. You can use the Installation settings wizard to set thesebeforehand or change them afterwards:v teamserver.server.port

The port number.v teamserver.server.isSecure

True if the connection is secure.v teamserver.server.hostname

The name of the host.


Parameter Use

teamserver.<extractorValidator>.class Specify a ruleset extractor validator class touse for the given extractorValidator name.The class must implement theIlrExtractorValidator interface. After thisclass has been defined, specify this name asthe extractor validator to use when defininga ruleset extractor.

teamserver.build.path Define where the cache of the IRL is locatedon the file system. The path is computed asfollows: first, use this property with thename of the user who launched the server asthe root for the cache(<build.path>_<username>). If it is notdefined, use the system propertyjava.io.tmpdir and add rtscache (forexample, <temp dir>/rtscache_<username>).If the system property is not defined, use theserver directory and add rtscache (forexample, <server dir>/rtscache_<username>).


teamserver.brl.verbalizer.<locale> Specify the verbalizer class for the givenlocale. The class must implement theIlrVerbalizer interface.

The following Ant tasks can be used to add or remove configuration parameters:

set-config-param

Sets a configuration parameter for a given user. If the user is not specified,it sets a global parameter.

Parameters:


v -Dserver.url=<server url>


v [-Duser=<username>]

v -Dkey=<parameter key>

v -Dvalue=<parameter value>

For example:

ant set-config-param -Dkey=locale -Dvalue=en_US

remove-config-param

Drops the given configuration parameter for a given user. If the user is notspecified, it drops the global configuration parameter.

Parameters:v -Dserver.url=<server url>




print-config-param

Prints the global parameters or given user parameters if username isspecified. If no key is specified, all keys are printed.





Repackaging the Decision Center archive:

You can repackage the Decision Center archive using an Ant task.

You can add new .jar files to the Decision Center archive by running therepackage-ear or repackage-war Ant task with these parameters:v -DtargetEar=<target ear> or -DtargetWar=<target war>

v -DsourceEar=<source ear> or DsourceWar=<source war>

v -DdescriptorsDir=<descriptors directory>: A directory that is copied into theMETA-INF directory of the target EAR (not mandatory).

v -DadditionalJars=<"myjar1.jar,myjar2.jar, myjarn.jar">: Additional .jarfiles to store in the lib directory of the target archive (not mandatory).

v -DtmpDir=<directory>: A directory that can be specified to store temporary files(not mandatory).

v -DwebResourcesDir=<web resources directory>: A directory that is copied intothe WAR library (not mandatory).

v -Dconsole=both|enterprise|business: Specifies whether to repackage theBusiness or Enterprise WAR files. The default is both.

This task does not use the server.url and datasourceName parameters. If you havecustomized Decision Center you must package the custom .jar files before yourepackage the Decision Center archive using this task.


Additional steps to configure the Decision Center BusinessconsoleThe search function in the Decision Center Business console is based on the Solrsearch engine. You must configure the engine to provide this functionality.Related tasks:“Using a remote Solr search engine”You set up the search function in Decision Center Business console to work with aremote instance of the Apache Solr search engine.

Using a remote Solr search engine:

You set up the search function in Decision Center Business console to work with aremote instance of the Apache Solr search engine.

About this task

The search function in Decision Center Business console uses an embeddedinstance of the Apache Solr search engine. Alternatively, you can have the searchfunction work with a remote instance of the search engine, which you can run onanother computer, or the same computer but in a dedicated web application.

Procedure

To configure the search function to run with a remote instance of the Solr searchengine:1. Install the Apache Solr search engine on another computer, or as part of a

dedicated web application on your computer. (For information on installing theSolr server, visit the Apache Solr web site.)

2. Locate the decisioncenter-solr-home.zip file in the Decision Centerteamserver folder on your computer. (The Decision Center installation programplaced the folder on your computer.)

3. Unzip the file in a directory in the remote instance of the Solr server.4. Configure the home directory of the remote Solr server to use the location of

the unzipped configuration files (see documentation on the Apache Solr website).

5. Configure the Decision Center preferences.properties file to point to the URLof the Solr server.

Related concepts:“Additional steps to configure the Decision Center Business console”The search function in the Decision Center Business console is based on the Solrsearch engine. You must configure the engine to provide this functionality.“Setting parameters for the Solr search engine”Configure the search function in the Decision Center Business console to run withthe Apache Solr search engine.

Setting parameters for the Solr search engine:

Configure the search function in the Decision Center Business console to run withthe Apache Solr search engine.

Decision Center Business console provides a function for searching rule projects.When you install this feature, it uses an embedded instance of the Apache Solrsearch engine. Alternatively, you can have the search function run with a remote


http://lucene.apache.org/solr/


instance of the search engine, which you can install on another computer, or thesame computer but in a dedicated web application (see “Using a remote Solrsearch engine” on page 29).

There are three parameters to set for the search engine:

Table 3. Search parameters

Parameter Description

search.SearchProvider This parameter takes one of the followingvalues:

v SolrEmbedded: Use to select the embeddedSolr search engine.

v SolrRemote: Use to select a remoteinstance of the Solr search engine.

search.SolrEmbeddedDataDir Use this optional parameter to direct theindex of the embedded version(SolrEmbedded) to a specific directory on theDecision Center.

search.SolrRemoteUrl Use this parameter with SolrRemote toprovide the URL of the remote Solr searchengine.

You set the configuration parameters for the search engine within thepreferences.properties file for Decision Center. For more information on thepreferences.properties file, see Configuration parameter maintenance.

The following table provides examples for setting the parameters inpreferences.properties to work with the Solr search engine:

Table 4. Configuration table for search properties

Solr server Parameter settings

External server

(The URL of the external server depends on theinstallation. For this example, the remote address of thesearch engine is http://mysearchserver:8983/solr.)

Set the preferences.properties file as follows:

search.SearchProvider=SolrRemotesearch.SolrRemoteUrl=http://mysearchserver:8983/solr

Embedded server(In this example, you store the index inthe c:/temp/DC-SearchIndex directory on yourcomputer.)


search.SearchProvider=SolrEmbeddedsearch.SolrEmbeddedDataDir=c:/temp/DC-SearchIndex

If you do not specify a directory for search.SolrEmbeddedDataDir, Decision Centerstores the search index in a temporary directory. When the server stops running, italso stops using the temporary directory. When the server restarts, it creates a newtemporary directory, and completely reindexes the repository.

If you specify a directory for search.SolrEmbeddedDataDir, the directory and itscontent persist across server restarts, and the server does not reindex the repositorywith each restart.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.bu.rules/topics/con_config_install_param.htm

Related tasks:“Using a remote Solr search engine” on page 29You set up the search function in Decision Center Business console to work with aremote instance of the Apache Solr search engine.

Additional steps to configure Decision Validation ServicesOptionally, you can deploy, configure, and test Decision Validation Services tocomplement your Decision Center configuration on WebSphere Application Server.

Before you start:

Tasks that you must perform before configuring Decision Validation Services, and alist of steps that you should take to ensure a successful configuration.

Before following the instructions to deploy and configure Decision ValidationServices, you must install the following elements:1. Optionally, install Rule Designer.2. Install Rule Execution Server and Decision Center, and configure both of these

applications.

Note:

On WebSphere Application Server, Decision Validation Services uses the defaultWork manager wm/default to run simulations and tests in managed threads.Therefore, make sure that it is defined in the application server where youconfigure Decision Validation Services.

For more information on configuring a work manager using the WebSphereApplication Server Administration Console:v On WebSphere Application Server 7, see Configuring work managers.v On WebSphere Application Server 8, see Configuring work managers.


The following table summarizes the steps that you follow to configure DecisionValidation Services.

Note:

You can also perform the configuration by following the steps in Configuring RuleExecution Server on WebSphere Application Server for z/OS® using wsadminscripts.

Step Required

“Step 1: Creating Decision Warehouse database resources”on page 32Tip:

If you have used the Rule Execution Server console to createdatabase resources (see Populating a database using theRule Execution Server console), you do not have to performthis task.

Optional


http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.base.doc/info/aes/asyncbns/tasks/tasb_workmanager.html

https://infocenter.ilogfr-bso.fr.ibm.com/infocenter/dmanager/v8r0/index.jsp?topic=%2Fcom.ibm.wodm.dcenter.config%2Fconfig_dc_websphere%2Ftpc_was_before_dvs_config.html

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.zos.dserver.config/topics/tpc_ds_config_wsadmin_scripts.htm



http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/shared_config_websphere_topics/tpc_was_pop_from_console.htm


Step Required

“Step 2: Deploying the Decision Validation Services archive”on page 33

This archive is the default SSP archive packaged with theinstaller.

Optional. Do this step if youwant to check the availabilityof the feature. You can alsouse the default archive if youhave an XML XOM in whichcase the SSP archive does nothave to be repackaged.

“Step 3: Checking the availability of Decision ValidationServices” on page 34

Optional

“Step 4: Packaging Decision Validation Services using Ant”on page 36

Optional

“Step 5: Redeploying the Decision Validation Servicesarchive” on page 36

Step 1: Creating Decision Warehouse database resources:

You can use SQL scripts to create a dedicated schema in the database.

If you set the Rule Execution Server persistence to datasource or jdbc in Selectingand applying the persistence type and you intend to use Decision Warehouse tostore your test execution results, you must create a dedicated schema in thedatabase containing these tables and views. To do so, you can use the providedSQL scripts, located in <WODM_InstallDir>/executionserver/databases. A readmefile in this directory provides additional information about the scripts.

The script that creates the Decision Warehouse database schema is namedtrace_<database_name>.sql.

Note:

The Installation Settings wizard in the Rule Execution Server console creates all therequired tables for Rule Execution Server and for Decision Warehouse. If you areconfiguring Decision Validation Services and you have already run the InstallationSettings wizard to create the tables, you do not have to create database resourcesmanually. However, if you did not use the wizard to create database resources, youmust run the script to create the Decision Warehouse database schema.

When you use DB2 (except on z/OS), the scripts that create the Rule ExecutionServer database tables are written for databases that use automatic storage.v BP32K is the buffer pool that is expected in SYSCAT.BUFFERPOOLS. If BP32K is not

there, you can use the existing buffer pool or create a new buffer pool namedBP32K. Use the following command to query SYSCAT.BUFFERPOOLS for the existingbuffer pool:Select * from SYSCAT.BUFFERPOOLS

Otherwise, use the following command to create a buffer pool named BP32K:CREATE BUFFERPOOL BP32K SIZE 2000 PAGESIZE 32K

v You must update the trace_db2.sql script and select the custom option in theInstallation Settings wizard to run it. Modify the following line in the script tospecify storage for the table space:CREATE TABLESPACE RESDWTS PAGESIZE 32K BUFFERPOOL BP32K;

Here is an example of the table space specification in the script:


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/shared_config_topics/tpc_res_changing_persistence.htm


CREATE TABLESPACE RESDWTS PAGESIZE 32K MANAGED BY DatabaseUSING [ FILE ’C:\DB2\Container.file’ 640 ] BUFFERPOOL BP32K;

v You might have to further modify the script based on your database settings.

Note:

If you completed this task as part of the Rule Execution Server configuration, youdo not have to do this a second time. It is included here solely for completeness.

If you use Command Editor to run the scripts, you must log in with the credentialsthat you use for the data source for Rule Execution Server.

Use any tool that can handle SQL to import and run the SQL scripts. The toolsprovided for each database include:

Database Database tool

IBM DB2 DB2 command line processor

Derby ij command line processor

H2 H2 console

HSQL HSQL database manager

MySQL mysql command line processor

Oracle sqlplus command line processor

SQL Server Query Tool

Sybase isql command line processor

To access the database, the database user must have the following credentials:v A user ID and a passwordv Complete privileges on the tables and view of the schema (create, insert, delete)v Create index privilegesv On Oracle, create trigger and create sequence privileges

When using an Oracle database, run all the scripts in the SQL Plus client.

Install a database client for the database that you use. Refer to the documentationof the database for more information.

The default CLOB size might not be sufficient for the FULL_EXECUTION_TRACE field inthe EXECUTION_TRACES table. You might need a size qualifier if SQL raisesexceptions with the <Lob-Value> reason code.

Step 2: Deploying the Decision Validation Services archive:

How to deploy the Decision Validation Services archive.

About this task

This step shows you how to deploy the Decision Validation Services archive. Thearchive must be deployed on the same server as the XU. You can use thisprocedure to deploy the default SSP archive packaged with the installer or anysubsequent deployment of a repackaged archive. Deploy the default SSP EAR ifyou want to check the availability of the feature. You can also deploy the defaultSSP EAR and use this to test your rules if you have an XML XOM. An XML XOM


is included in the ruleset archive inside a RuleApp, and therefore the SSP EARdoes not have to be repackaged to include the XOM.

If you are installing Decision Validation Services on z/OS, you can usecustomizable installation scripts to perform this task. For more information, refer toConfiguring Rule Execution Server on WebSphere Application Server for z/OSusing wsadmin scripts.

Procedure

To deploy an SSP archive:1. Open the Integrated Solutions Console.2. In the side panel, open Applications and click Websphere Enterprise

Applications

3. In the side panel, click Install.4. In the side panel, select Local file system, Browse to the following file, and

then click Next.<InstallDir>/executionserver/applicationservers/WebSphere8/jrules-ssp-WAS8.ear

5. Select the check box Detailed - Show all installation options and parameters.Expand Choose to generate default bindings and mappings and select thecheck box Generate Default Bindings. 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. Select the resAdministrators group. To do this, click the group name underAvailable, 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.14. Click Finish. 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-WAS7.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).19. Click OK.20. Click OK and Save directly to the master configuration.21. In the side panel, open Applications > Application Types > WebSphere

enterprise applications.22. In the Enterprise Applications page select the check box next to

jrules-ssp-WAS8 and click Start to start the application.

Step 3: Checking the availability of Decision Validation Services:




A specific testing URL is designed for you to check the rule session type, DAOfactory class for trace persistence, the class used to cache the Decision ValidationServices job, and the pool size for asynchronous execution.

To check the availability of Decision Validation Services:1. Enter the URL http://<host>:<port>/testing in a web browser.2. Log in to the (Scenario Service Provider) SSP application using a Rule

Execution Server role.The application displays a home page, which contains information about theSSP server.

Version

The version of Decision Server used.

Patch level

The patch level of Decision Server used.

License information

The type of license of this version.

RuleSession

The RuleSession type (POJO or J2SE).

DAO Factory Class

The DAO (Data Access Object) Factory class used to persist the trace intothe data warehouse.

Job store class

The name of the class used to persist the Decision Validation Services jobinto a cache to free the memory during long computations.

Job pool size

The size of the pool for the asynchronous execution.

Started since

The time and date when the SSP started.

Jobs currently running

The About screen provides information about the jobs currently runningafter you run Decision Validation Services in Decision Center:v A Job ID is listed in the table when a user clicks Run in Decision

Center.v The Created column records the date and time when each job is

initialized.v The Status column shows the number of scenarios that have already

been tested compared to the total number of scenarios.v The Start time records the time when a resource is allocated for the job.v The Parts column records the number of parts in the job:

– A job that is not executed in parallel has one part.– A job that is executed in parallel has one or more parts.

v The End time records the time when the execution of the job iscomplete, that is, all of the scenarios in the job have been tested.


The report for the job is automatically downloaded by Decision Center atthe end of the execution. If the scenario suite is run in the background, theuser downloads the report by viewing the list of scenario suites, and thenclicking the report link when it becomes available. After the report isviewed, the job is removed from the table. The job remains in the tableuntil the report is downloaded.

Step 4: Packaging Decision Validation Services using Ant:

You can configure Decision Validation Services archives by using an Ant task.

About this task

This section is for users installing on Windows and other supported distributedplatforms only.

You can configure Decision Validation Services archives by running the ssp-setupAnt file.

Procedure

To use the ssp-setup Ant task:1. Define the Ant task in your build file using the <taskdef> Ant element in one

of the following ways:v Define the task at the top level, or within a specific target:

<taskdef resource="res-tasks.properties"classpath="${<InstallDir>}/executionserver/lib/jrules-res-setup.jar"/>

v If the JAR file is available in your system, you can use:<taskdef resource="res-tasks.properties"/>

2. Use the <ssp-setup> Ant task to update an SSP artifact to your specificconfiguration and XOM.

3. Run the Ant task in one of the following ways:v From the command line: Execute Ant in the required directory, followed by

the name of the build file if necessary.v From Eclipse: Right-click the Ant file and click Run.

What to do next

You can now deploy the testing archive.

Step 5: Redeploying the Decision Validation Services archive:

How to redeploy the Decision Validation Services archive.

About this task

This step shows you how to redeploy the Decision Validation Services archive. Thearchive must be redeployed on the same server as the XU. You can use thisprocedure to redeploy the default SSP archive packaged with the installer or anysubsequent deployment of a repackaged archive. Redeploy the default SSP EAR ifyou want to check the availability of the feature. You can also redeploy the defaultSSP EAR and use this to test your rules if you have an XML XOM. An XML XOMis included in the ruleset archive inside a RuleApp, and therefore the SSP EARdoes not have to be repackaged to include the XOM.


Procedure

To redeploy an SSP archive (an archive has already been deployed):1. Open the Integrated Solutions Console.2. In the side pane, open Applications and click Websphere Enterprise

Applications.3. Select the deployed SSP application in the side pane and click Uninstall.4. Click OK to confirm uninstallation of the SSP application.5. Click Save to save the changes directly to the master configuration.6. Follow the previous procedure in “Step 2: Deploying the Decision Validation

Services archive” on page 33 to deploy the new SSP.

TroubleshootingIn case of problems or poor performance, you can allocate more memory to yourapplications.

For more troubleshooting information, contact Troubleshooting and support.

Providing more memory for applications:

If you experience core dumps or Java out-of-memory errors, you can make morememory available to WebSphere Application Server by increasing the maximumheap size for the Java Virtual Machine (JVM).

Procedure

To increase the WebSphere Application Server memory settings:1. In the WebSphere Application Server console, open Servers > Server Types >

WebSphere application servers.2. In the Application servers panel, click the name of your server.3. Under Server Infrastructure, expand Java and Process Management and click

Process definition.

Note: On z/OS, an additional layer provides three resources that can beadministered: Adjunct, Control, and Servant. If you are working in thatenvironment, select Servant.

4. Under Additional Properties, click Java Virtual Machine.5. Set the Initial heap size and Maximum heap size fields to the appropriate

values.For example, you can enter the following values:v For a 32-bit configuration: 512 and 1024 MB respectivelyv For a 64-bit configuration: 1024 and 4096 MB respectively

6. Click OK, then Save to save the changes directly to the master configuration.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.family/topics/con_support_troubleshoot.htm

Related information:“Before you start” on page 1To configure the Decision Center consoles on WebSphere Application Server, youmust follow specific steps. Some are mandatory, while others are optional.“Opening the Decision Center Enterprise console” on page 167You open the Decision Center console in a web browser.

Configuring the Decision Center consoles on WebSphereApplication Server for Linux on System z

To be able to use the Decision Center consoles on an instance of WebSphereApplication Server for Linux on System z®, you set up the persistence for theresources, create a JDBC provider, deploy the provided archives for this server, andactivate security.

Before you startTo configure Decision Center console on WebSphere Application Server for Linuxon System z, you must follow specific steps. Some are mandatory, while others areoptional.

A specific integration extension for the IBM Process Server platform is available.For more information, refer to this page: WebSphere Operation DecisionManagement Integration SupportPacs

To understand the tasks you must complete, refer to “What steps to follow” onpage 39.

You finish the configuration by Completing the configuration using the DecisionCenter console or Completing the configuration using Ant tasks.

After your configuration is finished, Decision Center is ready to use (see “Openingthe Decision Center Enterprise console” on page 167). The first time you openDecision Center , it does not contain a rule project. You must publish a projectfrom Rule Designer (see Publishing a project).

This guide assumes that you are using a profile that has administrative securityenabled.

Software Prerequisites

You must have installed the following software before you configure DecisionCenter:v WebSphere Application Server for zLinux V7.0 or V8.0v DB2 Version 9.5 or 10v Java 1.6 included in your PATH statement.

You also need the following rights:v Access to the WebSphere Application Server Integrated Solutions Consolev DB2 Administrator authority to CREATE a database and CREATE & UPDATE

tablesv Authority to start and stop the WebSphere Application Server




http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_completing_was_linux.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_completing_was_linux.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_completing_ant_was_linux.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tsk_rts_publishing.htm


The following table summarizes the steps that you follow to configure DecisionCenter on WebSphere Application Server.

Step Required

Step 1: Enforcing database user permissions

“Step 2: Setting up Java 2 connection security” on page 41

“Step 3: Configuring securityon WebSphere ApplicationServer” on page 41

“Defining a user registry” onpage 41

Optional

“Creating users and groups”on page 42

Optional

“Security policies for theDecision Center Console” onpage 44

“Step 4: Creating the DB2 database” on page 44

“Step 5: Creating a JDBC provider” on page 44

“Step 6: Creating a datasource and connection pool”on page 45

“Creating a data source andconnection pool” on page 45

“Testing the connection tothe database” on page 46

“Step 7: Deploying theDecision Center EAR onWebSphere ApplicationServer” on page 47


Optional

“Deploying the EAR” onpage 48

“Verifying the deployment ofthe Decision CenterEnterprise console” on page50

Optional

“Changing the class loadingsequence” on page 48

“Step 8: Completing the configuration” on page 50

Use one of the two methodsto complete the installation.

Starting the Decision Center console Optional

Running the Decision Center console diagnostics Optional


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_db_permissions_was_linux.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tpc_rts_starting_console.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.config/shared_config_topics/tsk_rts_diagnostic.htm



Note:




Databasepermission

Operation





CREATE ANYINDEX


DROP ANYINDEX


CREATE ANYROLE


CREATE ANYSEQUENCE


DROP ANYSEQUENCE


SELECT ANYSEQUENCE


ALTER ANYTABLE


CREATE ANYTABLE


DROP ANYTABLE


INSERT ANYTABLE


SELECT ANYTABLE


UPDATE ANYTABLE


CREATE ANYVIEW



Databasepermission

Operation





DROP ANYVIEW


Step 2: Setting up Java 2 connection securityHow to create J2C authentication data in WebSphere Application Server 8.0.

About this task

If you completed this task as part of the Rule Execution Server installation, you donot need to do it a second time. The procedure is included here solely forcompleteness. See Setting up Java 2 connection security for more information.

Procedure

To set up connection security:1. From the WebSphere Application Server Integrated Solutions Console, open

Security > Global Security.2. Expand Java Authentication and Authorization Service and select J2C

authentication data.3. Click New and provide the DB2 Administrator's credentials in the User ID and

Password fields.4. Click Apply and Save directly to the master configuration.

Step 3: Configuring security on WebSphere Application ServerDecision Center access is managed by the application server security. To accessDecision Center in WebSphere Application Server 8.0, you must define a userregistry.

Defining a user registry:

How to define a file-based federated user repository as a user registry.

Information about users and groups resides in a user registry. In WebSphereApplication Server, a user registry authenticates a user and retrieves informationabout users and groups to perform security-related functions, includingauthentication and authorization. WebSphere Application Server supports thefollowing types of user registries:v Federated repositoryv Local operating systemv Standalone Lightweight Directory Access Protocol (LDAP) registryv Standalone custom registry

A federated user repository serves as the active user registry.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/config_ds_res_was8/tsk_zlinux_secure_j2conn.htm

v If you do not have groups or users defined or if you want define new groups orusers, go through the steps described in “Creating users and groups” on page 8.The following rules apply:– Every user of Decision Center must belong to at least one of the mandatory

groups rtsAdministrator, rtsConfigManager, rtsInstaller, or rtsUser.Adherence to these groups determines the parts of Decision Center that a usercan access.

– You must create all these groups in the application server.– For testing purposes, also create a default user and password for each of

these groups.– In addition, if you want to perform the Decision Center permissions tutorial

in your own installation, you must create the two custom groups Validatorand Eligibility.

v If you already have groups or users defined that can match the expected role,you will proceed to connect them to the roles during the applicationdeployment.

The following table summarizes groups, their uses, and their default users andpasswords.

Group Use Default user and password


rtsAdmin, rtsAdmin


rtsConfig, rtsConfig


rtsUser1, rtsUser1

rtsInstaller Mandatory, gives the useraccess to the InstallationManager.

rtsAdmin, rtsAdmin


Val, Val


Eli, Eli

Creating users and groups:

Security relies on users and user groups. You define the groups to which the usersbelong in the application server. For this purpose, you configure a federatedrepository as a user registry.

Before you begin

At this stage of the configuration, creating users and groups is optional:v If you already have suitable groups and users defined, skip this procedure and

connect users to their appropriate roles when you deploy your applications.v If you do not have groups and users defined or if you want to define new

groups and users, proceed with the following steps.


About this task

This step explains how to configure a federated user repository as the active userregistry in the WebSphere Application Server Integrated Solutions Console.

Procedure

To configure a federated repository:1. In the Integrated Solutions Console, open Security > Global security.2. Configure the repository security as follows:

v If Federated repositories is already selected under Current realmdefinition, make sure Enable application security is selected. If you selectEnable application security, you must click Apply and Save to save thechanges to the master configuration.

v If is not already selected, click Security Configuration Wizard. Completethe wizard as follows

a. In Step 1, to specify the level of protection, select Enable applicationsecurity and click Next.

b. In Step 2, select Federated repositories and click Next.c. In Step 3, type the name in the Primary administrative user name field

and websphere in the Password field, then click Next.d. In Step 4, review the security configuration summary and click Finish.e. Click Save to save the changes to the master configuration.f. Restart WebSphere Application Server. You then have to log into the

Integrated Solutions Console as the primary administrative user.3. In the side panel, open Users and Groups > Manage Groups, and click

Create.4. Enter rtsUser as the group name and click Create.5. Click Create Like and create another group named rtsAdministrator and

click Create.6. Click Create Like and create another group named rtsConfigManager and

click Create.7. Click Create Like again and enter another group named rtsInstaller and

click Create, then click Close.8. If you want to perform the Decision Center permissions tutorial in your own

installation, create two additional groups: Validator and Eligibility.9. In the side panel, open Users and Groups > Manage Users, and click Create.

10. Enter rtsUser1 as the User ID with a password rtsUser1. Also specify thegiven name and last name.

11. Click Group Membership and then click Search. Select the rtsUser group andclick Add. Click Close and then click Create and Close again.

12. Create another user named rtsAdmin with password rtsAdmin. Repeat theprevious step and assign the user to the rtsAdministrator and rtsInstallergroups.Then create a user named rtsConfig with password rtsConfig. Repeat theprevious step and assign the user to rtsConfigManager group.

13. Skip this step if you do not intend to perform the Decision Center permissionstutorial. Create a user named Val with password Val and add the user to the


rtsUser, Validator, and Eligibility groups. Then create another user namedEli with password Eli and add the user to the rtsUser and Eligibilitygroups.

14. Restart your application server.

Security policies for the Decision Center Console:

How Decision Center overrides the server policies.

After the global security of WebSphere is activated, the MBean server cannot beaccessed from the deployed application.

These security policies must be overridden for the Decision Center Consolebecause it needs to record and manage a set of MBeans. Decision Center ispackaged with a specific policy file that overrides the server policies.

This was.policy file is packaged in the jrules-teamserver-WAS8.ear file, located inthe META-INF directory.

When you enable Java 2 Security on WebSphere, the was.policy file must beupdated to give read and write permissions on each directory where RuleDoc ispublished, similar to the following example:

permission java.io.FilePermission "<path to my ruledoc folder>${/}-","read, write, delete";

If you do not update the was.policy file, users cannot synchronize RuleDoc to thefile system.

Step 4: Creating the DB2 databaseAn empty DB2 database is required for Decision Center.

About this task

You must create an empty database for Decision Center.

Procedure

To create the DB2 database:1. If the Decision Center database does not exist, you must create it. You need

DB2 Administrator permission to create the database using the followingcommands:su {DB2AdminName}db2CREATE DATABASE {RTSDBName}

2. After you have created the empty database, you can close the DB2 commandline client:quitexit

Step 5: Creating a JDBC providerHow to create a JDBC provider in WebSphere Application Server 8.0 to enableDecision Center.


About this task

The first step in creating a data source is to create a JDBC provider.

Procedure1. Log in to the Integrated Solutions Console.2. In the pane, open Resources > JDBC and click JDBC Providers.3. In the pane in Scope, select Node=xxx, Server=yyy (where xxx is the name of

your node and yyy the name of your server) and click New.4. In Step 1 select:

Database type

DB2

Provider type

DB2 Universal JDBC Driver Provider

Implementation type

Select Connection pool data source, then type a name (for example,“DB2 Universal JDBC Driver Provider for Decision Center”).

Click Next.5. In Step 2 leave all class path values, including the blanks, as the default

values. Click Next.6. A summary is provided in Step 3.

Check that the class path to the JAR of your driver and the implementationclass are correct. Default values are usually sufficient.

7. Click Finish and Save to save the changes directly to the masterconfiguration.

8. The DB2 installation might have installed the file db2jcc_license_cisuz.jarin a location that is not in the WebSphere path. Find thedb2jcc_license_cisuz.jar file (it is best to do this as the root user to avoidpermissions messages) using the following command:find / -name db2jcc_license_cisuz.jar

9. From the WebSphere Integrated Solutions Console open Environment >WebSphere variables. Click DB2UNIVERSAL_JDBC_DRIVER_PATH.

10. Set the value to the path discovered by the find command.11. Click OK and Save to save the changes to the master configuration.

Step 6: Creating a data source and connection poolCreating a data source assumes that your database is already running.

Creating a data source and connection pool:

You must create a connection pool and a data source in WebSphere ApplicationServer to enable Decision Center.

About this task

After you have created your JDBC provider, you can create a data source andconnection pool.

Note:


If WebSphere Application Server is used in cluster mode, you must define the datasource at node level in the cluster (as opposed to cluster level). See Rule ExecutionServer deployment on cluster environments.

Procedure

To create a data source and a connection pool:1. In the Integrated Solutions Console, open Resources > JDBC and Data

sources.2. In the Scope side panel, select the scope that you selected for the JDBC

provider in “Step 5: Creating a JDBC provider” on page 44, and then clickNew.

3. In Step 1, enter a name for the data source in the Data source name field andjdbc/<your_data_source_name> in the JNDI name field, and click Next.

Important: The name of the data source is not important here, but in the JNDIname, you must reuse the data source name that you entered. For example, ifyou entered ilogDataSource as the data source name, set the JNDI name tojdbc/ilogDataSource. Otherwise, Decision Center cannot use the data source.

4. In Step 2 choose Select an existing JDBC provider, then select the JDBCprovider that you created in “Step 5: Creating a JDBC provider” on page 44and click Next.

5. In Step 3, set the specific database properties for the data source:a. Enter the following values:

Driver type

4

Database name

Type your database name, for example RTSDB.

Server name

Type your server name.

Port number

Type your port number.b. Clear the option Use this data source in container managed persistence

(CMP).c. Click Next.

6. In Step 4, select the DB2 Administrator's authentication alias from theComponent-managed authentication alias option, and then click Next.In Step 5, a summary of the data source is provided.

7. Click Finish and Save to save the changes to the master configuration.

Testing the connection to the database:

How to test the connection to your database.

About this task

After you have created a data source and connection pool, and set the customproperties, test the connection to your database.




Procedure

To test the connection to your database:1. In the Integrated Solutions Console open Resources > JDBC and click Data

sources.2. Select the check box next to the data source you want to test and click Test

connection.The status of the connection is indicated at the top of the screen.Potential connection errors might be:v Java class ..com.ibm.db2.jcc is not found

Check that the jcc drivers classpath is correctly set.v Null Userid is not supported — SQL ERRORCODE 4461,

Authentication has failed. Check that the JAAS-J2C Authenticationcredentials are correct.

Step 7: Deploying the Decision Center EAR on WebSphereApplication ServerDeploying the Decision Center EAR on WebSphere Application Server V8.0requires you to declare custom groups, deploy the EAR, then change the ClassLoader sequence.

Declaring custom groups:

Before you can deploy the EAR file, you must declare your custom groups in thedeployment descriptor.

About this task

The Decision Center EAR references the basic groups rtsUser, rtsConfigManager,rtsAdministrator, and rtsInstaller.

However, you must add any custom groups that you declared previously, asdescribed in “Creating users and groups” on page 42, including the Validator andEligibility groups created for the Decision Center tutorials. You add customgroups by editing the deployment descriptor files in the EAR file<++JRULESHOME++>jrules-teamserver-WAS<version_number>.ear before deploying,where <++JRULESHOME++> is your z/OS zFS JRules installation directory.

Note:

v You might want to make a copy of the EAR before modifying it.v To use the Decision Center permissions mechanism, you upload groups to the

database. For more information, see Completing the configuration using theDecision Center console.

Procedure

To add your custom groups to the Decision Center deployment descriptor:1. Add your custom group as a role in the SECURITY - ROLE section of

teamserver.war/WEB-INF/web.xml of jrules-teamserver-WAS<version_number>.ear in the EAR file.<security-role>

<role-name>my_custom_group</role-name></security-role>..




2. If you are configuring Decision Center for WebSphere Application Server V8.0,repeat the same action in the decisioncenter.war/WEB-INF/web.xml file.

3. Add your custom group to META-INF/application.xml in the EAR file....<security-role>


Changing the class loading sequence:

After you have deployed the EAR file, you must set the class loading sequence toparent last.

About this task

After you have deployed the Decision Center EAR file, set the class loadingsequence. The Decision Center application does not support the default parentfirst configuration.

Procedure

To change the class loading sequence:1. In the panel, open Applications > Application Types > WebSphere

enterprise applications.2. Click ILOG Decision Center or the name that you specified for the Decision

Center application.3. In the Modules section, click Manage Modules.4. Click teamserver, select Class loader order > Classes loaded with local class

loader first (parent last), then click OK.5. If you are configuring on WebSphere Application Server V8.0, click

decisioncenter and repeat the same action.6. Click Save to save the changes directly to the master configuration.7. In the panel, open Applications > Application Types > WebSphere

enterprise applications.8. Select the check box next to ILOG Decision Center and click Start to start the

application.

What to do next

You can now verify the deployment of Decision Center. SeeStep 5: Verifying thedeployment of the Decision Center console.

Deploying the EAR:

How to deploy the Decision Center EAR on WebSphere Application Server.

About this task

After you have added your custom groups to the deployment descriptors in theDecision Center EAR, you deploy the EAR on WebSphere Application Server.

Important:

v When you deploy the Decision Center EAR, the process sets the persistencelocale. After you save a rule to the database, you no longer need to change the




persistence locale. If you want to install Decision Center in a language otherthan English, take note of the instructions provided in Step 4: Set PersistenceLocale.

v If you redeploy the Decision Center EAR, the redeployment has the followingconsequences:– The class loading sequence is lost (see “Changing the class loading sequence”

on page 48). Decision Center reverts to the default parent first setting.– All users (such as rtsUser1, rtsAdmin) lose their role, even though they

belong to the correct group. You notice this when you sign in to the DecisionCenter console. A message is displayed, for example, rtsUser1 does not havethe correct role.

Procedure

To deploy the EAR:1. In the side panel of the Integrated Solutions Console, click Applications >

New Application and then New Enterprise Application.2. Click Browse and navigate to the following Decision Center EAR file, and

then click Next.v <++JRULESHOME++>jrules-teamserver-WAS7.ear

v <++JRULESHOME++>jrules-teamserver-WAS8.ear

<++JRULESHOME++> is your z/OS zFS WebSphere Operational DecisionManagement installation directory.

3. Select the Detailed - Show all installation options and parameters check box.4. Expand Choose to generate default bindings and mappings and select the

check box Generate Default Bindings, and then click Next.5. Click Continue to accept the security warning.6. In Step 1, click Next to accept the default settings.7. In Step 2, select the target server and click Next.

Keep the default setting if you only have one server.8. For Step 3 to Step 8, click Next to accept the default settings.9. Click Step 9 to map security roles to users and groups.

The application server uses the roles that are defined in the deploymentdescriptors. You must map these to the groups found in the security settings.a. Select a check box next to a role in the table and click Map groups.b. Click Search in the middle of the page to display the groups.c. Map the group to the role that you are editing by moving it to the

Selected column.d. Click OK and repeat for all the roles.

After you have completed the assignments, they are shown as in thefollowing table. If you have groups or users, you can map those to theexisting role instead.

RoleSpecialsubjects Mapped groups

rtsUser None rtsUser

rtsAdministratorNone rtsAdministrator

rtsConfigManagerNone rtsConfigManager

rtsInstaller None rtsInstaller




RoleSpecialsubjects Mapped groups

Validator None Validator

Eligibility None Eligibility

10. Click Next.A summary is displayed.

11. Click Finish.12. After the installation has completed, click Save to save your workspace

changes to the master configuration.

Verifying the deployment of the Decision Center Enterprise console:

After you have deployed Decision Center on your application server, verify thedeployment.

Procedure

To verify the deployment of Decision Center:1. Enter the default URL to access Decision Center in a browser.

v The default URL to access Decision Center is http://localhost:<PORT_NUMBER>/teamserver.

v On WebSphere Application Server V8.0, each console has a different defaultURL:– For the Enterprise Console: http://localhost:<PORT_NUMBER>/teamserver– For the Business Console: http://localhost:<PORT_NUMBER>/

decisioncenter

v If your browser is not running on the same host as the application server,replace localhost with the address of the host.

v If your web application is mapped to a host on a port that is different fromthe port number shown, change the port number to your host port number.

2. Select the help option to view the help.

Step 8: Completing the configurationExplains how to complete the configuration. You can perform this step using theDecision Center console or Ant tasks.

Completing the configuration from the Decision Center Enterprise console:

You can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.







Note:




Action Description



Set up messagefiles










Note:






About this task


.brdx.


Procedure


extensions (brmx/brdx), or Custom extensions (Zip).3. Click Generate SQL to generate the script that creates the database tables

based on the contents of your rule model files.4. After generating the script, select the Execute the SQL script check box, and

then click Next.

What to do next










1. Click New.2. Enter a locale.3. Browse to the location of the message file for this locale.


4. Click Apply.


When you click Next, the page “Step 3: Set up groups” on page 17 opens.



You do this step only if you want to use the Decision Center project access andpermission mechanisms. You have to have added all the groups that you want tosee in the available list when enforcing project security or setting permissions inDecision Center. For more information, refer to the topics on Groups andPermissions in the Decision Center help.


To set up groups:



















Parameter Used to








Parameter Used to


Note:




v To create a new parameter, click New.v To change an existing parameter:

a. Select the check box next to the parameter.b. Click Modify to change the parameter, or click Delete to remove the





Completing the configuration using Ant tasks:

Ant tasks provide an alternative method for completing or modifying theconfiguration. These tasks perform the same configuration steps as the InstallationSettings wizard in the Decision Center console.


To run Decision Center Ant tasks, you must first set up the appropriateenvironment variables.

Before you begin

When preparing to run Ant tasks, make sure that the following conditions are met:v You must have version 1.7.1 (or later) of Ant set up on your system. If Ant is not

installed or your version is older than version 1.7.1, you must set up yourenvironment to use the correct version of Ant.To test your current version of Ant, type the following command in a WindowsCommand Prompt or UNIX shell: ant -version


You can download Ant from the Apache web site, or you can use the Ant 1.7.1distribution packaged at <WODM_InstallDir>/shared/tools/ant, where<WODM_InstallDir> is your WebSphere Operational Decision Managementinstallation directory.

v Make sure that any environment variables required by WebSphere ApplicationServer are correctly set up. To do so, use the setupCmdLine.bat orsetupCmdLine.sh script in the <WAS_Install_Dir>/profiles/<profile_name>/bindirectory. This script sets up a full WebSphere Application Server environment,including the WAS_HOME, WAS_LOGGING, and WAS_CLASSPATH variables.For more information:– WebSphere Application Server 7.0 InfoCenter– WebSphere Application Server 8.0 InfoCenter

About this task


Procedure

To set up your environment to use Ant:1. Set the ANT_HOME environment variable to <WODM_InstallDir>/shared/tools/

ant.2. Add the directory <WODM_InstallDir>/shared/tools/ant/bin to your PATH

environment variable.

Results





source to use for the task. The default value is jdbc/ilogDataSource).

Exampleant execute-schema -Dserver.url=<protocol://host:port>/teamserver/ -DdatasourceName=jdbc/ilogDataSource -Dfile=my_sql_file.sql


The file <WODM_InstallDir>/teamserver/bin/teamserver-anttasks.propertiesdefines the value of some common parameters and others that depend on the






application server used. You do not have to include these parameters in your Anttask command if they are properly defined in this file. The content of theteamserver-anttasks.properties file is as follows:# Default properties# ------------------------------------rtsAdmin.login=rtsAdminrtsAdmin.password=rtsAdmin




















Alternatively, you can create the database schema step by step, which is useful ifyou want to look at the generated SQL schema. See “Creating the schema using astep-by-step sequence” on page 22.

Note:














For example:










For example:















Note:
























The task connects to the given data source from the application server. It reads themodel description given in the parameters, and generates the SQL script required


to remove the existing schema. Because many database tables are linked throughforeign keys, these tables must be removed in a specific order and the scriptgeneration handles these constraints.













v -Dlocale=<locale>






Changing the persistence locale does not change the language in which rulesdisplay in Decision Center. Changing the persistence locale in Decision Center is


necessary only to match the locale of Rule Designer when synchronizing your ruleprojects, and to access the tutorials in your locale.

Note:















Parameter Use



Parameter Use





set-config-param







For example:


remove-config-param






print-config-param

















Additional steps to configure the Decision Center BusinessconsoleThe search function in the Decision Center Business console is based on the Solrsearch engine. You must configure the engine to provide this functionality.

Using a remote Solr search engine:

You set up the search function in Decision Center Business console to work with aremote instance of the Apache Solr search engine.

About this task

The search function in Decision Center Business console uses an embeddedinstance of the Apache Solr search engine. Alternatively, you can have the searchfunction work with a remote instance of the search engine, which you can run onanother computer, or the same computer but in a dedicated web application.

Procedure

To configure the search function to run with a remote instance of the Solr searchengine:1. Install the Apache Solr search engine on another computer, or as part of a

dedicated web application on your computer. (For information on installing theSolr server, visit the Apache Solr web site.)

2. Locate the decisioncenter-solr-home.zip file in the Decision Centerteamserver folder on your computer. (The Decision Center installation programplaced the folder on your computer.)

3. Unzip the file in a directory in the remote instance of the Solr server.



4. Configure the home directory of the remote Solr server to use the location ofthe unzipped configuration files (see documentation on the Apache Solr website).

5. Configure the Decision Center preferences.properties file to point to the URLof the Solr server.

Setting parameters for the Solr search engine:

Configure the search function in the Decision Center Business console to run withthe Apache Solr search engine.

Decision Center Business console provides a function for searching rule projects.When you install this feature, it uses an embedded instance of the Apache Solrsearch engine. Alternatively, you can have the search function run with a remoteinstance of the search engine, which you can install on another computer, or thesame computer but in a dedicated web application (see “Using a remote Solrsearch engine” on page 29).

There are three parameters to set for the search engine:

Table 6. Search parameters

Parameter Description

search.SearchProvider This parameter takes one of the followingvalues:

v SolrEmbedded: Use to select the embeddedSolr search engine.

v SolrRemote: Use to select a remoteinstance of the Solr search engine.

search.SolrEmbeddedDataDir Use this optional parameter to direct theindex of the embedded version(SolrEmbedded) to a specific directory on theDecision Center.

search.SolrRemoteUrl Use this parameter with SolrRemote toprovide the URL of the remote Solr searchengine.

You set the configuration parameters for the search engine within thepreferences.properties file for Decision Center. For more information on thepreferences.properties file, see Configuration parameter maintenance.

The following table provides examples for setting the parameters inpreferences.properties to work with the Solr search engine:

Table 7. Configuration table for search properties

Solr server Parameter settings

External server

(The URL of the external server depends on theinstallation. For this example, the remote address of thesearch engine is http://mysearchserver:8983/solr.)


search.SearchProvider=SolrRemotesearch.SolrRemoteUrl=http://mysearchserver:8983/solr

Embedded server(In this example, you store the index inthe c:/temp/DC-SearchIndex directory on yourcomputer.)


search.SearchProvider=SolrEmbeddedsearch.SolrEmbeddedDataDir=c:/temp/DC-SearchIndex



http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.bu.rules/topics/con_config_install_param.htm

If you do not specify a directory for search.SolrEmbeddedDataDir, Decision Centerstores the search index in a temporary directory. When the server stops running, italso stops using the temporary directory. When the server restarts, it creates a newtemporary directory, and completely reindexes the repository.

If you specify a directory for search.SolrEmbeddedDataDir, the directory and itscontent persist across server restarts, and the server does not reindex the repositorywith each restart.

Additional steps to configure Decision Validation ServicesOptionally, you can deploy, configure, and test Decision Validation Services tocomplement your Decision Center configuration on WebSphere Application Server.

Before you start:

Tasks that you must perform before configuring Decision Validation Services, and alist of steps that you should take to ensure a successful configuration.

Before following the instructions to deploy and configure Decision ValidationServices, you must install the following elements:1. Optionally, install Rule Designer.2. Install Rule Execution Server and Decision Center, and configure both of these

applications.

Note:

On WebSphere Application Server, Decision Validation Services uses the defaultWork manager wm/default to run simulations and tests in managed threads.Therefore, make sure that it is defined in the application server where youconfigure Decision Validation Services.

For more information on configuring a work manager using the WebSphereApplication Server Administration Console:v On WebSphere Application Server 7, see Configuring work managers.v On WebSphere Application Server 8, see Configuring work managers.


The following table summarizes the steps that you follow to configure DecisionValidation Services.

Note:

You can also perform the configuration by following the steps in Configuring RuleExecution Server on WebSphere Application Server for z/OS using wsadminscripts.


http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.base.doc/info/aes/asyncbns/tasks/tasb_workmanager.html

https://infocenter.ilogfr-bso.fr.ibm.com/infocenter/dmanager/v8r0/index.jsp?topic=%2Fcom.ibm.wodm.dcenter.config%2Fconfig_dc_websphere%2Ftpc_was_before_dvs_config.html




Step Required

“Step 1: Creating Decision Warehouse database resources”on page 32Tip:

If you have used the Rule Execution Server console to createdatabase resources (see Populating a database using theRule Execution Server console), you do not have to performthis task.

Optional


This archive is the default SSP archive packaged with theinstaller.

Optional. Do this step if youwant to check the availabilityof the feature. You can alsouse the default archive if youhave an XML XOM in whichcase the SSP archive does nothave to be repackaged.


Optional


Optional

“Step 5: Redeploying the Decision Validation Servicesarchive” on page 36

Step 1: Creating Decision Warehouse database resources:

You can use SQL scripts to create a dedicated schema in the database.



Note:



there, you can use the existing buffer pool or create a new buffer pool namedBP32K. Use the following command to query SYSCAT.BUFFERPOOLS for the existingbuffer pool:






Select * from SYSCAT.BUFFERPOOLS



Here is an example of the table space specification in the script:CREATE TABLESPACE RESDWTS PAGESIZE 32K MANAGED BY DatabaseUSING [ FILE ’C:\DB2\Container.file’ 640 ] BUFFERPOOL BP32K;


Note:







H2 H2 console










Step 2: Deploying the Decision Validation Services archive:

How to deploy the Decision Validation Services archive.


About this task

This step shows you how to deploy the Decision Validation Services archive. Thearchive must be deployed on the same server as the XU. You can use thisprocedure to deploy the default SSP archive packaged with the installer or anysubsequent deployment of a repackaged archive. Deploy the default SSP EAR ifyou want to check the availability of the feature. You can also deploy the defaultSSP EAR and use this to test your rules if you have an XML XOM. An XML XOMis included in the ruleset archive inside a RuleApp, and therefore the SSP EARdoes not have to be repackaged to include the XOM.

If you are installing Decision Validation Services on z/OS, you can usecustomizable installation scripts to perform this task. For more information, refer toConfiguring Rule Execution Server on WebSphere Application Server for z/OSusing wsadmin scripts.

Procedure

To deploy an SSP archive:1. Open the Integrated Solutions Console.2. In the side panel, open Applications and click Websphere Enterprise

Applications

3. In the side panel, click Install.4. In the side panel, select Local file system, Browse to the following file, and

then click Next.<InstallDir>/executionserver/applicationservers/WebSphere8/jrules-ssp-WAS8.ear

5. Select the check box Detailed - Show all installation options and parameters.Expand Choose to generate default bindings and mappings and select thecheck box Generate Default Bindings. 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. Select the resAdministrators group. To do this, click the group name underAvailable, 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.14. Click Finish. 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-WAS7.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).19. Click OK.20. Click OK and Save directly to the master configuration.




21. In the side panel, open Applications > Application Types > WebSphereenterprise applications.

22. In the Enterprise Applications page select the check box next tojrules-ssp-WAS8 and click Start to start the application.

Step 3: Checking the availability of Decision Validation Services:

A specific testing URL is designed for you to check the rule session type, DAOfactory class for trace persistence, the class used to cache the Decision ValidationServices job, and the pool size for asynchronous execution.



Version


Patch level


License information


RuleSession


DAO Factory Class


Job store class


Job pool size


Started since






been tested compared to the total number of scenarios.v The Start time records the time when a resource is allocated for the job.


v The Parts column records the number of parts in the job:– A job that is not executed in parallel has one part.– A job that is executed in parallel has one or more parts.



Step 4: Packaging Decision Validation Services using Ant:

You can configure Decision Validation Services archives by using an Ant task.

About this task



Procedure








What to do next


Step 5: Redeploying the Decision Validation Services archive:

How to redeploy the Decision Validation Services archive.

About this task

This step shows you how to redeploy the Decision Validation Services archive. Thearchive must be redeployed on the same server as the XU. You can use this


procedure to redeploy the default SSP archive packaged with the installer or anysubsequent deployment of a repackaged archive. Redeploy the default SSP EAR ifyou want to check the availability of the feature. You can also redeploy the defaultSSP EAR and use this to test your rules if you have an XML XOM. An XML XOMis included in the ruleset archive inside a RuleApp, and therefore the SSP EARdoes not have to be repackaged to include the XOM.

Procedure

To redeploy an SSP archive (an archive has already been deployed):1. Open the Integrated Solutions Console.2. In the side pane, open Applications and click Websphere Enterprise

Applications.3. Select the deployed SSP application in the side pane and click Uninstall.4. Click OK to confirm uninstallation of the SSP application.5. Click Save to save the changes directly to the master configuration.6. Follow the previous procedure in “Step 2: Deploying the Decision Validation

Services archive” on page 33 to deploy the new SSP.

Configuring the Decision Center consoles using profiletemplates

You can create new profiles for the Decision Center consoles and configure aWebSphere Application Server cluster for high availability and scalability.

To create a new stand-alone server to host Decision Center, you must first createa new profile. You can create a profile using the Profile Management Tool or themanageprofiles command.

Decision Center profile templatesWhen you install Decision Center, the installer copies files for cluster configurationto the directory for shared profiles and to the WebSphere Application Serverdirectory for profile templates.

The following table lists what files are copied to each directory.<WODM_InstallDir> is the directory where you installed Decision Center and<WAS_InstallDir> is the directory where you installed WebSphere ApplicationServer. If you specify <WAS_InstallDir> when you install Decision Center, theprofile templates are copied to that directory as shown in the table.

Important: If you do not install the product Samples and Tutorials, you mustmanually copy the folders from <WODM_InstallDir> to <WAS_InstallDir>.

Table 8. Installation of profile template files and directories

Target directory When Copied files

WODM_InstallDir/teamserver/applicationservers/WebSphere8

At productinstallation

The Decision Center profile template toaugment a deployment manager profile andthe EAR files.

WODM_InstallDir/shared/profiles/profileTemplates/rules

At productinstallation

The Decision Center profile template toaugment a deployment manager profile.


Table 8. Installation of profile template files and directories (continued)

Target directory When Copied files

WODM_InstallDir/shared/profiles/profileTemplates/rules

At profileaugmentation

The management/dc subdirectory thatcontains the scripts to augment adeployment manager profile.

WAS_InstallDir/profileTemplates/rules

At profileaugmentation

If you have specified <WAS_InstallDir>, theinstaller also copies to this directory themanagement/dc subdirectory that contains thescripts to augment a deployment managerprofile.

Configuring Decision Center on a new profileTo create a new stand-alone instance of Decision Center, you must first create aDecision Center profile. You can create a profile using the Profile ManagementTool, or using the manageprofiles command.

Before you begin

During profile creation, you are asked to select the database manager that hosts thetables for the execution server run time. Unless you are using Apache Derby, createthis database before you configure a new profile. See Creating a data source andconnection pool.

About this task

Depending of your operating system, you can either use the Profile ManagementTool or the manageprofiles command create a new profile:v On a 32-bit operating system, you can use the Profile Management Tool. The

Profile Management Tool is not supported on an HP-UX operating system, onany 64-bit operating system, or on z/OS.

v On a 32-bit operating system or any other operating system, you can use themanageprofiles command.

The following procedure describes how to use the manageprofiles command toconfigure Decision Center on a new profile.

Procedure1. Open a command prompt (Windows) or a terminal emulator (Linux and UNIX

environments) and navigate to the <WAS_InstallDir>/bin directory.2. Run the manageprofiles command by using manageprofiles.bat for Windows

or manageprofiles.sh for Linux and UNIX environments. You must provide thefollowing parameters:

-createTo create the new profile.

-templatePath <template_path>where <template_path> is the location of the profile template. Provide thepath to <WAS_InstallDir>/profileTemplates/rules/default/dc.

Use the following optional parameters:

-dsHome installation locationwhere installation location is the fully-qualified path of the Decision Centerinstallation directory <InstallDir>. You must specify this parameter if youhave installed Decision Center in a non-default location.


-profileName profile_namewhere profile_name is the name of the profile.

-cellName cell_namewhere cell_name is the name of the cell.

-nodeName node_namewhere node_name is the name of the node.

-hostName host_namewhere host_name is the host name of the computer hosting the profile.

-serverName server_namewhere server_name is the server name.

-enableAdminSecurity true|falsewhere true switches on WebSphere Application Server administrativesecurity. If you provide this parameter, you must also provide-adminUserName and -adminPassword. The default is false if you do notspecify this parameter, and security will not be active. You must alsoprovide -adminUserName and -adminPassword.

-adminUserName usernamewhere username is the user ID to access WebSphere Application Server.Only required if enableAdminSecurity is enabled.

-adminPassword passwordwhere password is the password for the user ID to access WebSphereApplication Server. Only required if enableAdminSecurity is enabled.

-dbType database_typewhere database_type specifies the database product. Valid values are:v Derby_Embedded: the default valuev DB2_Universal

v Derby_NetworkServer

v Oracle

v MS_SQL_Server

-dbName database_namewhere database_name is the name of the database. Required unless -dbTypeis Derby_Embedded.

-dbUserId database_user_namewhere database_user_name is the user ID to access the database server.Required unless -dbType is Derby_Embedded.

-dbPassword passwordwhere password is the password for the user ID to access the databaseserver. Required unless -dbType is Derby_Embedded.

-dbJDBCClasspath database_jdbc_classpathwhere database_jdbc_classpath specifies the path to the JDBC class path files.Required unless -dbType is Derby_Embedded.

-dbJDBCLicenseClasspath database_jdbc_license_classpathwhere database_jdbc_license_classpath specifies the path to the JDBC classpath files. Only required if -dbType is DB2_Universal.

-dbHostName host_namewhere host_name is the host name for the database server. Required unless-dbType is Derby_Embedded.


-dbServerPort port_numberwhere port_number is the port of the TCP/IP service, or the port on whichthe database is listening. Required unless -dbType is Derby_Embedded.

Results

After running the manageprofiles command, the profile is created.

Examples

The following examples show how to configure Decision Center with the defaultmessaging provider on Windows and Linux.

The first example creates a new application server profile on Windows usingembedded Apache Derby as the database provider and WebSphere ApplicationServer default messaging as the messaging provider.manageprofiles.bat -create -templatePath "C:\Program Files\IBM\WODM80\WODM\WAS\profileTemplates\rules\default\dc" -dcHome "C:\Program Files\IBM\WODM

The second example creates a new application server profile on Linux and UNIXenvironments using embedded Apache Derby as the database provider andWebSphere Application Server default messaging as the messaging provider.manageprofiles.sh -create -templatePath"/opt/ibm/WODM80/WODM/WAS/profileTemplates/rules/default/dc" -dcHome "/opt/ibm/WODM80/WODM"

Augmenting an existing profile with Decision CenterTo create a new instance of Decision Center on an existing WebSphere ApplicationServer, you can augment the profile using the manageprofiles command.

Before you begin

Before you augment an existing WebSphere Application Server application serverprofile, ensure that all application servers in the profile are stopped.

During profile creation; you are asked to select the database manager, which hoststhe tables for the event runtime. If you are not using Apache Derby; create thedatabase before you create a new profile. See Creating a data source andconnection pool.

About this task

You can use the manageprofiles command or the Profile Management Tool toaugment an existing profile:v The manageprofiles command is supported on all operating systems.v The Profile Management Tool is only supported on 32-bit operating systems. The

Profile Management Tool is not supported on an HP-UX operating system, onany 64-bit operating system, or on z/OS.

The procedure describes how to use the manageprofiles command to augmentDecision Center on an existing profile.

Procedure1. Open a command prompt (Windows) or a terminal emulator (Linux and UNIX

environments) and navigate to the <WAS_InstallDir>/bin directory.


2. Run the manageprofiles command, using manageprofiles.bat for Windows ormanageprofiles.sh for Linux and UNIX environments. Provide the followingparameters:

-augmentTo augment the existing profile.

-unaugmentTo undo the augmentation of the profile.

-templatePath <template_path>where <template_path> is the location of the profile template. Provide thefollowing value for the application server profile: <WAS_InstallDir>/profileTemplates/rules/default/dc.

-profileName profile_namewhere profile_name is the name of the existing application server profile thatyou are augmenting.

Optionally, you can specify the following parameters:

-dsHome installation locationwhere installation location is the fully-qualified path that is the installationlocation for Decision Center. You must specify this parameter if you haveinstalled Decision Center in a location different to the default.

-profileName profile_namewhere profile_name is the name of the profile.

-cellName cell_namewhere cell_name is the name of the cell.

-nodeName node_namewhere node_name is the name of the node.

-hostName host_namewhere host_name is the host name of the computer hosting the profile.

-serverName server_namewhere server_name is the server name.

-enableAdminSecurity true|falsewhere true switches on WebSphere Application Server administrativesecurity. If you provide this parameter, you must also provide-adminUserName and -adminPassword. The default is false if you do notspecify this parameter.

-adminUserName usernamewhere username is the user ID to access WebSphere Application Server.Only required if enableAdminSecurity is enabled.

-adminPassword passwordwhere password is the password for the user ID to access WebSphereApplication Server. Only required if enableAdminSecurity is enabled.

-dbType database_typewhere database_type specifies the database product. Valid values are:v Derby_Embedded: the default valuev DB2_Universal

v Derby_NetworkServer

v Oracle

v MS_SQL_Server


-dbName database_namewhere database_name is the name of the database. Required unless -dbTypeis Derby_Embedded.

-dbUserId database_user_namewhere database_user_name is the user ID to access the database server.Required unless -dbType is Derby_Embedded.

-dbPassword passwordwhere password is the password for the user ID to access the databaseserver. Required unless -dbType is Derby_Embedded.

-dbJDBCClasspath database_jdbc_classpathwhere database_jdbc_classpath specifies the path to the JDBC class path files.Required unless -dbType is Derby_Embedded.

-dbJDBCLicenseClasspath database_jdbc_license_classpathwhere database_jdbc_license_classpath specifies the path to the JDBC classpath files. Only required if -dbType is DB2_Universal.

-dbHostName host_namewhere host_name is the host name for the database server. Required unless-dbType is Derby_Embedded.

-dbServerPort port_numberwhere port_number is the port of the TCP/IP service, or the port on whichthe database is listening. Required unless -dbType is Derby_Embedded.

Results

After running the manageprofiles command, the profile is now augmented.

Examples

The following examples show how to configure Rule Execution Server with thedefault messaging provider on Windows and Linux.

The first example augments an existing application server profile called AppSrv01on Windows using embedded Apache Derby as the database provider.manageprofiles.bat -augment-templatePath "C:\Program Files\IBM\WODM80\WODM\WAS\profileTemplates\rules\default\dc" -dcHome"C:\Program Files\IBM\WODM80\WODM" -profileName AppSrv01

The second example augments an existing application server profile calledAppSrv01 on Linux and UNIX environments using embedded Apache Derby asthe database provider.manageprofiles.sh -augment-templatePath "/opt/ibm/WODM80/WODM/WAS/profileTemplates/rules/default/dc" -dcHome/opt/ibm/WODM80/WODM -profileName AppSrv01

The following examples show how to unaugment Decision Center from an existingprofile.

The first example unaugments an existing Decision Center application serverprofile called WODMSrv01 on Windows.manageprofiles.bat -unaugment -templatePath"C:\Program Files\IBM\WODM80\WODM\WAS\profileTemplates\rules\default\dc"-profileName WODMSrv01


The second example unaugments an existing Decision Center application serverprofile called WODMSrv01 on Linux and UNIX.manageprofiles.sh -unaugment -templatePath"/opt/ibm/WODM80/WODM/WAS/profileTemplates/rules/default/dc"-profileName WODMSrv01

Configuring the Decision Center consoles for high availabilityand scalabilityTo achieve high availability and scalability, you can configure your applicationservers in clusters. An application server cluster provides workload management(WLM) and failover for the applications that are deployed on the cluster.

Decision Center provides “managed” templates for you to create and augment aWebSphere Application Server cluster.

You can either augment the default deployment manager profile or create a newdesignated profile. You then run the .bat or .sh with the parameters that arenecessary to configure the cluster. If the cluster name does not exist in the targetnode, the script creates it, so that you can configure clusters for any topology.

Augmenting a deployment manager profile with Decision Center:

For high availability and scalability of your applications, you can configureDecision Center on a WebSphere Application Server cluster by running aconfiguration script. You must first augment a management profile.

Before you begin

Before you start the script to augment the profile, you must install Decision Center,create a default deployment manager profile, and make sure that a node exists:1. Install Decision Center, which includes WebSphere Application Server and its

profile templates.2. Create a default deployment manager profile by running the Profile

Management Tool, unless one exists already. For more information, see theWebSphere Application Server Information Center. This step creates a newdirectory, for example profiles/Dmgr01/bin.

3. Create a node. A target node is mandatory. The node receives the baseconfiguration. The node must be started and visible by the deploymentmanager. You can create a default node on another computer, use an existingnode, or use the -createNode option to create the target node on the computerwhere the configuration is run.

About this task

You augment the deployment manager profile so that you can create additionalnodes using the provided template.

Procedure

Launch the manageprofiles file with the -augment options.v On Windows: <WAS_InstallDir>\bin\manageprofiles.bat -augment

-profileName Dmgr01 -templatePath <WAS_InstallDir>\profileTemplates\rules\management\dc


http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.cgwas.doc%2Finfo%2Fae%2Fae%2Ftgrid_pro_instances.html

v In UNIX environments: <WAS_InstallDir>/bin/manageprofiles.sh -augment-profileName Dmgr01 -templatePath <WAS_InstallDir>/profileTemplates/rules/management/dc

wherev <WAS_InstallDir> is the directory where you installed WebSphere Application

Server.v Dmgr01 is the name of the profile deployment manager that you created as a

prerequisite.

Results

The manageprofiles[.bat|.sh] command has the following effects:1. It creates the users rtsAdmin, rtsUser1, and rtsConfig.2. It copies the configureDCCluster.bat script for Windows or

configureDCCluster.sh script for UNIX platforms to the deployment managertarget directory, for example profiles/Dmgr01/bin.

Running the configureDCCluster script to create a cluster:

After you have augmented the default management profile, you can run the scriptthat configures Decision Center on a WebSphere Application Server cluster.

Before you begin

Before you start the script to augment the profile, you must set the WODM_HOMEenvironment variable. The configuration script that you run in step 2 on page 80uses that variable.

About this task

After you have augmented the management profile, you set the clusterconfiguration properties, and run the configuration script.

Note: You cannot use the configuration script to initialize the cluster nor to add anode to an existing cluster.

Procedure

1. Edit the configureDCCluster.properties file to set the cluster name anddatabase values.You can find this file in the dmgr/bin/rules/ directory. The configurationproperties must contain values for the following keys:

wodm.dcrules.clusterNameThe value can be the name of an existing cluster. If no cluster exists already,a cluster is created. For example:DecisionCluster

wodm.dcrules.db.typeThe database type: DB2, Oracle, or MSSQL

wodm.dcrules.db.jdbcDriverPathThe path to the JDBC drivers. Separate the driver names with a colon (;).For example: D:/software/IBM/WODM80/drivers/db2jcc.jar;D:/software/IBM/WODM80/drivers/db2jcc_license_cu.jar;

wodm.dcrules.db.nameThe name of the database. For example: MyDB


wodm.dcrules.db.hostnameThe name of the host where the database is hosted: For example:MyDB_server

wodm.dcrules.db.portThe port number to establish the connection to the database

wodm.dcrules.db.userThe user name to connect to the database. For example: db_user1

wodm.dcrules.db.passwordThe password for the user to connect to the database. For example:db_user1_pwd

2. Navigate to the <profile_name>/bin directory and start the configureDCClusterscript with the required parameters.The general command line syntax is: configureDCCluster[.sh|.bat]-ParameterName1 parameterValue1 -ParameterName2 parameterValue2 ... . Ifyou make a mistake, such as a missing parameter or a wrong node name, youcan execute the script again.v On Windows:

WAS_Installdir\profiles\Dmgr01\bin\configureDCCluster.bat -dmgrAdminUsername websphere -dmgrAdminPassword websphere -clusterPropertiesFile WAS_Ins

v On UNIX:WAS_Installdir/profiles/Dmgr01/bin/configureDCCluster.sh -dmgrAdminUsername websphere -dmgrAdminPassword websphere -clusterPropertiesFile WAS_Inst

Table 9. Cluster configuration parameters

Parametername Required Description

-dmgrAdminUsernameMandatory The WebSphere Application Server administrator’s useridentifier that you defined when you installed DecisionCenter

-dmgrAdminPasswordMandatory The WebSphere Application Server administrator’spassword that you defined when you installed DecisionCenter.

-clusterPropertiesFileMandatory The full path to the properties file.

-uninstall Optional Removes all the applications and resources from thecluster. The cluster itself is not removed because itmight contain other applications. See “UninstallingDecision Center from a cluster” on page 82.

-createNode Optional If you specify this parameter, the script creates adefault node profile with the name set in the-targetNodeName parameter.

-targetNodeNameOptional By default, the name of the target installation node isset to RulesNode01.

-dmgrHostNameOptional Use this parameter to specify the name of the host onwhich the deployment manager is located. Thisparameter is mandatory if you create the target nodeby setting the -targetNodeName parameter.

-dmgrPort Optional The SOAP TCP port of the deployment manager. Bydefault, 8879.

Results

The script performs the following actions:v Installs the JDBC provider and the data source at node level.


v Installs the Decision Center application at the cluster level. Users are mapped toapplication groups when an application is deployed.

v Starts the deployment manager server if it is not already started.v Configures security.v Creates the rtsAdmin, rtsInstaller, rtsUser1, and rtsConfig users.v Configures users and groups.v Maps users and groups to roles.v Starts the cluster, servers, and applications.

When the script completes, the cluster is up and running. The user should thenconfigure the load balancing system, such as IBM HTTP Server (IHS).

Note: Depending on your hardware configuration, and because the DecisionCenter EAR file is very large, you might need to connect to the Decision Centeradministration console to verify whether the cluster is correctly started and, if it isnot, start it manually.

Unaugmenting Decision Center from an existing cluster:

You can unaugment Decision Center from existing profiles without deleting thecluster.

About this task

Use the manageprofiles command to unaugment Decision Centerfrom existingprofiles in a cluster.

Procedure

Launch the manageprofiles file with the following -unaugment options:v On Windows: <WAS_InstallDir>\bin\manageprofiles.bat -unaugment

-profileName Dmgr01 -templatePath <WAS_InstallDir>/profileTemplates\rules\management\dc -nodeName DecisionNode -cellName DecisionCell-targetNodeName DecisionCenterNode01

v In UNIX environments: <WAS_InstallDir>/bin/manageprofiles.sh -unaugment-profileName Dmgr01 -templatePath <WAS_InstallDir>/profileTemplates/rules/management/dc -nodeName DecisionNode -cellName DecisionCell-targetNodeName DecisionCenterNode01

wherev <WAS_InstallDir> is the directory where you installed WebSphere Application

Server.v Dmgr01 is the name of the profile deployment manager that you created as a

prerequisite to configuring the cluster.v dc is the abbreviation of Decision Center.v -nodeName and -cellName are the names of the node and cell that you defined

when you created the deployment manager profile.v -targetNodeName is the name of the node to which you installed Decision Center.


Results

The command removes the rtsAdmin, rtsInstaller, rtsUser1, and rtsConfig users.The cluster is kept as is to prevent any risk of deleting previously existingconfigurations.

Uninstalling Decision Center from a cluster:

You can uninstall Decision Center from an existing cluster.

About this task

To uninstall Decision Center from a cluster, you use the same configuration scriptthat you use to configure the cluster.

Procedure

1. Navigate to the <profile_name>/bin directory.2. Launch the configureDCCluster[.sh|.bat] script with the -uninstall

argument.The general command line is:configureDCCluster[.sh|.bat] -dmgrAdminUsername username -dmgrAdminPassword password -clusterPropertiesFile filePath -uninstall

v On Windows:<WAS_InstallDir\profiles\Dmgr01\bin\configureDCCluster.bat -dmgrAdminUsername websphere -dmgrAdminPassword websphere -clusterPropertiesFile <WAS_I

v On UNIX:<WAS_InstallDir/profiles/Dmgr01/bin/configureDCCluster.sh -dmgrAdminUsername websphere -dmgrAdminPassword websphere -clusterPropertiesFile <WAS_In

Table 10. Cluster configuration parameters

Parametername

Mandatory/Optional Description

-dmgrAdminUsernameMandatory The WebSphere Application Server administrator’s useridentifier that you defined when you installed DecisionCenter

-dmgrAdminPasswordMandatory The WebSphere Application Server administrator’spassword that you defined when you installed DecisionCenter.

-clusterPropertiesFileMandatory The full path to the properties file.

-uninstall Mandatory Removes all the applications and resources from thecluster. The cluster itself is not removed because itmight contain other applications.

-createNode Optional If you specify this parameter, the script creates adefault node profile with the name set in the-targetNodeName parameter.

-targetNodeNameOptional By default, the name of the target installation node isset to RulesNode01.

-dmgrHostNameOptional Use this parameter to specify the name of the host onwhich the deployment manager is located. Thisparameter is mandatory if you create the target nodeby setting the -targetNodeName parameter.

-dmgrPort Optional The SOAP TCP port of the deployment manager. Bydefault, 8879.


Results

This command has the following results:v Uninstalls the clusterized application (teamserver).v Uninstalls the data source.v Removes application users and groups.

Configuring the Decision widget for Business SpaceBusiness Space is the browser-based graphical user interface powered byWebSphere Application Server. It lets business users interact with content providedby Decision Center and other WebSphere products. Decision Center supplies aDecision widget for developing business logic.

Configuring the Decision widget using a wsadmin scriptYou can run a wsadmin command to deploy and configure the Decision widget onWebSphere Application Server. After the wsadmin script runs successfully, you canadd the Decision widget to your Business Space.

Before you begin

Before you deploy and configure the Decision widget, you must install BusinessSpace. For more information, see Configuring Business Space, installing eventwidgets, and using Business Space.

About this task

You can run a wsadmin command to complete the configuration of the Decisionwidget. After the configuration command runs successfully, you can add theDecision widget to your Business Space.

Procedure

To invoke the wsadmin script for the Decision widget:1. Navigate to the profile/bin subdirectory in the directory where WebSphere

Application Server is installed. For example: <WAS_InstallDir>/<MyServer>/profiles/<Profile1>/bin.You must run the wsadmin tool from this directory.

2. From the command line, invoke the wsadmin script to configure the Decisionwidget. The following example shows the deployment of the Decision widgetto a server named server1 on a node named MyServerNode01:wsadmin -lang jython -f <InstallDir>/decisionWidget/installWidget.pyMyServerNode01 server1 <InstallDir>/decisionWidget/teamserverWidget.zip

Specify the absolute directory path to the location where the Decision widgetinstallWidget.py file and the teamserverWidget.zip file are installed.Specify the name of the node on which you want to deploy the widget. Youcan determine the node name from the application servers table in theWebSphere Application Server Network Deployment administrative console.Log in to the console, then click Servers > Server Types > WebSphereApplication servers. The node name is listed next to the server name.

3. After running the wsadmin script, you must start the application from theWebSphere Application Server Network Deployment administrative console.a.

Log in to the administrative console.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.config/topics/integrating-bs.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.config/topics/integrating-bs.htm

b.

Click Applications > Application types > WebSphere enterpriseapplications.

c.

Locate and select the teamserver4bs_<node>_<server> application.d.

Click Start.

Results

The following message is displayed at the top of the administrative console whenthe application starts successfully:

The teamserver4bs_SamplesNode_SamplesServer application has already beenstarted.

Start Business Space and add the Decision widget to an existing space, or to a newspace. For more information, see Accessing Business Space.

Decision Center for Business Space is the same application as the web version ofDecision Center. However, some features provided in the web version are notavailable in the Decision widget. For more information, see Business Spacelimitations.

Enabling single sign-on for the Decision widgetYou can activate single sign-on in the Decision widget, if you already have theDecision Center console configured on the same server. After single sign-on isactivated you no longer have to sign-on in both applications.

About this task

If the Decision Center console and business space are deployed on the same server,you can activate single sign-on for the Decision widget. When single sign-on isactivated, login is automatic and you are not required to enter a login andpassword to use the widget.

Procedure

To enable single sign-on:1. Using a text editor, modify the following XML file in the widget definition file:

<InstallDir>/decisionWidget/teamserverWidget.zip/ear/teamserver4bs.ear/teamserver4bs.war/teamserver.xml.

2. Set the sso attribute to true.3. Set the value of the rtsUrl attribute to a Decision Center URL.4. Save the changes, then restart Business Space.

Configuring the Decision Center Enterprise console on Tomcat 7.0To be able to use the Decision Center Enterprise console on a new instance ofTomcat, you must deploy the provided archives for this server, and perform anumber of configuration tasks.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.config/topics/bs_accessingbusinessspace.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.bu.events/introducing/con_intro_limitations.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.bu.events/introducing/con_intro_limitations.htm

Before you startReview the tasks that you must perform to complete the installation.

Before you start, do the following:1.

Delete any teamserver installations in the /temp and /webapps directories under<TOMCAT_HOME>. This ensures that the installation recompiles the JavaServerPages.

2.

Set TOMCAT_HOME as an environment variable.

After you have prepared your environment, refer to “What steps to follow” for thetasks that you must complete to configure the Decision Center console for yourapplication server.

With your application server configured, you might need to proceed to “Additionalsteps to configure Decision Validation Services” on page 105 to configure DecisionValidation Services.

After finishing the installation, you can use Decision Center (see “Opening theDecision Center Enterprise console” on page 167). There is no rule project the firsttime you open the console. You must publish a project from Rule Designer (see“Publishing a project” on page 165).

Note:

v If you have rule projects created with a previous product version, refer to theMigrating topics on how to upgrade the Rule Team Server database schema.

v You must set an environment variable named JRE_HOME to the directory in whichyou installed the JRE. Alternatively, you can use the JDK instead of the JRE. Inthis case, you must set an environment variable named JAVA_HOME to thedirectory in which you installed the JDK.


The following table lists the steps for installing Decision Center on Tomcat 7.0.

Step Mandatory/optional

“Step 1: Enforcing database user permissions” on page 86

“Step 2: Creating a data source and connection pool” onpage 87


“Groups and permissions”on page 88


Optional

“Step 4: Deploying the Decision Center WAR” on page 91


Recommended



Step Mandatory/optional

“Step 6: Completing DecisionCenter configuration” onpage 92

“Completing theconfiguration from theDecision Center Enterpriseconsole” on page 92

Use one of the two methodsto complete the installation.“Completing the

configuration using Anttasks” on page 97



Note:




Databasepermission

Operation





CREATE ANYINDEX


DROP ANYINDEX


CREATE ANYROLE


CREATE ANYSEQUENCE


DROP ANYSEQUENCE


SELECT ANYSEQUENCE


ALTER ANYTABLE


CREATE ANYTABLE



Databasepermission

Operation





DROP ANYTABLE


INSERT ANYTABLE


SELECT ANYTABLE


UPDATE ANYTABLE


CREATE ANYVIEW


DROP ANYVIEW


Step 2: Creating a data source and connection poolYou declare a data source to store the data used by the Decision Center console.

Before you begin

You must have a database to create a data source. For a list of supporteddatabases, see the "System requirements" section in the Readme file for a link to thehardware and software requirements of the product.

About this task

To create a data source and a connection pool for Decision Center on Tomcat, youcopy the driver for your database to the Tomcat directory, and then you declare thedatabase and link it to the Decision Center management archive.

Procedure1. Copy your database driver JAR file to the <TOMCAT_HOME>/lib directory. For

example, the Derby database drivers are derby.jar and derby-plugin.jar. (Thefile derby.jar is provided with the product.)

2. Open the <TOMCAT_HOME>/conf/server.xml file.3. In the file, declare the database and link it to teamserver.war by adding the

following code just before the </Host> tag that closes the localhost definition:<Context docBase="teamserver.war" path="/teamserver" reloadable="true">

<Resource name="jdbc/ilogDataSource" auth="Container"type="javax.sql.DataSource"username="##dbUser##" password="##dbPassword##"driverClassName="##driverClassName##"url="##URL##" />

</Context>

4. Complete the common properties for local transaction data sources:

username and password


The tags username="##dbUser##" and password="##dbPassword##" areused to create the database the first time you run the system. Replace##dbUser## and ##dbPassword##, placing your user name and passwordbetween the quotation marks. After the database is created, you mustuse your user name and password.

driverClassName

The class that is used to handle the connections to the database. Forexample:

driverClassName="org.apache.derby.jdbc.EmbeddedDriver"

URL

This provides the JDBC connection URL. For example:

url="jdbc:derby:server://localhost:<PORT>/RTSB"

In this case, server://localhost:<PORT>/RTSB is the location of thedatabase folder RTSB.

You can also create the database when declaring it. For example:

url="jdbc:derby:c:/derbydata;create=true"

In this example, you create a database named derbydata on the local C:drive the first time you open the Decision Center console on Tomcat.

5. Save the file.

Step 3: Configuring securityTo configure security for Decision Center on the Tomcat application server, youcreate user groups and define permissions for them. You can also create customgroups, provided that you declare them in the list of Tomcat users and uploadthem to the database.

Groups and permissionsYou define user names, passwords, and groups.

Every user of Decision Center must belong to at least one of the mandatorygroups: rtsAdministrator, rtsConfigManager, rtsInstaller, and rtsUser. Thesegroups determine which parts of Decision Center a user can access.

You must create these groups for Tomcat. For testing purposes, use the suggestedconfiguration below to create a default user name and password for each group.

The following table shows the available groups and descriptions.

Table 11. Decision Center permission groups

Group Use

rtsAdministrator Mandatory, gives the user access as anadministrator.

rtsInstaller Mandatory, gives the user access to theInstallation Settings wizard.

rtsConfigManager Mandatory, gives the user configurationmanager access.

rtsUser Mandatory, gives the user standard access.


Table 11. Decision Center permission groups (continued)

Group Use

Eligibility Optional custom group, used in the DecisionCenter permissions tutorial: Tutorial:Implementing permissions

Validator Optional custom group, used in the DecisionCenter permissions tutorial: Tutorial:Implementing permissions

Suggested configuration

The following table shows the permission groups, and gives an example of thedefault user name and password that you can assign to each group.

Table 12. An example of user name and password for each permission group

Group Default user/password

rtsAdministrator, rtsConfigManager, rtsUserrtsAdmin/rtsAdmin

rtsInstall/rtsInstall

rtsConfigManager, rtsUser rtsConfig/rtsConfig

rtsUser rtsUser1/rtsUser1

Eligibility Eli/Eli

Validator Val/Val

Follow these steps to implement a suggested configuration with a default user foreach of the basic groups.1. Open the <TOMCAT_HOME>/conf/tomcat-users.xml file.2. In the file, add the following code for roles and users to just before the closing

tag </tomcat-users>:<role rolename="rtsConfigManager"/><role rolename="rtsUser"/><role rolename="rtsAdministrator"/><role rolename="rtsInstaller"/><role rolename="Eligibility"/><role rolename="Validator"/><user username="rtsUser1" password="rtsUser1" roles="rtsUser"/><user username="rtsAdmin" password="rtsAdmin" roles="rtsUser,rtsInstaller,rtsAdministrator"/><user username="rtsConfig" password="rtsConfig" roles="rtsUser,rtsConfigManager"/><user username="rtsInstall" password="rtsInstall" roles="rtsUser,rtsInstaller"/><user username="Eli" password="Eli" roles="Eligibility,rtsUser"/><user username="Val" password="Val" roles="Validator,Eligibility,rtsUser"/>

3. Save the file.

You must create the custom groups Validator and Eligibility to follow theDecision Center Tutorial: Implementing permissions. This is explained further in“Declaring custom groups.”

Declaring custom groupsWhen you create custom groups, you must declare them by adding them to the filethat lists Tomcat users.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dcenter.bu.events/tutorials/tut_ev_permissions.htm





About this task

The Decision Center WAR references the basic groups rtsUser, rtsConfigManager,rtsAdministrator, and rtsInstaller.

To use custom groups with the Decision Center permissions mechanism, you mustdeclare them as follows:1.

Add them to the <TOMCAT_HOME>/conf/tomcat-users.xml file.2.

Upload them to the database from the Installation Settings wizard.

Table 13. An example of custom permission groups, roles, and credentials

Group UseDefaultuser/password Roles

Validator Optional customgroup, used in theDecision Centerpermissions tutorial:Tutorial:Implementingpermissions

Val/Val Validator, Eligibility,rtsUser

Eligibility Optional customgroup, used in theDecision Centerpermissions tutorial:Tutorial:Implementingpermissions

Eli/Eli Eligibility, rtsUser

The following procedure shows you how to create and declare the Validator andEligibility custom groups for the Decision Center Tutorial: Implementingpermissions.

Procedure1. Open the <TOMCAT_HOME>/conf/tomcat-users.xml file.2. In the file, add the custom groups just before the closing tag </tomcat-users>.

For example:<role rolename="Eligibility"/><role rolename="Validator"/><user username="Eli" password="Eli" roles="Eligibility,rtsUser"/><user username="Val" password="Val" roles="Eligibility,Validator,rtsUser"/>

3. Save the file.4. Upload the custom groups to the database from the Installation Settings wizard

of the Decision Center console.










Related information:“Completing the configuration from the Decision Center Enterprise console” onpage 15You can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.

Step 4: Deploying the Decision Center WARYou copy the Decision Center management archive to the web applicationdeployment directory of Tomcat.

About this task

To use the Decision Center console on Tomcat, you must copy the managementWAR file to a deployment folder.

Procedure

Copy the file <InstallDir>/teamserver/applicationservers/tomcat7/teamserver.war to the <TOMCAT_HOME>/webapps directory.

Important: The process of deploying the Decision Center management WAR filesets the persistence locale. After you have saved a rule to the database, you mustnot change the persistence locale. If you want to install Decision Center in alanguage other than English, see “Step 4: Set the persistence locale” on page 18.

What to do next

You can now verify the deployment of the Decision Center console.

Step 5: Verifying the deployment of the Decision CenterEnterprise console

After you have finished configuring Decision Center for your application server,verify that you have deployed the archive successfully.

About this task


Procedure





Step 6: Completing Decision Center configurationAfter you have set database user permissions, created a data source, and deployedthe Decision Center WAR file, you complete the configuration either from theDecision Center console or by running Ant tasks.

Completing the configuration from the Decision CenterEnterprise consoleYou can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.






Note:




Action Description



Set up messagefiles











Note:




About this task


.brdx.


Procedure




then click Next.

What to do next




For example:



status=StatuseffectiveDate=Effective DateexpirationDate=Expiration Datenew=Newdefined=Defined













To set up groups:



Parameter Used to








Note:











Completing the configuration using Ant tasksAnt tasks provide an alternative method for completing or modifying theconfiguration. These tasks perform the same configuration steps as the InstallationSettings wizard in the Decision Center console.


To run Decision Center Ant tasks, you must first set up the required environmentvariables.

To run Ant tasks, you must have version 1.7.1 (or later) of Ant set up on yoursystem. If Ant is not installed or your version is older than version 1.7.1, you mustset up your environment to use the correct version of Ant. You can download Antfrom the Apache web site, or you can use the Ant 1.7.1 distribution packaged at<WODM_InstallDir>/shared/tools/ant, where <WODM_InstallDir> is yourWebSphere Operational Decision Management installation directory.

To test your current version of Ant:

v

Type the following command in a Windows Command Prompt or UNIX shell:ant -version

To set up your environment to use Ant:

1. Set the ANT_HOME environment variable to <WODM_InstallDir>/shared/tools/ant.

2. Set the JAVA_HOME environment variable to the path to your JDK installation(1.6).

3. Add the directory <WODM_InstallDir>/shared/tools/ant/bin to your PATHenvironment variable.





source to use for the task. The default value is jdbc/ilogDataSource).ant execute-schema -Dserver.url=<protocol://host:port>/teamserver/ -DdatasourceName=jdbc/ilogDataSource -Dfile=my_sql_file.sql










Also, take note of any special instructions in this file concerning your applicationserver.

The appserver.name property configures the class path for the Ant tasks. If youhave to add specific drivers to your class path, you can add them to<WODM_InstallDir>/teamserver/lib/classpath-teamserver.xml.


















Note:















For example:









For example:
















Note:





































v -Dlocale=<locale>








Note:
















Parameter Use






set-config-param







For example:


remove-config-param






print-config-param

















Additional steps to configure Decision Validation ServicesTo configure Decision Validation Services on Tomcat, you can create DecisionWarehouse database resources, deploy the testing.war archive, and check theavailability of the services. You can also run an Ant task to package DecisionValidation Services.

Before you startBefore you deploy and configure Decision Validation Services, you must install theproduct modules and configure them for the application server.

Start by doing the following:1.

Install Rule Execution Server, Rule Designer and Decision Center on the samecomputer. Decision Validation Services is added to these modules.

2.

Download and run the Java EE add-on for your application server.3.

Follow the instructions to configure Rule Execution Server and Decision Centeron the application server.


Refer to “What steps to follow” for the tasks you must complete.

Instead of completing the configuration steps listed in “What steps to follow,” youcan use an Ant task to deploy and configure Decision Validation Services.

Only users belonging to resAdministrators or resMonitors groups can see theDecision Warehouse tab in the Rule Execution Server Console after DecisionValidation Services is configured.


The following table shows the configuration steps for Decision Validation Services:

Step Required

“Step 1: Creating Decision Warehouse database resources”on page 32

Tip:

If you used the Installation Manager to create databaseresources (see Populating a database by using the RuleExecution Server Console), or you used the SQL scripts (seePopulating a database by running SQL scripts), you do nothave to perform this task.

Optional


This archive is the default testing archive packaged with theDecision Validation Services installer.

Optional. Do this step if youwant to check the availabilityof the feature. You can alsouse the default archive if youhave an XML XOM. In thiscase, you do not have torepackage the archive.



Optional. You can use thistask as an alternative methodfor configuring or modifyingthe Decision ValidationServices installation.However, this step ismandatory when you wantto run a test or simulation ona rule project that uses a JavaXOM.

Step 1: Creating Decision Warehouse database resourcesYou can use SQL scripts to create a dedicated schema in the database.



http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/config_ds_res_tomcat/tpc_tcat_pop_from_console.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/config_ds_res_tomcat/tpc_tcat_pop_from_console.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/config_ds_res_tomcat/tpc_tcat_dbscripts.htm




Note:








Note:







H2 H2 console











Step 2: Deploying the Decision Validation Services archiveTo deploy the Decision Validation Services archive, you must copy the archive fileto the appropriate location, add the necessary link to your database, and thenrestart the application server.

About this task

To check that Decision Validation Services is available, you can deploy a specificarchive, called testing.war, instead of the default archive. You must deploy it onthe same server as the Execution Unit (XU). You can apply this procedure todeploy the default testing archive packaged with the installer or any subsequentdeployment of a repackaged archive.

You can also deploy the default testing archive, and use it to test your rules if youhave an XML XOM. The ruleset archive includes an XML XOM inside a RuleApp,so you do not have to repackage the archive to include the XOM.

Procedure

To deploy the Decision Validation Services archive on Tomcat:1. Copy the file <InstallDir>/executionserver/applicationservers/tomcat7/

testing.war to <TOMCAT_HOME>/webapps.2. Open the <TOMCAT_HOME>/conf/server.xml file.3. In the file, add the following link to your database for testing.war just before

the tag that closes the localhost definition </Host>:<Context path="/testing"

docBase="testing.war"debug="0"reloadable="true"crossContext="true">

<Logger className="org.apache.catalina.logger.FileLogger"prefix="localhost_res_log."suffix=".txt" timestamp="true"/>

<ResourceLink name="jdbc/resdatasource"global="jdbc/resdatasource"type="javax.sql.DataSource"/>

</Context>

4. Save the file.5. If necessary, restart Tomcat and the Rule Execution Server Console so that the

Decision Validation Services function correctly.


Step 3: Checking the availability of Decision Validation ServicesA specific testing URL is designed for you to check the rule session type, DAOfactory class for trace persistence, the class used to cache the Decision ValidationServices job, and the pool size for asynchronous execution.



Version


Patch level


License information


RuleSession


DAO Factory Class


Job store class


Job pool size


Started since











Step 4: Packaging Decision Validation Services using AntYou can configure Decision Validation Services archives by using an Ant task.

About this task



Procedure








What to do next


Providing more memory for applicationsIn case of core dumps or Java out-of-memory errors when running a WebSphereOperational Decision Management module, you can increase the memory availableto the Tomcat application server.

About this task

You can make more memory available to the Tomcat application server byincreasing the maximum heap size for the Java Virtual Machine (JVM) in thecatalina script.


Procedure

To increase the memory settings for Tomcat:1. Stop your application server.2. Increase the maximum heap size option for the Java Virtual Machine (JVM) in

the catalina script.For example, you can override the default heap size by using the -Xms and -Xmxswitches to specify the initial and maximum sizes respectively:%JAVA_HOME%\bin \java -Xms128m -Xmx512m -XX:MaxPermSize=128m

This example also sets the permanent generation heap to a maximum value of128 MB.To determine the appropriate heap size for the environment, submit yourapplications to stress tests.

3. Save the file and restart the application server.

Configuring the Decision Center Enterprise console on JBoss 5 and6.1

To use the Decision Center Enterprise console on a new instance of the JBossapplication server, you must deploy the provided archives for this server andperform a number of configuration tasks.

Before you startTo configure Decision Center on JBoss 5 and 6.1, you must follow specific steps.Some steps are mandatory, while others apply in certain cases only.

Before you start, clean up your environment as described below:1. Delete the /work and /tmp directories from the folder in which you deploy

Decision Center.2. If not already done, set JBOSS_HOME as an environment variable.

When you have a clean environment, refer to “What steps to follow” on page 112to understand the tasks that you must complete to configure Decision Center onyour application server.

You can complete the configuration of your application server with the InstallationSettings wizard in the Decision Center console or with Ant scripts.

When the installation is finished, you can launch Decision Center (see “Openingthe Decision Center Enterprise console” on page 167 for more information). Noticethat the first time you open Decision Center, it does not contain rule projects. Youmust publish a project from Rule Designer (see “Publishing a project” on page 165for more information).

Note:

If you want to work with rule projects that were created with JRules 7, you mustmigrate the database schema as described in Migrating the Rule Team Serverdatabase.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.family.migrating.rules/topics/tpc_mig_migrating_db.htm



The installation steps that you follow to install Decision Center on JBoss 5 and 6.1are summarized in the following table:

Step Required



“Step 3: Configuring securityon JBoss” on page 115



Optional

“Step 4: Deploying the Decision Center EAR on JBoss” onpage 117


Recommended

“Step 6: Completing yourDecision Centerconfiguration” on page 118


Use one of the two methodsto complete the installation.Required for distributedplatforms only.

“Completing theconfiguration using Anttasks” on page 123

“Verifying your configuration of Decision Center” on page165

“Running the Decision Center Enterprise consolediagnostics” on page 168

Recommended



Note:





Databasepermission

Operation





CREATE ANYINDEX


DROP ANYINDEX


CREATE ANYROLE


CREATE ANYSEQUENCE


DROP ANYSEQUENCE


SELECT ANYSEQUENCE


ALTER ANYTABLE


CREATE ANYTABLE


DROP ANYTABLE


INSERT ANYTABLE


SELECT ANYTABLE


UPDATE ANYTABLE


CREATE ANYVIEW


DROP ANYVIEW


Step 2: Creating a data source and connection poolYou must create a data source and connection pool in JBoss to enable DecisionCenter.

Before you begin

Your database must be running before you create a data source. For moreinformation about supported databases, see the WebSphere Operational DecisionManagement Readme file.

Procedure1. In the <JBOSS_HOME>/server/default/deploy directory, create an XML descriptor

file that ends with -ds.xml, for example rts-derby-ds.xml.


Note:

You can find data source examples in the directory <JBOSS_HOME>/docs/examples/jca.The following example is based on the file derby-ds.xml provided in<JBOSS_HOME>/docs/examples/jca.

rts-derby-ds.xml<?xml version="1.0" encoding="UTF-8"?><datasources>

<local-tx-datasource><jndi-name>jdbc/ilogDataSource</jndi-name><connection-url>jdbc:derby:${jboss.server.data.dir}${/}derby${/}rtsdb;create=true</connection-url><driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class><user-name>sa</user-name><password></password><min-pool-size>5</min-pool-size><max-pool-size>20</max-pool-size><idle-timeout-minutes>5</idle-timeout-minutes><track-statements/><depends>jboss:service=Derby</depends>

</local-tx-datasource><mbean code="org.jboss.jdbc.DerbyDatabase"

name="jboss:service=Derby"/></datasources>

2. Set the values of the properties in this file. By default, JBoss uses localtransaction data sources identified by the tags:<local-tx-datasource> ... </local-tx-datasource>

The properties to set depend on the type of data source that you create and thedatabase you want to connect to. A minimum set of properties to set in theXML descriptor includes:v

Common properties

JNDI name

This property is independent from the type of data source anddatabase and must be set to this value:

<jndi-name>jdbc/ilogDataSource</jndi-name>

Connection URL

This property is for local transaction data sources. It defines theJDBC connection URL. For example:

<connection-url>jdbc:derby:${jboss.server.data.dir}${/}derby${/}rtsdb;create=true</connection-url>

Driver class

This property is for local transaction data sources. It defines the classthat handles the connections to the database. For instance:

<driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>

Make sure you have the equivalent .jar files in<JBOSS_HOME>/server/default/lib, for example derby.jar andderby-plugin.jar.

User name and Password


These properties are for local transaction data sources.The tags<user-name> and <password> are used to create the database the firsttime the system is run. After the database is created, you must usethe user name and password specified.

v Custom properties

Data sources might require additional properties or services to beoperational. For example, for embedded databases (such as Hsqldb orDerby), you must start the database first. Databases are started using aservice. In the XML descriptor, this dependency is translated using the tags<depends> ... </depends>.

What to do nextv If you have to be 100% compliant with Java EE specifications, you must disable

direct JNDI data source lookup. Instructions on how to do so are provided in<WODM_InstallDir>/teamserver/lib/jrules-teamserver.jar(/ilog/rules/teamserver/preferences.properties).

v

For Derby:– If you want to use an embedded Derby database, copy the file derby.jar

from the directory <Derby_InstallDir>/lib to the directory<JBOSS_HOME>/server/default/lib. Also, copy the file derby-plugin.jar fromthe directory <JBOSS_HOME>docs/examples/varia to the directory<JBOSS_HOME>/server/default/lib.

– The database name is the directory in which the database is created.– The MBean org.jboss.jdbc.DerbyDatabase is provided in a plug-in packaged in

derby-plugin.jar.

Step 3: Configuring security on JBossYou control access to Decision Center and enforce security by defining user groupsand associated roles.

Groups and permissionsYou control access to Decision Center and enforce security by defining user groupsand associated roles. Some of these groups are mandatory.

Any user of Decision Center must belong to at least one of these mandatorygroups:v rtsAdministrator

v rtsConfigManager

v rtsInstaller

v rtsUser

Adherence to these groups determines what parts of Decision Center a user canaccess. You must create all these groups. For testing purposes, also create a defaultuser/password for each of these groups.

In addition, if you want to perform the Decision Center permissions tutorial inyour own installation, you must create two custom groups (Validator andEligibility)

The following table summarizes the mandatory and custom groups and theirassociated role, default user, and password.


Group Use Default User/Password


rtsAdmin/rtsAdmin


rtsConfig/rtsConfig


rtsUser1/rtsUser1

rtsInstaller Mandatory, gives the useraccess to the InstallationSettings wizard.

rtsAdmin/rtsAdmin


Val/Val


Eli/Eli

You declare groups and users in the files roles.properties and users.properties.

The following procedure is a suggested configuration with a default user for eachof the basic groups. Also, remember that groups Validator and Eligibility andtheir users are only necessary if you want to do the Decision Center permissionstutorial in your own installation.1. Create the files roles.properties and users.properties in the configuration

directory: <JBOSS_HOME>/server/default/conf.2. In file roles.properties, map users to their groups, for example:

rtsUser1=rtsUserrtsConfig=rtsConfigManager, rtsUserrtsAdmin=rtsAdministrator,rtsInstaller,rtsUserEli=Eligibility,rtsUserVal=Validator,Eligibility,rtsUser

3. In file users.properties, declare the user and password combinations, forexample:rtsUser1=rtsUser1rtsConfig=rtsConfigrtsAdmin=rtsAdminEli=EliVal=Val

Declaring custom groupsIn addition to mandatory groups, you can create custom groups.

About this task

The Decision Center EAR references the basic groups: rtsUser, rtsConfigManager,rtsAdministrator, and rtsInstaller.

Any custom groups, including Validator and Eligibility, must be:v Added to the deployment descriptors before deploying the EAR, otherwise you

get warnings in your console.


v Uploaded to the database (see “Completing the configuration from the DecisionCenter Enterprise console” on page 15), if you want to use the Decision Centerpermissions mechanism.

Note:

You might want to make a copy of the EAR before modifying it.

Procedure

To add your custom groups to the deployment descriptors, add your custom groupas a role in <WODM_InstallDir>/teamserver/applicationservers/JBoss5/jrules-teamserver-JBOSS5.ear/META-INF/application.xml (on JBoss 5) or in<WODM_InstallDir>/teamserver/applicationservers/JBoss6/jrules-teamserver-JBOSS6.ear/META-INF/application.xml (on JBoss 6.1)...<security-role>

<role-name>my_custom_group</role-name></security-role>...

Note: The EAR file is a compressed file. You must open it to extract the files thatmust be changed, and then replace the files in the EAR.

Step 4: Deploying the Decision Center EAR on JBossTo deploy the Decision Center EAR on JBoss, you must copy the EAR archive tothe deployment directory of your application server.

Procedure

Copy the file <WODM_InstallDir>/teamserver/applicationservers/JBoss5/jrules-teamserver-JBOSS5.ear (on JBoss 5) or the file <WODM_InstallDir>/teamserver/applicationservers/JBoss6/jrules-teamserver-JBOSS6.ear (on JBoss 6.1) to thedeploy folder:<JBOSS_HOME>/server/default/deploy

Important:

Deploying the Decision Center EAR sets the persistence locale. After you save arule to the database, you cannot change the persistence locale. If you want toinstall Decision Center in a language other than English, take note of theinstructions provided in “Step 6: Completing your Decision Center configuration”on page 118.



About this task



Procedure




Step 6: Completing your Decision Center configurationAfter you have created a data source, defined security settings, and deployed theDecision Center EAR file, you complete the configuration either from the DecisionCenter console or by running Ant tasks. If your database is DB2 for z/OS, generatethe schema on z/OS for reasons of performance. You can, however, use the wizardto import extension files.







Note:




Action Description





Action Description

Set up messagefiles










Note:




About this task


.brdx.


Procedure


extensions (brmx/brdx), or Custom extensions (Zip).



3. Click Generate SQL to generate the script that creates the database tablesbased on the contents of your rule model files.

4. After generating the script, select the Execute the SQL script check box, andthen click Next.

What to do next















You do this step only if you want to use the Decision Center project access andpermission mechanisms. You have to have added all the groups that you want to


see in the available list when enforcing project security or setting permissions inDecision Center. For more information, refer to the topics on Groups andPermissions in the Decision Center help.


To set up groups:



















Parameter Used to








Note:




v To create a new parameter, click New.


v To change an existing parameter:a. Select the check box next to the parameter.b. Click Modify to change the parameter, or click Delete to remove the










v






















Note:















For example:









For example:







The model description (.brmx extension).


v -DextensionData=<data file>








Note:












To remove a database schema, you proceed in two steps:1. Create the SQL script required to remove the database schema.


2. Execute the SQL script that you created.

























v -Dlocale=<locale>







Note:
















Parameter Use






set-config-param








For example:


remove-config-param






print-config-param
















Additional steps to configure Decision Validation ServicesThere are additional steps that you must perform to configure Decision ValidationServices.


Before you startBefore deploying and configuring Decision Validation Services, you must completethe following steps.1. Install Rule Execution Server.2. Install Decision Center.3. Configure both of these applications on the same application server.

After these installations are complete, see “What steps to follow” to understand theadditional tasks that you might have to complete.

Note:

Only users belonging to the resAdministrators or resMonitors groups are able tosee the Decision Warehouse tab in the Rule Execution Server console after DecisionValidation Services is configured.


The configuration steps you follow to configure Decision Validation Services aresummarized in the following table:

Step Required


Optional. If you have usedthe Rule Execution Serverconsole to create databaseresources, you do not haveto perform this task. SeePopulating a database byusing the Rule ExecutionServer console for moreinformation.

“Step 2: Deploying the Decision Validation Services archivefor the first time” on page 134

This archive is the default SSP archive packaged with theDecision Validation Services installer.

Optional. This steps allowsyou to check the availabilityof the feature.Note:

You can also use the defaultSSP archive if you have anXML XOM. In this case, youdo not have to repackage thearchive to include the XMLXOM.


Optional


Optional. You can use thistask as an alternative methodfor configuring or modifyingthe Decision ValidationServices installation.



http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/config_ds_res_jboss/tpc_jboss_pop_from_console.htm





Note:








Note:







H2 H2 console














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

About this task

If you want to check the availability of Decision Validation Services, you mustdeploy the default SSP (Scenario Service Provider) EAR as described below.

Note:

You must deploy the archive on the same server as the Execution Unit (XU).

Procedure

Copy the JBoss file <WODM_InstallDir>/executionserver/applicationservers/JBoss5/jrules-ssp-JBOSS5.ear (on JBoss 5) or <WODM_InstallDir>/executionserver/applicationservers/JBoss6/jrules-ssp-JBOSS6.ear (on JBoss6.1) to <JBOSS_HOME>/server/<server configuration>/deploy.You can use this procedure to deploy the default SSP archive packaged with theinstaller or any subsequent deployment of a repackaged archive.If you have an XML XOM, you can also use the SSP EAR to test your rules.

Note:

Because the ruleset archive inside a RuleApp includes an XML XOM, you do nothave to repackage the SSP EAR to include the XOM.





Version


Patch level


License information


RuleSession


DAO Factory Class


Job store class


Job pool size


Started since









The report for the job is automatically downloaded by Decision Center atthe end of the execution. If the scenario suite is run in the background, theuser downloads the report by viewing the list of scenario suites, and then


clicking the report link when it becomes available. After the report isviewed, the job is removed from the table. The job remains in the tableuntil the report is downloaded.


About this task



Procedure








What to do next



For more information, see Troubleshooting and support resources.

Providing more memory for applicationsIf you experience core dumps or Java out-of-memory errors when running RuleExecution Server, you can make more memory available to your application server.

Procedure

To increase the JBoss application server memory settings:1. Stop your application server.2. Open the file <JBOSS_HOME>/bin/run.conf.bat if you are on Windows, or the

script <JBOSS_HOME>\bin\run.conf if you are on Linux or UNIX.



3. Find the following line and alter the values to suit your server usage: setJAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:MaxPermSize=256m

Configuring the Decision Center Enterprise console on WebLogicServer 10.3.2

To use the Decision Center Enterprise console on a new instance of the WebLogicapplication server, you must deploy the provided archives for this server andperform a number of configuration tasks.

Before you startTo configure Decision Center on WebLogic Server, you must follow specific steps.Some of these steps are mandatory, while others apply in certain cases only.

“What steps to follow” below summarizes the steps for configuring DecisionCenter on WebLogic Server.

You can complete the configuration of your application server either with theInstallation Settings wizard of the Decision Center console or with Ant scripts.

Once the installation is finished, you can launch Decision Center (see “Verifyingyour configuration of Decision Center” on page 165 for more information). Noticethat the first time you open Decision Center, it does not contain rule projects. Youhave to publish a project from Rule Designer (see “Publishing a project” on page165 for more information).

Note:

If you want to work with rule projects that were created with JRules 7 beforeWebSphere Operational Decision Management 8.0, you have to migrate thedatabase schema as described in Migrating the Rule Team Server database.


The installation steps that you follow to install Decision Center on WebLogicServer are summarized in the following table:

Step Required





“Creating groups inWebLogic Server” on page141

“Creating users in WebLogicServer” on page 143



Step Required

“Step 4: Deploying the Decision Center EAR” on page 144


Optional

“Step 6: Completing DecisionCenter configuration” onpage 146


Use one of the two methodsto complete the installation.Required for distributedplatforms only.

“Completing theconfiguration using Anttasks” on page 151

“Verifying your configuration of Decision Center” on page165

“Running the Decision Center Enterprise consolediagnostics” on page 168

Optional



Note:




Databasepermission

Operation





CREATE ANYINDEX


DROP ANYINDEX


CREATE ANYROLE



Databasepermission

Operation





CREATE ANYSEQUENCE


DROP ANYSEQUENCE


SELECT ANYSEQUENCE


ALTER ANYTABLE


CREATE ANYTABLE


DROP ANYTABLE


INSERT ANYTABLE


SELECT ANYTABLE


UPDATE ANYTABLE


CREATE ANYVIEW


DROP ANYVIEW


Step 2: Creating a data source and connection poolYou must create a data source and connection pool in WebLogic Server to enableDecision Center.

About this task

Your database must be running before you create a data source. For moreinformation about the supported databases, see the Readme file.

Procedure

To create a data source and connection pool:1. Start the WebLogic Server.2. Log on to the WebLogic Server Administration console.3. In the Domain Structure open Services > JDBC, and click Data Sources. The

Summary of JDBC Data Sources page opens.4. Click Lock & Edit, and then in the Summary of JDBC Data Sources page

under Data Sources, click New.


5. Give a name to your data source (for example, Decision Center Data Source)and type jdbc/ilogDataSource for the JNDI name.

6. Select a Database Type and Database Driver and click Next.

Note:

To use Decision Center with an Oracle XA data source, you must first specifya non-XA driver, then create the database schema (see “Completing theconfiguration from the Decision Center Enterprise console” on page 15), andthen switch to an XA data source through the WebLogic Server Administrationconsole.

7. You are provided with information on Transaction Options and the driveryou have selected.If you select an XA database driver, the data source supports globaltransactions and uses the Two-Phase Commit global transaction protocol. Noother transaction configuration options are available in this case.Click Next.

8. Define the Connection Properties.

Database name

Enter rtsdb.

Host name

Enter localhost.

Port

Enter the port (for example, 0 for the embedded Derby database).

Database User Name

Enter RTS.

Password

Use RTS and confirm it.Click Next.

9. In the Test Database Connection page, clear the content of the Test TableName field if the database does not exist yet, and then click TestConfiguration to ensure that the connection pool is operational. If thefollowing message is shown, your connection pool is ready to be used.Connection test succeeded.

Click Next.10. In the Create a New JDBC Data Source page, under Servers select

AdminServer and click Finish.11. Click Activate Changes.

Step 3: Configuring securityYou control access to Decision Center and enforce security by defining user groupsand associated roles.

Groups and permissionsEnable the definition of the username, passwords, and groups in text files withoutencryption.


Any user of Decision Center must belong to at least one of these mandatorygroups:v rtsAdministrator

v rtsConfigManager

v rtsInstaller

v rtsUser

Adherence to these groups determines what parts of Decision Center a user canaccess. You must create all these groups in WebLogic Server. For testing purposes,also create a default user/password for each of these groups.

In addition, if you want to perform the Decision Center permissions tutorial inyour own installation, you have to create two custom groups (Validator andEligibility).

The table below summarizes the mandatory and custom groups and theirassociated role, default user and password.

Group Use Default user/password


rtsAdmin/rtsAdmin1


rtsConfig/rtsConfig1


rtsUser1/rtsUser1

rtsInstaller Mandatory, gives the useraccess to the InstallationSettings wizard.

rtsAdmin/rtsAdmin1


Val/Validator1


Eli/Eligibility1

Creating groups in WebLogic ServerCreate groups and enable the definition of the username, passwords, and groups intext files without encryption.

Overview:

In WebLogic Server, you create groups in three steps.1. “Adding all groups to the security realm.” This step is mandatory for all

groups used in Decision Center.2. “Declaring global roles” on page 142. This step is mandatory for all groups

used in Decision Center.3. Upload groups to the database. You do this later, using the Installation Settings

wizard. For more information, see “Completing the configuration from theDecision Center Enterprise console” on page 15.

Adding all groups to the security realm:


Create new groups and add all the groups to the security realm.

About this task

Adding groups to the security realm is mandatory for all groups used in DecisionCenter.

Procedure

To add a group to the security realm:1. In the WebLogic Server Administration console, in Domain Structure click

Security Realms.2. In the Summary of Security Realms page, under Realms click the name

myrealm.3. In the Settings for myrealm page, click Users and Groups.4. Click the Groups tab. In the Groups page, click New.5. In the Create a New Group page, add the rtsAdministrator group and type

Decision Center for the description. Leave Provider set toDefaultAuthenticator. Click OK.

6. When you have added the rtsAdministrator group, add the following groupnames and their descriptions using step 4 and step 5 of this procedure.

Group name Description

rtsConfigManager Decision Center configuration manager

rtsInstaller Decision Center installer

rtsUser Decision Center user

Validator Optional Decision Center tutorial group

Eligibility Optional Decision Center tutorial group

Declaring global roles:

After adding mandatory groups to the security realm, you must declare globalroles.

About this task

Declaring global roles is mandatory for all groups used in Decision Center.

Procedure

To declare global roles:1. In the Domain Structure, select Security Realms.2. In the Summary of Security Realms page, under Realms click the name

myrealm.3. In the Settings for myrealm page, click Roles and Policies.4. Click the Realm Roles tab.5. Expand Global Roles and click Roles.6. In the Global Roles window click New.7. In Role Properties, type the rtsAdministrator group name you created and

click OK.


8. In the Global Roles window, click the role name you just created.9. Click Add Conditions. In Predicate List select Group, and click Next.

10. For Group Argument Name specify the same name as the role (for example,rtsAdministrator) and click Add and Finish and Save.

11. Repeat step 6 to step 10 above to define the remaining required global roles(use the breadcrumbs at the top of the page for easy navigation), and ifrequired the two optional roles, Validator and Eligibility:v rtsConfigManagerv rtsInstallerv rtsUserv Validatorv Eligibility

Results

Note:

To use the Decision Center permissions mechanism, you also have to uploadgroups to the database (see “Completing the configuration from the DecisionCenter Enterprise console” on page 15)

Creating users in WebLogic ServerCreate users and add them to the groups you have previously defined.

About this task

The following table gives a suggested configuration where you create a defaultuser for each of the basic groups. Also, remember that users Val and Eli are onlynecessary if you want to do the Decision Center permissions tutorial in yourinstallation.

Table 16. Suggested user names

User Description Password Is added to groups...

rtsAdmin Decision Centeradministrator

rtsAdmin1 rtsAdministrator,rtsInstaller

rtsConfig Decision Centerconfigurationmanager

rtsConfig1 rtsConfigManager

rtsUser1 Decision Center user rtsUser1 rtsUser

Eli Decision Centertutorial user

Eligibility1 Eligibility, rtsUser

Val Decision Centertutorial user

Validator1 Validator, Eligibility,rtsUser

Procedure

To add a user:1. In the WebLogic Server Administration console, in Domain Structure click


myrealm.


3. In the Settings for myrealm page, click User and Groups. Click the Users tab.4. In the Users page click New.5. In the Create a New User page enter the user name, a description, the

password, and confirm the password (see Table 16 on page 143). Click OK. Thefollowing message is shown at the top of the page:User created successfully

6. Repeat for the other users listed in Table 16 on page 143.

What to do next

To change the length of the Password field:1. In the settings for myrealm, select Providers > Authentication.2. Click the name DefaultAuthenticator, then in the Settings for

DefaultAuthenticator page, click the Provider Specific link.3. Set the Minimum Password Length to the required number of characters and

click Save.4. Restart the server to apply the change.

Adding users to groups in WebLogic ServerAdd the users to the groups you have previously defined.

About this task

After you have created the users, you add the users to groups.

Procedure

To add users to groups:1. In the WebLogic Server Administration console, in Domain Structure click


myrealm.3. In the Settings for myrealm page, click User and Groups. Click the Users tab.4. In the Users page click the user name you want to add to the group. For

example, click rtsAdmin.5. Click the Groups tab. Select rtsAdministrator in the Available column and

click the right-arrow to move rtsAdministrator to the Chosen column. Nowadd rtsInstaller to the Chosen column.

6. Click Save.7. Repeat steps 4 through to 6 for all the users listed in the table Table 16 on page

143.

Step 4: Deploying the Decision Center EARYou must upload the Decision Center EAR to deploy it on your application server.

About this task

When you have configured security settings, you can deploy the packagedDecision Center EAR on WebLogic Server.

Note:


Deploying the Decision Center EAR sets the persistence locale. After you save arule to the database, you must no longer change the persistence locale. If you wantto install Decision Center in a language other than English, take note of theinstructions provided in “Step 4: Set the persistence locale” on page 18 in“Completing the configuration from the Decision Center Enterprise console” onpage 15.

Procedure

To deploy the EAR:1. In the WebLogic Server Administration console, in Domain Structure click

Deployments.2. In the Summary of Deployments page, under Deployments click Install.3. In the Install Application Assistant click the upload your file(s) link.4. Click Browse next to Deployment Archive and upload the following file:

<InstallDir>/teamserver/applicationservers/WebLogic10/jrules-teamserver-WL10.ear

Click Next.5. Select the check box next to the jrules-teamserver-WL10.ear.

Click Next.6. Select Install this deployment as an application and click Next.7. In the Optional Settings page, for Security select DD Only: Use only roles

and policies that are defined in the deployment descriptors..For Source accessibility, select Use the defaults defined by the deployment'stargets.Click Finish.

8. In the Summary of Deployments page for the deployment, expandjrules-teamserver-WL10. You can see teamserver is listed under Modules.

9. Click Deployments in the Domain Structure. Select the check box next tojrules-teamserver-WL10 and click Start > Servicing All Requests.



About this task


Procedure





Step 6: Completing Decision Center configurationAfter you have created a data source, defined security settings, and deployed theDecision Center EAR file, you complete the configuration either from the DecisionCenter console or by running Ant tasks.







Note:




Action Description



Set up messagefiles







Action Description






Note:




About this task


.brdx.


Procedure




then click Next.

What to do next



















To set up groups:

Using the Setup Groups page in the Installation Settings wizard, you upload yourcustom groups and create the default groups for rtsUser and rtsConfigManager asfollows:


1. Click New.2. Type the group name.3. Click Apply.4. When you have added all the groups, proceed in one of the following ways:


















Parameter Used to








Note:








that you performed in the Installation Settings wizard.


4. Click OK to finish.







v











The <protocol://host:port> URL is defined in the file <WODM_InstallDir>/teamserver/bin/teamserver-anttasks.properties. If your browser is not running on the samehost as the application server, replace localhost with the address of the machine. If



your web application is mapped to a host on a port that is different from the portnumber shown, change the port number to your host port number.







Note:

On WebLogic Server, replace the rtsAdmin password with rtsAdmin1 in theteamserver-anttasks.properties file.








Extensions to the Decision Center rule model are stored in two XML files. One ofthe files contains the model description itself (usually, the .brmx extension is used),and the second one contains data to initialize enumerations and hierarchies



(usually, the .brdx extension is used). You can use Ant tasks to load the rule modelfrom the two XML files and build the SQL script required to get the properdatabase schema.










Note:















For example:









For example:
















Note:














To create the SQL script required to delete a database schema, run thegen-drop-schema Ant task with the following parameters:


v -Dserver.url=<server url>























v -Dlocale=<locale>







Note:











The port number.


v teamserver.server.isSecureTrue if the connection is secure.

v teamserver.server.hostnameThe name of the host.


Parameter Use






set-config-param







For example:


remove-config-param







print-config-param
















Additional steps to configure Decision Validation ServicesThere are additional steps that you have to perform to configure DecisionValidation Services.

Before you startTasks you must perform before deploying and configuring Decision ValidationServices.

Before following the instructions to deploy and configure Decision ValidationServices, you must:1.


Install Rule Execution Server.2.

Install Decision Center.3.

Configure both of these applications on the same application server.

Once these installations are complete, see “What steps to follow” to understand theadditional tasks that you might have to complete.

Note:

Only users belonging to the resAdministrators or resMonitors groups are able tosee the Decision Warehouse tab in the Rule Execution Server console after DecisionValidation Services is configured.


The configuration steps you follow to configure Decision Validation Services aresummarized in the following table:

Step Required


Optional. If you have usedthe Rule Execution Serverconsole to create databaseresources, you do not haveto perform this task. SeePopulating a database usingthe Rule Execution Serverconsole for moreinformation.

“Step 2: Deploying the Decision Validation Services archivefor the first time” on page 162

This archive is the default SSP archive packaged with theDecision Validation Services installer.

Optional. This step allowsyou to check the availabilityof the featureNote:

You can also use the defaultSSP archive if you have anXML XOM. In this case, youdo not have to repackage thearchive to include the XMLXOM.


Optional


Optional. You can use thistask as an alternative methodfor configuring or modifyingthe Decision ValidationServices installation.


If you set the Rule Execution Server persistence to datasource or jdbc in Selectingand applying the persistence type and you intend to use Decision Warehouse to


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.config/config_ds_res_weblogic/tpc_wlogic_pop_from_console.htm





store your test execution results, you must create a dedicated schema in thedatabase containing these tables and views. To do so, you can use the providedSQL scripts, located in <WODM_InstallDir>/executionserver/databases. A readmefile in this directory provides additional information about the scripts.


Note:








Note:







H2 H2 console












Step 2: Deploying the Decision Validation Services archive forthe first timeDeploy the Decision Validation Services archive.

About this task

If you want to check the availability of Decision Validation Services, you mustdeploy the default SSP (Scenario Service Provider) EAR as described below.

Note:

You must deploy the archive on the same server as the XU

You can use this procedure to deploy the default SSP archive packaged with theinstaller or any subsequent deployment of a repackaged archive.

If you have an XML XOM, you can also use the SSP EAR to test your rules.

Note:

Because the ruleset archive inside a RuleApp includes an XML XOM, you do nothave to repackage the SSP EAR to include the XOM.

Procedure

To deploy the archive:1. Open the WebLogic Server administration console.2. In Domain Structure click Deployments.3. In the Summary of Deployments page under Deployments, click Install.4. In the Install Application Assistant click the upload your file(s) link.5. Click Browse next to Deployment Archive and upload the following file,

depending on your version of WebLogic:


WebLogic 10.x

<InstallDir>/executionserver/applicationservers/WebLogic10/jrules-ssp-WL10.ear

Click Next.6. Select the EAR file and click Next.7. Select Install this deployment as an application and click Next.8. Select Use the defaults defined by the deployment's targets and click Finish.9. In the Summary of Deployments, select the EAR file and select Start >

Servicing all requests.10. In the Start Application Assistant, click Yes to start the deployment.11. Verify that the archives have been deployed (State is Active).




Version


Patch level


License information


RuleSession


DAO Factory Class


Job store class


Job pool size


Started since



The About screen provides information about the jobs currently runningafter you run Decision Validation Services in Decision Center:


v A Job ID is listed in the table when a user clicks Run in DecisionCenter.

v The Created column records the date and time when each job isinitialized.

v The Status column shows the number of scenarios that have alreadybeen tested compared to the total number of scenarios.

v The Start time records the time when a resource is allocated for the job.v The Parts column records the number of parts in the job:





About this task



Procedure








What to do next




For more information, see Troubleshooting and support resources.

Providing more memory for applicationsIf you experience core dumps, or Java out-of-memory errors when running aDecision Server module, this procedure shows how to make more memoryavailable to your application server.

Procedure

To increase the WebLogic application server memory settings:1. Stop your application server.2. Increase the maximum heap size option for the Java Virtual Machine (JVM) in

the startWebLogic script. For example, the default heap size can be overriddenby using the -Xms and -Xmx switches to specify the initial and maximum sizesrespectively:This example also sets the permanent generation heap to a maximum value of128 MB.Consult the Oracle WebLogic product documentation for the heap size, basedon application architecture and the number of memory-intensive processesrunning on the host system. Stress-test applications to determine theappropriate heap size for the environment.%JAVA_HOME%\bin java -Xms128m -Xmx512m -XX:MaxPermSize=128m

3. Save the file and restart the application server.

Verifying your configuration of Decision CenterYou can start using Decision Center after you have deployed the Decision Centerarchive.

Publishing a projectAfter completing the installation, Decision Center is ready to be used but does notcontain a rule project. You have to publish a rule project from Rule Designer.

About this task

If you want to carry out the tutorials found in the Decision Center online help, youalso have to publish the following rule projects from Rule Designer:v loanvalidation-rules (with loanvalidation-xom)v loanvalidation-rules-dependent

v squery-loanvalidation-rules (with squery-loanvalidation-xom)

To open Rule Designer, click Start > All Programs > IBM > package_group > RuleDesigner.

Procedure

To import the projects for the Decision Center tutorials:



1. In Rule Designer click File > Import > General > Existing Projects intoWorkspace, and click Next.

2. Click Select root directory, browse to <InstallDir>/studio/tutorials/sharedand click OK.

3. Select the projects and click Finish.4. Then publish them to Decision Center.Related information:“Opening the Decision Center Enterprise console” on page 167You open the Decision Center console in a web browser.“Completing the configuration from the Decision Center Enterprise console” onpage 15You can work from the Decision Center Enterprise console to complete or modifythe configuration after you have deployed the Decision Center archive to yourapplication server.“Completing the configuration using Ant tasks” on page 20Ant tasks provide an alternative method for completing or modifying theconfiguration. These tasks perform the same configuration steps as the InstallationSettings wizard in the Decision Center console.“User registries” on page 7The user registries store information about users and user groups. Every user mustbelong to a group. You create and define the groups in the application server.“Configuring the Decision Center consoles on WebSphere Application Server forLinux on System z” on page 38To be able to use the Decision Center consoles on an instance of WebSphereApplication Server for Linux on System z, you set up the persistence for theresources, create a JDBC provider, deploy the provided archives for this server, andactivate security.“Before you start” on page 38To configure Decision Center console on WebSphere Application Server for Linuxon System z, you must follow specific steps. Some are mandatory, while others areoptional.

Publishing the projects for the Decision Center tutorials toDecision Center

After importing a project for Decision Center, you publish them to the server.

Procedure

To publish projects to the Decision Center:1. In Rule Designer, right-click the loanvalidation-rules rule project, and click

Decision Center > Connect.2. Complete the Decision Center Configuration dialog as follows. The warning

message Connection not established displays until you establish theconnection.

User namertsAdmin

PasswordrtsAdmin

URL http://localhost:<port>/teamserver


If your browser is not running on the same host as the applicationserver, replace localhost with the address of the machine. If your Webapplication is mapped to a host on a port that is different to the portnumber shown, change the port number to your host port number.

Data sourceLeave this field empty.

Note:

v If security is enabled, use https://localhost:<PORT_NUMBER>/teamserver.v If you are working with the Decision Center Business Console, the default

URL is http://localhost:<PORT_NUMBER>/decisioncenter.3. Click Connect.

The connection is established when the warning message closes and the Projectconfiguration area becomes active.

4. In the Project configuration area, check that Create a new project on DecisionCenter is selected, and then click Finish.

5. The Synchronize Complete - Decision Center Participant dialog opens when thepublishing process is complete. Click OK to close this dialog.

6. A dialog opens asking you if you want to change to Team Synchronizingperspective. Click Yes.An empty Synchronize view opens, indicating that the projects in RuleDesigner and Decision Center are the same. This means that your rules are nowpublished to Decision Center.

Opening the Decision Center Enterprise consoleYou open the Decision Center console in a web browser.

After you have deployed the Decision Center EAR or WAR to your applicationserver, you can open the Decision Center console by typing teamserver with theroot URL in a web browser: http://localhost:<PORT_NUMBER>/teamserver.

Note: If security is enabled, use https://localhost:<PORT_NUMBER>/teamserver.

If your browser is not running on the same host as the application server, replacelocalhost with the address of the machine. If your web application is mapped to ahost with a port that is different from the default port, use the port number of thehost.

By default, the data source is jdbc/ilogDataSource. If you want to specify adifferent data source, you have to pass it as a request parameter in the URL. Forexample:

http://localhost:7001/teamserver?datasource=jdbc/serverextendedbrm.

The locale of the sign-in page is English by default. You can specify a localeparameter in the teamserver URL that switches the sign-in page to the requiredlocale. For example:

http://localhost:<port>/teamserver?locale=es (assuming that your message filesare localized).


If you sign in with another locale in the URL and want to change the localeafterward, click Options in the top banner. This saves the locale and restores it thenext time you sign in.

If you open Decision Center but no database exists, you automatically access theInstallation Settings wizard with only the Install tab available.

After completing the installation, Decision Center is ready to use but does notcontain a rule project. When you open Decision Center at this point, you see theConfigure tab with a message that Decision Center cannot find a project, and youshould publish a rule project with Rule Designer or contact your administrator.

If you see this message, you have to publish a rule project from Rule Designer (formore information, see “Publishing a project” on page 165).

This message also has a link to Run diagnostics (see “Running the Decision CenterEnterprise console diagnostics”).

Running the Decision Center Enterprise console diagnosticsYou can verify that the Decision Center Enterprise console has been successfullydeployed and configured by running the diagnostics.

Procedure

To run the diagnostics:1. Sign in to the Decision Center Enterprise console.2. In the Decision Center Console click the Configure tab.3. Click Diagnostics.

You see a report showing all the diagnostic tests that have just been run. Acheck mark is shown next to each check. Click Expand All to show detailsabout all checks.

Opening the Decision Center Business consoleYou open the Decision Center console in a web browser.

After you have deployed the Decision Center EAR or WAR to your applicationserver, you can open the Decision Center Business console by typingdecisioncenter with the root URL in a web browser: http://localhost:<PORT_NUMBER>/decisioncenter.

Note: If security is enabled, use https://localhost:<PORT_NUMBER>/decisioncenter.

If your browser is not running on the same host as the application server, replacelocalhost with the address of the machine. If your web application is mapped to ahost with a port that is different from the default port, use the port number of thehost.

By default, the data source is jdbc/ilogDataSource. If you want to specify adifferent data source, you have to pass it as a request parameter in the URL. Forexample:

http://localhost:7001/decisioncenter?datasource=jdbc/serverextendedbrm.


The locale of the sign-in page is English by default. You can specify a localeparameter in the decisioncenter URL that switches the sign-in page to therequired locale. For example:

http://localhost:<port>/decisioncenter?locale=es (assuming that your messagefiles are localized).

If you sign in with another locale in the URL and want to change the localeafterward, click Options in the top banner. This saves the locale and restores it thenext time you sign in.


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM United Kingdom Laboratories,Mail Point 151,Hursley Park,Winchester,Hampshire,England SO21 2JN

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those


websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM United Kingdom Laboratories,Mail Point 151,Hursley Park,Winchester,Hampshire,England SO21 2JN

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee or


imply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Notices 173

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Index

AAnt tasks

configuring Decision Center 20, 55,97, 123, 151

creating the database schema 22, 23,57, 58, 98, 99, 125, 152, 153

defining and uploading messagefiles 26, 61, 102, 128, 156

execute-schema 23, 59, 100, 126, 154executing the database schema 23,

59, 100, 126, 154gen-create-schema 23, 58, 99, 125,

153gen-drop-schema 25, 60, 101, 127,

155print-config-param 27, 62, 103, 129,

157remove-config-param 27, 62, 103,

129, 157removing a database schema 25, 60,

101, 127, 155repackage-ear 28, 64, 105, 131, 159repackage-war 28, 64, 105, 131, 159repackaging the Decision Center

archive 28, 64, 105, 131, 159set-config-param 27, 62, 103, 129, 157set-extensions 22, 57, 98, 125, 152setting configuration parameters 27,

62, 103, 129, 157setting the persistence locale 26, 61,

103, 129, 157setting up the environment 20, 55,

97, 123, 151ssp-setup 36, 71, 110, 136, 164upload-extensions 24, 59, 100, 126,

154upload-messages 26, 61, 102, 128, 156upload-roles 24, 59, 101, 127, 155uploading groups to the database 24,

59, 101, 127, 155uploading the database schema

extension 24, 59, 100, 126, 154asynchronous execution

pool size 35, 70, 109, 135, 163

Bbusiness rule applications

providing more memory for 110

Ccatalina script

heap size 110changing, class loading sequence

Decision Center 12, 48class loading sequence, changing

Decision Center 12, 48

clustersconfiguring on WebSphere Application

Server 78, 79Decision Center 72

removing Decision Center from 82configuration parameters

adding or removing 27, 62, 103, 129,157

for WebSphere Application Serverclusters 78, 79, 81

setting up 19, 54, 95, 122, 149configuring

creating a data source 45creating a JDBC provider 45

configuring Decision Centerconfiguring security 88creating a connection pool

Tomcat 87creating a data source 87creating groups 88creating permissions 88custom groups 90declaring custom groups 11defining user registry 41deploying Decision Validation

Services 108, 134deploying the management WAR

file 91on WebSphere Application Server

overview 38using federated repository 42

configuring Decision Center consolediagnostics 168

configuring Decision Centerson WebSphere Application Server

overview 1configuring Decision Validation

Services 36, 71, 110, 136, 164checking availability of Decision

Validation Services 35, 70, 109, 135,163

creating database resources 32, 67,106, 133, 160

on Tomcat 105redeploying Decision Validation

Services 36, 71configuring Decision Validation Services

on JBoss 132configuring Decision Validation Services

on WebLogic 159connection pool

creating 4, 45, 113, 139connection pools

in Decision Centercreating 87

custom groupsDecision Center 90

custom groups, declaringDecision Center 11, 47

Ddata source

creating 4, 45, 113, 139data sources

in Decision Centercreating 87

databaseconnecting 46testing connection 7

database resourcesfor Decision Validation Services 32,

67, 106, 133, 160database schema

creating 22, 23, 57, 58, 98, 99, 125,152, 153

executing 23, 59, 100, 126, 154removing 25, 60, 101, 127, 155uploading extension 24, 59, 100, 126,

154databases

permissionsDecision Center 2, 40, 86, 112, 138

Decision Centeradding custom groups 116adding groups 115adding users 115clusters, configuring on WebSphere

Application Server 72configuring for JBoss 111configuring for WebLogic Server 137configuring security 115configuring the database 16, 52, 93,

119, 147configuring with Ant tasks 20, 55,

97, 123, 151deploying on JBoss 117deploying on WebLogic Server 144Installation Settings wizard 15, 50,

92, 118, 146opening 167, 168repackaging the archive 28, 64, 105,

131, 159setting up configuration

parameters 19, 54, 95, 122, 149setting up groups 17, 53, 94, 120, 148setting up message files 17, 52, 93,

120, 148setting up persistence locale 18, 53,

95, 121, 149verifying deployment 14, 91, 117, 145WebSphere Application Server clusters

removing 82Decision Center console

configuringcompleting the configuration 15

diagnostics 168Decision Center Console

deploying 91Decision Validation Services

checking availability 35, 70, 109, 135,163


Decision Validation Services (continued)configuring 132, 159

on Tomcat 105on WebSphere Application

Server 31, 66deploying 33, 69, 108, 134, 162packaging using Ant 36, 71, 110, 136,

164redeploying 36, 71

declaringcustom groups in Decision

Center 11, 90declaring, custom groups

Decision Center 47defining, user registry

Decision Center 7, 41deploying

Decision Center WAR file 91Decision Validation Services 33, 69,

108, 134, 162jrules-teamserver-WAS8.ear 48

deploying, Decision Center EARDecision Center 13, 48

diagnosticsDecision Center console

running 168dropping a database schema

See removing

Eear, deploying

Decision Center 13, 48encryption

See permissionsenvironment variables

for Ant 20, 55, 97, 123, 151

Ffederated repository, using


Ggroups

adding 115Decision Center 88, 90on WebLogic Server 141setting up 17, 53, 94, 120, 148uploading to the database 24, 59,

101, 127, 155WebLogic Server 141

Hheap size

setting for Tomcat 110

IInstallation Settings wizard 15, 50, 92,

118, 146Configure Database 16, 52, 93, 119,

147

Installation Settings wizard (continued)Set Configuration Parameters 19, 54,

95, 122, 149Set Persistence Locale 18, 53, 95, 121,

149Set up Groups 17, 53, 94, 120, 148Set up Message File 17, 52, 93, 120,

148installing

connecting to database 46creating a connection pool 4, 45creating a data source 4, 45creating a JDBC provider 4database, connecting to 46database, testing connection 7on WebLogic Server

groups 141permissions 141users 143

installing Decision Centerclass loading sequence, changing 12,

48declaring custom groups 47defining user registry 7deploying the Decision Center

EAR 13, 48enforcing user permissions 2, 40, 86,

112, 138security policies 10, 44using federated repository 8

installing Rule Execution Serverdeploying Decision Validation

Services 162

JJava

out-of-memory error 110JBoss application server

configuring for Decision Center 111configuring security 115creating a connection pool 113creating a data source 113deploying the Decision Center

EAR 117verifying deployment of Decision

Center 14, 91, 117, 145JDBC provider,

creating 45JDBC provider, creating 4jrules-teamserver-WAS8.ear

deploying 48

Mmemory consumption

providing more memory forapplications 110

message filesdefining and uploading 26, 61, 102,

128, 156setting up 17, 52, 93, 120, 148

Oopening


Ppackaging

Decision Validation Services 36, 71,110, 136, 164

parametersSee configuration parameters

permissions 115Decision Center 88Decision Center installation 2, 40, 86,

112, 138on WebLogic Server 141WebLogic Server 141

persistence localesetting 26, 61, 103, 129, 157setting up 18, 53, 95, 121, 149

Profile Management Tools 78, 79profile templates

to configure Decision Center 72publishing rule projects

from Decision Center 165

Rredeploying

Decision Validation Services 36, 71removing

database schema 25, 60, 101, 127, 155rule projects

publishingfrom Decision Center 165

SScenario Service Provider (SSP)

ssp-setup Ant task 36, 71, 110, 136,164

securityconfiguring

for Decision Center 88enabled when configuring Decision

Center 1, 38security policies

Decision Center 10, 44SQL scripts

to remove a database schema 25, 60,101, 127, 155

ssp-setup, Ant task 36, 71, 110, 136, 164

Uuser registry, defining

Decision Center 7, 41users

adding 115on WebLogic Server 143


WWAR files

deploying Decision Center 91WebLogic Server application server

configuring for Decision Center 137creating a connection pool 139creating a data source 139deploying the Decision Center

EAR 144verifying deployment of Decision

Center 14, 91, 117, 145WebSphere Application Server

cluster configuration 78, 79removing applications 81

clusters, configuring 72, 78, 79, 81setting up the Ant tasks

environment 20, 55

Index 177

��

Printed in USA

IBMWebSphere Operational Decision Management Version 8 … · 2018-06-11 · Using a remote Solr...

Documents

Transcript of IBMWebSphere Operational Decision Management Version 8 … · 2018-06-11 · Using a remote Solr...