IBM WebSphere Operational Decision Management: Configuring

IBM WebSphere Operational Decision ManagementVersion 8 Release 0

Configuring Decision Server for z/OS

��

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

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 Server for z/OS . . 1Configuration overview. . . . . . . . . . . 1Performing the initial configuration. . . . . . . 3

Step 1: Authorizing the load library. . . . . . 3Step 2: Customizing the JCL variables . . . . . 4Step 3: Creating the working data sets . . . . . 5Step 4: Creating the working directory. . . . . 6Step 5: Configuring a DB2 persistence layer . . . 6

Configuring a DB2 database as the persistencelayer for zRule Execution Server for z/OS . . 6Configuring a DB2 database as the persistencelayer for Rule Execution Server on WebSphereApplication Server for z/OS . . . . . . . 7

Step 6: Completing the steps specific to yourenvironment . . . . . . . . . . . . . 8

Configuring your rule execution environment . . . 8Configuring zRule Execution Server for z/OS . . 9

Before you start . . . . . . . . . . . 9Server groups . . . . . . . . . . . . 9Supported topologies . . . . . . . . . 10

Topology 1: Single server group andconsole . . . . . . . . . . . . . 10Topology 2: Single server group with ashared console . . . . . . . . . . 12Topology 3: Single server with XUdeployed into single CICS JVM server . . 14Topology 4: Single server with XUdeployed into multiple CICS regions . . . 16

Configuring a group of zRule ExecutionServer for z/OS instances. . . . . . . . 18Configuring CICS to execute rules on zRuleExecution Server for z/OS . . . . . . . 20Configuring IMS to execute rules on zRuleExecution Server for z/OS . . . . . . . 21Configuring zRule Execution Server for z/OSon a CICS JVM server . . . . . . . . . 22Securing zRule Execution Server for z/OSresources . . . . . . . . . . . . . 24

Security options . . . . . . . . . . 24Securing access to the working directoryand the installation directory . . . . . 24Managing server security . . . . . . . 25

Starting a new server instance . . . . . . 30Verifying the configuration . . . . . . . 31

Configuring Rule Execution Server on WebSphereApplication Server for z/OS . . . . . . . . 31

Configuring security on WebSphereApplication Server for z/OS . . . . . . . 31

Using RACF as your security repository . . 32Using a federated repository. . . . . . 36

Configuring Rule Execution Server onWebSphere Application Server for z/OS withDB2 . . . . . . . . . . . . . . . 39

Before you start . . . . . . . . . . 39Step 1: Configuring security on WebSphereApplication Server for z/OS . . . . . . 40

Step 2: Configuring JDBC. . . . . . . 41Step 3: Creating a data source andconnection pool . . . . . . . . . . 42Step 4: Setting the component andcontainer managed aliases for the datasource . . . . . . . . . . . . . 43Step 5: Setting the currentSQLID . . . . 43Step 6: Testing the connection to thedatabase . . . . . . . . . . . . 44Step 7: Deploying the Rule ExecutionServer Management EAR . . . . . . . 44Step 8: Deploying the Rule ExecutionServer MBean descriptors. . . . . . . 45Step 9: Deploying the XU RAR . . . . . 46Step 10: Deploying the hosted transparentdecision service EAR . . . . . . . . 48Step 11: Setting the web container customproperty . . . . . . . . . . . . 49Verifying the configuration . . . . . . 49

Configuring Rule Execution Server onWebSphere Application Server for z/OS withwsadmin scripts . . . . . . . . . . . 50

Before you start . . . . . . . . . . 50Submitting the JCL job . . . . . . . 50Verifying the configuration . . . . . . 51

Optional configuration steps. . . . . . . 51Configuring WebSphere Optimized LocalAdapters (WOLA) . . . . . . . . . 51Integrating WebSphere MQ in WebSphereApplication Server to supportasynchronous execution . . . . . . . 57Configuring Rule Execution Server indifferent environments. . . . . . . . 64Rule Execution Server deployment oncluster environments . . . . . . . . 65

Configuring a COBOL rule subprogram into aCOBOL application . . . . . . . . . . . 68

COBOL-generated code integration . . . . 68Linking code by using a COBOL static link . . 69Linking code by using a COBOL dynamic link 70Calling a CICS wrapper program to integratethe code . . . . . . . . . . . . . 71

Configuring your system for usage data collection 72Configuring zRule Execution Server for z/OS tocollect data . . . . . . . . . . . . . 72Configuring Rule Execution Server on WebSphereApplication Server for z/OS to collect data . . . 72Configuring COBOL rule subprograms to collectdata . . . . . . . . . . . . . . . . 73

Usage monitoring tools . . . . . . . . 73Configuring z/OS . . . . . . . . . . 74

Configuration tasks. . . . . . . . . 74Defining the Resource Manager as a z/OSsubsystem . . . . . . . . . . . . 74Loading the COBOL load module into theLPA . . . . . . . . . . . . . . 75

© Copyright IBM Corp. 2008, 2012 iii

Configuring the Resource Managersubsystem . . . . . . . . . . . . 76

Compiling, linking, and running yourprograms . . . . . . . . . . . . . 77Sample COBOL code for usage data collection 78

Configuring the event runtime on z/OS . . . . . 79Preparing to install on z/OS. . . . . . . . 79

Installing a stand-alone configuration. . . . 80Installing on z/OS . . . . . . . . . . 81Loading the product code from the installationmedia onto z/OS . . . . . . . . . . 82Creating a component directory . . . . . 82

Creating the event runtime database on z/OS . . 83Editing the db2zOS.sql script . . . . . . 84

Configuring the event runtime to run onWebSphere Application Server . . . . . . . 85Installing on a managed node on z/OS . . . . 87Installing graphical tools when the event runtimeis on z/OS . . . . . . . . . . . . . 89Verifying your z/OS installation . . . . . . 90Tuning your z/OS configuration . . . . . . 94Uninstalling on z/OS . . . . . . . . . . 96

Notices . . . . . . . . . . . . . . 99Trademarks . . . . . . . . . . . . . . 101

Index . . . . . . . . . . . . . . . 103

iv IBM WebSphere Operational Decision Management: Configuring Decision Server for z/OS

Configuring Decision Server for z/OS

To use Decision Server on a new instance of WebSphere® Application Server onz/OS®, you must deploy the provided archives for this server and perform anumber of configuration tasks.

To configure multiple instances of zRule Execution Server for z/OS to develop,test, and put your application into production, you define these different instancesusing configuration partitioned data sets.

You create the DB2® event runtime database to store assets such as businessobjects, events, and actions. See “Creating the event runtime database on z/OS” onpage 83.

Configuration overviewAfter you install Decision Server for z/OS and authorize the load library, youconfigure one or more execution environments.

To set up a Decision Server execution environment, you must customize the datasets, JCL variables, runtime variables, and z/OS jobs provided, and then use themto configure new execution environments. Depending on your needs, you coulduse identical environments to maximize execution throughput or you could useone type of environment for legacy rules and another type for rules authored inDecision Center. The configuration process consists of initial steps that are commonto all execution environments, followed by environment-specific steps.

Decision Server provides the following execution environments:v zRule Execution Server for z/OSv zRule Execution Server for z/OS running on a CICS® JVM serverv Rule Execution Server on WebSphere Application Server for z/OSv Event runtime on WebSphere Application Server for z/OSv COBOL rule subprograms.

Data sets and directories

The SMP/E installation for Decision Server creates a number of data sets anddirectories on your z/OS system.

The following table lists the data sets that are installed. In the data set names,++HBRHLQ++ represents the high-level qualifier assigned to the data sets duringinstallation.

Data set Description

++HBRHLQ++.SHBRAUTH APF-authorized load modules.

++HBRHLQ++.SHBRCICS CICS-specific load modules.

++HBRHLQ++.SHBRCOBC COBOL copybooks.

++HBRHLQ++.SHBRCOBS COBOL sample code.

++HBRHLQ++.SHBREXEC Installation-specific executable files.

© Copyright IBM Corp. 2008, 2012 1


++HBRHLQ++.SHBRINST SMP/E jobs.

++HBRHLQ++.SHBRJCL Runtime samples and configuration jobs.

++HBRHLQ++.SHBRLOAD Product load modules.

++HBRHLQ++.SHBRPARM Runtime configuration parameters.

++HBRHLQ++.SHBRPROC Runtime JCL procedures.

++HBRHLQ++.SHBRWASC Property files for WebSphere ApplicationServer installation.

The following table lists the directories that are installed:

Directory Description

/usr/lpp/zDM/V8R0M0/executionserver Runtime files for Rule Execution Server onWebSphere Application Server for z/OS.

/usr/lpp/zDM/V8R0M0/zexecutionserver Runtime files for zRule Execution Server forz/OS.

Configuration steps

The following diagram shows the steps for configuring each Decision Server forz/OS execution environment:

Note: Perform this step only if it was not performed previously.

2 IBM WebSphere Operational Decision Management: Configuring Decision Server for z/OS

Performing the initial configurationDecision Server for z/OS configuration consists of initial steps for every executionenvironment followed by steps specific to each environment.

Step 1: Authorizing the load libraryAfter you install the Decision Server for z/OS data sets, you must make the++HBRHLQ++.SHBRAUTH load library APF-authorized.

About this task

If the load library is not already authorized, add the Decision Server load library tothe list of authorized libraries.

If you execute your rules in a CICS or IMS environment using WebSphereOptimized Local Adapters (WOLA), the WOLA load libraries must also beAPF-authorized. For more information, see “Configuring CICS to execute rulesusing WOLA” on page 53 and “Configuring IMS to execute rules using WOLA”on page 54.

Configuring Decision Server for z/OS 3

Procedure1. Add the ++HBRHLQ++.SHBRAUTH load library to the list of APF-authorized

libraries using the following command:SETPROG APF,ADD,DSNAME=++HBRHLQ++.SHBRAUTH,SMS

where ++HBRHLQ++ represents the high-level qualifier assigned to DecisionServer data sets during installation.

2. Provide RACF® authorization for the ++HBRHLQ++.SHBRAUTH load library usingthe following command:RALTER PROGRAM * ADDMEM(’++HBRHLQ++.SHBRAUTH’//NOPADCHK)SETROPTS WHEN(PROGRAM) REFRESH

Step 2: Customizing the JCL variablesIn the SHBRPARM(HBRINST) data set member, customize the JCL variables for theexecution environment you are configuring.

About this task

The JCL variables are used to generate the working data sets and initialize theruntime variables used by the execution environment instance. In theSHBRPARM(HBRINST) member, related variables are grouped by executionenvironment or feature. Customize the variables that are general to all executionenvironments. They are listed under the heading "Variables to be customized forDecision Server for z/OS". Also customize any variables that are specific to yourenvironment. For example, customize the variables listed under "Variables to becustomized for CICS" only if you are using CICS to run your COBOL applications.

Procedure

To customize the JCL variables:1. Edit the ++HBRHLQ++.SHBRPARM(HBRINST) data set member, where ++HBRHLQ++

represents the high-level qualifier assigned to Decision Server for z/OS datasets during installation.

2. Customize the variables according to the directions in JCL and runtimevariables.

What to do next

Check for the following errors:v Missing a required variable

The following JCL variables must be initialized.– ++HBRWORKDS++

– ++HBRHLQ++

– ++HBRINSTPATH++

– ++HBRSSIDLIST++

v Incorrect version of zRule Execution Server for z/OS SHBRPARM(HBRINST)data set member.The SHBRPARM(HBRINST) data set member is for version 7.5 of zRuleExecution Server for z/OS instead of version 8.0.

v Duplicate valuesThe following pairs of JCL variables must have the different values.– ++HBRHLQ++ and ++HBRWORKDS++


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


– ++HBRWORKPATH++ and ++CICSWORKPATH++

– ++HBRCONSOLEPORT++ and ++HBRCONSOLECOMPORT++

– ++HBRSSPPORT++ and ++HBRCONSOLEPORT++

– ++HBRSSPPORT++ and ++HBRCONSOLECOMPORT++

v Non-integer values where an integer is requiredThe following variables must be set to integer values.– ++HBRCONSOLEPORT++

– ++HBRCONSOLECOMPORT++

– ++HBRSSPORT++

v Invalid value or incorrect caseThe following variables have case-sensitive values.– ++HBRPERSISTENCETYPE++ must be set to FILE or DB2.– ++HBRMODE++ must be set to NORMAL, NORULE, or TEST

– ++HBRLANG++ must be set to a value specified in SHBRPARM(HBRINST) inmixed case as shown.

– ++HBRTRACELEVEL++ must be set to FINE, INFO, WARNING, SEVERE, or OFF.

Step 3: Creating the working data setsCreate the working data sets based on the JCL variables you customized.

The HBRUUPTI job creates the working data sets based on the JCL variables you setin the SHBRPARM(HBRINST) member. The working data sets contain customized JCLfor configuring and running a Decision Server for z/OS execution environment.

The HBRUUPTI job takes the following actions:1. Copies the required data sets and assigns them the high-level qualifier

represented by the ++HBRWORKDS++ JCL variable.2. Assigns the JCL variable settings in the SHBRPARM(HBRINST) member to all

occurrences of the corresponding runtime variable in the other data setmembers and in internal data sets.For example, ++HBRCONSOLECOMHOST++ represents the hostname of themachine where the zRule Execution Server for z/OS console is to run. If youset ++HBRCONSOLECOMHOST++ to the value localhost in HBRINST, thecorresponding runtime variable, HBRCONSOLECOMHOST, is set to localhostwherever it is referenced.

3. Uses the JCL variable settings to generate the working data sets.

Note: When configuring zRule Execution Server for z/OS server groups, HBRUUPTIrepeats these actions for each subsystem ID specified in ++HBRSSIDLIST++.

To create the working data sets:1. In the ++HBRHLQ++.SHBRJCL(HBRUUPTI) data set member, customize the value of

the ++HBRHLQ++ variable, which represents the high-level qualifier assignedto the data set during installation.

2. Submit the ++HBRHLQ++.SHBRJCL(HBRUUPTI) job.

The job generates the working data sets listed in the following table:



++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL Customized JCL for creating instances of theexecution environment.

++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM Customized parameter files.

++HBRWORKDS++.<HBRSSID_NAME>.SHBRPROC Customized started tasks.

++HBRWORKDS++.<HBRSSID_NAME>.SHBRWASC Property files for WebSphere ApplicationServer installation.

The variable, <HBRSSID_NAME>, represents a subsystem ID in the server groupdefined by the ++HBRSSIDLIST++ JCL variable.

Note: If you are configuring a zRule Execution Server for z/OS server group, youcan define more server groups by completing the following steps for eachadditional group:1. Update ++HBRSSIDLIST++ with the subsystem IDs of the servers in the new

group.2. Repeat the previous procedure for creating the working data sets.

Step 4: Creating the working directoryConfigure the working directory, which is used to store internal data such as logs.If you are using a file system for your persistence layer, the deployed artifacts arealso stored in the working directory.

Before you begin, specify the location of the working directory by setting the++HBRWORKPATH++ JCL variable in the ++HBRHLQ++.SHBRPARM(HBRINST) member.

To create the working directory, submit the++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCRTI) job, where ++HBRWORKDS++represents the high-level qualifier assigned to the working data sets.

Note: You need only perform this step once because all servers in the server groupshare a single working directory.

Step 5: Configuring a DB2 persistence layerTo use a database rather than a file system, configure the persistence layeraccording to the following steps.

Note: Perform this step only if a persistence layer has not been previouslyconfigured.

Configuring a DB2 database as the persistence layer for zRuleExecution Server for z/OSzRule Execution Server for z/OS can use a DB2 database to store RuleApps andother artifacts.

About this task

The best practice is to use a DB2 database as your persistence type, particularly ina production environment.

Note: The default persistence type is the directory specified by the++HBRWORKPATH++ JCL variable.


Procedure

To configure a DB2 database as the persistence layer:1. Define a RACF group to control access to the database by completing the

following steps:a. Create the HBRSSID_GROUP RACF group and add it to an existing

superior group using the following command:ADDGROUP <HBRSSID_GROUP> SUPGROUP(SYS1) OWNER(SYS1)

b. Give the HBRSSID_GROUP RACF group access to the DB2 class and theprofiles for batch and CICS using the following commands. The databaseadministrator performs this task.PERMIT <MY_DB2_SSID>.BATCH CLASS(DSNR) ID(<HBRSSID_GROUP>) ACCESS(READ)PERMIT <MY_DB2_SSID>.SASS CLASS(DSNR) ID(<HBRSSID_GROUP>) ACCESS(READ)

2. Ask your database administrator to create the database tables by running thejobs listed in the following table, in the order shown. The data set members arein the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL data set, where++HBRWORKDS++ represents the high-level qualifier assigned to the workingdata sets and HBRSSID_NAME represents a subsystem ID in the server groupdefined by the ++HBRSSIDLIST++ JCL variable.

Note: Verify that the jobs contain the correct settings. The settings were copiedfrom the ++HBRHLQ++.SHBRPARM(HBRINST) member when you created theworking data sets. The best practice for a single server is to use the valuerepresented by HBRSSID_GROUP as your schema name. The++DB2CURRSQLID++ variable in the HBRINST member sets the schema name.

Data set member Description

HBRDSCDB Creates the table for storing the deployedRuleApps.

HBRDSXOM Creates the table for storing the deployedExecution Object Models (XOMs).

HBRDSCTR Creates the trace tables.

3. Give the HBRSSID_GROUP RACF group access to the newly-created tables byrunning the following job:++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRDSGRN)

4. Give database access to the user ID to be used by the server to connect to thedatabase. Use the following command:CONNECT ++DB2USER++ GROUP(<HBRSSID_GROUP>)

where ++DB2USER++ represents the user ID used to access the database.

Configuring a DB2 database as the persistence layer for RuleExecution Server on WebSphere Application Server for z/OSRule Execution Server on WebSphere Application Server for z/OS can use a DB2database to store RuleApps and other artifacts.

About this task

The best practice is to use a DB2 database as your persistence type, particularly ina production environment.

Note: The default persistence type is the file system directory specified by the++HBRWORKPATH++ JCL variable.


Procedure1. Create the <HBRSSID_GROUP> RACF group and add it to an existing superior

group using the following command:ADDGROUP <HBRSSID_GROUP> SUPGROUP(SYS1) OWNER(SYS1)

2. Create the database tables by running the jobs listed in the following table inthe order shown. The data set members are in the++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL data set, where ++HBRWORKDS++represents the high-level qualifier assigned to the working data sets. Thedatabase administrator performs this task.

Note: Verify that the jobs contain the correct settings. The settings were copiedfrom the ++HBRHLQ++.SHBRPARM(HBRINST) member when you created theworking data sets. The best practice is to use the value represented byHBRSSID_GROUP as your schema name. The ++DB2CURRSQLID++ variablein the HBRINST member sets the schema name.

Data set member Description

HBRDSCDB Creates the table for storing the deployedRuleApps.

HBRDSXOM Creates the table for storing the deployedExecution Object Models (XOMs).

HBRDSCTR Creates the trace tables.

3. Give the HBRSSID_GROUP RACF group access to the newly-created tables byrunning the following job:++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRDSGRN)

4. If you did not run the HBRDSCTR job, edit the++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRDSGRN) job to remove the entries togrant access to those trace tables.

5. Give database access to the user ID to be used by the server to connect to thedatabase. Use the following command:CONNECT ++DB2USER++ GROUP(<HBRSSID_GROUP>)

where ++DB2USER++ represents the user ID used to access the database.

Step 6: Completing the steps specific to your environmentYou have finished the initial configuration steps. Continue the configuration bycompleting the steps specific to your environment.

Click one of the following topics to complete the configuration steps for yourenvironment:v “Configuring zRule Execution Server for z/OS” on page 9v “Configuring zRule Execution Server for z/OS on a CICS JVM server” on page

22v “Configuring Rule Execution Server on WebSphere Application Server for z/OS”

on page 31v “Configuring the event runtime on z/OS” on page 79v “Configuring a COBOL rule subprogram into a COBOL application” on page 68

Configuring your rule execution environmentConfigure the Decision Server for z/OS rule execution environment you havechosen to deploy.


Configuring zRule Execution Server for z/OSAfter you install Decision Server for z/OS and complete the initial configurationsteps, you can configure one to 32 zRule Execution Server for z/OS instances as aserver group.

Before you startPrepare to complete the configuration of a zRule Execution Server for z/OSinstance.

Before you complete the final steps for configuring the zRule Execution Server forz/OS instance, you should have read “Configuration overview” on page 1 andperformed the initial configuration steps listed in “Performing the initialconfiguration” on page 3.

To complete the configuration process, proceed as follows:1. Determine the server and console topology that meets your needs.2. Create the subsystem you want the server to run in.3. Configure the rule execution environments.4. Optionally secure zRule Execution Server for z/OS resources, functions, and

data.5. Verify that the server and console are configured correctly.

Server groupszRule Execution Server for z/OS instances are configured as server groups toenable rule execution to be transferred to another server if a server fails or if thereis a planned outage.

A server group can include 1 to 32 server instances. You create a server groupwhen you customize the server group membership list variable,++HBRSSIDLIST++, in the SHBRPARM(HBRINST) data set member. The list consists ofsubsystem IDs separated by commas. For example: HBR1,HBR2,HBR3.

The first ID in the list is the primary server, from which you start the sharedconsole. Rule execution begins on the first available server in the list. Other serversexecute rulesets only if rule execution is transferred to them. To route ruleexecution to a particular server, specify its ID first.

If a server crashes, hangs, abends, or shuts down, rule execution transfersautomatically to the next active server in the list. The inactive server remains in theserver group, and when it restarts, rule execution transfers automatically back tothe original server. No action is required by the COBOL application to accomplishthese transfers.

Note: zRule Execution Server for z/OS on a CICS JVM server can be configuredonly as a server group with a single server. As a result, rule execution cannot betransferred to another member if a server becomes inactive.

The following procedure describes how COBOL applications execute rules using agroup of servers:1. Applications connect to a group of servers using one of the following methods:

v Batch jobs or IMS™ applications use the HBRCONN API to connect to theservers specified in the list.

v CICS applications use the HBRC transaction to connect to the serversspecified in the list.


To ensure that all servers in the list can take over rule execution, verify that allservers in the list are running and that the HBRCONN API call returns acompletion code of HBR_CC_OK (0).

2. After connecting to the servers successfully, COBOL applications use theHBRRULE API once for each ruleset to be executed.

3. When the execution of all the rulesets is complete, the COBOL applications usethe HBRDISC API to disconnect from the servers.

The HBRA-CONN-SSID field in the HBR-CONN-AREA data area returns the subsystemID of the server that completed the execution of the ruleset. If ruleset executiondoes not complete successfully, this field is set to blanks.Related tasks:“Configuring a group of zRule Execution Server for z/OS instances” on page 18Configure a group of zRule Execution Server for z/OS instances to execute rulesfor COBOL applications running as batch jobs.

Supported topologiesYou can configure zRule Execution Server for z/OS in a number of topologiesbased on your production needs and your existing configurations. The followingtopics explain the topology options and how to configure them.

Topology 1: Single server group and console:

Topology 1 consists of a server group containing a single zRule Execution Serverfor z/OS instance and a Rule Execution Server Console, both running in a singleaddress space.

This topology is typically used to run batch and IMS jobs. However, you can alsouse it to run CICS applications on zRule Execution Server for z/OS instead ofusing a CICS JVM server.

The following diagram illustrates the key components of the configuration. The++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM data set members that configure eachcomponent are shown in parentheses. The variable, <HBRSSID_NAME>, representsa subsystem ID in the server group defined by the ++HBRSSIDLIST++ JCLvariable.


To configure topology 1, set the variables in the++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM data set members as shown in thefollowing table. See JCL and runtime variables for more information.

Note: Be sure to set the variables after you create the working data sets in “Step 3:Creating the working data sets” on page 5. Otherwise, your settings will beoverwritten.

Data set member Variable Setting

HBRMSTR HBRCONSOLE YES to provide the server with adedicated console.

HBRCNSL HBRCONSOLEPORT The port number that the webbrowser uses to access the RuleExecution Server Console.

For example: 34141.




HBRCMMN HBRCONSOLECOMPORT The port number that the zRuleExecution Server for z/OS uses tocommunicate with the console.

For example: 44141.

HBRCMMN HBRCONSOLECOMHOST localhost

HBRPSIST HBRPERSISTENCETYPE The type of persistence layer used tostore deployed artifacts. Set thisvariable to DB2.

HBRPSIST HBRDBURL The URL for accessing the DB2database.

Example for a Universal JDBC DriverType 4 connection:

jdbc:db2://winmvsm.ibm.com:49100+/DSN910GP:currentSQLID=HBR1

Topology 2: Single server group with a shared console:

Topology 2 consists of a server group containing multiple zRule Execution Serverfor z/OS instances and a shared Rule Execution Server Console, running in asingle address space.

This topology is typically used to run batch and IMS jobs. However, you can alsouse it to run CICS applications on zRule Execution Server for z/OS instead ofusing a CICS JVM server.



To configure topology 2, set the variables in the++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM data set members as shown in thefollowing table. See JCL and runtime variables for more information.





For example: 34141.

HBRCMMN HBRCONSOLECOMPORT The port number that the zRuleExecution Server for z/OS instanceuses to communicate with theconsole.

For example: 44141.


HBRPSIST HBRPERSISTENCETYPE The type of persistence layer used tostore deployed artifacts. Set thisvariable to DB2.




HBRPSIST HBRDBURL The URL for accessing the DB2database.



To configure each additional server, set the following variables in the++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRMSTR) data set member for thatserver:

Variable Setting

HBRCONSOLE NO to indicate that the server does not haveits own console.

HBRCONSOLECOMPORT The port number that the zRule ExecutionServer for z/OS instance uses tocommunicate with the console.

For example: 44141.

Topology 3: Single server with XU deployed into single CICS JVM server:

Topology 3 consists of a zRule Execution Server for z/OS instance and a RuleExecution Server Console running in a single address space with the ExecutionUnit (XU) is deployed into a single CICS region.



To configure topology 3, set the variables in the++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM data set members as shown in thefollowing table. The variable, HBRSSID_NAME, represents a subsystem ID in theserver group defined by the ++HBRSSIDLIST++ JCL variable. See JCL and runtimevariables for more information.



HBRCICSD HBRPERSISTENCETYPE DB2 to indicate that CICS is to use tothe zRule Execution Server for z/OSdatabase.





HBRCICSD HBRDBURL The URL for accessing the DB2database.

Example for a Universal JDBC DriverType 4 connection:jdbc:db2://winmvsm.ibm.com:49100+/DSN910GP:currentSQLID=HBR1

HBRCICSJ HBRUSEJVMS YES to indicate that the server is torun on a CICS JVM server.

HBRCMMN HBRCONSOLECOMPORT The port number that the zRuleExecution Server for z/OS uses tocommunicate with the console.

For example: 44141.



For example: 34141.


HBRMSTR HBRMODE Set to NORULE to have the server usethe CICS JVM to process rules.

Topology 4: Single server with XU deployed into multiple CICS regions:

Topology 4 consists of a zRule Execution Server for z/OS instance and a RuleExecution Server Console running in a single address space with the ExecutionUnit (XU) deployed into multiple CICS regions.

The following diagram illustrates the key components of the configuration. The++HBRWORKDS++.<HRBSSID_NAME>.SHBRPARM data set members that configure eachcomponent are shown in parentheses.


To configure topology 4, set the variables in the++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM data set members as shown in thefollowing table. HBRSSID_NAME represents a subsystem ID in the server groupdefined by the ++HBRSSIDLIST++ JCL variable. See JCL and runtime variables formore information.




HBRMSTR HBRMODE Set to NORULE to have the server usethe CICS JVM to process rules.


For example: 34141.

HBRCMMN HBRCONSOLECOMPORT The port number that thezRuleExecution Server for z/OS uses tocommunicate with the console.

For example: 44141.


HBRCICSD HBRPERSISTENCETYPE The type of persistence layer used tostore deployed artifacts. Set thisvariable to DB2.




HBRCICSD HBRDBURL The URL for accessing the DB2database.



HBRCICSJ HBRSSID_NAME A subsystem ID in the server groupdefined by the ++HBRSSIDLIST++JCL variable.

For example: HBR1.

HBRCICSJ HBRUSEJVMS YES to indicate that the server is torun on a CICS JVM server.

HBRCICSJ HBRWORKPATH The location of the working directoryfor the server. Each CICS regionrequires a working directory in aseparate UNIX System Services filesystem.

For example: /u/hbr1/jvmserver1.

For each additional CICS configuration, create a separate++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCICSn) data set member, where n isthe CICS region number. For example, create the++HBRWORKDS++.SHBRPARM(HBRCICS2) data set member for CICS region 2.

In each HBRCICSn data set member, set the variables as shown in the followingtable:

Note: The JCL variable, ++HBRWORKDS++, which represents the high-levelqualifier for the working data sets, must have a different value for each server.

Variable Setting

HBRSSID_NAME A subsystem ID in the server group definedby the ++HBRSSIDLIST++ JCL variable.

For example: HBR1.

HBRUSEJVMS YES to indicate that the server is to run on aCICS JVM server.

HBRWORKPATH The location of the working directory for theserver. Each CICS region requires a workingdirectory in a separate UNIX SystemServices file system.

For example: /u/hbr1/jvmserver2.

Configuring a group of zRule Execution Server for z/OSinstancesConfigure a group of zRule Execution Server for z/OS instances to execute rulesfor COBOL applications running as batch jobs.


Before you begin

You must have performed the initial configuration steps as described in“Performing the initial configuration” on page 3.

About this task

Complete the following steps to configure a group of 1 to 32 zRule ExecutionServer for z/OS instances with a shared console.

See “Topology 1: Single server group and console” on page 10 and “Topology 2:Single server group with a shared console” on page 12 for information abouttopology configuration options.

Note: In the following procedure, <HBRSSID_NAME> represents a subsystem IDin the server group defined by the ++HBRSSIDLIST++ JCL variable.

Procedure1. Define a new subsystem for each server instance to run in. The system

programmer performs this task using the following command: SETSSIADD,SUBNAME=<HBRSSID_NAME>. If the command completes successfully, thefollowing message is displayed: IEFJ022I SETSSI ADD COMMAND FOR SUBSYSTEM<HBRSSID_NAME> COMPLETED SUCCESSFULLY.

2. Enable each server instance to run as a started task. For each server instance,copy the following data sets to the SYS1.PROCLIB data set or to a suitableequivalent. The system programmer performs this task.a. Copy the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRPROC(HBRXMSTR) data set

member of each server instance to SYS1.PROCLIB(<HBRSSID_NAME>MSTR).For example, to enable as started tasks server instances HBR1 and HBR2,copy HBR.WORKDS.HBR1.SHBRPROC(HBRXMSTR) to SYS1.PROCLIB(HBR1MSTR) andHBR.WORKDS.HBR2.SHBRPROC(HBRXMSTR) to SYS1.PROCLIB(HBR2MSTR).

b. Copy the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRPROC(HBRXCNSL) data setmember of each server instance to SYS1.PROCLIB(<HBRSSID_NAME>CNSL).For example, for server instance HBR1, copyHBR.WORKDS.HBR1.SHBRPROC(HBRXCNSL) to SYS1.PROCLIB(HBR1CNSL).

c. Authorize the <HBRSSID_NAME>MSTR member for each server and the<HBRSSID_NAME>CNSL member of the primary server as started taskprocedures. Use the following commands:RDEFINE STARTED <HBRSSID_NAME>MSTR.* STDATA(USER(<HBRSSID_USER>)GROUP(<HBRSSID_GROUP>))RDEFINE STARTED <HBRSSID_NAME>CNSL.* STDATA(USER(<HBRSSID_USER>)GROUP(<HBRSSID_GROUP>))SETR REF RACLIST(STARTED)

where <HBRSSID_USER> represents the server user ID and<HBRSSID_GROUP> represents the name of the RACF security groupprovided to you by your security administrator.


Related concepts:“Server groups” on page 9zRule Execution Server for z/OS instances are configured as server groups toenable rule execution to be transferred to another server if a server fails or if thereis a planned outage.

Configuring CICS to execute rules on zRule Execution Server forz/OSAfter you configure a zRule Execution Server for z/OS server group, you canconfigure CICS to execute rules on the server group members.

Before you begin

Verify that you meet the following prerequisites:v You have configured a zRule Execution Server for z/OS server group as

described in “Configuring a group of zRule Execution Server for z/OSinstances” on page 18.

v In “Step 2: Customizing the JCL variables” on page 4, you have customized theCICS-related JCL variables listed in Variables to configure CICS to execute ruleson an instance of zRule Execution Server for z/OS.

See “Supported topologies” on page 10 for information about topologyconfiguration options.

About this task

Use the following procedure to configure CICS to execute rules on zRule ExecutionServer for z/OS.

You can optionally configure CICS to execute the HBRC transaction at startup toconnect to the server instance automatically, if it is running. With this option, CICSis immediately ready to execute rules. If the server is not running, CICS starts upnormally but you must execute the HBRC transaction manually before ruleexecution can begin.

Note: This configuration is supported for CICS version 3.2 or later. If you areusing CICS 4.1 or later, consider running zRule Execution Server for z/OS insidethe CICS JVM server. For more information, see “Configuring zRule ExecutionServer for z/OS on a CICS JVM server” on page 22.

In the following procedure, the variable, HBRSSID_NAME, represents a subsystemID in the server group defined by the ++HBRSSIDLIST++ JCL variable.

Note: If your server group includes more than one member, specify the firstsubsystem ID in HBRSSIDLIST for HBRSSID_NAME.

Procedure1. Submit the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCSD) job to define the

resources required by CICS.2. In the CICS system initialization table, add the list name represented by

++CICSLIST++ to the list of resource definition groups specified by the GRPLISTparameter.

3. Edit the CICS JCL to include the zRule Execution Server for z/OS data sets:a. Add the ++HBRHLQ++.SHBRAUTH library to the STEPLIB concatenation.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.zos.dserver.ref/topics/con_ds_jcl_and_runtime_vars.htm#YcxWhneb__VariablesToConfigureCICSToExecuteRu

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.zos.dserver.ref/topics/con_ds_jcl_and_runtime_vars.htm#YcxWhneb__VariablesToConfigureCICSToExecuteRu

b. Ensure that the ++HBRHLQ++.SHBRCICS data set is added to the DFHRPLconcatenation.

c. Pass the necessary runtime variables to the server by adding theSHBRPARM(HBRCICZ) and SHBRPARM(HBRCMMN) data set members to theHBRENVPR DD statement. as shown in the following DD statements://HBRENVPR DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCICSZ)// DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCMMN)

d. If you plan to run the Miniloan sample application to verify yourconfiguration, add the following DD statement to the SHBRPARM(HBRSCEN)data set member. The HBRSCEN member contains input values to theMiniloan application.//SCENARIO DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRSCEN)

4. Start the zRule Execution Server for z/OS and the Rule Execution Serverconsole.

5. Start CICS and install the HBRGROUP resources using the following command:CEDA INSTALL GROUP(HBRGROUP)

6. Test the configuration by running the HBRC transaction to connect CICS to zRuleExecution Server for z/OS. If CICS succeeds in connecting to the server,message GBRZC9001I is issued. If CICS fails to connect to the server, messageGBRZC9000E is issued with a return code containing diagnostic information.

7. Optional: To configure CICS to connect automatically at startup to the runningserver instance, take either of the following actions:v If you do not have a program list table defined, add the PLTPI=HB parameter

to the CICS system initialization table.v If you already have a program list table defined and specified in your CICS

system initialization table, add the HBRCCON program to the list by includingthe following statement: DFHPLT TYPE=ENTRY,PROGRAM=HBRCCON.

Configuring IMS to execute rules on zRule Execution Server forz/OSAfter you configure a zRule Execution Server for z/OS server group, you canconfigure IMS to execute rules on the server group members.

Before you begin



v In “Step 2: Customizing the JCL variables” on page 4, you have customized theJCL variables listed in Variables to configure IMS to execute rules on an instanceof zRule Execution Server for z/OS.

See “Supported topologies” on page 10 for information about topologyconfiguration options.

Note:

v This configuration is supported for IMS versions 10, 11, and 12.v zRule Execution Server for z/OS supports the ability of IMS to launch batch

applications using batch message processing (BMP) or Data Language/I (DLI).Message processing regions (MPR) for calling rules is not supported.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.zos.dserver.ref/topics/con_ds_jcl_and_runtime_vars.htm#YcxWhneb__VariablesToConfigureIMSToExecuteRul

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.zos.dserver.ref/topics/con_ds_jcl_and_runtime_vars.htm#YcxWhneb__VariablesToConfigureIMSToExecuteRul

Procedure

Ensure that your program and transaction code are defined to IMS.

Configuring zRule Execution Server for z/OS on a CICS JVMserverAfter you configure a group of zRule Execution Server for z/OS servers, you canconfigure the server group to run on a CICS JVM server.

Before you begin



v In “Step 2: Customizing the JCL variables” on page 4, you have customized theCICS-related JCL variables in Variables to configure zRule Execution Server forz/OS running on a CICS JVM server.

Note: ++HBRWORKDS++ represents the high-level qualifier assigned to theworking data sets and ++HBRHLQ++ represents the high-level qualifier assignedto the data sets during installation.

About this task

Use the following procedure to configure a zRule Execution Server for z/OS servergroup to run on a CICS JVM server with CICS version 4.1 or later.

See “Topology 3: Single server with XU deployed into single CICS JVM server” onpage 14 and “Topology 4: Single server with XU deployed into multiple CICSregions” on page 16 for information about topology configuration options.

You can configure CICS JVM Server as a highly available, scalable environmentusing standard CICSPlex® System Management (CPSM) capabilities. In thisconfiguration, the Task Related User Exit (TRUE) calls the HBRCJVMS programusing the EXEC CICS LINK command, which is routed to the specified CICS region.To create this configuration, you must perform the following procedure on both thecalling CICS JVM server and the eventual rule execution CICS regions. For moreinformation about CPSM, see CICS Transaction Server for z/OS information center.

In the following steps, HBRSSID_NAME represents represents a subsystem ID inthe server group defined by the ++HBRSSIDLIST++ JCL variable.

Procedure1. Submit the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCRTCI) job to create a

working directory for the server on CICS. The ++CICSWORKPATH++ JCLvariable specifies the location of the working directory.

2. Run either of the following jobs to create the default CICS JVM profile in theworking directory specified by the ++CICSWORKPATH++ JCL variable:v If you use CICS TS version 4.2 or later, submit the

++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCJVMP) job to create the profile,HBRJVM.

v If you use CICS TS version 4.1, submit the++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCJS41) job to create the profile,HBRJVM41.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.zos.dserver.ref/topics/con_ds_jcl_and_runtime_vars.htm#YcxWhneb__VariablesToCreateANewCICSJVMServerF

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.zos.dserver.ref/topics/con_ds_jcl_and_runtime_vars.htm#YcxWhneb__VariablesToCreateANewCICSJVMServerF

http://publib.boulder.ibm.com/infocenter/cicsts/v3r1/index.jsp

3. In the CICS system initialization table, look for the variable, JVMPROFILEDIR,which points to the JVM profiles directory as described in the CICS V4.2information center at CICS Transaction Server for z/OS, Version 4 Release 2. Ifthis parameter is not listed, define a new JVMPROFILEDIR to store your JVMprofile.

4. Copy one of the profile files, HBRJVM or HBRJVM41, from the location specifiedby the ++CICSWORKPATH++ variable to the JVMPROFILEDIR directory for yourCICS region. Ensure that the profiles files have appropriate read permissionsset so that CICS can open them.

Note: If you are using the JVM server for another purpose you must mergethe profiles generated profile with the preexisting one. Otherwise, you canreplace any existing profile file with the generated one.

5. Define the CICS resources required by the server:a. Submit the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCSD) job to define

resources required by all CICS versions.b. Run either of the following jobs to define resources specific to your version

of CICS:v If you use CICS TS version 4.2 or later, submit the

++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCSDJ) job.v If you use CICS TS version 4.1, submit the

++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCSD41) job.6. In the CICS system initialization table, add ++CICSLIST++ to the list of

resource definition groups specified by the GRPLIST parameter.7. Edit the CICS region startup JCL to include the zRule Execution Server for

z/OS data sets:a. Add the ++HBRHLQ++.SHBRAUTH library to the STEPLIB concatenation.b. If you are using a DB2 database, ensure that the STEPLIB for your CICS

started task includes the DB2 load data sets, SDSNLOD2 and SDSNLOAD.c. Ensure that the ++HBRHLQ++.SHBRCICS data set is added to the DFHRPL

concatenation.d. Pass runtime variables to the server by adding the following SHBRPARM data

set members to the HBRENVPR DD statement. The HBRCICSD data setmember includes necessary DB2 runtime variables.The following JCL shows the member names://HBRENVPR DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCICSJ)// DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCMMN)// DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCICSD)

e. If you plan to run the Miniloan sample application to verify yourconfiguration, add the following DD statement. The HBRSCEN data setmember contains input values to the Miniloan application.//SCENARIO DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRSCEN)

8. Start the zRule Execution Server for z/OS and the Rule Execution Serverconsole.

9. Start CICS and install the HBRGROUP resources using the followingcommand:CEDA INSTALL GROUP(HBRGROUP)

10. If you are using a database, connect the DB2CONN resource to the databaseby completing the following steps:a. Issue the following CICS command to display the active definition of the

DB2CONN resource:


http://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts42.home.doc/welcomePage/welcomePage.html

CEMT INQUIRE DB2CONN

b. Change the CONNECTST property from Notconnected to Connected.c. If you want CICS to connect to the database automatically at start up, set

the system initialization table (SIT) parameter, DB2CONN=YES.11. Test the configuration by running the HBRC transaction to connect CICS to

zRule Execution Server for z/OS.If CICS succeeds in connecting to the server, message GBRZC9001I is issued. IfCICS fails to connect to the server, message GBRZC9000E is issued with a returncode containing diagnostic information.To disconnect from the server, run the HBRD transaction.See messages for details.

12. Use the console to view the CICS JVM server instance where the zRuleExecution Server for z/OS is running.

Securing zRule Execution Server for z/OS resourcesYou can optionally control access to zRule Execution Server for z/OS resources,files, and functions by using RACF.

Security options:

You can secure all zRule Execution Server for z/OS resources or only specific ones.You also have the option of leaving resources unsecured. The appropriate securitylevel depends on how you use the server.

If you plan to run your zRule Execution Server for z/OS instance in a productionenvironment, you might want to secure some or all of your zRule Execution Serverfor z/OS resources. On the other hand, if you plan to run your server instance in adevelopment or test environment, you might decide to leave resources unsecured.

Note: If you use a security product other than RACF, bypass the followinginstructions and issue the equivalent security commands for your product.

Within the file system, you can secure the following resources:v The working directory so that only authorized user IDs can access internal data.v The installation directory so that only authorized user IDs can access the files

needed to run the server.

Using RACF, you can secure the following resources:v The server resources you use to perform the following tasks:

– Issue zRule Execution Server for z/OS commands from the z/OS console (orequivalent).

– Sign into the Rule Execution Server Console.– Connect to zRule Execution Server for z/OS to execute rulesets.

v A subset of server resources. For example, you can secure access to the RuleExecution Server Console only.

You also have the option of disabling security or running the server withoutsecurity. The topics that follow explain how to configure support for the differentoptions.

Securing access to the working directory and the installation directory:


You can secure access to the working directory and the installation directory forthe server instance so that only authorized user IDs can access them.

The working directory, represented by the ++HBRWORKPATH++ JCL variable,holds data such as installation logs, component details, and trace output. Theinstallation directory, represented by the ++HBRINSTPATH++ variable, containsfiles needed to run the server instance.

Give the server user ID the following permissions:v Read, write and execute permissions to the ++HBRWORKPATH++ directory.v Read and execute permissions to the ++HBRINSTPATH++ directory.

Note: For more information about these variables, see JCL and runtime variables.

Managing server security:

You can enable or disable security for zRule Execution Server for z/OS instances orspecific server resources.

Creating the RACF classes for securing server resources:

Create and activate the RACF classes you need to secure the server resources foryour zRule Execution Server for z/OS server.

About this task

You manage security for zRule Execution Server for z/OS using RACF classes.When you create and activate the HBRADMIN class, server security is enabled forall zRule Execution Server for z/OS instances running on the z/OS system. Userscan then be authorized for certain tasks using the different classes.

Procedure

1. Run the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCRECL) job forevery server in the server group, where HBRSSID_NAME represents asubsystem ID specified in the ++HBRSSIDLIST++ JCL variable. The JCL createsthe following RACF classes:

Table 1. RACF classes for server security

Class Description

HBRADMIN Controls whether server security andsecurity for specific server resources areenabled or disabled.

HBRCONN Specifies the user IDs that are authorized toconnect to the zRule Execution Server forz/OS and execute rulesets. This class isignored if server security is disabled.

HBRCMD Specifies the user IDs that are authorized toissue zRule Execution Server for z/OScommands such as START, STOP, PAUSE orRESUME from the z/OS console (orequivalent). This class is ignored if serversecurity is disabled.



Note: The supplied JCL gives each class a POSIT value of 128. You shouldcustomize this POSIT value for your own local security setup. Additionalinformation on POSIT values can be found in Security Server RACF SecurityAdministrator's Guide.

