Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Remote Promotions : Setting Up the Remote Promotions Environment

Setting Up the Remote Promotions Environment
Ensure your systems are properly configured for remote promotions. Because remote promotion generates several layers of nested transactions, there must be at least six peer servers available for each user that is involved with the remote promotion.
Configuration Requirements
Remote promotions require that each node must be configured with the necessary table entries. At the node where you are administering promotions, you must specify:
Each table instance must contain an entry for each node where a promotion can originate.
Example
The following example uses two nodes called LONDON and CHICAGO. If promotions are submitted at LONDON and administered remotely at CHICAGO, the CHICAGO node would require the following table entries for promotions to be possible at both nodes:
One entry for LONDON, one entry for CHICAGO.
@PROM_BACKUPDS ('LONDON')
Identifies the backup data set used for source promotion.
@PROM_BACKUPDS ('CHICAGO')
Identifies the backup data set used for target promotion.
@PROM_NSEC_DEF ('LONDON')
One entry for each object type being promoted.
Identifies the security setting for each object type promoted from source node.
If you also want to administer promotions from the LONDON node, the LONDON node would require the exact same entries as the CHICAGO node above.
Customizing @SCHEDULEMODEL
In z/OS, nodes must have the @SCHEDULEMODEL('MVS','PROM_ALLOC') member customized on each node where promotions are administered, unless data set allocation is done outside TIBCO Object Service Broker. If you are doing batch promotions, other members of @SCHEDULEMODEL are also required.
Customizing @PROM_BACKUPDS
A backup file is allocated for each table instance of @PROM_BACKUPDS that has an entry with the promotion’s source node as the primary key. Another backup file is allocated for a copy of the promotion based on the entry in @PROM_CONSTANTS that has the promotion’s source node as the primary key.
Setting the ALLOC_DATASET Field
In environments where files do not need to be pre-allocated (that is, Windows and Solaris), set the value of the ALLOC_DATASET field to N. The promotion step to allocate data sets ignores any table entries where ALLOC_DATASET=N.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved