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 for all platforms are located in
TIBCO Object Service Broker Installation and Operations.
Installation instructions for the Service Gateway for Files, which includes the SDK, are located in
TIBCO Object Service Broker Managing External Data. The Adabas server is installed as part of the SDK.
You can implement security for the server using standard TIBCO Object Service Broker security:
Because Adabas does not provide an interface in ADALNK to pass security information to Adabas, the server threads get their security permissions and user identification from the server address space. It is possible, however, to pass some information to Adabas through the ADALNK user exits. For information and assistance, contact TIBCO Support.
To guarantee consistency when updating both TIBCO Object Service Broker TDS and Adabas data from a single instance of the server in a single transaction, you must use Fail Safe level‑1 processing.
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.
TIBCO Object Service Broker for z/OS Installation and Operations for detailed information about TIBCO Object Service Broker communications.
TIBCO Object Service Broker Messages with Identifiers for information on messages produced by the server.
TIBCO Object Service Broker Security for information on security for tables.