2. If the BPX.SERVER FACILITY class profile is defined, give the server user IDread access to the class profile using the following commands:PERMIT BPX.SERVER CLASS(FACILITY) ID(<HBRSSID_USER>) ACCESS(READ)SETROPTS RACLIST(FACILITY) REFRESH

where HBRSSID_USER represents the server ID under which the server runs.

Disabling types of security:

You can disable all security for a zRule Execution Server for z/OS server or onlyspecific types of security.

About this task

When you create and activate the HBRADMIN RACF class, server security isenabled for all zRule Execution Server for z/OS servers running on the z/OSsystem.

In some cases, you might want to disable server security for one or more servers.For example, you might not want to secure servers in a development or testenvironment. Alternatively, you might want to disable certain types of security fora server while maintaining other types of security. For example, you might want tocontrol access to the Rule Execution Server console but allow any application toconnect to the server.

To disable a type of security for a server, add the corresponding resource profile tothe HBRADMIN class. The following table lists the resource profiles and the typesof security they disable:

Resource profile Description

<HBRSSID_NAME>.NO.SUBSYS.SECURITY Disables all security for a particular server. If serversecurity is disabled, HBRCONN and HBRCMD classesare not used.

<HBRSSID_NAME>.NO.CONNECT.SECURITY Disables connection security for a particular server, butmaintains other types of security.

<HBRSSID_NAME>.NO.RESCONSOLE.SECURITY Disables console security for a particular server, butmaintains other types of security.

<HBRSSID_NAME>.NO.COMMAND.SECURITY Disables command security for a particular server, butmaintains other types of security.Note: If you disable command security, any user canissue zRule Execution Server for z/OS commands fromthe z/OS console.

To disable security for a single server, set <HBRSSID_NAME> to a subsystem ID inthe ++HBRSSIDLIST++ JCL variable. To manage server security for multipleservers or for the entire server group, specify a wildcard as the subsystem ID. Formore information, see the JCL variable, ++HBRSSIDLIST++, in JCL and runtimevariables.




If you are managing multiple servers, you can use a wildcard as describedpreviously to specify the subsystem ID, HBRSSID_NAME, in the resource profilereferred to in the following procedure.

Procedure

1. Add the resource profile to the HBRADMIN class using the followingcommand:RDEFINE HBRADMIN <RESOURCE_PROFILE> UACC(NONE)

where <RESOURCE_PROFILE> represents one of the resource profiles listed inthe previous table.

2. Refresh the HBRADMIN class using the following command:SETROPTSRACLIST(HBRADMIN)REFRESH

Managing connection security:

Use connection security to ensure that only authorized user IDs can connect tozRule Execution Server for z/OS to execute rulesets.

About this task

Connection security uses the HBRCONN RACF class to authorize user IDs toconnect to the server. However, if the HBRADMIN class includes either of thefollowing resource profiles, connection security for the server is disabled and theHBRCONN class is ignored.v <HBRSSID_NAME>.NO.SUBSYS.SECURITYv <HBRSSID_NAME>.NO.CONNECT.SECURITY

To manage connection security for a single server, set HBRSSID_NAME to asubsystem ID in the ++HBRSSIDLIST++ JCL variable. To manage connectionsecurity for multiple servers or for the entire server group, specify a wildcard asthe subsystem ID. For more information, see the JCL variable, ++HBRSSIDLIST++,in JCL and runtime variables.

Note: In some cases, you might want to disable connection security but maintainthe other types of security. See “Disabling types of security” on page 26 for moreinformation.

To implement connection security, authorize the user ID under which the serverruns and the user IDs of any applications that execute rulesets.

If you are managing multiple servers, you can use a wildcard as describedpreviously to specify the subsystem ID, HBRSSID_NAME in the followingprocedure.

Procedure

1. Authorize the server user ID:a. Create the resource profile, HBRSSID_NAME, in the HBRCONN RACF

class. Use the following command: RDEFINE HBRCONN <HBRSSID_NAME>UACC(NONE)

b. Give the server user ID UPDATE access to the HBRSSID_NAME resourceprofile. Use the following command: PERMIT <HBRSSID_NAME>CLASS(HBRCONN) ID(<HBRSSID_USER>) ACCESS(UPDATE) where<HBRSSID_USER> represents the server user ID.



Note: The zRule Execution Server for z/OS will fail to initialize unless<HBRSSID_USER> has UPDATE access to this profile.

c. Refresh the HBRSSID_NAME resource profile using the following command:SETROPTS RACLIST(HBRCONN) REFRESH

2. Authorize the applications:a. Give READ access to the HBRSSID resource profile to each user ID you

want to authorize. Use the following command: PERMIT <HBRSSID_NAME>CLASS(HBRCONN) ID(<USER_ID>) ACCESS(READ)

Note: For batch jobs, <USER_ID> is the RACF user ID used by the batchjob. For CICS transactions, <USER_ID> is the user ID assigned to the CICSaddress space.

b. Refresh the HBRSSID_NAME resource profile using the followingcommand: SETROPTS RACLIST(HBRCONN) REFRESH

Managing console security:

Use console security to ensure that only authorized user IDs can access the RuleExecution Server Console.

About this task

Console security controls the ability to sign into the Rule Execution Server Console.If console security is enabled, users must enter a user ID and password to sign in.If the HBRADMIN class includes either of the following resource profiles, consolesecurity for the server instance is disabled and any other console-related resourceprofiles in the HBRADMIN class are ignored:v <HBRSSID_NAME>.NO.SUBSYS.SECURITYv <HBRSSID_NAME>.NO.RESCONSOLE.SECURITY

To manage console security for a single server, set <HBRSSID_NAME> to asubsystem ID in the server group specified by the ++HBRSSIDLIST++ JCL variable.To manage console security for multiple servers or for the entire server group,specify a wildcard as the subsystem ID. For more information, see the JCL variable,++HBRSSIDLIST++, in JCL and runtime variables.

Note: In some cases, you might want to disable console security but maintain theother types of security. See “Disabling types of security” on page 26 for moreinformation.

The following table lists the profiles and the roles they represent. Roles are listedin order of increasing authority.

Resource profile Role description

<HBRSSID_NAME>.ROLE.RESMON Users with monitoring rights are onlyallowed to view and explore RuleApps,rulesets, decision services, Execution Units,and statistics. They are not allowed tomodify them. They can also select a traceconfiguration and view and filter traceinformation in Decision Warehouse (appliesonly to Rule Execution Server on WebSphereApplication Server for z/OS).



Resource profile Role description

<HBRSSID_NAME>.ROLE.RESDEP In addition to monitoring rights, users withdeploying rights are allowed to deployRuleApp archives and to edit and removeentities (RuleApps, rulesets, decisionservices, Java Execution Object Module(XOM) resources and libraries), and rundiagnostics.

<HBRSSID_NAME>.ROLE.RESADMIN Users with administrator rights have fullcontrol over the deployed resources andaccess to information on the server. They cancarry out the following actions:

v Deploy, browse, and modify RuleApps,Java XOM resources and libraries.

v Monitor the decision history, purge, andback up the history.

v Select a trace configuration, view andfilter trace information, and clear traceinformation in Decision Warehouse.

v Run diagnostics and view serverinformation.

Procedure

1. Define each resource profile shown in the previous table to the HBRADMINclass. Use the following command: RDEFINE HBRADMIN <RESOURCE_PROFILE>UACC(NONE)

2. Assign each user ID to one of the resource profiles using the followingcommand: PERMIT <RESOURCE_PROFILE> CLASS(HBRADMIN) ID(<USER_ID>)ACCESS(UPDATE)

3. Refresh the HBRADMIN class using the following command: SETROPTSRACLIST(HBRADMIN) REFRESH

Managing command security:

Use command security to ensure that only authorized users can issue zRuleExecution Server for z/OS commands from the z/OS console.

About this task

Command security uses the HBRCMD RACF class to authorize user IDs to issuezRule Execution Server for z/OS commands. However, if the HBRADMIN classincludes either of the following resource profiles, command security for the serverinstance is disabled and the HBRCMD class is ignored:v <HBRSSID_NAME>.NO.SUBSYS.SECURITYv <HBRSSID_NAME>.NO.COMMAND.SECURITY

To manage command security for a single server, set <HBRSSID_NAME> to asubsystem ID in the server group specified by the ++HBRSSIDLIST++ JCL variable.To manage command security for multiple servers or for the entire server group,specify a wildcard as the subsystem ID. For more information, see the JCL variable,++HBRSSIDLIST++, in JCL and runtime variables.



Note: In some cases, you might want to disable command security but maintainthe other types of security. See “Disabling types of security” on page 26 for moreinformation.

To enable zRule Execution Server for z/OS command security, define a resourceprofile to the HBRCMD class for each command you want to secure. Then,authorize each user ID individually to issue each command. For example, youmust separately authorize a user ID to issue the PAUSE command and the RESUMEcommand.

The following table lists the resource profiles and the commands that they control.

Resource profile Command

<HBRSSID_NAME>.SET.TRACE SET TRACE

<HBRSSID_NAME>.SET.RESCONSOLE SET RES-CONSOLE

<HBRSSID_NAME>.PAUSE PAUSE

<HBRSSID_NAME>.RESUME RESUME

See Commands for more information.

If you are managing multiple servers, you can use a wildcard as describedpreviously to specify the subsystem ID, HBRSSID_NAME, in the resource profilereferred to in the following procedure.

Procedure

1. Define to the HBRCMD class each resource profile shown in the previous table.Use the following command: RDEFINE HBRCMD <RESOURCE_PROFILE> UACC(NONE)

2. Authorize each user ID to issue each command. Use the following RACFcommand: PERMIT <RESOURCE_PROFILE> CLASS(HBRCMD) ID(<USER_ID>)ACCESS(UPDATE) where <RESOURCE_PROFILE> is a resource profile listed inthe previous table.The following example shows how to authorize user ID, SYSPROG1, to issuethe SET TRACE command: PERMIT <HBRSSID_NAME>.SET.TRACE CLASS(HBRCMD)ID(SYSPROG1) ACCESS(UPDATE)

3. Refresh the HBRCMD class. Use the following command: SETROPTSRACLIST(HBRCMD) REFRESH

Starting a new server instanceStart one or more newly-created zRule Execution Server for z/OS instances.

About this task

Start a zRule Execution Server for z/OS instance and open the Rule ExecutionServer Console.

Note: To start a server instance running on CICS JVM server, start your CICSsystem instead.

Procedure1. At the z/OS console (or equivalent) command line, issue the command, START

<HBRSSID_NAME>MSTR, where HBRSSID_NAME represents a subsystem ID in theserver group defined by the ++HBRSSIDLIST++ JCL variable. Repeat the


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

comand for each additional server in ++HBRSSIDLIST++. When the serverstarts, the zRule Execution Server for z/OS console is immediately accessible.

2. Display the Rule Execution Server Console by opening a browser andnavigating to http://<hostname>:++HBRCONSOLEPORT++/res, where hostname isthe TCP/IP name of the z/OS machine where you are running zRule ExecutionServer for z/OS and ++HBRCONSOLEPORT++ is the HTTP port you specify toaccess the console from your web browser.

3. Sign in to the console using your zRule Execution Server for z/OS user ID andpassword.If you are unable to sign in, see Troubleshooting zRule Execution Server forz/OS.

Verifying the configurationVerify that you have successfully configured your new instance or server group.

About this task

Use diagnostic tests to verify that you have successfully configured your newinstance or server group.

Procedure1. Display the Rule Execution Server console by opening a browser and

navigating to http://<hostname>:++HBRCONSOLEPORT++/res, where hostname isthe TCP/IP name of the z/OS machine where you are running the server and++HBRCONSOLEPORT++ is the HTTP port used by the console tocommunicate with the server.

2. Sign in to the console using a user ID in the resAdministrators group. If youcannot sign in, make sure you have the required authorization. For moreinformation, see Troubleshooting.

3. For the new server instance or for each server in the server group:a. Click the Diagnostics tab.b. Click Run Diagnostics. A report lists the diagnostic tests that ran.c. Click Expand All to view the details.

Configuring Rule Execution Server on WebSphere ApplicationServer for z/OS

To use Rule Execution Server on WebSphere Application Server for z/OS, you setup security, then you deploy and configure either manually through DB2 orautomatically by running scripts, and optionally you complete the configurationfor WebSphere MQ or for a cluster.

Configuring security on WebSphere Application Server for z/OSSecurity configuration on WebSphere Application Server for z/OS can use the localoperating system registry. Work with your z/OS system administrator to define theappropriate users, groups, and roles.

WebSphere Application Server for z/OS uses various kinds of user registries: localoperating system, standalone Lightweight Directory Access Protocol (LDAP)registry, a standalone custom registry, and federated repositories. Only one type ofuser registry can be active. This active registry is shared by all product serverprocesses. On Linux, WebSphere Application Server provides a custom registrysample named FileRegistrySample. On z/OS, WebSphere Application Server canuse the local operating system registry. In this scenario, users, groups and roles are


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

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

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

defined outside of WebSphere Application Server. Contact your z/OS systemadministrator to know which security registry and settings you require, and letthem know which users and groups you need at the operating system level.

You must enable WebSphere Application Server administrative security andapplication security. You can deactivate the operating system check in theadvanced properties of the Local operating system registry in WebSphereApplication Server for z/OS. However, if you do deactivate this check, you mustmap the roles.

For more information, see Configuring local operating system registries.

Using RACF as your security repository:

Install Rule Execution Server for z/OS on WebSphere Application Server whensecurity is managed on the WebSphere system by using the Resource AccessControl Facility (RACF).

Step 1: Checking the existing setup:

You must confirm that WebSphere Application Server for z/OS uses the RACFlocal operating system security repository before proceeding. Security is configuredwhen the application server is installed.

Before you begin

Make sure WebSphere Application Server for z/OS is installed to use RACF beforeyou start change settings through the Integrated Solutions Console.

About this task

When you install WebSphere Application Server for z/OS, you must set a numberof options for storing security information. The two most common methods consistof using a federated repository or a local operating system repository, for example,RACF. When WebSphere Application Server for z/OS uses a RACF repository,security access for applications is managed in RACF through the z/OS systemadministrator (or whomever is in charge of RACF). For more information aboutRACF commands, refer to the z/OS V1R12.0 Security Server RACF CommandLanguage Reference SA22-7687-15.

Note: With application security, Rule Execution Server applications use EJBROLErole values to determine which users and groups are allowed access and whattasks they can perform. These roles must be defined in RACF. See “Step 2:Creating RACF EJB roles” on page 33.

Procedure

1. In the side panel, open Security > Global security.2. If Local operating system is already selected under Current realm definition,

make sure Enable application security is selected.If you select Enable application security you must click Apply and Save toapply the changes to the master configuration.

Note: Perform the following steps after your WebSphere Application Serverfor z/OS administrator has set up this WebSphere Application Server for z/OSinstance to use the local operating system security provider.


http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.express.doc/info/exp/ae/tsec_localos.html?resultof=%22%6f%70%65%72%61%74%69%6e%67%20%73%79%73%74%65%6d%20%72%65%67%69%73%74%72%69%65%73%22%20

http://publib.boulder.ibm.com/infocenter/zos/v1r12/topic/com.ibm.zos.r12.icha400/toc.htm

http://publib.boulder.ibm.com/infocenter/zos/v1r12/topic/com.ibm.zos.r12.icha400/toc.htm

a. Click Security Configuration Wizard.b. In Step 1, to specify the level of protection, select Enable application

security and click Next.c. In Step 2, select Local operating system and click Next.d. In Step 3, set the name in the Primary administrative user name field and

click Next.e. In Step 4, review the security configuration summary and click Finish.f. Click Save to save the changes to the master configuration.g. Restart WebSphere Application Server for z/OS.

You must log into the Integrated Solutions Console as the primaryadministrative user.

3. Check whether the HLQ property has been set.If it is not set and you expect it to be, confirm the situation with you systemadministrator.When you use RACF, you can set a high level qualifier (HLQ) at installationtime to differentiate between separate installations of WebSphere ApplicationServer for z/OS.a. Open Security > Global security, then click Custom properties.b. In the list of properties, check for the HLQ property named

com.ibm.security.SAF.profilePrefix and make a note of its value.

What to do next

You can now move on either by following the steps in “Configuring RuleExecution Server on WebSphere Application Server for z/OS with wsadminscripts” on page 50 or by using the WebSphere Application Server for z/OSIntegrated Solutions Console to complete the remaining installation steps, startingwith “Step 2: Configuring JDBC” on page 41.

Step 2: Creating RACF EJB roles:

Create the standard set of RACF EJB roles to allow users various access rights inRule Execution Serverr.

About this task

Rule Execution Server uses a standard set of roles: resAdministrators,resDeployers and resMonitors to grant different sets of users specific access rights.A Java EE group also represents a category of users, but it has a different scopefrom a role. A group is designated for the entire server, whereas a role covers onlya specific application in a server.

You can issue commands from the TSO command line or you can use a JCL batchscript.

In the following steps, <hlq> is the value that you assigned to the HLQ propertynamed com.ibm.security.SAF.profilePrefix in 3b of “Step 1: Checking theexisting setup” on page 32. If the HLQ property contains a value, it should befollowed by a period.

Note: If you issue the commands from ISPF, you must use option 6, TSO andwkstn cmds, because profiles are case sensitive.


Procedure

To create RACF EJB roles:1. Create the resAdministrators role with the following command:

RDEF EJBROLE <hlq>resAdministrators

2. Create the resDeployers role with the following command:RDEF EJBROLE <hlq>resDeployers

3. Create the resMonitors role with the following command:RDEF EJBROLE <hlq>resMonitors

Step 3: Creating RACF groups:

After you have defined the RACF EJB roles, you can define the RACF groups.

About this task

After you have defined the RACF EJB roles, you define the names of the RACFgroups to use for resAdministrators, resDeployers, and resMonitors access.v If these groups already exist, you can skip this step.v If new groups are required, create three new groups by using TSO commands.

Procedure

To create RACF groups:1. Use the following command to create the group to use for the

resAdministrators role:ADDGROUP RESADM

This example uses the group name RESADM, but you can use any name for thegroup.

2. Use the following command to create the group to use for the resDeployersrole:ADDGROUP RESDEP

This example uses the group name RESDEP, but you can use any name for thegroup.

3. Use the following command to create the group to use for the resMonitors role:ADDGROUP RESMON

This example uses the group name RESMON, but you can use any name for thegroup.

Step 4: Giving groups access to EJB roles:

Give the RACF groups access to the RACF EJB roles.

Before you begin

You have defined the <hlq> parameter in “Step 2: Creating RACF EJB roles” onpage 33.

About this task

After you have assigned users to appropriate RACF groups, give the groups accessto the RACF EJB roles.


Procedure

To give RACF groups access to RACF EJB roles, enter the following TSOcommands:1. Use the following commands to give members of the administrators group an

administrative role:PE <hlq>resAdministrators CLA(EJBROLE) ID(RESADM) ACCESS(READ)PE <hlq>resDeployers CLA(EJBROLE) ID(RESADM) ACCESS(READ)PE <hlq>resMonitors CLA(EJBROLE) ID(RESADM) ACCESS(READ)

This example uses the group name RESADM, but you can use any name for thegroup.

2. Use the following commands to give members of the deployers group a deployrole:PE <hlq>resDeployers CLA(EJBROLE) ID(RESDEP) ACCESS(READ)PE <hlq>resMonitors CLA(EJBROLE) ID(RESDEP) ACCESS(READ)

This example uses the group name RESDEP, but you can use any name for thegroup.

3. Use the following command to give members of the monitors group a monitorrole:PE <hlq>resMonitors CLA(EJBROLE) ID(RESMON) ACCESS(READ)

This example uses the group name RESMON, but you can use any name for thegroup.

Step 5: Giving users access to groups:

Assign users to RACF groups.

About this task

After you have assigned RACF groups access to the RACF EJB roles, you giveindividual users access to Rule Execution Server by enter the following TSOcommands to assign them membership in a group.

Procedure

To assign individual users membership in groups:1. Use the following command to assign user lucinda membership in the RESADM

group:CONNECT lucinda GROUP(RESADM)

This example uses the group name RESADM, but you can use any group name.2. Use the following command to assign user adam membership in the RESDEP

group:CONNECT adam GROUP(RESDEP)

This example uses the group name RESDEP, but you can use any group name.3. Use the following command to assign user aurelie membership in the RESMON

group:CONNECT aurelie GROUP(RESMON)

This example uses the group name RESMON, but you can use any group name.4. Use the following command to update the RACF system to activate the

changes:SETR RACLIST(EJBROLE) REFRESH


Configuring RACF security for Rule Execution Server using a JCL batch script:

Use a JCL batch script to configure RACF security for Rule Execution Server.

About this task

Instead of creating RACF EJB roles and RACF groups manually, you can customizeand submit the JCL batch script provided.

Procedure

1. Customize the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRDCRCF) data setmember according to the instructions in the member. ++HBRWORKDS++represents the high-level qualifier assigned to the working data sets and<HBRSSID_NAME> represents a subsystem ID in the server group defined bythe ++HBRSSIDLIST++ JCL variable.

2. In the HBRDCRCF member, change the RTSADM, RTSCONF, and RTSUSER RACFgroup names to those you are using.

3. Submit the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRDCRCF) job.4. Give users access to the RACF groups as described in “Step 5: Giving users

access to groups” on page 35).

What to do next

Finish the installation by completing one of the following procedures:v “Configuring Rule Execution Server on WebSphere Application Server for z/OS

with DB2” on page 39v “Configuring Rule Execution Server on WebSphere Application Server for z/OS

with wsadmin scripts” on page 50

Using a federated repository:

Use the following steps if you configure Rule Execution Server on WebSphereApplication Server for z/OS managing security through a federated repository. Youmap Rule Execution Server users to WebSphere Application Server roles to ensurethe correct security levels.

Proceed as follows:1. Confirm that WebSphere Application Server for z/OS is configured for use with

federated repositories. A federated repository is configured when theapplication server is installed.

2. Complete the installation either by following the steps in either “ConfiguringRule Execution Server on WebSphere Application Server for z/OS with DB2”on page 39 or “Configuring Rule Execution Server on WebSphere ApplicationServer for z/OS with wsadmin scripts” on page 50.

Step 1: Creating users and groups:

Create users and groups and assign them roles using a user registry with afederated repository.

Before you begin

If you do not have groups and users defined or if you want to define new groupsand users, proceed with the following steps. If you already have suitable groups


and users defined that can match the expected roles, skip this procedure andconnect users and groups to their appropriate roles when you deploy yourapplications.

About this task

WebSphere Application Server uses various kinds of user registries (OS, LDAP, orCustom). You can configure a user registry with a federated repository.

The following variables in the ++HBRHLQ++.SHBRPARM(HBRINST) member create thespecified users and groups in the local repository, which map to the RuleExecution Server console in WebSphere Application Server.

Table 2. Variables for Rule Execution Server users and groups

Variable Default value Description

++RESADMIN++ resAdministrators The administrator user groupfor the Rule ExecutionServer.

++RESDEPLOY++ resDeployers The deployer user group forthe Rule Execution Server.

++RESMONITOR++ resMonitors The monitor user group forthe Rule Execution Server.

++RESADMINUSER++ resAdmin An admin user for the RuleExecution Server.

++RESDEPLOYUSER++ resDeployer A deployer user for the RuleExecution Server.

++RESMONITORUSER++ resMonitor A monitor user for the RuleExecution Server.

In most cases, the default values are sufficient, but if you want to use customgroups and add other users you can change these values. The user passwords areset to the same as the user id. You can add new users or edit these users in theWebSphere Application Server console under Users and Groups.

Procedure

To configure a user registry with a federated repository:1. Log in to the Integrated Solutions Console.2. In the side panel open Security > Global security.3. Configure 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 and 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 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.

You must log into the Integrated Solutions Console as the primaryadministrative user. The secure port is used, for examplehttps://example.hursley.ibm.com:1234/ibm/console/logon.jsp

4. In the side panel open Users and Groups > Manage Groups, and clickCreate.

5. Enter resAdministrators as the group name, type a description if required,and click Create.

6. Click Create Like and create another group named resDeployers. Type adescription if required. Click Create.

7. Click Create Like again and enter another group named resMonitors. Type adescription if required. Click Create. Click Close.

8. In the side panel open Users and Groups > Manage Users.Click Create.

9. Enter resAdmin as the User ID with a password resAdmin. Also specify thegiven name and last name.

10. Click Group Membership, then click Search. Select the resAdministrators,resDeployers and resMonitors groups and click Add. Click Close, then clickCreate and Close again.

11. Create another user named resDeployer with password resDeployer. Repeatthe previous step and assign the user to the resDeployers and resMonitorsgroups.Then create a user named resMonitor with password resMonitor. Repeat theprevious step and assign the user to the resMonitors group.

12. Restart your application server or your deployment manager.

Step 2: Mapping the resAdministrators group to the Monitor role:

Map the resAdministrators users to the WebSphere Monitor role when you areusing a federated repository so Rule Execution Server has sufficient securitycredentials to access MBeans.

About this task

To access the MBeans of the Rule Execution Server model, an application musthave sufficient security credentials, restricted to the Monitor role in the WebSphereauthentication system.

Rule Execution Server users can be given access to the MBeans of the model byconfiguring a mapping between the resAdministrators group declared in thecustom registry and the Monitor role.

Procedure

1. In the Integrated Solutions Console open Users and Groups > Administrativegroup roles.

2. Click Add. For Role(s) select Monitor, then click Search and move the entrybeginning with resAdministrators from the Available column to the Mappedto role column (use the arrow button).Click OK.

3. Click the Save directly to the master configuration.


4. Restart your application server or your deployment manager.

Results

After you complete this section you can either complete the installation byfollowing the steps in “Configuring Rule Execution Server on WebSphereApplication Server for z/OS with wsadmin scripts” on page 50, or by using theIntegrated Solutions Console to complete the remaining installation steps startingwith “Step 2: Configuring JDBC” on page 41.

Configuring Rule Execution Server on WebSphere ApplicationServer for z/OS with DB2After you have set up security, one way of configuring Rule Execution Server on anew instance of WebSphere Application Server for z/OS is to proceed manuallywith DB2. Basically, you set up persistence for the resources, create a JDBCprovider, and deploy the provided archives for this server.

Before you start:

Before you complete the configuration, review the software prerequisites andconfiguration steps for Rule Execution Server on WebSphere Application Server forz/OS.

Before you start a WebSphere Application Server for z/OS configuration, you mustcomplete the steps in “Performing the initial configuration” on page 3.

You can use wsadmin scripts to configure the WebSphere Application Server forz/OS as an alternative to using the WebSphere Application Server IntegratedSolutions Console. For more information, refer to “Configuring Rule ExecutionServer on WebSphere Application Server for z/OS with wsadmin scripts” on page50.

Specific integration extension are available. For more information, refer to IBM®

Support Pacs page.

Software Prerequisites

You must have installed the following software before you configure RuleExecution Server:v WebSphere Application Server for z/OSv DB2 for z/OS Version 9.1 or Version 10v Rule Execution Server on WebSphere Application Server for z/OS.

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

tablesv Authority to start and stop the WebSphere Application Serverv Confirmation that WebSphere Application Server for z/OS is using the local

operating system security repository (RACF) before proceeding. Security isconfigured at the time WebSphere Application Server is installed.


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

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

Configuration steps

The following table summarizes the steps to configure Rule Execution Server onWebSphere Application Server for z/OS.

Configuration Steps Required

“Step 1: Configuring security on WebSphere ApplicationServer for z/OS”

You can now either complete the configuration by following the steps in “Configuring RuleExecution Server on WebSphere Application Server for z/OS with wsadmin scripts” onpage 50, or by using the Integrated Solutions Console to complete the followingconfiguration steps.

“Step 2: Configuring JDBC” on page 41

“Step 3: Creating a data source and connection pool” onpage 42

“Step 4: Setting the component and container managedaliases for the data source” on page 43

“Step 6: Testing the connection to the database” on page 44

“Step 7: Deploying the Rule Execution Server ManagementEAR” on page 44

“Step 5: Setting the currentSQLID” on page 43

“Step 8: Deploying the Rule Execution Server MBeandescriptors” on page 45

“Step 9: Deploying the XU RAR” on page 46

“Step 10: Deploying the hosted transparent decision serviceEAR” on page 48

Recommended

“Step 11: Setting the web container custom property” onpage 49

If you deploy the hostedtransparent decision serviceEAR you must complete this

step.

Verifying the deployment and configuration Recommended

Step 1: Configuring security on WebSphere Application Server for z/OS:

When you choose to configure Rule Execution Server on WebSphere ApplicationServer for z/OS by using DB2, the first step consists in setting up administrativesecurity and application security.

Rule Execution Server access is managed by the application server security. Toaccess Rule Execution Server in WebSphere Application Server for z/OS, you mustdefine a user registry as explained in “Configuring security on WebSphere


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

Application Server for z/OS” on page 31. Two examples are provided, one usingRACF, the other using a federated repository.

For information on WOLA security configuration:v WebSphere Application Server 7.0: WebSphere Application Server 7 Information

Centerv WebSphere Application Server 8.0: WebSphere Application Server 8 Information

Center

Step 2: Configuring JDBC:

Create a JDBC provider in WebSphere Application Server for z/OS to enable RuleExecution Server.

Setting WebSphere Application Server for z/OS variables:

Set environment variables to configure the JDBC connection.

About this task

To create JDBC, you must first set WebSphere Application Server for z/OSvariables.

Procedure

1. Navigate to Environment > WebSphere variables and clickDB2UNIVERSAL_JDBC_DRIVER_PATH.

2. In the Value field, type the directory location for db2jcc.jar anddb2jcc_license_cisuz.jar.For example: /usr/lpp/db2910/classes

3. Click Apply, then click Save.4. Click DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH.5. In the Value field, type the native library path.

For example: /usr/lpp/db2910/lib6. Click Apply, then click Save.

Creating the J2C authentication alias:

After you have set the variables for WebSphere Application Server for z/OS, youcreate the J2C authentication alias.

Procedure

To create the J2C authentication alias:1. Navigate to Security > Global security and expand Java Authentication and

Authorization Service.2. Click J2C authentication data, then click New.3. Type resDB2user in the Alias field.4. Type an active RACF user ID in the User ID field.5. Type the password for the RACF User ID in the Password field.6. Click Apply, then click Save.

Creating the JDBC provider:


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




The final step in configuring the JDBC is to create the JDBC provider.

About this task

After you have set variables for WebSphere Application Server for z/OS and createthe J2C authentication alias, you finish configuring JDBC by creating the JDBCprovider.

Note: You can install the JDBC provider onto the cell, node, cluster, or serverlevel. This procedure documents installation at node level.

Procedure

1. Navigate to Resources > JDBC > JDBC providers.2. In the Scope side panel, select Node=xxx, Server=yyy, where xxx is the name

of your node and yyy the name of your server, and then click New.3. In Step 1, select the following values:

Option Description

Database type DB2

Provider type DB2 Universal JDBC Driver Provider

Implementation type Select XA datasource, then type a name suchas, for example, DB2 Universal JDBC DriverProvider for RES.

4. Click Next.5. Skip Step 2.

A summary is provided in Step 3.6. Check that the class path to the JAR file of your driver and the implementation

class are correct. Default values are usually sufficient.7. Click Finish and Save to save the changes to the master configuration, making

sure that the Synchronize changes with Nodes check box is selected.

Step 3: Creating a data source and connection pool:

Create a connection pool and a data source in WebSphere Application Server forz/OS to enable Rule Execution Server.

About this task

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

Procedure

1. In the Integrated Solutions Console, open Resources > JDBC > Data sources.2. In the Scope side panel, select the scope that you set for the JDBC provider in

“Step 2: Configuring JDBC” on page 41.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, if


you entered resdatasource as the data source name, set the JNDI name tojdbc/resdatasource. Otherwise, Rule Execution Server cannot use the datasource.

4. In Step 2, select the JDBC provider that you created in “Step 2: ConfiguringJDBC” on page 41 and click Next.

5. In Step 3, enter the specific database properties for the data source:

Driver type4

Database nameType your database name, for example DSN910GP.

Server nameType you server name.

Port numberType your port number.

6. Clear the Use this data source in container managed persistence (CMP)option, then click Next.

7. In Step 4, set up any required security aliases and click Next.See “Step 4: Setting the component and container managed aliases for the datasource” for details of the procedure. In Step 5, a summary of the data source isprovided.

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

Step 4: Setting the component and container managed aliases for the datasource:

Set the aliases for resDB2user on the Rule Execution Server data source.

Before you begin

You created the resDB2user alias in “Creating the J2C authentication alias” on page41.

About this task

As part of setting up security, you set the authentication aliases managed,respectively, by the component and by the container for the resDB2user alias onresdatasource.

Procedure

1. Open Resources > JDBC and Data sources and click resdatasource.2. In the Security settings section for Component-managed authentication alias,

select the <node name>/resDB2user alias, where <node name> is the name of theWebSphere Application Server node on which you are configuring RuleExecution Server.

3. Select <node name>/resDB2user for the Container-managed authentication alias.4. Click Apply and Save to save directly to the master configuration.

Step 5: Setting the currentSQLID:

Set the currentSQLID parameter for resdatasource.


Procedure

1. Open Resources > JDBC and Data sources and click resdatasource.2. Under Additional Properties, click Custom properties, then click

currentSQLID and type the name required in the Value field.For a single server, the value is the schema name of your tables. For example:HBR1.

3. Click Apply and Save directly to the master configuration.

Step 6: Testing the connection to the database:

It is good practice to test the connection before continuing the configuration.

About this task

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

Procedure

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

2. Select the check box next to the data source that you want to test and click Testconnection.The status of the connection is indicated at the top.

Step 7: Deploying the Rule Execution Server Management EAR:

Deploy the Rule Execution Server EAR file on WebSphere Application Server.

Procedure

1. Open the Integrated Solutions Console.2. Open Applications > New Application and click New Enterprise

Application.3. In the panel, select Remote file system, browse to the following file, and click

Next.v On WebSphere Application Server V7.0: <InstallDir>/executionserver/

applicationservers/WebSphere7/jrules-res-management-WAS7-for-zos.ear

v On WebSphere Application Server V8.0: <InstallDir>/executionserver/applicationservers/WebSphere8/jrules-res-management-WAS8-for-zos.ear

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

Generate Default Bindings check box, and 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, proceed as follows:

v If you have only one server, skip this step.v If you have more than one server, select the server to which you want to

deploy the application, select the check box for Rule Execution ServerConsole and click Next.

9. In Step 3 through Step 8, click Next to accept the default settings.After Step 6, you receive a warning if you have not deployed a XU RAR yet.You can ignore this warning.


10. Depending on whether or not you use an RACF repository, proceed asfollows:v If you use an RACF repository, ignore this step.v If you do not use an RACF repository, click Step 9: Map security roles to

users or groups to map the security roles to users and groups:a. Select the check box next to the resAdministrators role.b. Click Map groups and click Search.

The groups are shown in a column titled Available.c. Select the resAdministrators item as follows:

1) Click resAdministrators under Available.2) Click the arrow button to move resAdministrators to the Selected

column.d. Click OK to return to the Mapping Users to Roles page.e. Repeat 10a through 10d to map the resDeployers and resMonitors roles

for the other groups, making sure that only the check box next to the rolethat you are assigning is selected.

After you have completed the assignments, they are shown as follows:

Role Mapped groups

resAdministrators resAdministrators

resDeployers resDeployers

resMonitors resMonitors

11. In Step 10 and Step 11, click Next to accept the default settings.Step 12 provides a summary.

12. Click Finish.13. When installation has completed, open Application > Application Types >

WebSphere enterprise applications.14. Click ILOG Rule Execution Server.15. Click Manage Modules.16. Click Rule Execution Server Console.17. Under General Properties, for Class loader order, select Classes loaded with

local class loader first (parent last).18. Click OK, then click Save to save directly to the master configuration.19. In the panel, open Applications > Application Types > WebSphere

enterprise applications.20. In the Enterprise Applications page, select the check box next to Rule

Execution Servers and click Start to start the application.

Step 8: Deploying the Rule Execution Server MBean descriptors:

To configure Rule Execution Server for WebSphere Application Server, you mustalso deploy the MBean descriptors.

Before you begin

Make sure you give the application server process enough access right to read thejrules-mbean-descriptors.jar file. For example, change the permissions on thefile using a chmod 777 command.


About this task

The Rule Execution Server architecture is based on the Java Management Extension(JMX) API. MBeans are Java objects used by the JMX API. To configure RuleExecution Server for WebSphere Application Server, you must deploy the MBeandescriptors, either globally for all Rule Execution Server instances or for a singleRule Execution Server instance.v To deploy globally, copy the <InstallDir>/executionserver/lib/jrules-mbean-

descriptors.jar file to the <WAS_HOME>/lib directory.v To deploy to a targeted server instance, follow the procedure below.

Procedure

To deploy MBean descriptors:1. Open the Integrated Solutions Console.2. In the panel, open Servers > Server Types > WebSphere application servers.3. In the Application servers pane, click the name of your server.4. Under Server Infrastructure, expand Java and Process Management and click

Process definition.

Note: In WebSphere Application Server for z/OS, an additional layer providesthree resources that can be administered: Adjunct, Control, and Servant. If youare working in that environment, select the Servant.

5. Under Additional Properties, click Java Virtual Machine.6. In the Classpath field, add <InstallDir>/executionserver/lib/jrules-mbean-

descriptors.jar.7. Click OK, then Save to save the changes directly to the master configuration.

Step 9: Deploying the XU RAR:

Deploy the Execution Unit (XU) RAR on WebSphere Application Server for z/OS.

About this task

This phase of the Rule Execution Server configuration consists in deploying theExecution Unit (XU) resource adapter archive (RAR) on WebSphere ApplicationServer for z/OS and add the properties by which to identify it. The RAR filecontains the XU and the persistence layer.

In the following procedure, <version_number> refers to the version of WebSphereApplication Server for z/OS to which you deploy the XU RAR.

Important: In some cases, because of your application constraints, you might haveto deploy the XU inside the application. It is your decision to choose theappropriate deployment mode of the XU: either embed it into the EAR or deploy itas a global connector. In any case, be aware of the following consequences.v When the XU is deployed as a global connector:

– The deployed Java EE applications might use its third-party libraries (such asASM) instead of the libraries deployed in the application server.

– Use a parent last setting for the XU Java EE application if your Java EEapplication does not support the version of the third-party librariesdistributed with Decision Server. If you cannot use a parent last setting, youmight need to embed the XU into the EAR that executes the rules.


v If you choose an embedded XU packaging, use a parent last setting for thecode library if the third-party libraries version deployed at the level of theapplication-server code library are not compatible with the XU.

Procedure

1. Open the Integrated Solutions Console.2. In the panel, open Resources > Resource Adapters and click Resource

adapters, then click Install RAR.3. In the panel, select Remote file system and Browse to the location in UNIX

System Services (USS) of z/OS where the archives reside:<InstallDir>/executionserver/applicationservers/WebSphere<version_number>/jrules-res-xu-WAS<version_number>.rar

4. In Scope, select the node where you want to install the XU RAR file and clickNext.

5. On the General Properties page, set the name for the XU, such as ILOG RES XUResource Adapter, and click OK.

6. Navigate to the created XU resource adapter and change the scope to view theadapter.

7. Under Additional Properties, click J2C connection factories and New.8. Enter the following values:

v Name: xu_cfv JNDI name: eis/XUConnectionFactory

9. Click OK and Save to save the changes to the master configuration.10. Optional: If necessary, you can define more than one XU resource adapter.

Additional XU resource adapters are required when you have more than onenode in your environment or you want to isolate the developmentenvironment and testing environment in one single node. On WebSphereApplication Server for z/OS, you can install the XU resource adapter at thenode level and then you can create another copy of the resource adapter thathas a specific server or cluster as the scope.For example, to define on the server level a XU resource adapter that hasalready been installed at the node level:a. In the panel, open Resources > Resource Adapters and click Resource

adapters.b. Select the scope Node=xxx, Server=yyy, where xxx is the name of your

node, yyy is the name of your server.c. Click New and enter the name of the XU as XU.d. In Archive Path, select ${CONNECTOR_INSTALL_ROOT}/jrules-res-xu-

WAS<version_number>.rar.e. In Class Path, enter ${CONNECTOR_INSTALL_ROOT}/jrules-res-xu-

WAS<version_number>.rar.f. Click OK.g. Repeat steps 5 through 9 to define the connection factory.

11. Restart the server.

Tip: Whenever you install or uninstall a XU, you must restart yourapplication server.


What to do next

For more information, especially for instructions about packaging a connector intoan EAR or about installing additional XU resource adapters, see one of thefollowing information centers:v WebSphere Application Server Version 7.0 Information Centerv WebSphere Application Server Version 8.0 Information Center

Step 10: Deploying the hosted transparent decision service EAR:

Optionally, deploy the hosted transparent decision service EAR file.

About this task

If you require the hosted transparent decision service, you must deploy the EARfile onto the same node as the Execution Unit (XU).

Procedure

To deploy the EAR:1. Open the Integrated Solutions Console.2. In the pane, click Applications > New Application and New Enterprise

Application.3. In the panel, select Remote file system, browse to the archive files, and click

Next.<InstallDir>/executionserver/applicationservers/WebSphere<version_number>/jrules-res-htds-WAS<version_number>-for-zos.ear

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

box Generate Default Bindings, and click Next.6. Click Continue to accept the security warning.7. For Step 1 through Step 10, click Next to accept the default settings.

Step 11s provides a summary.8. Click Finish.9. After the deployment has completed, click Save to save directly to the master

configuration.10. In the panel, open Applications > Application Types > WebSphere

enterprise applications and click jrules-res-htds-WAS8-for-zos orjrules-res-htds-WAS7-for-zos.

11. Click Manage Modules.12. Click DecisionService.13. Under General Properties, for Class loader order, select Classes loaded with

parent class loader first.14. Click OK.15. Click OK, then click Save to save directly to the master configuration.16. In the panel, open Applications > Application Types > WebSphere

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

jrules-res-htds-WAS8 or jrules-res-htds-WAS7 and click Start to start theapplication.


http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp


What to do next

By default, the ruleset.xmlDocumentDriverPool.maxSize ruleset property value isset to 1. This value might cause a bottleneck if several clients are executing ahosted transparent decision service concurrently. For better performance, increasingthe value of this property. The optimal value depends on the number of concurrentexecutions of the ruleset. For example, if you have five concurrent clients, 5 mightbe a good value.

Set this value from the Ruleset View in the Rule Execution Server console asfollows:1. Click the Explorer tab.2. Click RuleApps in the Navigator panel to display the RuleApps View.3. Click the name of the RuleApp that contains the ruleset in the RuleApps View.4. In the RuleApp View, click the relevant ruleset.5. In the Ruleset View, click Add Property. A New Ruleset Property dialog opens.6. Select the predefined property ruleset.xmlDocumentDriverPool.maxSize in the

drop-down list.7. Set the required value.8. Click Add.

Step 11: Setting the web container custom property:

After you have deployed the hosted transparent decision service, you must set aweb container custom property.

About this task

The hosted transparent decision service requires that you set the web containercustom property DecodeUrlAsUTF8 to False to support a localized ruleset path. Beaware that this setting impacts all applications deployed on the server. For moreinformation about checking that the hosted transparent decision service has beendeployed successfully, refer to the Rule Execution Server Console online help.

Procedure

To set the web container custom property:1. Open the Integrated Solutions Console.2. Click Servers > Server Types > WebSphere application servers and the server

name.3. Under Container Settings, click Web container settings > Web container.4. Under Additional Properties, click Custom properties.5. Click New and enter DecodeUrlAsUTF8 as the Name and False as the Value.6. Click Apply and Save directly to the master configuration.

Results

You can now run diagnostics to verify the deployment of Rule Execution Server(see Verifying the deployment and configuration).

Verifying the configuration:

Verify that you have successfully configured your new instance or server group.


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

About this task


Procedure

1. Display the Rule Execution Server console by opening a browser andnavigating to http://<hostname>:++HBRCONSOLEPORT++/res, where hostname isthe TCP/IP name of the z/OS machine where you are running the server and++HBRCONSOLEPORT++ is the HTTP port used by the console tocommunicate with the server.



Configuring Rule Execution Server on WebSphere ApplicationServer for z/OS with wsadmin scriptsAfter you have set up security, the other way to configure Rule Execution Serveron a new instance of WebSphere Application Server for z/OS consists in runningthe provided scripts, which automatically roll out the complete deployment andconfiguration steps.

Before you start:

You can configure Rule Execution Server on WebSphere Application Server forz/OS with DB2 by running a set of scripts.

Important:

During the execution of the wsadmin scripts, the WebSphere Application Servermight be restarted. If this is a problem, perform a manual configuration.

The process is as follows:1. Complete the prerequisites:

a. “Performing the initial configuration” on page 3b. “Configuring security on WebSphere Application Server for z/OS” on page

312. Run the JCL job as indicated in “Submitting the JCL job.”

Submitting the JCL job:

Submit the JCL job to complete the Rule Execution Server configuration.

About this task

After you have configured the JCL scripts in the++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL data set as explained in “Performing theinitial configuration” on page 3, you can submit the job to configure RuleExecution Server.



Procedure

