![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The following sample TIBCO Object Service Broker network subset revolves around the Local Office node that runs on z/OS. Although the two external databases and the TIBCO Object Service Broker peer rules server are called remote nodes from a networking perspective, they actually reside in the same z/OS operating system image as the local node.The peer TIBCO Object Service Broker nodes are all physically remote. One also operates on z/OS, on a physically separate system from the local node. The other two operate on the Windows and Solaris operating systems.The resource detail entries for the sample network are shown in the following table. The schedule name for these resource entries is WEEKDAYS05.
Resource Type Resource Name Intermediate Rollback Early Release Last User Commit Level PEER2b. PEER2b. PEER3b.
Resource type of API can represent either a Peer Server or a Service Gateway for Files. You must define different resource names for a Service Gateway for Files and a Peer Server. Do not use the name DEFAULT0 for a Service Gateway for Files.
For resource types of HRN and HIN, the resource name must be the COMMID of the remote Data Object Broker.
Schedule Name Applicable Days (MTWTFSS) Exception Date Start Time Online Only Maximum Connection Count
• The Default schedule for type API is in effect for this resource. Refer to Resource Management Option for an example of this resource. The Default schedule specifies a maximum of 16 resources, therefore 16 resources in this group are enabled starting at 5:00 a.m. seven days weekly, without overriding schedule entries.
Because API can represent either a Peer Server or a Service Gateway for Files you must ensure that the name for a Service Gateway for Files differs from the name of a Peer Server.
Connects to a remote TIBCO Object Service Broker node, the Head Office, for outgoing distributed data accesses.The term outgoing does not refer to data flow direction. Data flows in both directions on this resource. It means that applications in the local node can instigate outgoing distributed data accesses to the remote node and it initiates the connection request.
• Connects to another remote TIBCO Object Service Broker node (at the Manufacturing location) for outgoing remote data accesses.
• No scheduling entries are explicitly defined for this resource group, therefore by default it uses the DEFAULT0 resource type schedule for an HRN resource type.
• This is for incoming remote data accesses from the same remote TIBCO Object Service Broker node at the Manufacturing location as Resource 3.
• No scheduling entries are explicitly defined for this resource group, therefore by default it uses the DEFAULT0 resource type schedule for an HIN resource type.
• This connection accommodates incoming data access requests from the remote TIBCO Object Service Broker node, the Sales Office.Since this resource is specifically for incoming requests, the local node is unable to send data access requests to the remote node. Any data flow in this resource must be initiated from the remote node.
• No scheduling entries are explicitly defined for this resource group, therefore by default it uses the DEFAULT0 resource type schedule for an HIN resource type.
• The Service Gateway for IDMS/DB is connected to the local Data Object Broker. If CAIDMS data is required by the manufacturing or sales node, a distributed request is routed to the Service Gateway for IDMS/DB via the local Data Object Broker.
• This resource group has its own unique schedule entry with type = IDM and identifier = DBSRVR1.
• Data accesses directed to the DB2 database from applications hosted by the local node, the Manufacturing Office, or the Sales Office are relegated to this resource, which connects to the DB2 database.
• This resource group has its own unique schedule entry with type = DB2 and identifier = DBSRVR2.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |