Managing Peer Servers

You require peer servers within an Execution Environment for peer-to-peer distributed data between TIBCO Object Service Broker nodes (a node is equivalent to a Data Object Broker). The peer server provides the distributed data services for a Data Object Broker receiving incoming (or inbound) connections from a peer node. The following sections describe how to set up peer-to-peer distributed data connections between Data Object Brokers across various platforms.

The following graphic shows an outbound request, from Node A’s point of view, of data that is distributed on Node B:

Defining a Peer Server

On Windows and Solaris, peer servers are established only if the PEERS Data Object Broker parameter is included in the Data Object Broker parameter file, crparm, located in the install_path/database directory.

On z/OS, you define peer servers through the PEERSERVERID, PEERSERVERNUM, TDS, and MDL Execution Environment parameters and the Resource Management facility available from the Administration menu.

See Also

Connecting Windows to Windows or Solaris for details about crparm requirements

Connecting Windows or Solaris to z/OS Using TCP/IP for details about the PEERSERVERID and PEERSERVERNUM Execution Environment parameter and Resource Management requirements

Appendix A, Sample Configurations for sample configurations

TIBCO Object Service Broker Parameters for detailed information about the Execution Environment and Data Object Broker parameters

TIBCO Object Service Broker for z/OS Installing and Operating for detailed information about the Resource Management facility

Starting a Peer Server

A peer server starts implicitly when a client session that uses the peer server starts.

Shutting Down a Peer Server with the STOPSERVER Command

You can shut down a peer server using the Data Object Broker operator command STOPSERVER, for example:

•

hrncr STOPSERVER=SVRIDserverid

•

hrncr STOPSERVER=server_userid

•

hrncr STOPSERVER=ALLPRS

The value for serverid or server_userid is case sensitive. Refer to Available Operator Commands for more information about hrncr.

Automatic Restart of a Peer Server

If a logical error is detected during peer server operation and the server terminates, the Execution Environment logs the error and restarts the server. When a peer server terminates normally, the server session is not restarted and the total number of peer or rules-based servers is reduced by one.

Format of Peer server_userid

Peer server_userids must be unique to a Data Object Broker, as multiple Execution Environments with peer servers can connect to the Data Object Broker. Peer server_userids are generated in the following format:

@EERRRXX

where:


@	is the at sign, with which all server_userids start, to differentiate servers from regular users.
EE	contains the first two characters of the name for the Execution Environment.
RRR	is the three-character string resulting from a hash on the Execution Environment name.
XX	contains the two alphanumeric characters (base 36) derived from the server number for the server in the Execution Environment. An Execution Environment associates a unique identifier for each peer server it starts. Alphanumeric characters are used rather than numbers to allow for more than 99 servers. Example: @HR2WU01

Monitoring Peer Servers

Use the User Activity option in the TIBCO Object Service Broker Administration Utility (option I) to display peer server activity. Press PF2 to view a region list. Select SERVER and press PF2 to display available peer servers. You can also use the rsview utility to view, on standard out (stdout), a report about your peer server connections.

See Also

Chapter 6, Monitoring TIBCO Object Service Broker for more information about the User Activity option.

TIBCO Object Service Broker for Open Systems Utilities for details about rsview.

Peer Server Logs

The Data Object Broker log displays information about peer server activity such as startup, termination, and restart. In addition, a peer server log (also called a session log) is generated for each peer server.

Data Object Broker Log

This log displays all peer server activity for a particular Data Object Broker. The following sample messages would appear for one peer server:

2012/09/22 14:55:06 S6BUA021I User ’@HR2WU01’ logged on from ’CC001’

2012/09/22 14:55:13 S6BUA023I PRS server DEFAULT0(THR2WU01) logged on from ’@HR2WU01’

where:


@HR2WU01	is the peer server user ID. (that is, the session for a peer server). A session log is also generated with the user name as filename.
PRS	is the server type.
DEFAULT0	is the default peer server ID.
THR2W01	is the peer server_userid.

Session Log

The peer server log is written to the path specified by the SERVERLOGPATH Execution Environment parameter.