1. Submit the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRDSWAS) JCL job.When the job is finished, you should see this message:[exec]----------------------------------------------------------[exec] RES install tasks all done[exec]----------------------------------------------------------...BUILD SUCCESSFUL

2. Check the job spool STDOUT and STDERR for the logs.If the job fails, the installation properties for WebSphere Application Server forz/OS can be found in the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRWASC(HBRRES)data set member, which is created in “Step 3: Creating the working data sets”on page 5 of the initial configuration.


Verify that you have successfully configured your new instance or server group.

About this task


Procedure

1. Display the Rule Execution Server console by opening a browser andnavigating to http://<hostname>:++HBRCONSOLEPORT++/res, where hostname isthe TCP/IP name of the z/OS machine where you are running the server and++HBRCONSOLEPORT++ is the HTTP port used by the console tocommunicate with the server.



Optional configuration stepsWhen configuring Rule Execution Server on WebSphere Application Server forz/OS, you can enhance your configuration with options such as configuringWOLA, integrating WebSphere MQ, setting up a multiserver configuration, ordeploying onto a server cluster.

Configuring WebSphere Optimized Local Adapters (WOLA):

WebSphere Optimized Local Adapters (WOLA) is a feature of WebSphereApplication Server for z/OS that manages communication between WebSphereApplication Server and an external address space, such as CICS, batch, and IMS,that resides on the same logical partition.

You use WOLA in combination with WebSphere Application Server for z/OS toperform bidirectional exchanges between your COBOL programs and RuleExecution Server.



Make sure you have set the WOLA runtime variables in the HBRINST memberbefore configuring your execution environment.

Configuring the WOLA load libraries on WebSphere Application Server for z/OS:

You use WebSphere Optimized Local Adapters (WOLA) in combination withWebSphere Application Server for z/OS to perform bidirectional exchangesbetween your COBOL applications and Rule Execution Server. Install WOLA forruleset execution from COBOL.

Before you begin

Ensure that you have installed WebSphere Application Server for z/OS V8.0.0.3 orhigher, or V7.0 Fix Pack 21 or higher.

To use the WOLA feature, you must deploy an EJB application to an applicationserver that runs in 64-bit mode. The EJB application will use the inboundconnections of WOLA.

Note: You must install WOLA on WebSphere Application Server if you want toexecute rulesets from your COBOL application.

About this task

To configure the load libraries for WOLA, you must create symbolic links in theWebSphere Application Server configuration file system to the optimized localadapter modules and plug-in JAR files in the product file system. You must do thisfor each node that requires WOLA support.

Procedure

To install WOLA:

Follow the instructions in the WebSphere Application Server infocenter:

Option Description

For WebSphere Application Server V7.0 Follow the instructions in Enabling theserver environment to use optimized localadapters

For WebSphere Application Server V8.0 Follow the instructions in Enabling theserver environment to use optimized localadapters

It is assumed that you install the WOLA load libraries in ++HBRHLQ++.SHBRWOLA.If you use IMS or CICS, ensure that the load module libraries are added to theSTEPLIB list for IMS or CICS and that they are APF-authorized.

Configuring batch jobs to execute rules using WOLA:

To call Rule Execution Server on WebSphere Application Server for z/OS fromyour COBOL application you must specify the WebSphere Optimized LocalAdapters (WOLA) load library, and the parameters required to locate the instanceof WebSphere Application Server for z/OS.


http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.multiplatform.doc%2Finfo%2Fae%2Fae%2Ftdat_enableconnector.html






About this task

To enable COBOL applications to call Rule Execution Server through WOLA, youfirst configure Rule Execution Server and WOLA on the same instance ofWebSphere Application Server for z/OS. Then you modify the JCL that launchesyour COBOL application, and set the SHBRPARM(HBRWOLA) data set memberwith the appropriate values.

Procedure

1. Add the following line to the STEPLIB in the JCL that launches the application:DD DISP=SHR,DSN=++HBRWOLALOADLIB++where ++HBRWOLALOADLIB++ is the locationwhere you installed the WOLA load library.

2. To identify the parameter file, add the following line in the JCL that launchesthe application://HBRENVPR DDDISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRWOLA)

3. Modify the following lines in the parameter file++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRWOLA):v HBRTARGETRES=++HBRTARGETRES++

v HBRWOLACELL=++HBRWOLACELL++

v HBRWOLANODE=++HBRWOLANODE++

v HBRWOLASERVER=++HBRWOLASERVER++

The last three lines must be modified to specify the WebSphere ApplicationServer instance that you want to use.If you are calling your application from IMS, add a DFSESL DD statement toyour JCL. This statement must identify the WOLA load library and the IMSSDFSRESL library.

Configuring CICS to execute rules using WOLA:

After you configure a Rule Execution Server on WebSphere Application Server forz/OS instance, you can configure CICS to execute rules on the newly-configuredserver through WOLA.

About this task

Use the following procedure to configure CICS to execute rules on Rule ExecutionServer on WebSphere Application Server for z/OS through WOLA.

You can optionally configure CICS to execute the HBRC transaction at startup toconnect to the server instance automatically, if it is running. With this option, CICSis immediately ready to execute rules. If the server is not running, CICS starts upnormally but you must execute the HBRC transaction manually before ruleexecution can begin.

Procedure

1. Submit the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCSD) job to define theresources required by CICS.

2. Submit the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRJCL(HBRCWOLA) job to definethe resources required for WOLA under CICS.

3. In the CICS system initialization table, add the list names BBOLIST and++CICSLIST++ to the list of resource definition groups specified by theGRPLIST parameter.


4. Edit the CICS JCL to include the Rule Execution Server data sets:a. Add the ++HBRHLQ++.SHBRAUTH and the ++HBRHLQ++.SHBRWOLA libraries to the

STEPLIB concatenation.b. Add the ++HBRHLQ++.SHBRCICS and the ++HBRHLQ++.SHBRWOLA libraries to the

DFHRPL concatenation.c. Pass the necessary runtime variables to the server by adding the

SHBRPARM(HBRWOLA) and SHBRPARM(HBRCMMN) data set members to theHBRENVPR DD statement. as shown in the following DD statements://HBRENVPR DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRWOLA)// DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRCMMN)

d. If you plan to run the Miniloan sample application to verify yourconfiguration, add the following DD statement to the SHBRPARM(HBRSCEN)data set member. The HBRSCEN member contains input values to theMiniloan application.//SCENARIO DD DISP=SHR,DSN=++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM(HBRSCEN)

5. Start the Rule Execution Server.6. Start CICS and install the HBRGROUP resources using the following command:

CEDA INSTALL GROUP(HBRGROUP)

7. Install the BBOACSD group using the following command:CEDA INSTALL GROUP(BBOACSD)

8. Activate the optimized local adapters TRUE program using the followingcommand:BBOC START_TRUE

You can use the BBOC transaction to start, stop, enable, or disable tracing forthe TRUE module.

9. Test the configuration by running the HBRC transaction to connect CICS to RuleExecution Server. If CICS succeeds in connecting to the server, messageGBRZC9001I is issued. If CICS fails to connect to the server, messageGBRZC9000E is issued with a return code containing diagnostic information.

10. Optional: To configure CICS to connect automatically at startup to the runningserver instance, take either of the following actions:v If you do not have a program list table defined, add the PLTPI=HB parameter

to the CICS system initialization table.v If you already have a program list table defined and specified in your CICS

system initialization table, add the HBRCCON program to the list by includingthe following statement: DFHPLT TYPE=ENTRY,PROGRAM=HBRCCON.

Configuring IMS to execute rules using WOLA:

To call Rule Execution Server on WebSphere Application Server for z/OS from anIMS program you must set up a PROCLIB member, pass the SSM parameter intothe IMS startup, and specify the WebSphere Optimized Local Adapters (WOLA)load library along with the parameters required to locate the instance ofWebSphere Application Server for z/OS.

About this task

To enable COBOL applications to call Rule Execution Server through WOLA, youfirst configure Rule Execution Server and WOLA on the same instance ofWebSphere Application Server for z/OS. Then you modify the IMS startup data,and set the SHBRPARM(HBRWOLA) data set member with the appropriate values.For more information on the Information Management System (IMS)-specific


installation and setup requirements, see Enabling optimized local adapters supportin IMS

Procedure

1. Create an external subsystem IMS PROCLIB member, or update your existingmember to include the following entry: WOLA,BBOA,BBOAIEMT

2. Pass the SSM parameter into your IMS startup data.3. Include the WOLA load library, created during the WOLA setup, in your IMS

Control region startup: STEPLIB and the DFSESL DDs.4. Restart IMS to register the changes.

Deploying the WOLA EJBs:

To complete the configuration of WOLA, you deploy an EJB application thatimplements the WebSphere Optimized Local Adapters (WOLA) interface onWebSphere Application Server for z/OS V7.0 and V8.0.

About this task

The WOLA EAR file contains two EJB modules:v res-wola-proxy-ejb: the entry point for the WOLA invocation. It accepts

inbound requests from the API stub and delegates the requests to the workerEJB module.

v res-wola-worker-ejb: the EJB module that forwards the requests to RuleExecution Server.

The following procedure guides you through the installation of the WOLA EARfile on WebSphere Application Server for z/OS.

Procedure

1. In the WebSphere Application Server console, select New Application > NewEnterprise Application.

2. Specify the path of the EAR file:

Option Description

WebSphere Application Server V7.0 <InstallDir>/executionserver/applicationservers/WebSphere7/jrules-res-wola.ear

WebSphere Application Server V8.0 <InstallDir>/executionserver/applicationservers/WebSphere8/jrules-res-wola.ear

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

box Generate Default Bindings, and click Next.5. In Step 1, click Next to accept the default settings.6. In Step 2, take one of the following actions:

a. If you have only one server, skip this step.b. If you have more than one server, select the server to which you want to

deploy the application, select the check box for the two modules, and clickNext.

7. In Step 3 through Step 4, click Next to accept the default settings.


http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tdat_enableconnectorims.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tdat_enableconnectorims.html

8. In Step 5, provide the following JNDI names for the beans:a. For the EJB module res-wola-proxy-ejb-8.0.jar: select the option JNDI

name for all interfaces Target Resource JNDI Name and enter the nameejb/com/ibm/rules/wola/ProxyExecutionSessionBean.

b. For the EJB module res-wola-worker-ejb-8.0.jar: select the option JNDIname for all interfaces Target Resource JNDI Name and enter the nameejb/com/ibm/rules/wola/PojoExecutionSessionBean.

Important: The JNDI names of the modules must be distinct, otherwise youcan get a NameAlreadyBoundException when you start the EJB.

9. In Step 6:

Option Description

WebSphere Application Server V7.0 Map the EJB reference for the proxy bean tothe worker bean by enteringejb/com/ibm/rules/wola/PojoExecutionSessionBean in the TargetResource JNDI Name column forres-wola-proxy-ejb-8.0.jar.

Click Next until Finish.

WebSphere Application Server V8.0 Click Next.

10. In Step 7 on WebSphere Application Server V8.0, map the EJB reference forthe proxy bean to the worker bean by entering ejb/com/ibm/rules/wola/PojoExecutionSessionBean in the Target Resource JNDI Name column forres-wola-proxy-ejb-8.0.jar.

11. On WebSphere Application Server V8.0, click Next until Finish.12. After the EJB deployment is complete, click Save to save it to the WebSphere

Application Server master configuration.13. Start the application Decision Server WOLA EndPoint:

a. In the WebSphere Application Server console, select Applications >Application Types > WebSphere enterprise applications.

b. In the Enterprise Applications page, select the check box next to DecisionServer WOLA EndPoint.

c. Click Start.


Test your configuration by running the WOLA Miniloan sample on Rule ExecutionServer for z/OS .

About this task

After you configure the WOLA (WebSphere Optimized Local Adapters) loadlibraries and deploy the WOLA EJB EAR file, you need to make sure that theconfiguration works correctly. The simplest way to validate the functionality ofWOLA is to use the Miniloan sample program. The sample runs in a batch job andcalls the EJB application running on the server through WOLA.

Procedure

Run the Miniloan sample as a batch job using the Rule Execution Server andWOLA instance you have configured on WebSphere Application Server for z/OS.


For more information, see Sample: Running the Miniloan application as a batch job

Integrating WebSphere MQ in WebSphere Application Server to supportasynchronous execution:

If you use the WebSphere MQ messaging provider support in WebSphereApplication Server, you can deploy Java EE applications that directly leverage theenterprise messaging capabilities of WebSphere MQ.

WebSphere MQ integration overview:

The Java Message Service (JMS) API enables access to rule services. To use amessage-driven rule bean, you must create the necessary resources under theWebSphere MQ JMS provider. Both the publish-and-subscribe and thepoint-to-point models are supported.

A Decision Server rule service can be accessed by an asynchronous invocationpattern that uses the Java Message Service (JMS) API. When a JMS messagearrives, the EJB container calls a message-driven rule bean (MDB). The MDB canreside locally or remotely from the client application. In turn, the message-drivenrule bean calls the rulesets that are running in the Execution Unit (XU). The realcall to the rule engine is delegated to a simple rule session.

In WebSphere Application Server, the client application is the scenario running inWebSphere Application Server that calls the rule service, the server is theapplication server where Rule Execution Server is installed. Rule Execution Serveris usually running remotely to the client application.

To use a Decision Server message-drive rule bean, you must create the necessaryresources under the WebSphere MQ JMS provider at the proper scope for both theclient and the server side to make them visible for the client application and theDecision Server MDB respectively. Decision Server implements both standards ofasynchronous messaging: the Publish-and-Subscribe Model and the Point-to-PointModel. The following procedure demonstrates how to set up both a point-to-pointmessaging model and a publish-and-subscribe model. If you need only one ofthem, you can comment out the resource reference in the deployment descriptor ofDecision Server MDB.

Before installation, you must create the following resources in WebSphere MQ:v Queue: JRulesIn, JRulesOutv Topic: JRulesTopicIn, JRulesTopicOut

Use these resources to submit rule execution requests and obtain execution results.

You must perform the following tasks to integrate WebSphere MQ in WebSphereApplication Server:1. “Creating the WebSphere MQ queue connection factory” on page 582. “Creating the WebSphere MQ input queue” on page 583. “Creating the WebSphere MQ output queue” on page 594. “Creating a topic connection factory” on page 595. “Creating the WebSphere MQ input topic” on page 606. “Creating the WebSphere MQ output topic” on page 607. “Creating the WebSphere MQ queue activation specification” on page 618. “Creating the WebSphere MQ topic activation specification” on page 62


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

9. “Installing the message-driven rule bean” on page 6310. “Enabling server-wide Last Participant Support” on page 63

Creating the WebSphere MQ queue connection factory:

To create the WebSphere MQ queue connection factory, you create the queue, thenyou configure the connection factory by following the connection factory wizard.

Procedure

To create a queue connection factory to connect WebSphere MQ with the DecisionServer MDB:1. Log in to the Integrated Solutions Console.2. Open Resources > JMS and click JMS Providers.3. In the panel, select the WebSphere MQ messaging provider.4. Under Additional Properties, click Queue connection factories.5. Click New.6. In Step 1: Configure basic attributes, set the fields Name and JNDI name as

follows, then Click Next.

Name JRules Queue Connection Factory

JNDI namejms/BRESQueueConnectionFactory

7. In Step 2: Select connection method, select Enter all the requiredinformation into this wizard and click Next.

8. In Step 2.1: Supply queue connection details, type the name of your queuemanager or queue sharing group, then click Next.

9. In Step 2.2: Enter connection details, type the connection details to establish aconnection to the queue manager or queue sharing group, then click Next.The default queue port is 1414.

10. In Step 3: Test connection, click Test connection.If your message queue is running, you see the following message:A connection was successfully made to WebSphere MQ.

11. Click Next.A summary opens showing the details of the connection factory.

12. Click Finish and then click Save to save directly to the master configuration.

Creating the WebSphere MQ input queue:

After you have created the WebSphere MQ queue connection factory, you can nowcreate the JMS queue destination for receiving a request message. To do so, you setthe scope to node or server level, you select the provider, name the queue, andfinally save the configuration.

Procedure

To create the JMS queue:1. In the Integrated Solutions Console, open Resources > JMS and click Queues.2. Set the scope to either Node level or Server level, then click New.3. In the panel, select WebSphere MQ messaging provider, then click OK.


4. In General Properties, set the fields Name, JNDI name, and Queue name asfollows:

Name JRules Input Queue

JNDI namejms/BRESQueueIn

Queue nameJRulesIn

5. Type in the name of your queue manager or queue sharing group name, thenclick OK.

6. Click Save to save directly to the master configuration.

Creating the WebSphere MQ output queue:

After you have created the input queue for request messages, you must also createthe JMS queue destination for sending a response message. To do so, you set thescope to node or server level, select the provider, name the queue, and save.

Procedure

To create the output queue:1. In the Integrated Solutions Console, open Resources > JMS and click Queues.2. Set the scope to either Node level or Server level, then click New.3. In the panel, select WebSphere MQ messaging provider, then click OK.4. In General Properties, set the fields Name, JNDI name, and Queue name as

follows:

Name JRules Output Queue

JNDI namejms/BRESQueueOut

Queue nameJRulesOut

5. Type in the name of your queue manager or queue sharing group name, thenclick OK.


Creating a topic connection factory:

After you have created the queue factory, input queue, and output queue, youmust create a topic connection factory. To do so, you set the scope to node orserver, select the provider and JNDI name, enter the connection details, test theconnection, and save.

Procedure

To create a topic connection factory:1. In the Integrated Solutions Console, open Resources > JMS and click Topic

connection factories.2. Set the scope to either Node level or Server level, then click New.3. In the panel, select WebSphere MQ messaging provider, then click OK.4. In Step 1: Configure basic attributes set the fields Name, and JNDI name as

follows and click Next.


Name JRules Topic Connection Factory

JNDI namejms/BRESTopicConnectionFactory



7. In Step 2.2: Enter connection details, type the connection details to establish aconnection to the queue manager or queue sharing group (the default queueport is 1414), then click Next.



10. Click Finish, then click Save to save directly to the master configuration.

Creating the WebSphere MQ input topic:

After you have created the WebSphere MQ topic connection factory, you can createthe JMS topic destination for receiving a request message. To do so, you set thescope to node or server level, select the provider, set the JNDI and input topicnames, and save.

Procedure

To create the JMS input topic:1. In the Integrated Solutions Console, open Resources > JMS and click Topics.2. Set the scope to either Node level or Server level, then click New.3. In the panel, select WebSphere MQ messaging provider, then click OK.4. In General Properties, set the fields Name, JNDI name, and Topic name as

follows, then click OK.

Name

JRules Input Topic

JNDI name

jms/BRESTopicIn

Topic name

JRulesTopicIn


Creating the WebSphere MQ output topic:

After you have created the WebSphere MQ topic connection factory and inputtopic, you must also create the JMS queue destination for sending a responsemessage. To do so, you set the scope to node or server level, select the provider, setthe JNDI and output topic names, and save.


Procedure

To create the JMS output topic:1. In the Integrated Solutions Console, open Resources > JMS and click Topics.2. Set the scope to either Node level or Server level, then click New.3. In the panel, select WebSphere MQ messaging provider, then click OK.4. In General Properties, set the fields Name, JNDI name, and Topic name as

follows and then click OK.

Name

JRules Output Topic

JNDI name

jms/BRESTopicOut

Topic name

JRulesTopicOut


Creating the WebSphere MQ queue activation specification:

After you have configured WebSphere MQ queues, you create the queue activationspecification.

About this task

The queue activation specification manages the relationship between the DecisionServer message-driven rule beans (MDB) running in WebSphere Application Serverand a destination in WebSphere MQ. To create the activation specification, you setthe scope to node or server level, select the provider, set the specification and JNDInames, enter the connection details, and save.

Procedure

To create the activation specification:1. In the Integrated Solutions Console, open Resources > JMS and click

Activation specifications.2. Set the scope to either Node level or Server level, then click New.3. In the panel, select WebSphere MQ messaging provider, then click OK.4. In Step 1: Configure basic attributes set the fields Name, and JNDI name as

follows and then click Next.

Name

JRules Activation Spec

JNDI name

eis/IlrRuleExecutionEJB

5. In Step 1.1: Specify MDB destination data, set the field Destination JNDIname to jms/BRESQueueIn, set the Destination type to Queue, then click Next.




8. In Step 2.2: Enter connection details, type the connection details to establish aconnection to the queue manager or queue sharing group, then click Next.The default queue port is 1414.



11. Click Finish, then click Save to save directly to the master configuration.

Creating the WebSphere MQ topic activation specification:

After you have created the queue activation specification, you create the topicactivation specification.

About this task

The topic activation specification manages the relationship between the DecisionServer message-driven rule beans (MDB) running in WebSphere Application Serverand a destination in WebSphere MQ. To create the activation specification, you setthe scope to node or server level, select the provider, set the specification and JNDInames, enter the connection details, and save.

Procedure

To create the topic activation specification:1. In the Integrated Solutions Console, open Resources > JMS and click

Activation specifications.2. Set the scope to either Node level or Server level, then click New.3. In the panel, select WebSphere MQ messaging provider, then click OK.4. In Step 1: Configure basic attributes set the fields Name, and JNDI name as

follows, and then click Next.

Name JRules Topic Activation Spec

JNDI nameeis/IlrRuleExecutionTopicEJB

5. In Step 1.1: Specify MDB destination data set the field Destination JNDIname to jms/BRESTopicIn, set the Destination type to Topic, then click Next.

6. In Step 1.2: Configure Durable Subscription, select Nondurablesubscription, then click Next.


8. In Step 2.1: Supply queue connection details, type the name of your queuemanager or queue sharing group, then click Next.The default queue port is 1414.

9. In Step 2.2: Enter connection details, type the connection details to establish aconnection to the queue manager or queue sharing group, then click Next.


11. Click Next.


A summary opens showing the details of the connection factory.12. Click Finish, then click Save to save directly to the master configuration.

Installing the message-driven rule bean:

After you have created the queue and topic activation specifications, you install theDecision Server message-driven rule bean (MDB) in WebSphere Application Serveras an enterprise application. To do so, you create a new enterprise application.

Procedure

To install the Decision Server message-driven rule bean:1. Open the Integrated Solutions Console.2. In the panel, open Applications > New Application and click New Enterprise

Application.3. In the panel, select Local file system and Browse to the following path:

<InstallDir>/executionserver/applicationservers/WebSphere<version_number>/jrules-res-mdb-WAS<version_number>.jar.

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

check box Generate Default Bindings.7. Click Next, then click Continue to accept the security warning.8. Click Step 5: Bind listeners for message-driven beans.

a. Type jms/BRESTopicIn as the Destination JNDI name forIlrRuleExecutionTopicEJB.

b. Type jms/BRESQueueIn as the Destination JNDI name forIlrRuleExecutionEJB.

