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


Chapter 13 Managing TIBCO Object Service Broker Networked Resources : Sample TIBCO Object Service Broker Network Configurations

Sample TIBCO Object Service Broker Network Configurations
Description of a Sample Network
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.
Illustration of a TIBCO Object Service Broker Network
The following illustrates the sample TIBCO Object Service Broker network:
Resource Detail Entries
The resource detail entries for the sample network are shown in the following table. The schedule name for these resource entries is WEEKDAYS05.
Early Release
Last User
Commit Level

1
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.

2
For resource types of HRN and HIN, the resource name must be the COMMID of the remote Data Object Broker.

Resource Schedule Entries
The resource schedule entries for the sample network are as follows:
Applicable Days (MTWTFSS)
Start Time
Maximum Connection Count
Description of Resources
Resource 1: API DEFAULT0
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.

 
S6BADM33 S6H1DOBB RESOURCE DETAIL FOR API DEFAULT0 2007MAY11 09:16:22
 
INTERMEDIATE ROLLBK Y EARLY RELEASE Y LAST USER REUSE Y COMMIT LEVEL 2
RETRY INTERVAL 0 TP NAME USER ID PREFIX FAILURES 0
NODE INDOUBTS N MONITOR/SMF N
 
CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 0 0 16 0 0 0 0
 
SCHEDULE NAME COMMON
 
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 05:00 N 16
 
 
 
 
 
 
ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
NO MORE DATA TO BE DISPLAYED

 
 
Resource 2: HRN PEER1
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.
 

 
S6BADM33 S6H1DOBB RESOURCE DETAIL FOR HRN PEER1 2007MAY11 09:16:22
 
INTERMEDIATE ROLLBK Y EARLY RELEASE Y LAST USER REUSE Y COMMIT LEVEL 2
RETRY INTERVAL 0 TP NAME USER ID PREFIX PRD FAILURES 0
NODE HEADOFFICE INDOUBTS N MONITOR/SMF Y
 
CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 0 0 25 0 0 0 0
 
SCHEDULE NAME COMMON
 
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 00:00 N 25
 
 
 
 
 
 
ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
NO MORE DATA TO BE DISPLAYED

 
Resource 3: HRN PEER2
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.
 

 
S6BADM33 S6H1DOBB RESOURCE DETAIL FOR HRN PEER2 2007MAY11 09:16:22
 
INTERMEDIATE ROLLBK Y EARLY RELEASE Y LAST USER REUSE Y COMMIT LEVEL 2
RETRY INTERVAL 0 TP NAME USER ID PREFIX FAILURES 0
NODE MANUFACTURING INDOUBTS N MONITOR/SMF N
 
CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 10 10 10 0 0 0 0
 
SCHEDULE NAME COMMON
 
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 00:00 N 10
 
 
 
 
 
 
ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
NO MORE DATA TO BE DISPLAYED

 
Resource 4: HIN PEER2
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.
 

 
S6BADM33 S6H1DOBB RESOURCE DETAIL FOR HIN PEER2 2007MAY11 09:16:22
 
INTERMEDIATE ROLLBK Y EARLY RELEASE Y LAST USER REUSE Y COMMIT LEVEL 2
RETRY INTERVAL 0 TP NAME USER ID PREFIX FAILURES 0
NODE MANUFACTURING INDOUBTS N MONITOR/SMF Y
 
CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 0 0 25 0 0 0 0
 
SCHEDULE NAME COMMON
 
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 00:00 N 25
 
 
 
 
 
 
ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
NO MORE DATA TO BE DISPLAYED

 
Resource 5: HIN PEER3
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.
 

 
S6BADM33 S6H1DOBB RESOURCE DETAIL FOR HIN PEER3 2007MAY11 09:16:22
 
INTERMEDIATE ROLLBK Y EARLY RELEASE Y LAST USER REUSE Y COMMIT LEVEL 2
RETRY INTERVAL 0 TP NAME USER ID PREFIX FAILURES 0
NODE SALESOFFICE INDOUBTS N MONITOR/SMF Y
 
CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 0 0 10 0 0 0 0
 
SCHEDULE NAME COMMON
 
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 00:00 N 10
 
 
 
 
 
 
ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
NO MORE DATA TO BE DISPLAYED

 
Resource 6: IDM DBSRVR1
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.
 

 
S6BADM33 S6H1DOBB RESOURCE DETAIL FOR IDM DBSRVR1 2007MAY11 09:16:22
 
INTERMEDIATE ROLLBK Y EARLY RELEASE Y LAST USER REUSE N COMMIT LEVEL 0
RETRY INTERVAL 0 TP NAME USER ID PREFIX FAILURES 0
NODE INDOUBTS N MONITOR/SMF Y
 
CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 0 0 10 0 0 0 0
 
SCHEDULE NAME COMMON
 
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 00:00 N 10
 
 
 
 
 
 
ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
NO MORE DATA TO BE DISPLAYED

 
Resource 7: DB2 DBSRVR2
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.
 

 
S6BADM33 S6H1DOBB RESOURCE DETAIL FOR DB2 DBSRVR2 2007MAY11 09:16:22
 
INTERMEDIATE ROLLBK Y EARLY RELEASE N LAST USER REUSE N COMMIT LEVEL 1
RETRY INTERVAL 0 TP NAME USER ID PREFIX FAILURES 0
NODE INDOUBTS N MONITOR/SMF N
 
CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 10 10 10 0 0 0 0
 
SCHEDULE NAME COMMON
 
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 00:00 N 10
 
 
 
 
 
 
ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
NO MORE DATA TO BE DISPLAYED

 
 

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