Copyright © Cloud Software Group, Inc. All Rights Reserved |
Connecting the Gateway to a Windows, or Solaris Data Object BrokerYou can configure the Data Object Broker and the Gateway to reside on different domains and operating systems (z/OS, Windows, or Solaris). The Gateway must be in the same domain as the DB2 database system.The following configuration tasks are required to access a Data Object Broker from a different operating environment than your Gateway:Prepare the TIBCO Object Service Broker relay file – RELAYCFG member in the CNTL data set. This file associates the TIBCO Object Service Broker communications identifier with the TCP/IP application addressing information.
TIBCO Object Service Broker for z/OS Installing and Operating for detailed information about preparing the TIBCO Object Service Broker relay file.TIBCO Object Service Broker Parameters for details about the parameters used in the relay file and how to specify them.Add the following parameters for the TCP/IP connection to the Data Object Broker directory file, huron.dir:
This must be the same value as the node name set in the RELAY parameter file described in Task A, Configure the TCP/IP connection on z/OS. The name of the host machine where the TIBCO Object Service Broker monitor process listens for connections. Specify the following value for the MAXDBMS parameter in the crparm file for your Data Object Broker.
This must be equal to or greater than the value specified in the SERVERS parameter in the startup JCL or HDB2SRVC SYSIN file.Specify the following value for the TDS parameter in the HDB2SRVC statement in the startup JCL or HDB2SRVC SYSIN file. See Gateway Parameters for more details about specifying gateway parameters.
TIBCO Object Service Broker for z/OS Installing and Operating for detailed information about preparing the relay file.TIBCO Object Service Broker Parameters for details about the parameters used in the relay file and how to specify them.
Copyright © Cloud Software Group, Inc. All Rights Reserved |