c. Click Next.9. Click Step 6: Map resource references to resources and then click Next.

Use the default binding for the referenced resources.Step 7 provides a summary.

10. Click Finish.11. When the installation has completed, click Save directly to the master

configuration.12. In the Integrated Solutions Console, open Applications > Application Types

> WebSphere enterprise applications.13. In the Enterprise Applications page, select the check box next to

jrules-res-mdb-WAS<version_number>.jar and click Start to start theapplication.

Enabling server-wide Last Participant Support:

To complete the integration of WebSphere MQ, you enable Last ParticipantSupport.

About this task

To finish integrating WebSphere MQ in WebSphere Application Server forasynchronous execution, you enable Last Participant Support (LPS) so that a singleone-phase commit resource is used with any number of two-phase commit


resources in the same global transaction. To do so, you set theACCEPT_HEURISTIC_HAZARD custom property to true in the Integrated SolutionsConsole and then restart the application server.

Procedure

To enable server-wide LPS:1. Open the Integrated Solutions Console.2. Click Servers > Server Types > WebSphere application servers and the server

name.The properties page for the application server opens

3. Under Container Settings, expand Container Services and click TransactionService.The properties page for the transaction service opens.

4. Under Additional Properties, click Custom properties.5. On the Custom Properties page, click New and type ACCEPT_HEURISTIC_HAZARD

as the Name and TRUE as the Value.6. Click Apply and Save directly to the master configuration.7. Restart your application server.

Configuring Rule Execution Server in different environments:

Configuration settings required to enable Rule Execution Server on differentenvironments in a single cell.

About this task

It is very likely that the development of your BRMS requires more than a singledeployment of Rule Execution Server. The development life cycle of a business ruleapplication is similar to any other software development process, including stagesfor implementation, testing, deployment, and maintenance. At the very least, youare likely to need an environment for your development team, one for your QAteam, and another one for in-production applications. In the cases where youconfigure Rule Execution Server in a single cell, it is good practice to isolate therulesets that you use on each server, and ensure that the Execution Units (XUs) donot interfere with each other.

Note: These instructions assume that you do not configure multiple instances ofRule Execution Server in a single cell.

To set up different environments in a single cell, follow these steps:1. Set up different data sources.2. Deploy and configure a XU for each environment.3. Deploy the Rule Execution Server console for each environment.

Procedure

To configure Rule Execution Server in different environments:1. Set up different data sources.

Use a unique JNDI name. For example: jdbc/resdatasourceEnv1 andjdbc/resdatasourceEnv2.

2. Deploy a XU for each environment and define a J2C connection factory.


a. In the side panel, open Resources > Resource Adapters > J2C connectionfactories and click the name of the connection factory xu_cf) See Step 9:Deploying the XU RAR for information on creating a connection factory.

b. Modify the JNDI name to eis/XUConnectionFactoryEnv1.

Note: You must modify the execution components that call this XU so thatthey use this JNDI instead of the default.

c. Under Additional Properties, click Custom properties.d. Click the plugins property.e. In the Value field, change xuName=default in the property to

xuName=xuEnv1, and then click OK.f. Click the persistenceProperties property.g. In the Value field, change JNDI_NAME=jdbc/resdatasource to

JNDI_NAME=jdbc/resdatasourceEnv1.h. Click OK and Save to save the changes to the master configuration.i. Repeat the same process for XUs in other environments.

3. Deploy the Rule Execution Server console for each environment.a. To modify the deployment descriptor of the Rule Execution Server console

EAR: in the web.xml file, uncomment the JMX_XU_QUERY_PART parameter andspecify xuName=xuEnv1.

b. Deploy the Rule Execution Server console EAR on the server in the resourcereference settings in the application server.1) Set the JNDI for the data source to jdbc/resdatasourceEnv1.2) Set the JNDI name for the XU to eis/ConnectionFactoryEnv1.

c. Repeat the process to deploy the Rule Execution Server console for the otherenvironments.

4. Restart the node agents after you complete the configuration5. Call the XU instances to register the XU with the Rule Execution Server

console.

Rule Execution Server deployment on cluster environments:

Taking into account cluster configuration and topology, you can deploy RuleExecution Server to WebSphere Application Server cell in cluster mode.

Cluster configuration and topology:

When you deploy Rule Execution Server onto server clusters, each node hosts oneExecution Unit (XU) which is used only by a local rule session. The clustertopology significantly affects the notification mechanism.

Within the Java EE framework, clusters provide mission-critical services to ensureminimal downtime and maximum scalability. A cluster is a group of applicationservers that transparently run your Java EE application as if it were a single entity.

Cluster implementations on Java EE application servers come with their own set ofterminology. Each of the following terms are important to understand how yourcluster performs:v Cluster and component failover servicesv HTTP session failoverv Single points of failure in a cluster topology


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

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

On a cluster configuration, deploy an Execution Unit (XU) on each node. There isone XU for each node of a cluster. Use the administration console of applicationservers to handle cluster deployment. A XU instance can be used only by a local(same node) rule session. The rule session and the XU communicate using directJava method calls, so the XU does not require serialization.

A cluster that uses Rule Execution Server involves a collaboration between theRule Execution Server MBeans. The topology of the cluster has significantinfluence on the management of the notification mechanism when a resource ischanged.

The management model is likely to use several times a basic scenario of adistributed notification mechanism within a cluster to interact with the variousExecution Unit (XU) instances. A XU MBean is deployed with the XU tocollaborate with the Rule Execution Server JMX infrastructure.

The following sequence applies:1. A management client sets a resource on a ruleset MBean.2. The ruleset makes a query to the MBean Server to retrieve all the XU instances

in the cluster (this operation requires a specific implementation for eachapplication server).

3. A notification is sent to each instance.

Rule Execution Server deployment on WebSphere Application Server cells:

Deployment of Rule Execution Server in a WebSphere Application Server cell(distributed or z/OS) relies on a number of best practices.

A WebSphere Application Server cell is a virtual unit that consists of a deploymentmanager and one or more nodes. When deploying the different Rule ExecutionServer components on WebSphere Application Server or WebSphere ApplicationServer for z/OS, it is important that you deploy the management module onto asingle server in the cell. Only a single management module is necessary to manageall Execution Units (XU) on each server.


It is important to define a logical subset of servers. You must set up theconfiguration in the following way:v Dedicate a stand-alone server of the cell outside the cluster to the deployment of

the Rule Execution Server management module. A failover mechanism is notnecessary.

v Dedicate a cluster of servers or stand-alone servers to the deployment of the XU.You can install the XU (.rar file) only at the node level and you must declarethe resource adapter at the node or server level so that every server in the nodecontains this definition.

v Define the data source at the node level (see the documentation about creatingJDBC providers).

Such a configuration guarantees that a single management module is instantiatedin the WebSphere Application Server cell, as illustrated in the following diagram.

The notification mechanism uses a simple pattern because Rule Execution ServerMBeans rely on the distributed MBean mechanism provided by WebSphereApplication Server. When an MBean is registered in a server of a WebSphereApplication Server cell, it is automatically visible to the Deployment ManagerMBean Server.

To notify each Execution Unit of changes in the management model, query theDeployment Manager MBean Server, then notify each Execution Unit retrieved bythe query.


For more information, see:v WebSphere Application Server Version 7.0 Information Centerv WebSphere Application Server Version 8.0 Information Centerv Building Java EE applications with a WebSphere cluster environment

Configuring a COBOL rule subprogram into a COBOLapplication

You can integrate the generated COBOL code into a COBOL calling program usinga static or a dynamic link, or using CICS channels and containers.

COBOL-generated code integrationYou can generate a COBOL program to execute rules and then link it into aCOBOL calling application.

Generate the COBOL program in Rule Designer, Decision Center, or using an Antcommand. Then integrate the generated COBOL program with a COBOL callingprogram and run both on a z/OS subsystem.

You can run the generated COBOL program in the following types of application:v Batchv CICSv IMS

If you generate the code in Rule Designer, the source file resides in the directoryyou specified during code generation, ready to upload to z/OS. If you useDecision Center, you download the output from the Decision Center codegeneration process onto your local machine. If you used an Ant command, thegenerated COBOL program is saved to: <InstallDir>/studio/lib.




http://www.ibm.com/developerworks/websphere/library/techarticles/0606_zhou/0606_zhou.html

Related tasks:“Calling a CICS wrapper program to integrate the code” on page 71If you use the CICS usage option when you generate the COBOL code, you mustalso update the CICS calling program so that it calls the wrapper program toexecute the COBOL program for rule execution.“Linking code by using a COBOL dynamic link” on page 70Use a dynamic link to link the generated COBOL program independently from thecalling program.“Linking code by using a COBOL static link”You can link the generated COBOL program by adding a static link to eachprogram that calls it.

Linking code by using a COBOL static linkYou can link the generated COBOL program by adding a static link to eachprogram that calls it.

About this task

Using a static link you can compile, link, and then run the generated COBOL codeinside the calling program, but you must statically link it with every program thatcalls it. If the generated program changes, you must relink it to all its callingprograms for the changes to take effect.

You link the generated COBOL program into the calling program using a CALLstatement.

Procedure1. Declare the generated COBOL program as a constant in the

WORKING-STORAGE section of the calling program. For example:01 GENERATED-PROG PIC X(8) VALUE ’MINICBL’

Where MINICBL is the name of the generated COBOL program file.2. Add a CALL statement to the PROCEDURE DIVISION of the calling program

that uses this constant. For example:CALL GENERATED-PROG USING BORROWER LOAN

You reference each Top Level data item with a USING clause.3. Compile the calling program.

Results

The rules are now ready to be executed.

Example static link to a batch program

The following code extract shows how to link the generated COBOL code to aCOBOL calling program, using a CALL statement in the PROCEDURE DIVISION.The XOM is based on a COBOL copybook named miniloan that has two Top Leveldata items: LOAN and BORROWER. These items translate into two classes in the BOM,named Loan and Borrower. The generated COBOL program file is named MINICBL.IDENTIFICATION DIVISION.PROGRAM-ID. MAIN.

DATA DIVISION.WORKING-STORAGE SECTION.

COPY MINILOAN.


01 TABLEINDEX PIC 999.01 GENERATED-PROGRAM PIC X(8) VALUE " MINICBL".

PROCEDURE DIVISION.ROOT.

MOVE "JOHN" TO NAME OF BORROWERMOVE 100 TO CREDITSCORE OF BORROWERMOVE 10000 TO YEARLYINCOME OF BORROWERMOVE 10000 TO AMOUNT OF LOANMOVE 5 to YEARLYINTERESTRATE OF LOANMOVE 1000 TO YEARLYREPAYMENT OF LOANMOVE "N" TO APPROVED OF LOANMOVE 0 TO MESSAGECOUNT OF LOAN

CALL "MINICBL" USING LOAN BORROWER

IF APPROVED OF LOAN = "Y"DISPLAY "Loan approved"

ELSEDISPLAY "Loan not approved"MOVE 1 TO TABLEINDEXPERFORM UNTIL TABLEINDEX > MESSAGECOUNT OF LOAN

DISPLAY MESSAGES OF LOAN (TABLEINDEX)COMPUTE TABLEINDEX = TABLEINDEX + 1

END-PERFORMEND-IFGOBACK.

Related information:“COBOL-generated code integration” on page 68You can generate a COBOL program to execute rules and then link it into aCOBOL calling application.

Linking code by using a COBOL dynamic linkUse a dynamic link to link the generated COBOL program independently from thecalling program.

About this task

Using a dynamic link, you can link the generated COBOL program independentlyfrom the calling program. This way of linking is similar to using a CICS EXEC CICSLINK, except that with a dynamic link, both the generated COBOL program and theCOBOL calling program must reside in the same CICS system.

Tip: With an EXEC CICS LINK, the programs can be in different CICS systems.

Procedure1. Declare the generated COBOL program as a constant in the

WORKING-STORAGE section of the calling program. For example:01 GENERATED-PROG PIC X(8) VALUE ’MINICBL’

Where MINICBL is the name of the generated COBOL program file.2. Add a CALL statement to the PROCEDURE DIVISION of the calling program

that uses this constant. For example:CALL GENERATED-PROG USING BORROWER LOAN

You reference each Top Level data item with a USING clause.3. To link the COBOL program dynamically, select one of the following compile

options:v For a batch program, specify DYNAM=YES.v For a CICS program, specify DYNAM=NO.


4. To link the COBOL code into a CICS program, specify CICS=NO.

Note: If you specify CICS=YES, CICS expects a COMMAREA to be passed to theCOBOL-generated program. The generated COBOL program does not include adummy COMMAREA, so specifying CICS=YES can result in 0C4 ABENDs occurring.

Results

When you run the calling program, the rules are executed.Related information:“COBOL-generated code integration” on page 68You can generate a COBOL program to execute rules and then link it into aCOBOL calling application.

Calling a CICS wrapper program to integrate the codeIf you use the CICS usage option when you generate the COBOL code, you mustalso update the CICS calling program so that it calls the wrapper program toexecute the COBOL program for rule execution.

About this task

If you want to host the generated COBOL program in a different CICS region tothe calling application, you can use the CICS usage option. In this case, theCOBOL code generator generates a CICS wrapper program, as well as the COBOLcode for rule execution. If you use the CICS usage option, you must also updatethe CICS calling program so that it calls the wrapper program to execute theCOBOL program for rule execution.

Procedure

To update the CICS calling program:1. Add an EXEC CICS PUT CONTAINER statement for each group item.

For example, if you have two group items, LOAN and BORROWER, you might createthe following statements:EXEC CICS PUT CONTAINER(LOAN-CONTAINER)

CHANNEL(MINILOAN-CHANNEL)FROM(Loan) FLENGTH(Length of Loan)END-EXEC

EXEC CICS PUT CONTAINER(BORROWER-CONTAINER)CHANNEL(MINILOAN-CHANNEL)FROM(Borrower) FLENGTH(Length of Borrower)END-EXEC

2. Replace the COBOL call statement with an EXEC CICS LINK PROGRAM statementthat specifies the name of the channel that you want to pass to the wrapperprogram.

3. Add an EXEC CICS GET CONTAINER statement for each Top Level data itemmodified by the generated COBOL program.You must have the GET CONTAINER commands to get any information from thecontainers that has been modified by the COBOL program. The GET CONTAINERcommand picks up the information from the PUT CONTAINER command at theend of the wrapper program.


Note: If the generated COBOL program increases the size of a data item, forexample, if the generated program modifies an OCCURS DEPENDING ON variable,use COBOL pointers to retrieve the data.

Results

You can now translate, compile and link the calling program, the wrapperprogram, and the generated COBOL code. This action is slightly different from anormal COBOL compile because all the EXEC CICS statements must be translated tocompile the code successfully.Related information:“COBOL-generated code integration” on page 68You can generate a COBOL program to execute rules and then link it into aCOBOL calling application.

Configuring your system for usage data collectionIf your IBM license requires you to monitor your usage of COBOL programsgenerated by COBOL management, you must perform a configuration stepdepending on your execution environment.

Configuring zRule Execution Server for z/OS to collect dataYou can collect usage data on an instance of zRule Execution Server for z/OS.

About this task

To activate the collection of usage data on an instance of zRule Execution Serverfor z/OS, add a variable to the ++HBRWORKDS++.<HBRSSID_NAME>.SHBRPARM data set.

Procedurev For an instance of zRule Execution Server for z/OS server, add the following

variable to the HBRMSTR member:HBRIFAUSAGE=YES

v For an instance of zRule Execution Server for z/OS on CICS JVM server, add thefollowing variable to the HBRCICSJ member:HBRIFAUSAGE=YES

Configuring Rule Execution Server on WebSphere ApplicationServer for z/OS to collect data

You can collect usage data on an instance of Rule Execution Server on WebSphereApplication Server for z/OS.

About this task

Activate the collection of usage data from an instance of Rule Execution Server onWebSphere Application Server for z/OS by submitting a JCL job.

Procedure

Submit one of the following jobs depending on your installation:v SHBRJCL(HBRDMREG): if your installed product includes rules and events

componentsv SHBRJCL(HBRBRREG): if your installed product includes the rules components only


Configuring COBOL rule subprograms to collect dataTo configure usage data collection for a COBOL rule subprogram you must carryout a number of steps to use the System Management Facility (SMF).

Usage monitoring toolsThe System Management Facility (SMF) collects runtime usage data for COBOLsource programs generated by COBOL management at runtime. The generated ruleexecution program communicates with SMF through the COBOL ResourceManager.

If your IBM license requires you to monitor your usage of the COBOL sourceprograms that you generate using COBOL, you must set the usage data collectionflag in Rule Designer so that you can collect COBOL source program usage data.Usage data is collected at runtime by the z/OS® System Management Facility(SMF).

Communication between generated COBOL source program and SMF is handledby the COBOL Resource Manager, which executes as a z/OS subsystem. Atruntime, the generated COBOL source program notifies the Resource Managerwhen execution starts and ends. The Resource Manager passes this data to SMF,and SMF generates the appropriate program usage records.

To enable usage data collection, you must configure z/OS, set the usage datacollection flag in Rule Designer before you generate the COBOL code, and thencarry out some additional tasks when compiling and linking the generatedprogram.

The following diagram illustrates the role of the Resource Manager, and the overallsequence of events that result in usage data collection.


Related tasks:“Defining the Resource Manager as a z/OS subsystem”You must define the COBOL Resource Manager as a valid z/OS subsystem so thatthe z/OS system recognizes it.“Configuring the Resource Manager subsystem” on page 76Before you can start the COBOL Resource Manager, you must configure the JCLmember BRCSUBS.“Compiling, linking, and running your programs” on page 77To collect program usage data, you perform some additional steps whencompiling, linking, and running the generated COBOL program.

Configuring z/OSFor the generated COBOL source programs to participate in program usage datacollection, you must carry out a number of z/OS configuration tasks.Related tasks:“Defining the Resource Manager as a z/OS subsystem”You must define the COBOL Resource Manager as a valid z/OS subsystem so thatthe z/OS system recognizes it.“Configuring the Resource Manager subsystem” on page 76Before you can start the COBOL Resource Manager, you must configure the JCLmember BRCSUBS.“Compiling, linking, and running your programs” on page 77To collect program usage data, you perform some additional steps whencompiling, linking, and running the generated COBOL program.

Configuration tasks:

To collect usage data, you must configure the required libraries and z/OScomponents, set the usage data collection flag, and then carry out some additionaltasks when compiling and linking the generated code.

Before you can collect usage data for generated COBOL source programs, youmust carry out the following z/OS configuration tasks:1. Define the COBOL Resource Manager as a z/OS subsystem.2. Configure the Resource Manager subsystem

Note:

These are one-off tasks that configure your system for program usage monitoringfor any generated COBOL programs that you run on it.Related tasks:“Defining the Resource Manager as a z/OS subsystem”You must define the COBOL Resource Manager as a valid z/OS subsystem so thatthe z/OS system recognizes it.“Configuring the Resource Manager subsystem” on page 76Before you can start the COBOL Resource Manager, you must configure the JCLmember BRCSUBS.“Compiling, linking, and running your programs” on page 77To collect program usage data, you perform some additional steps whencompiling, linking, and running the generated COBOL program.

Defining the Resource Manager as a z/OS subsystem:


You must define the COBOL Resource Manager as a valid z/OS subsystem so thatthe z/OS system recognizes it.

About this task

You define the Resource Manager as a z/OS subsystem by giving it a name andthen adding it to the list of defined z/OS subsystems. You can define itdynamically, or you can define it permanently by adding a definition to the systemparameter library (parmlib) member IEFSSNxx.

Procedure

1. Do one of the following, depending on whether you want to add thesubsystem dynamically or permanently:

Add subsystem dynamically Add subsystem permanently

Issue the following z/OS system command:

SETSSI ADD,SUBNAME=++SUBS++

Add the following definition to the IEFSSNxxmember:

SUBSYS SUBNAME(++SUBS++)

Where ++SUBS++ is the name given to the COBOL Resource Manager, specificto your installation and naming conventions.

2. Optional: Check that the Resource Manager has been added to the list of z/OSsubsystems using the following z/OS system command:D SSI,LIST,SUB=++SUBS++

Related information:“Configuration tasks” on page 74To collect usage data, you must configure the required libraries and z/OScomponents, set the usage data collection flag, and then carry out some additionaltasks when compiling and linking the generated code.“Usage monitoring tools” on page 73The System Management Facility (SMF) collects runtime usage data for COBOLsource programs generated by COBOL management at runtime. The generated ruleexecution program communicates with SMF through the COBOL ResourceManager.“Sample COBOL code for usage data collection” on page 78When you enable usage data collection, the generated COBOL source programadds a reference to the BRCCONST and BRCCONWS copybooks.“Configuring z/OS” on page 74For the generated COBOL source programs to participate in program usage datacollection, you must carry out a number of z/OS configuration tasks.

Loading the COBOL load module into the LPA:

The BRCF7100 program is the COBOL load module that interacts with SMF. Youmust load this program into the link pack area (LPA). You can load the programdynamically, or load it permanently by adding a definition to the parmlib memberPROGxx.

About this task

To load the program use one of the following methods:


Procedure

v SETPROG LPA,ADD,MODNAME=(BRCF7100),DSNAME=++HBRHLQ++.SHBRAUTH where++HBRHLQ++ is your user-defined high level qualifier. This command loads themodule dynamically.

v LPA ADD MODNAME(BRCF7100) DSNAME(++HBRHLQ++.SHBRAUTH) Add the definition tothe parmlib member PROGxx.

v D PROG,LPA,MODNAME=BRCF7100 This z/OS system command checks that theprogram has been loaded into the LPA.

Configuring the Resource Manager subsystem:

Before you can start the COBOL Resource Manager, you must configure the JCLmember BRCSUBS.

About this task

To be able to start the COBOL Resource Manager, you configure the JCL memberBRCSUBS, which is stored in the SHBRJCL library. The JCL member tells you whichparts of the JCL you must change. You can submit it as a job or as a started task.

Procedure

To customize the JCL:1. Add your installation-specific jobcard.2. Update the STEPLIB.3. Replace the ++SUBS++ variable with the subsystem name defined for the COBOL

Resource Manager.This definition tells the generated COBOL program which subsystem to connectto.

4. Submit the job control.

Note:

v

This is a long-running job and must be executed while the generated COBOLprogram or programs are executing.

v

To terminate the COBOL Resource Manager, issue the z/OS command STOP<jobname>.

Results

You now set the usage monitoring flag in Rule Designer. See Monitoring generatedCOBOL program usage.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.designer.run/executing_cobol_topics/tsk_monitor_cobol_prog_usage.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.rules.designer.run/executing_cobol_topics/tsk_monitor_cobol_prog_usage.htm

Related information:“Configuration tasks” on page 74To collect usage data, you must configure the required libraries and z/OScomponents, set the usage data collection flag, and then carry out some additionaltasks when compiling and linking the generated code.“Usage monitoring tools” on page 73The System Management Facility (SMF) collects runtime usage data for COBOLsource programs generated by COBOL management at runtime. The generated ruleexecution program communicates with SMF through the COBOL ResourceManager.“Sample COBOL code for usage data collection” on page 78When you enable usage data collection, the generated COBOL source programadds a reference to the BRCCONST and BRCCONWS copybooks.“Configuring z/OS” on page 74For the generated COBOL source programs to participate in program usage datacollection, you must carry out a number of z/OS configuration tasks.

Compiling, linking, and running your programsTo collect program usage data, you perform some additional steps whencompiling, linking, and running the generated COBOL program.

About this task

Before you execute the generated COBOL program, make sure that you havecarried out the following tasks when compiling, linking, and running thegenerated COBOL program.

Procedure

To compile, link and run your programs:1. To enable the compiler to retrieve the COBOL copybooks provided for usage

data collection, add the COBOL copy library, ++HBRHLQ++.SHBRCOBC, to thecompile step SYSLIB DD statement.For example: //SYSLIB DD DISP=SHR,DSN=ZILOG ++HBRHLQ++.SHBRCOBC You mightalready have several libraries specified to SYSLIB. Add SHBRCOBC to theconcatenation.

2. To link your generated COBOL programs correctly:a. Add a reference to the COBOL load library in the linkedit step

//SHBRLOAD DD DISP=SHR,DSN=++HBRHLQ++.SHBRLOAD

You add this reference so that the linkedit step can resolve the COBOLResource Manager BRCC stubs.

b. Include the following binder statement in the linkedit step, to make surethat the binder includes the stub module that COBOL managementsupplies.INCLUDE SHBRLOAD(BRCCSTUB)

3. To enable the generated COBOL program to identify the Resource Manager touse when collecting usage monitoring data, add the following DD statement tothe job step that executes your COBOL program://R4CS++SUBS++ DD DUMMY

Where ++SUBS++ is the subsystem name, for example: //R4CSBRA2 DD DUMMY

At runtime, the generated COBOL program must be able to identify whichResource Manager to use usage data collection.


Related information:“Configuration tasks” on page 74To collect usage data, you must configure the required libraries and z/OScomponents, set the usage data collection flag, and then carry out some additionaltasks when compiling and linking the generated code.“Usage monitoring tools” on page 73The System Management Facility (SMF) collects runtime usage data for COBOLsource programs generated by COBOL management at runtime. The generated ruleexecution program communicates with SMF through the COBOL ResourceManager.“Sample COBOL code for usage data collection”When you enable usage data collection, the generated COBOL source programadds a reference to the BRCCONST and BRCCONWS copybooks.“Configuring z/OS” on page 74For the generated COBOL source programs to participate in program usage datacollection, you must carry out a number of z/OS configuration tasks.

Sample COBOL code for usage data collectionWhen you enable usage data collection, the generated COBOL source programadds a reference to the BRCCONST and BRCCONWS copybooks.

The following code extract shows an example of the type of code that is generatedwhen you set the usage data collection flag. It shows the references to the BRCCONSTand BRCCONWS copybooks in the WORKING-STORAGE SECTION, and the code thathandles usage data collection in the PROCEDURE DIVISION.

IDENTIFICATION DIVISION.PROGRAM-ID. R4CZOSRM IS INITIAL PROGRAM.

* This COBOL program is generated from the following ruleset: miniloan* Created at 2010/03/05 10:07:02.

DATA DIVISION.WORKING-STORAGE SECTION.

COPY BRCCONST.COPY BRCCONWS.

.

.

.

LINKAGE SECTION.COPY MINILOAN.

PROCEDURE DIVISION USING BORROWER LOAN.TASK1-SMF.

INITIALIZE BRCC-CONN-AREAMOVE "miniloan" TO BRCC-CONN-RULESET-NAME OF BRCC-R4C-DATAMOVE "20100305" TO BRCC-CONN-CREATE-DATE OF BRCC-R4C-DATAMOVE "100702" TO BRCC-CONN-CREATE-TIME OF BRCC-R4C-DATAMOVE BRCC-CONN-RS OF BRCC-R4C-CONSTANTS TOBRCC-CONN-CREATE-METHOD OF BRCC-R4C-DATACOPY BRCCINIT.PERFORM TASK2-MAINFLOWCOPY BRCCTERM.GOBACK.

* RuleFlow mainflowTASK2-MAINFLOW.

PERFORM TASK3-MAINFLOW-VALIDATIONPERFORM TASK4-MAINFLOW-ELIGIBILITY.


* RuleTask mainflow#validation...

Related tasks:“Defining the Resource Manager as a z/OS subsystem” on page 74You must define the COBOL Resource Manager as a valid z/OS subsystem so thatthe z/OS system recognizes it.“Configuring the Resource Manager subsystem” on page 76Before you can start the COBOL Resource Manager, you must configure the JCLmember BRCSUBS.“Compiling, linking, and running your programs” on page 77To collect program usage data, you perform some additional steps whencompiling, linking, and running the generated COBOL program.

Configuring the event runtime on z/OSTo configure the event runtime on z/OS, you install the event runtime on thez/OS system and Event Designer on any platform except z/OS.

About this task

Be aware of the following limitations if you install the event runtime on a z/OSsystem:v You can install WebSphere Operational Decision Management into a stand-alone

configuration of WebSphere Application Server.v However, you can also install into a WebSphere Application Server network

deployment configuration but you cannot cluster WebSphere OperationalDecision Management across the servers in the network deploymentconfiguration.

Preparing to install on z/OSConfiguring the event runtime in WebSphere Operational Decision Managementfor z/OS includes planning tasks for WebSphere Operational DecisionManagement as well as planning tasks for WebSphere Application Server.

About this task

The following table lists the tasks that you must perform and provides referencesto the documentation resources that can help you to install and configure theproduct:

Table 3. Information Center references.

Task Information Center resource

Determine the systemrequirements.

See WebSphere Operational Decision Management DetailedSystem Requirements.

Understand security optionsand prepare for securingyour system.

Security options are set in WebSphere Application Server.See Security planning overview information in the WebSphereApplication Server Information Center.

Implement WorkloadManagement in goal modeon each z/OS system ifnecessary.

See z/OS workload management (WLM) in the WebSphereApplication Server Information Center.


http://www-01.ibm.com/support/docview.wss?uid=swg27023067

http://www-01.ibm.com/support/docview.wss?uid=swg27023067

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/csec_plan.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.zseries.doc/info/zseries/ae/cins_prepwlmzos.html

Table 3. Information Center references. (continued)

Task Information Center resource

Implement ResourceRecovery Services (if notalready implemented) oneach z/OS system.

See Preparing Resource Recovery Services (RRS) in theWebSphere Application Server Information Center.

Plan for your performanceand monitoring systems.

See Monitoring end user response time in the WebSphereApplication Server Information Center.

Plan and define yourproblem diagnosisprocedures.

See Problem diagnostic plan strategy in the WebSphereApplication Server Information Center.

Consider automatic restartmanagement before youinstall WebSphereApplication Server for z/OS.

See Automatic restart management (ARM) in the WebSphereApplication Server Information Center.

Perform planning tasks inpreparation for loading theprogram materials from theinstallation media ontoz/OS.

For information about planning tasks associated withunloading the WebSphere Application Server for z/OSinstallation media, see Planning for installation in theWebSphere Application Server Information Center.

Depending on environment configuration variables and how you configured yourresponse file, you might have to perform additional configuration tasks tocomplete the configuration.

Installing a stand-alone configurationA stand-alone configuration, also known as a single server configuration, is thesimplest configuration you can use to deploy and run the event runtime inWebSphere Operational Decision Management.

A stand-alone configuration consists of a single node running an application serverand one daemon server in a single z/OS system or LPAR.

The application server runs the wberuntimeear application (the event runtime) andthe WebSphere Application Server administrative console, which you can use toconfigure WebSphere Operational Decision Management.

The daemon server is a unique server that runs constantly and has one controllerregion, which distributes server workload.

You can configure multiple application servers to run in a node. However, eachserver is isolated from the others. Each application server contains these items:v Its own root file system, cell, node, TCP ports, and administration interfacev Its own administration policy for its own cell domainv A separate flat file system to store its configuration information, in a set of XML

and XMI files

Application servers in a node do not use workload distribution or commonadministration. You can define additional application servers in a stand-alone cell,but you cannot control them by using the WebSphere Application Serveradministrative console.


http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.zseries.doc/info/zseries/ae/tins_preprrs.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tprf_monitoringresp.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.zseries.doc/info/zseries/ae/cins_diagbk.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.zseries.doc/info/zseries/ae/cins_armpol.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.soafepzseries.doc/info/zseries/ae/tins_planinstallz.html

The following figure shows a stand-alone configuration which consists of a singlenode running an application server and one daemon server in a single z/OSsystem or LPAR:

You must have the following configuration in place before you can create astand-alone configuration:v WebSphere Operational Decision Management must be installed as the

stand-alone server.v Your UNIX user ID must have permission to access the UNIX shell to run the

installation and augmentation scripts from inside the shell. Gaining permissionto access the shell involves modifying your RACF profile and creating a homedirectory in the UNIX shell. The home directory is where you begin a UNIXsession, and where you store environment variable files that are used whenprograms are run. You can also use the home directory as the main directory forstoring data.

v TheWebSphere Operational Decision Management product code must be loadedon to the system from tape, so that you can use it to install and configure.

Installing on z/OSBefore you can install and run the event runtime on WebSphere OperationalDecision Management for z/OS, you must install and configure WebSphereApplication Server for z/OS or WebSphere Application Server NetworkDeployment for z/OS. If installing to WebSphere Application Server NetworkDeployment on z/OS, the Decision Server Events application cannot be clustered.

About this task

Creating a WebSphere Application Server stand-alone server configurationprovides you with the default profile that you augment with WebSphereOperational Decision Management configuration data. For more information, seeCreating stand-alone application server cells on z/OS using the ProfileManagement Tool


http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.zseries.doc/info/zseries/ae/tins_pmtbase.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.zseries.doc/info/zseries/ae/tins_pmtbase.html

For information about creating a practice stand-alone configuration, see Building apractice WebSphere Application Server for z/OS cell .

What to do next

Next, install the WebSphere Operational Decision Management for z/OS productcode on top of WebSphere Application Server. See “Loading the product code fromthe installation media onto z/OS.”

Loading the product code from the installation media onto z/OSInstall the z/OS products and service on your system using SMP/E.

About this task

An IBM Custom-Build Product Delivery Option (CBPDO) is a set of product tapesfor one or more IBM software products that are bundled with cumulative service.

If you use CBPDO, follow the instructions in the copy of WebSphere OperationalDecision Management for z/OS: Program Directory that ships with your order.

You can download the Program Directory in PDF format from the WebSphereOperational Decision Management for z/OS download page. The ProgramDirectory includes instructions on how to load the product code from theinstallation media on to your z/OS system. The Program Directory also providesinstructions about how to set up the installation file system so that you can run theconfiguration scripts.

For further information, see the following information sources:v IBM Software Support Centerv WebSphere Application Server for z/OS product supportv PSP buckets

Procedurev If you are installing from a driving system, make sure that the maintenance level

of the target system meets the requirements for WebSphere Operational DecisionManagement for z/OS.

v When installation is complete, make sure that the installation file system ismounted at was_install_dir or a similar mount point of your choice on each targetsystem.

Creating a component directoryCreate a component directory where you can edit and run the Decision ServerEvents and WebSphere Operational Decision Management configuration scriptsand store logs.

About this task

To edit and run the Decision Server Events and WebSphere Operational DecisionManagement configuration scripts and to store logs, create a directory, known asthe component directory. When you edit and run the configuration scripts, you cancopy the scripts from the read-only directory to this home directory where youhave read and write permissions.


http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.zseries.doc/info/zseries/ae/tins_practiceinstall.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.installation.zseries.doc/info/zseries/ae/tins_practiceinstall.html

http://www.ibm.com/software/support/

http://www-947.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server_for_z~OS

http://www14.software.ibm.com/webapp/set2/psearch/search?domain=psp

Procedure

Create the component directory:v To mount a new file system, follow the instructions in z/OS UNIX System

Services Planning manual.v To create a directory in an already mounted file system use the mkdir command.

For example:mkdir -p component_dir

where component_dir is the full path to the component directory you want tocreate.

v From TSO, run the following commands:

Note: The MVS™ data set needs update permission for the OMVS task.ALLOCATE DATASET(’WBE.WBESZ1’) DSNTYPE(HFS) SPACE(5,5) DIR(1) CYLFREE DATASET(’WBE.WBESZ1’)MOUNT FILESYSTEM(’WBE.WBESZ1’) TYPE(HFS) MOUNTPOINT(’component_dir’)

Where component_dir is the full path to the component directory you want tocreate.

Note: The ALLOCATE command shown is an example. You must allocate enoughstorage to the data set so that it can contain the configuration files and logs thatare produced. Typically, the initial allocation size is 20 MB.

To delete the component directory use the following command UNMOUNTFILESYSTEM(’WBE.WBESZ1’) NORMAL.

Creating the event runtime database on z/OSDecision Server Events requires a database for the event runtime. This eventruntime is the shared, secured location that contains assets such as businessobjects, events, and actions.

About this task

The full list of supported database managers is available on the web at WebSphereOperational Decision Management Detailed System Requirements.

This information is used when configuring the event runtime database. See Eventruntime database settings.

To install, you must have CREATE and VIEW privileges on the event runtimedatabase.

Procedure1. To create the event runtime database, locate the db2zOS.sql script which is

supplied with Decision Server Events. The script is in the <InstallDir>/events/config/db directory.

2. Send the db2zOS.sql script to the Database Administrator (DBA). Ask the DBAto edit and run the script to create the event runtime database. Give the DBAthe following information:v The user ID and password that you want to use to access the event runtime

database. The user ID is used as the schema name to access product tables atrun time. The DBA must ensure that the user ID has CREATE and VIEWauthority on the event runtime database.


http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/bpxzb2A0/CCONTENTS

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/bpxzb2A0/CCONTENTS

http://www-01.ibm.com/support/docview.wss?uid=swg27023067#3

http://www-01.ibm.com/support/docview.wss?uid=swg27023067#3

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.ref/topics/repositorydbsettings.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.ref/topics/repositorydbsettings.htm

v The name that you want the DBA to name the event runtime database.v The instructions for editing the db2zOS.sql script that are provided in

“Editing the db2zOS.sql script.”v The DBA can use a sample JCL job called HBREVDDL to copy the database

Data Definition Language (DDL) into a Partitioned Data Set (PDS). The PDSis used to configure an Events database. The sample job is located in the++HBRWORKDS++.SHBRJCL working data set. Additional information onhow to use the sample is included in the HBREVDDL job.

3. Ask the DBA to provide to you the following information:v The host name to use to connect to the database.v The port number to use to connect to the database.

Results

The DB2 event runtime database is now created. The DDL is copied to theBSMISC1 member.

What to do next

Next, follow the instructions in “Installing on z/OS” on page 81 to installWebSphere Application Server on the LPAR on which you want to install DecisionServer Events.

Editing the db2zOS.sql scriptThe db2zOS.sql script creates the event runtime database on DB2 for z/OS.

About this task

The script must be run by someone with Database Administrator (DBA) authorityon DB2 for z/OS. Give a copy of the following instructions to the DBA when yousend them the script.

Procedure

Before you can run the db2zOS.sql script, you must edit the script to providedetails of your system, as shown in the following table. The following variablesmust be replaced in this SQL so that the correct values are used to create the eventruntime database:

Table 4. Variables in SQL script that must be replaced.

Variable in the script Description

@SQLID@ Change all occurrences of the variable to bethe user ID that runs this SQL against DB2.

@DBNAME@ Change all occurrences of the variable to bethe name of the database.

@STOGRP@ Change all occurrences of the variable to bethe name of the storage group that is usedfor the database.

@VOLUMES@ Change all occurrences of the variable to bethe name of the volumes that are used forthe database.


Table 4. Variables in SQL script that must be replaced. (continued)

Variable in the script Description

@VCAT@ Change all occurrences of the variable to bethe name of the integrated catalog facilitycatalog (vcat) that is used for the database.

@SCHEMA@ Change all occurrences of the variable to bethe user ID that uses to access the database.

All tables are created in bufferpool BP1 and all indexes are created in bufferpoolBP2. You can change these values depending on the bufferpools that you are using.

Configuring the event runtime to run on WebSphereApplication Server

After you have installed WebSphere Application Server and loaded the WebSphereOperational Decision Management code on to the z/OS system, you must runseveral configuration scripts to complete the installation.

Before you begin

To run the scripts you must have authority to access and deploy to the WebSphereApplication Server server. Ensure that the component directory has been created.See “Creating a component directory” on page 82.

Procedure1. Copy the configuration scripts from the product installation to the component

directory:cd <InstallDir>/eventscp -R config component_dir

Where component_dir is the example component directory that you created in“Creating a component directory” on page 82.

2. Edit the setenv file to add appropriate values for your installation. For moreinformation, see Editing the setenv file.

3. Run the following script to create the links that are required from theWebSphere Application Server profile directory to the WebSphere OperationalDecision Management home directory:component_dir/config/was/create_wbe_links.sh

This script creates symbolic links to the <WAS_HOME>/lib directory. If thatdirectory is a symbolic link, you must run <WAS_HOME>/bin/zExpandSymlinks.sh to convert the WebSphere Application Server symboliclinks to physical directories. For more details about zExpandSymlinks see IBMWebSphere Application Server V8 z/OS customization.

4. Stop then start WebSphere Application Server to pick up the new files. Formore information about starting and stopping WebSphere Application Server,see Managing application servers.

5. Create the WebSphere Application Server data connection that is required bythe event runtime by running the following script:component_dir/config/was/configure_wbe_datasource.sh event-runtime-db-user-nameevent-runtime-db-password

Where event runtime-db-user-name and event-runtime-db-password are the user IDand password that you use to access the event runtime database.


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

http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/topic/com.ibm.iea.was_v8/was/8.0/zOS/WASV8_zOS_Customization.pdf

http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/topic/com.ibm.iea.was_v8/was/8.0/zOS/WASV8_zOS_Customization.pdf

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/trun_svr_manage.html

When you create the database tables in “Creating the event runtime databaseon z/OS” on page 83, use the WebSphere Application Server administrationconsole to provide the currentSQLID custom property of “Event RuntimeDatasource”, as the schema name used in db2zOS.sql script.

6. Run the following script to set the event runtime properties:component_dir/config/wbe/update_wbeprops.sh

7. Run the following script to configure WebSphere Application Server:component_dir/config/was/configure_server_zOS.sh

8. Run the following script to install the wberuntimeear application:component_dir/config/was/install_app.sh

9. Configure the WebSphere Application Server messaging provider forWebSphere Operational Decision Management.If you are using the System Integration Bus for messaging, run the followingscripts to configure the JMS messaging provider:component_dir/config/was/configure_bus.shcomponent_dir/config/was/configure_messaging.sh

However, if you are using WebSphere MQ for messaging, ensure that the MQvariables are set in the component_dir/config/was/setenv.sh file and run thefollowing script:component_dir/config/was/configure_MQ_JMS_messaging.sh

Note: You must use at least version 7.0.1 of WebSphere MQ. For moreinformation, see Information about using the WebSphere MQ messagingprovider for WebSphere Application Server Version 8.0.

10. If you have enabled security in your WebSphere Application Server, run oneof the following scripts to enable the required users to access Decision ServerEvents:v If you use federated repositories, run component_dir/config/was/

enable_wbe_appsecurity.sh userid-needing-wodm-accesspassword-for-userid

where userid-needing-wodm-access is the user ID and password-for-userid is thepassword for the user ID.

v If you use RACF, define EJB roles for RACF security. To use the eventruntime with RACF security enabled, you must create the EJB roles byrunning sets of commands to create roles, give groups access to the EJBroles, and activate the changes.

In the following steps:v <SAF.profilePrefix> is the value that you identified for the property named

com.ibm.security.SAF.profilePrefix in “Step 1: Checking the existingsetup” on page 32.

v <UserName> is the name that you assigned to a specific group in “Step 3:Creating RACF groups” on page 34.

a. Use the following commands to create the RACF EJB roles to allow usersvarious access rights:1) RDEF EJBROLE (<SAF.profilePrefix>).WBEAdmins

2) RDEF EJBROLE (<SAF.profilePrefix>).WBEUsers

3) RDEF EJBROLE (<SAF.profilePrefix>).WBEDashboardUsers

4) RDEF EJBROLE (<SAF.profilePrefix>).WBERestApiUsers

5) RDEF EJBROLE (<SAF.profilePrefix>).WBERestApiPrivilegedUsers

6) RDEF EJBROLE (<SAF.profilePrefix>).WBEHTTPConnectorUsers


https://www-304.ibm.com/support/docview.wss?uid=swg21498708

https://www-304.ibm.com/support/docview.wss?uid=swg21498708

b. Use the following commands to give the groups access to the EJB roles:1) PE (<SAF.profilePrefix>).WBEAdmins CLASS(EJBROLE) ID(<UserName>)

ACCESS(READ)

2) PE (<SAF.profilePrefix>).WBEUsers CLASS(EJBROLE) ID(<UserName>)ACCESS(READ)

3) PE (<SAF.profilePrefix>).WBEDashboardUsers CLASS(EJBROLE)ID(<UserName>) ACCESS(READ)

4) PE (<SAF.profilePrefix>).WBERestApiUsers CLASS(EJBROLE)ID(<UserName>) ACCESS(READ)

5) PE (<SAF.profilePrefix>).WBERestApiPrivilegedUsersCLASS(EJBROLE) ID(<UserName>) ACCESS(READ)

6) PE (<SAF.profilePrefix>).WBEHTTPConnectorUsers CLASS(EJBROLE)ID(<UserName>) ACCESS(READ)

c. Use the following command to update the RACF system to activate thechanges:1) SETR RACLIST(EJBROLE) REFRESH

11. Stop then restart WebSphere Application Server. See Managing applicationservers.

Results

The event runtime on WebSphere Operational Decision Management for z/OS isnow installed and configured.

Installing on a managed node on z/OSYou can install the event runtime on a managed node on WebSphere ApplicationServer for z/OS.

Procedure1. Create your database tables and edit the setenv.sh file in component_dir/

config/was, component_dir/config/db, and component_dir/config/wbe to pointto the database tables. For more information, see Editing the setenv file.

Note: You must set the server as $dmgr in component_dir/config/was/setenv.sh.

2. Install WebSphere Operational Decision Management for z/OS as described in“Configuring the event runtime to run on WebSphere Application Server” onpage 85.

