A MSW address space should be started on each LPAR in a complex that requires access to a Data Object Broker. In this environment, Execution Environments and database servers on the same LPAR as a MSW will use cross memory communication to the MSW address space. The MSW address space will then use either cross memory communication, if the primary Data Object Broker is on the same LPAR, or the XCF communications protocol if it is not. However, this is not mandatory. Should Execution Environments or database gateways use either TCP/IP or XCF to communicate with its chosen MSW, and this MSW is not on the same LPAR as the primary Data Object Broker, system performance will be impacted.
MSWs may be initialized before or after the Data Object Broker, but both the Data Object Broker and the MSW must be initialized before any other TIBCO Object Service Broker components attempt to connect. Since the MSW address space can wait for the primary Data Object Broker to become available, it is recommended that all MSW address spaces are initialized before the primary Data Object Broker. In addition, if a MSW is not available to the primary Data Object Broker when it initializes, outgoing peer server access will fail. Outgoing peer servers should have retry capability set in their resource details for this reason.
In the multiple Data Object Broker environment, Data Object Brokers and MSWs communicate via either XCF or XMS. It is suggested that the Data Object Brokers in this environment use individual HCS RELAY configuration files that enable XCF only. In addition, for access to MSWs via TCP/IP, it will be necessary to have individual HCS RELAY configuration files to enable them to use different IP addresses.
This section describes the parameters used to enable multiple Data Object Brokers (the descriptions are provided here for convenience; also see
TIBCO Object Service Broker Parameters).
The following parameters initialize a system with three Data Object Brokers, where job name DC51ADB1 is the primary Data Object Broker. Unless shown, all other Data Object Broker parameters are identical as they would be for a normal configuration.
This section describes the parameters used to configure a MSW (the descriptions are provided here for convenience; also see
TIBCO Object Service Broker Parameters).
Customize the MSRUN or MSRUNSTC JCL and the MSRUNPRM parameters. Most of the parameters are similar to their Data Object Broker counterparts.
In addition, the following Data Object Broker parameters are supported by Message Switches and have the same functionality as when applied to Data Object Broker:
Messages Switches also support the Execution Environment parameter TDS. When used to configure Messages Switches, TDS represents the COMMID of the Data Object Broker to which the MSW will connect.
To allocate the Coupling Facility structure, specify the name of Coupling Facility structure to be used by the Data Object Broker group, and its initial and maximum size, as follows:
Values for the initial and maximum size can be estimated using the S6BBRCFC utility. For details, see
TIBCO Object Service Broker Utilities. Sufficient storage must be available in the specified Coupling Facility to allow key control blocks to be copied when an operator initiates a switch. For details on the switch process, see
Switch Processing.