Preparations for Installation

This section describes the steps to take in preparation for installation.

Installation of the TIBCO Object Service Broker Base Component

You must install the TIBCO Object Service Broker base component before configuring the server. The base component can reside on z/OS, Windows, or Solaris. Installation instructions are in the TIBCO Object Service Broker for z/OS Installation and Operations and TIBCO Object Service Broker for Open Systems Installing and Operating manuals.

Installation of the Server

Installation instructions for the Service Gateway for Files, which includes the SDK, are located in TIBCO Object Service Broker Managing External Data. The Datacom server is shipped as part of the SDK.

Implementation of TIBCO Object Service Broker Security

You can implement security for the server using standard TIBCO Object Service Broker security: To restrict access to DAT tables after they are defined, proceed with security as for any TIBCO Object Service Broker table.

CA Datacom Security Considerations

The server places the user ID in positions 4 through 11 of the User Information Block (UIB). When the X option is specified in the DEBUGPARMS field in the @SERVERDEBUG(DAT) table, the literal PXX is placed in positions 1 through 3 of the UIB. Additionally, user impersonation takes place if the startup parameter SECLEVEL is set to 1.

Refer to Specifying the Startup Parameters.

Fail Safe Processing Considerations

To guarantee consistency when updating both TIBCO Object Service Broker TDS data and CA Datacom data in a single transaction and through a single instance of the server, you can use Fail Safe Level 1 processing.

For more information, refer to Implementing Fail Safe Processing.

Communications Requirements

If all components reside in the same domain and in authorized libraries, Cross Memory Services is used for communications. In all other cases, TCP/IP is used for communications.