Copyright © Cloud Software Group, Inc. All Rights Reserved

@PEERSERVERID

Directs remote TIBCO Object Service Broker table accesses to a particular peer server on a remote TIBCO Object Service Broker system. (TBL)

Table Definition

These are the fields within the @PEERSERVERID table:

Field Name	Typ	Syn	Len	Dec	Key	Ord	Rq	Description
SERVER-LOCATION	I	C	16		P			Location of remote server.
SERVERID	I	C	8	0			Y	Name of remote server.

Usage Notes

•

On every TIBCO Object Service Broker access to a remote table (that is, when the LOCATION parameter on the table does not match the name of the local TIBCO Object Service Broker system), TIBCO Object Service Broker examines the table @PEERSERVERID on the local system. If the SERVERLOCATION field in a row in @PEERSERVERID matches the name of the remote TIBCO Object Service Broker system, the server name in the SERVERID field in that occurrence is appended to the request before it is sent to the remote system. If no match is found for the name of the remote TIBCO Object Service Broker system, the request is sent with the server name DEFAULT0 appended.

•	The @PEERSERVERID table is limited to an implementation-defined number of occurrences (currently 6). Attempting to insert more occurrences than supported raises the COMMITLIMIT exception; however, issuing a COMMIT statement does not permit more occurrences to be inserted into the table.

•	Supported operations are INSERT, GET, FORALL, REPLACE, and DELETE.

•	Selection and ordering are supported.

•	Parameter value (PRM) tables on @PEERSERVERID are not supported.

•	Subview (SUB) tables on @PEERSERVERID are not supported.

•	Triggers on @PEERSERVERID are not supported.

•	@PEERSERVERID behaves like a session table in that its content and effects are local to one TIBCO Object Service Broker session and are not seen by other users, even if they are sharing a single Execution Environment.

•	It is not an error to have invalid or nonexistent system or server names in @PEERSERVERID.

•	If a nonexistent or inactive server name is used, the error is discovered at the remote system, and a suitable message is returned from that system.

•	Only one server name can be used at a given remote system within a single transaction.

Exceptions

 

COMMITLIMIT

Maximum number of commits reached.

Example

The following example illustrates the use of @PEERSERVERID:

---

 

PSIRULE_1;

_

_ ------------------------------------------------------------------------

_ ------------------------------------------------------------+-----------

_ @PEERSERVERID.SERVERLOCATION = 'TORONTO'; | 1

_ @PEERSERVERID.SERVERID = 'SERVER1'; | 2

_ INSERT @PEERSERVERID; | 3

_ @PEERSERVERID.SERVERLOCATION = 'DALLAS'; | 4

_ @PEERSERVERID.SERVERID = 'DALCICS1'; | 5

_ INSERT @PEERSERVERID; | 6

_ GET EMPLOYEES('DALLAS') WHERE EMPNO = 12345; | 7

_ GET MANAGERS('TORONTO') WHERE EMNO = EMPLOYEES.MANNO; | 8

_ ------------------------------------------------------------------------

---

 

The PSIRULE_1 rule inserts two occurrences into @PEERSERVERID, with remote system names TORONTO and DALLAS. When the GET on table EMPLOYEES is executed (action 7), TIBCO Object Service Broker searches the @PEERSERVERID table and finds the occurrence matching remote system name DALLAS. Server name DALCICS1 is then appended to the request and the DALLAS system attempts to use this server to access the EMPLOYEES table.

When the GET on the MANAGERS table is executed (action 8), TIBCO Object Service Broker searches the @PEERSERVERID table and finds the occurrence matching the remote system name TORONTO. Server name SERVER1 is then appended to the request and the TORONTO system attempts to use this server to access the MANAGERS table.

Copyright © Cloud Software Group, Inc. All Rights Reserved