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


Chapter 10 Using Multiple Data Object Brokers : Configuring Data Object Brokers and Message Switches

Configuring Data Object Brokers and Message Switches
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.
Initialization
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.
Configuring Data Object Brokers
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).
Parameters
 
XCF group this Data Object Broker is to join. The presence of this parameter enables support of Multiple Data Object Brokers.
A valid XCF member name, up 8 characters
Member name of this Data Object Broker instance in the XCF group, defaulted to the job name of this Data Object Broker instance.
This Data Object Broker becomes the primary if no primary Data Object Broker already exists in the XCF Group.
This Data Object Broker initializes as a secondary Data Object Broker.
Name of Coupling Facility structure to be used by this Data Object Broker group.
Example – Parameter Values
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.

 
Parameter     Instance 1       Instance 2       Instance 3
 
JOBNAME       DC51ADB1         DC51ADB2         DC51ADB3
COMMID        S6DCDOBA         S6DCDOBA         S6DCDOBA
XCFGROUP      DCDOBA           DCDOBA           DCDOBA
XCFMEMBER     DCDOB1           DCDOB2           DCDOB3
XCFMODE       AUTOMATIC        SECONDARY        SECONDARY
XCFSTRUCTURE  S6BOSB_DCTDS_1   S6BOSB_DCTDS_1   S6BOSB_DCTDS_1

 
Sample Data Object Broker HCS Relay Parameter File

 
<relay xmlns='http://www.tibco.com/OSB/relayparms.xsd'>
  <xcfparms groupname='S6DCOSB'/> <!--No TCP/IP support XCF only-->
  <directory>
    <node name="DCDOB1">         <!--Entries for multiple DOBs-->
      <xcf />
    </node>
    <node name="DCDOB2">
      <xcf />
    </node>
    <node name="DCDOB3">
      <xcf />
    </node>
    <node name="S6DCDOBA">       <!--Entry for the MSW-->
      <xcf />
    </node>
  </directory>
</relay>

 
Configuring Message Switches
This section describes the parameters used to configure a MSW (the descriptions are provided here for convenience; also see TIBCO Object Service Broker Parameters).
Parameters
Customize the MSRUN or MSRUNSTC JCL and the MSRUNPRM parameters. Most of the parameters are similar to their Data Object Broker counterparts.
 
XCF group this Data Object Broker is to join. The presence of this parameter enables support of multiple Data Object Brokers.
A valid XCF member name, up to 8 characters
Member name of this Data Object Broker instance in the XCF group, defaulted to the job name of this Data Object Broker instance
Name of Coupling Facility structure to be used by this Data Object Broker group.
Number of seconds a MSW address space will wait for the primary Data Object Broker to become available. 0 = wait indefinitely.
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.
Example – Parameter Values
Sample MSW parameters to connect to a Data Object Broker group:

 
MAXUSERS          1024
XCFGROUP          DCDOBA
XCFMEMBER         DCMSW1
XCFWAITTIME       60
TDS               S6DCDOBA

 
Sample MSW HCS Relay Parameter File:

 
<relay xmlns="http://www.tibco.com/OSB/relayparms.xsd">
  <tcpipparms tcbnum="3" maxtcbsockets="1000" />
  <xcfparms groupname='S6DCOSB'/>
  <directory>
    <node name="S6DCDOBA">      <!--Entry for this MSW-->
      <xcf />
      <tcpip host="star.na.tibco.com" port="10021" />
    </node>
    <node name="DCDOB1">        <!--Entries for the multiple DOBs-->
      <xcf />
    </node>
    <node name="DCDOB2">
      <xcf />
    </node>
    <node name="DCDOB3">
      <xcf />
    </node>
    <node name="S6DCDOBB">       <!--Entry for a local Peer DOB-->
      <xcf />
    </node>
    <node name="DJCDOB">         <!--Entry for a remote Peer DOB-->
      <tcpip host="10.98.39.114" port="7249" />
    </node>
  </directory>
</relay>

 
 
Allocating the Coupling Facility Structure
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:
 
STRUCTURE NAME(name)
    SIZE(maxsize)
    INITSIZE(initsize)
 
 
Name of Coupling Facility structure. Must match the value of XCFSTRUCTURE used by the Data Object Broker group.
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.

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