Several instances

The UTM application can operate several entities (databases) of the Resource Manager, provided the Resource Manager supports multi-instance mode. In this case, you must specify a separate open string for each instance. Each open string must be entered in a separate line in the start parameter file. The name of the Resource Manager name must match the individual start parameter statements. For the open strings (databases), you must specify various names (entered in the DB= parameter within the strings, e.g. +DB=DBNAME1 and +DB=DBNAME2).

The general syntax for start parameters of several XA instances of a Resource Manager is:

.RMXA[xa-inst-name1] RM="name",OS="openstring1"
.RMXAxa-inst-name2 RM="name",OS="openstring2"
.RMXAxa-inst-name3 RM="name",OS="openstring3"
...

Here the value of xa-inst-name1, xa-inst-name2, etc. must always match the generation value of the XA-INST-NAME parameter of an RMXA statement of the KDCDEF generation.

Please observe the following three rules to ensure that the uniqueness of the assignment of XA instances to the UTM generation information is guaranteed in all cases:

• Use at most one empty XA instance name and at most one empty Oracle DB name per UTM application.

• All XA instance names must be unique in the UTM application.

• All Oracle DB names must be unique in the UTM application.

If the Resource Manager requires a close string, a close string must also be specified for each instance.

CAUTION!

In conjunction with a linked database connection (generated in openUTM), there must be no unlinked database connection.

For examples of start statements to the database system with which openUTM can be linked, refer to section "Example of Oracle start parameters".

Example

This example illustrates the connection of two Oracle XA databases to openUTM (Unix/Linux/Windows).

Start parameters:

.RMXA 
RM="Oracle_XA",OS="Oracle_XA+Acc=P/*UTMUSER/*UTMPASS+SqlNet=RAC2+SesTm=60+LogDir=.+DbgFl=0"
.RMXAEVE 
RM="Oracle_XA",OS="Oracle_XA+DB=EVESDB+Acc=P/*UTMUSER/*UTMPASS+SqlNet=RAC1+SesTm=60+LogDir=.+DbgFl=0"

The first start parameter contains only the prefix ".RMXA", i.e. an empty XA instance name, and is therefore assigned to the first XA Resource Manager generated in openUTM without an XA-INST-NAME parameter. In other words the first XA instance sets up a connection with the correspondingly generated access data ("MaxTheSuperman", etc.).

The second start parameter contains the prefix ".RMXAEVE", i.e. the second XA instance is assigned to the generated XA Resource Manager with XA-INST-NAME=EVE, and the access data generated for this ("Eve", etc.) is used by this XA Instance.

KDCDEF generation:

RMXA XASWITCH=xaoswd,USERID='MaxTheSuperman',PASSWORD='PasswordOfMax'
RMXA XASWITCH=xaoswd,USERID='Eve',PASSWORD='PasswordOfEve',XA-INST-NAME=EVE