3. Define EJB roles for RACF security. To use the event runtime with RACFsecurity enabled, you must create the EJB roles by running sets of commands tocreate roles, give groups access to the EJB roles, and activate the changes.In the following steps:v <SAF.profilePrefix> is the value that you identified for the property named

com.ibm.security.SAF.profilePrefix in “Step 1: Checking the existingsetup” on page 32.

v <UserName> is the name that you assigned to a specific group in “Step 3:Creating RACF groups” on page 34.

a. Use the following commands to create the RACF EJB roles to allow usersvarious access rights:1) RDEF EJBROLE (<SAF.profilePrefix>).WBEAdmins

2) RDEF EJBROLE (<SAF.profilePrefix>).WBEUsers





3) RDEF EJBROLE (<SAF.profilePrefix>).WBEDashboardUsers

4) RDEF EJBROLE (<SAF.profilePrefix>).WBERestApiUsers

5) RDEF EJBROLE (<SAF.profilePrefix>).WBERestApiPrivilegedUsers

6) RDEF EJBROLE (<SAF.profilePrefix>).WBEHTTPConnectorUsers

b. Use the following commands to give the groups access to the EJB roles:1) PE (<SAF.profilePrefix>).WBEAdmins CLASS(EJBROLE) ID(<UserName>)

ACCESS(READ)

2) PE (<SAF.profilePrefix>).WBEUsers CLASS(EJBROLE) ID(<UserName>)ACCESS(READ)

3) PE (<SAF.profilePrefix>).WBEDashboardUsers CLASS(EJBROLE)ID(<UserName>) ACCESS(READ)

4) PE (<SAF.profilePrefix>).WBERestApiUsers CLASS(EJBROLE)ID(<UserName>) ACCESS(READ)

5) PE (<SAF.profilePrefix>).WBERestApiPrivilegedUsers CLASS(EJBROLE)ID(<UserName>) ACCESS(READ)

6) PE (<SAF.profilePrefix>).WBEHTTPConnectorUsers CLASS(EJBROLE)ID(<UserName>) ACCESS(READ)

c. Use the following command to update the RACF system to activate thechanges:1) SETR RACLIST(EJBROLE) REFRESH

4. Add the event runtime cluster as a member to the service integration bus:a. Click Service integration > Buses > WbeBus > Bus members.b. Click Add. Click Cluster > EventRuntimeCluster, then click Next.c. Select a messaging engine policy setting from the options High availability,

Scalability, or Scalability with high availability. For more details aboutyour selection, see Messaging engine policy assistance.

d. To ensure the recovery of JMS messages after a failover, you must configurea message store. Set the type of message store by selecting either File storeor Data store. For more information about this concept and other highavailability concepts, see Establishing high availability. Click Next

e. On the Configure messaging engines panel, click the messaging enginename.

f. Set the data store values:1) Either, if you are using a file store, set the value of Log directory path to

point to a data store on a shared file system, for example,c:\filestoredirectory. Set the Permanent store directory path to pointto a data store on a shared file system.

2) Or, if you are using a database, set the Data connection JNDI name, theschema name and the authentication alias, to point to a data store on adatabase that you have already created.

Click Next.g. Click Change heap sizes. Accept the default values.h. Review the Summary information. Click Finish and Save.

5. Create three service integration bus destinations for the event runtimemessaging destinations:a. Click Service integration > Buses > WbeBus > Destinations.b. Click New.c. Click Queue, and click Next. In the Identifier field, type eventQueue, then

click Next.


http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/cjt1005_.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/welc6tophighavail.html

d. Repeat this step to create two further queues, with identifiers ofhistoryModuleQueue and durableEventQueue.

e. Click Finish and Save.6. Modify the provider endpoints for the connection factories to point to the

servers in your event runtime cluster:a. Click Resources > JMS > Connection factories.b. From the Scope list, click Cell=cell-name, where cell-name is the name of the

cell.c. Click WbeConnectionFactory

d. In the Provider endpoints field, type hostname:port,hostname:port, whereeach hostname:port pair corresponds to the host name andSIB_ENDPOINT_ADDRESS of the application server.

e. Click Apply and Save.7. Modify the provider endpoints for the JMS queue connection factory to point to

the servers in your event runtime cluster:a. Click Resources > JMS > Queue connection factories.b. From the Scope list, click Cell=cell-name, where cell-name is the name of the

cell.c. Click WbeQueueConnectionFactory

d. In the Provider endpoints field, type hostname:port,hostname:port, whereeach hostname:port pair corresponds to the host name andSIB_ENDPOINT_ADDRESS of the application server.

e. Click Apply and Save.8. If SIB messaging is used as the messaging provider by the event runtime and

the WbeBus service integration bus is configured with a cluster bus member,you must configure durable subscription home settings on the followingactivation specifications:v wbeca_file_asv wbeca_http_asv wbeca_jdbc_asv wbeca_jms_asv wbeca_soap_asSelect the durable subscription home from the available messaging engines forthe cluster.

Important: Do not change any other settings for the wbeca activationspecifications.

Installing graphical tools when the event runtime is on z/OSTo develop applications in Decision Server Events that you deploy to the eventruntime on z/OS, you must install Event Designer and Event Flow.

About this task

Event Designer and Event Flow can be installed on any operating system exceptz/OS, so you must install these components on a second computer with asupported operating system. Event Designer and Event Flow can connect to theremote event runtime that is hosted on z/OS.


To install the graphical tooling, select the graphical tooling components when youinstall Decision Server Events on the second computer. For more information, seeConfiguring Decision Server Events.

What to do next

When you have installed Event Designer and Event Flow, you can develop theassets that you require in your event application. Then you can deploy the assetsto the event runtime which is hosted on a z/OS system, by specifying the TCP/IPconnection details of the z/OS system when you connect to the event runtime inEvent Designer or Event Flow.

Verifying your z/OS installationYou can check that the event runtime on WebSphere Operational DecisionManagement for z/OS is properly installed and configured by loading thesupplied verification event project and sending an event through the eventruntime.

Before you begin

Install and configure WebSphere Operational Decision Management, includingconfiguring a JMS messaging provider.

Ensure that you have installed Event Designer on a separate computer.

If you switched on WebSphere Application Server security during installation, youmust configure user authentication to the event runtime before verifying theinstallation. See User authentication

Procedure1. On the computer on which you have installed the event runtime, ensure that

the WebSphere Application Server server is running.2. Check that the event runtime application has been installed and started on

WebSphere Application Server:a. Start the WebSphere Application Server administrative console. See

Starting the WebSphere Application Server administrative console.b. Log in to the WebSphere Application Server administrative console with a

user ID of your choice.c. In the navigation tree of the WebSphere Application Server administrative

console, click Applications > Application Types > WebSphere enterpriseapplications.

d. Ensure that the wberuntimeear application is listed and shown as started.e. If you have prepared the environment for testing, ensure that the

wbetesterear application is listed and shown as started.f. If you have installed Business SpaceEnsure, ensure that the following

applications are listed and shown as started:v BSpaceEAR_<node_name>_<server_name>

v BSpaceForms_<node_name>_<server_name>

v BSpaceHelp_<node_name>_<server_name>

v mm.was_<node_name>_<server_name>


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

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.config/topics/configuringuserauthentication.htm#userauthentication

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.admin/topics/administeringwas.htm#startingtheintegratedsolutionconsole

3. On the computer on which you installed the event runtime, create a directorycalled DecisionServerTest and make a note of the location in which youcreated the directory.

4. On the computer on which you installed Event Designer, open Event Designerand right-click in the Event Explorer view, then click Import. The Importwizard opens.

5. In the Import wizard, click Event Project from XML File > Next.6. Click Browse, navigate to <InstallDir>\connectors\validation and select the

event project called installValidation.xml. Click Next. Accept the defaultsettings for the rest of the wizard and click Finish to import the event projectinto your workspace.

7. In the Event Explorer view, expand the event project, expand the Outgoingfolder, and open the Outgoing action, shown in the following screen capture:

8. In the Action editor, click the Connector tab, shown in the following screencapture:


9. In the Folder on that computer field, replace the existing value with thecomplete path that points to the location of the DecisionServerTest directorythat you created. Save your changes.

10. To deploy the event project, right-click the event project in the Event Explorerview and select Deploy. The Deploy wizard opens, shown in the followingscreen capture:


11. Select Deploy all assets and click Next.12. Enter the connection details for your event runtime, shown in the following

screen capture:

Ensure that the host name and port values are correct for the WebSphereApplication Server instance in which the event runtime is deployed. The port


value is the WC_defaulthost port, which can be determined through theWebSphere Application Server administrative console. Enter the user ID andpassword, if security is enabled.

13. Click Finish to deploy the event project. A message is displayed indicatingthat the event project is deployed successfully. Close Event Designer.

14. Start the stand-alone technology connectors. See Running the stand-alonetechnology connector application on z/OS.This is an example of a successful connector startup:/usr/lpp/zDM/V8R0M0/events/connectors/bin>connectors.sh*********************************************************IBM Decision Server technology connectors (c)Copyright IBM Corp. 2003, 2011Version: IBM WebSphere Operational Decision Management 8.0.0.0Locale: en_GBJava version: 1.6.0*********************************************************BEER0561I: The technology connectors are waiting for wberuntimeear.BEER0644I: The technology connectors established communicationwith wberuntimeearBEER0590I: Connector event runtime checkpoint: 2009-04-14 08:58:10.718BEER2608I: Authentication mode: NoneBEER2609I: Event Runtime users group: WBEUsersBEER2610I: Event Runtime administration group: WBEAdminsBEER2611W: *** WARNING: SECURITY IS NOT ENABLED ***BEER2612W: User maestro is granted full access to the event runtimeBEER0611I: Initialization is completeBEER0670I: JNDI provider URL: corbaloc:iiop:localhost:2809Connectors>

For more information about starting connectors, including details about theoptional parameters, see Running technology connectors.

15. Send a test event to the event runtime by running cmdline.sh. Run<InstallDir>/connectors/bin/cmdline.sh <test-event-file>, where<test-event-file> is the complete path to where theinstallValidation_event.xml file is located, for example,<InstallDir>/connectors/bin/cmdline.sh /usr/lpp/zDM/V8R0M0/events/connectors/validation/installValidation_event.xml. A new file calledValidationTest random-number.xml is put in the DecisionServerTestdirectory, where random-number is a system-generated number that makes thefile name unique.

Note: In cmdline.sh there are relative paths (/../../) to setenv.sh files. Youpreviously modified these relative paths in the component directory, but notin the product installation directory that the relative path references (thecomponent directory is a copy of part of the product installation directory).You can fix this issue in one of two ways:v Either, edit the setenv.sh file to include a parameter that specifies the

location of the component directory.v Or, copy the connectors directory into the component directory. If you use

this solution, you must change the directory path to <InstallDir>/connectors/bin/cmdline.sh .

Results

You have now verified your z/OS installation.

Tuning your z/OS configurationSome tuning of the system might lead to higher performance when processingevents.


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.admin/topics/zos_runningtechnologyconnectors.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.admin/topics/zos_runningtechnologyconnectors.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.admin/topics/runningconnectors.htm

About this task

When considering how you tune your system, there are two main areas to look at:v The event runtime and WebSphere Application Serverv JMS messaging.

The event runtime and WebSphere Application Server

v Turn off logging. For more information, see Logs.v Turn off the recording of history, if not required. See Configuring the event

runtime to record history.v Use technology connectors only if required.

– If events are already in Decision Server Events format, better performancemight be achieved by avoiding the use of connectors. Send events directly tothe Decision Server Events event destinations and receive actions directlyfrom the Decision Server Events action destinations. For example, considerusing the destinations jms/eventDestination, jms/durableEventDestination, jms/actionTopic and jms/durableActionTopic

v Ensure that there are sufficient event rule processing threads. If you are unableto achieve full processor utilization on the Decision Server Events server,consider increasing the value of this property:as.director.server.ruleProcessorInstances.

v On z/OS, using the Type 2 JDBC driver to connect to a local DB2 databaseperforms better than the Type 4 driver. To modify the driver type use theWebSphere Application Server administrative console and navigate to Resources> JDBC > Data sources > WBE Datasource. You can modify the Driver type onthe WBE Datasoure page.

Note: To use the Type 2 driver you might have to set the Native library path onthe JDBC Provider and add the DB2 SDSNEXIT, SDSNLOAD, and SDSNLOD2libraries to the Servant procedure STEPLIB.

v Tune the database.– See DB2 tuning tips for z/OS.

v Tune the JVM.– Consider tuning the JVM in the Servant region and the JVM in the Adjunct

region.– Key tuning parameters are JVM heap size and garbage collection policy. A

small heap can cause frequent garbage collection, which can degradeperformance. A large heap can result in longer pause times.

– See Tuning the JVM.

JMS messaging

v For persistent messaging, consider using a zFS file system, as this offersimproved performance to HFS.

v The key tuning parameters relate to the choice of message reliability level,activation specifications, and size of the discardable data buffer. See Tuningmessaging performance with service integration technologies.

v Message reliability level: A lower reliability level generally provides a higherthroughput. The default reliability level for non-persistent JMS messages isExpress Non-Persistent, and for persistent JMS messages it is Reliable Persistent.The reliability level can be changed by using the connection factories. Use theWebSphere Application Server administrative console (for example, Resources >JMS > TopicConnectionFactories > WbeTopicConnectionFactory).


http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.admin/topics/wbelogs.htm

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.config/topics/tsk_configuring_history_runtime.htm#configuringwebspherebusinesseventsruntimetorecordhistory

http://submit.boulder.ibm.com/infocenter/idwb/v3r8m4/topic/com.ibm.ditaepic.doc/../com.ibm.wodm.dserver.events.config/topics/tsk_configuring_history_runtime.htm#configuringwebspherebusinesseventsruntimetorecordhistory

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/rprf_tunezdb2.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/container_tune_jvm.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tjn0026_.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tjn0026_.html

v Activation specification: Particularly for non-durable JMS events, considerdelivering the messages in batches from the input topic to Decision ServerEvents. This can deliver events more efficiently to Decision Server Events. Forexample, using the WebSphere Application Server administrative console,navigate to Resources > JMS > Activation specifications > wbe_events, and setMaximum batch size.

v Bypass the connectors and send events directly to WebSphere OperationalDecision Management by configuring WebSphere MQ to be the JMS provider.Performance improves when events are received from the WebSphere MQqueue. See Configuring WebSphere MQ to be the JMS provider.

Uninstalling on z/OSRemove the event runtime configuration and product code.

Before you begin

Ensure that you have completed the steps in Editing the setenv file.

About this task

Stop the wberuntimeear application and the technology connectors, then run theconfiguration scripts and SMP/e as directed to remove the configuration andproduct code.

Procedure1. If the connectors are running, stop the connectors.2. Uninstall the wberuntimeear application by using the configuration script.

Run the following command:component_dir/config/was/install_app.sh -undo

Where component_dir is the component directory that you created. See“Creating a component directory” on page 82.

3. Uninstall the connector applications by running the following command:component_dir/config/was/uninstall_ca.sh

You are prompted for a user name and password.4. Remove the data connection from WebSphere Application Server by running

the following command:component_dir/config/was/configure_wbe_datasource.sh -undo

5. If the System Integration Bus was selected as the messaging provider, removethe messaging configuration by running the following command:component_dir/config/was/configure_messaging.sh -undo

Otherwise, if WebSphere MQ was selected as the messaging provider, run thefollowing command:component_dir/config/was/configure_MQ_JMS_messaging.sh -undo

6. Remove the messaging bus configuration by running the following command:component_dir/config/was/configure_bus.sh -undo

7. Remove the application server configuration by running the followingcommand:component_dir/config/was/configure_server_zOS.sh -undo

8. Remove the Decision Server Events properties by running the followingcommand:


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


component_dir/config/wbe/update_wbeprops.sh -undo

9. Stop the WebSphere Application Server. For more information about startingand stopping the WebSphere Application Server, see Managing applicationservers.

10. Remove the Decision Server Events links from the WebSphere ApplicationServer profile directory by running the following command:component_dir/config/was/delete_wbe_links.sh

11. Run SMP/e to remove the product code from the system.

Results

The event runtime configuration and product code are now removed from thesystem.




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 101

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Index

Aaccess rights

for MBean descriptors 45asynchronous execution

support in Decision Server 57

Ccells

Rule Execution Server configuration ina cluster environment 64

CICSconfiguring forzRule Execution Server

for z/OS 20executing rules on Rule Execution

Server on WebSphere ApplicationServer for z/OS through WOLA 53

wrapper program, calling 71COBOL dynamic link 70COBOL static link 69code integration

CICS wrapper program 71using a dynamic link 70using a static link 69

command securityzRule Execution Server for z/OS 29

compiling generated code 77configuration

Decision Server for z/OS 1for z/OS 74Resource Manager JCL 76

configuringDecision Server for z/OS 3Rule Execution Server on WAS for

z/OS 3zRule Execution Server 3zRule Execution Server for z/OS 19zRule Execution Server for z/OS on

CICS JVM server 22configuring Rule Execution Server

connecting to database 44creating a connection pool 42creating a data source 42database, connecting to 44deploying the hosted transparent

decision service EAR 48deploying the management EAR 44deploying the XU RAR 46environments 64federated repository, using 36resgroup to the Monitor role,

mapping 38WebSphere Application Server for

z/OSWebSphere Optimized Local

Adapters (WOLA) 51connection factories

for WebSphere MQ input and outputqueues 58

connection factories (continued)for WebSphere MQ input and output

topics 59connection pool, creating

Rule Execution Server 42connection security

zRule Execution Server for z/OS 27console security

zRule Execution Server for z/OS 28

Ddata source, creating

Rule Execution Server 42database, connecting

Rule Execution Server 44DB2 persistence layer

zRule Execution Server for z/OS 6Decision Server for z/OS

configuring 3customizing JCL variables 4data sets and files installed 1load library 3securing directories 25working data sets 5

deploying 48WebSphere Application Server for

z/OS management EAR 44deploying the XU RAR 46deploying, hosted transparent decision

service EARRule Execution Server 48

deploying, management EARRule Execution Server 44

deploying, XU RAR,Rule Execution Server 46

diagnosticsRule Execution Server Console 31,

50, 51disabling security

zzRule Execution Server for z/OS 26

Eenvironments

Rule Execution Serverconfiguration 64

executing rules in batchusing WebSphere Optimized Local

Adapters (WOLA) 53

Ffederated repository, using

Rule Execution Server 36

Ggenerated COBOL code

compiling 77executing 77linking 77

Get Started for Sub-capacity Pricing 73GSSP 73

HHBRINST 4HBRUUPTI 5hosted transparent decision service EAR,

deployingRule Execution Server 48

IIMS

configuration 21executing rules on Rule Execution

Server on WebSphere ApplicationServer for z/OS through WOLA 54

versions 21input/output queues

creating the connection factory inWebSphere MQ 58

input/output queues, WebSphere MQactivation specification 61

input/output topics, WebSphere MQactivation specification 62creating the connection factory 59

installing Rule Execution Servercreating a JDBC provider 41

JJ2C authentication alias

WebSphere Application Server forz/OS

Rule Execution Server 41JCL

for Resource Managerconfiguration 76

JCL variables 4JDBC provider, creating

Rule Execution Server 41

LLast Participant Support (LPS)

enabling in WebSphere MQ 63linking generated code 77load library

zRule Execution Server for z/OS 3


Mmanagement EAR, deploying

Rule Execution Server 44mapping, resgroup to the Monitor role

Rule Execution Server 38MBeans

and WebSphere MQ 57descriptors for WebSphere Application

Server 7.0 45message-driven rule beans

and WebSphere MQinstallation 63queue activation specification 61topic activation specification 62

MQIntegrating WebSphere MQ in

WebSphere Application Server 57

Ooverview

Decision Server for z/OSconfiguration 1

Ppermissions

for MBean descriptors 45

Qqueues, WebSphere MQ

for request messages 58for response messages 59

RRACF classes for server security

zRule Execution Server for z/OS 25resgroup to the Monitor role, mapping

Rule Execution Server 38Resource Manager 73, 75rule execution 68Rule Execution Server on WAS for z/OS

configuring 3rule sessions

and WebSphere MQ integration 57running generated code 77

Ssecuring directories

Decision Server for z/OS 25security

configuring for WebSphereApplication Server for z/OS 40

configuring for WebSphere OptimizedLocal Adapters (WOLA) 40

security optionszRule Execution Server for z/OS 24

server groups 9configuring 19

server securityzRule Execution Server for z/OS 25

SMF 73SMF data collection

sample code 78System Management Facility 73

Ttopics, WebSphere MQ

for request messages 60for response messages 61

topologieszRule Execution Server for z/OS 10,

12, 14, 16transaction management

in WebSphere Application Server, LastParticipant Support 63

Uusage data collection

sample code 78

Vvariables

WebSphere Application Server forz/OS 41

WWebSphere Application Server

Rule Execution Server celldeployment 66

WebSphere Application Server for z/OSconfiguring WOLA load libraries 52security, configuring 40

WebSphere Application Server for z/OSvariables 41

WebSphere MQinput queue, creating 58input topic, creating 60integrating in WebSphere Application

Server 57Last Participant Support, enabling 63message-driven rule bean,

installing 63output queue, creating 59output topic, creating 61queue activation specification,

creating 61queue connection factory, creating 58topic activation specification,

creating 62topic connection factory, creating 59

WebSphere Optimized Local Adapters(WOLA) 51

deploying the EJB 55executing rules in batch 53executing rules in CICS 53executing rules in IMS 54security, configuring 40verifying the configuration 56

WOLASee WebSphere Optimized Local

Adapters (WOLA)

WOLA load librariesconfiguring on WebSphere Application

Server for z/OS 52working data sets

Decision Server for z/OS 5wsadmin scripts

configuring Rule Execution Server onWebSphere Application Server forz/OS 50

XXU RAR, deploying

Rule Execution Server 46XUConnectionFactory

default JNDI name 64

Zz/OS

WebSphere Optimized Local Adapters(WOLA) 51

z/OS subsystem 75zRule Execution Server

configuring 3zRule Execution Server for z/OS

before you start configuring 9command security 29configuring 19configuring CICS 20configuring IMS 21connection security 27console security 28DB2 persistence layer 6diagnostics 31, 50, 51RACF classes for server security 25security options 24server groups 9starting 30topologies 10, 12, 14, 16verifying configuration 31, 50, 51

zRule Execution Server for z/OS on CICSJVM server supported versions

CICS 22zRule Execution Server for z/OS security

server 25zzRule Execution Server for z/OS on

CICS JVM serverconfiguring 22

zzRule Execution Server for z/OSsecurity

disabling 26


��

Printed in USA

IBM WebSphere Operational Decision Management: Configuring

Documents

Transcript of IBM WebSphere Operational Decision Management: Configuring