![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The process used by TIBCO Object Service Broker to access data via its external Gateways, consists of the following basic steps:
1. The Data Object Broker receives a client request containing a table definition, which, in turn, contains a table type.
2. The Data Object Broker selects a Gateway (considered to be a shared resource) by matching the SERVERTYPE and SERVERID values in the request to a corresponding Gateway.
3. The Data Object Broker sends the request to the Gateway, which converts the request into the form expected by the external DBMS and then submits the transformed request.
4. Data returned by the external DBMS is converted into TIBCO Object Service Broker format, sent to the Data Object Broker, and then to the client session.Before you start the Gateway, you must configure the Execution Environment where the Gateway is to run.The setting of the SECLEVEL gateway parameter dictates what security information the Gateway uses to connect to an external DBMS when access to external data is requested. For example, if SECLEVEL=0, the Gateway uses the TIBCO Object Service Broker user ID and password to connect to an external DBMS. If SECLEVEL=1, the Gateway uses the TIBCO Object Service Broker client session ID, current group name, or an externally defined ID to connect to an external DBMS.Starting the Gateway creates a connection to the Data Object Broker. The Gateway maintains a connection with the Data Object Broker for the life of the entire Gateway session. Data is sent to the Data Object Broker in variable length buffers up to a maximum of 31 KB. If a single request requires more than 31 KB of data, multiple 31 KB buffers are sent until the request is complete.The External Environments manual for your operating environment for information on configuring the Execution Environment
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |