![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This section identifies the gateway parameters, their valid abbreviations, and their functions. To change the gateway parameters for an SLK table, refer to Supplying the Gateway Configuration Parameters.
Has meaning only if Security level=1. Specifies how the authorization ID is identified to the external DBMS. The default is USERID. Valid values:GROUP – The current TIBCO Object Service Broker security group. The name of this group can be up to 16 characters long, but only 8 characters are supported. A SECURITYFAIL occurs for more than eight characters. Note A TIBCO Object Service Broker security group has no password associated with it, so only an external ID with an empty password can be used.OTHER – Requires an externally defined user ID (OTHERUSERID) and password (OTHERPASSWORD). Use to specify the level of Fail Safe processing. The default value is zero. Valid values:1 – Activate Fail Safe Level 1. The Gateway informs the Data Object Broker that it can support Fail Safe level‑1 processing. If the Gateway is to attach to a z/OS Data Object Broker, the Data Object Broker’s connection attribute setting “commit level” must be set to 1. If not, the Gateway connection is rejected. Refer to Implementing Fail Safe Processing for more information. You must specify the TRXDB, FSTABLENAME, RECOVERYID, and RECOVERYPASSWORD parameters.0 – De-activate Fail Safe processing. The Gateway informs the Data Object Broker that it does not support Fail Safe level‑1 processing. If the Gateway is to attach to a z/OS Data Object Broker, the Data Object Broker’s connection attribute setting “commit level” must be set to 0. If not, the Gateway connection is rejected. Refer to Implementing Fail Safe Processing for more information. Required only if FSLEVEL=1. Use to specify the name of the table to be used as a transaction table in the external DBMS that is denoted by the TRXDB parameter. Each pool of TIBCO Service Gateway for ODBCs must have a unique IDPREFIX (for example, WINSK). The prefix is used to construct a unique name for each Gateway. The ID prefix can contain up to five characters, to which the Gateway appends two hexadecimal digits and uses the result to log in to TIBCO Object Service Broker. It uniquely identifies each Gateway to TIBCO Object Service Broker. There is no default; you must specify a value. The name of the local library for rules calls. Set the value to @SLK. Refer to the note at the end of this section for more information. Use to specify the password of the externally defined user ID. Has meaning only if EXTERNALUSERID=OTHER. The externally defined user ID. Has meaning only if EXTERNALUSERID=OTHER. Applicable only if Fail Safe Level=1. Identifies the authorization ID to use during recovery (that is, when querying the transaction table to see if the Gateway completed an in-doubt transaction). The ID can be up to eight characters. If not specified, the TIBCO Object Service Broker user ID (SESSIONUSERID) and password (SESSIONPASSWORD) are used. RECOVERYPASSWORD (RECPW) For use only with a Data Object Broker on z/OS. The mode that the Data Object Broker uses to release the Gateway at the end of a transaction. Use this mode to release a server more quickly for a new transaction in read-only situations. The default is ASYNC. Refer to the note at the end of this section for more information. Valid entries:ASYNC – The Data Object Broker releases the Gateway from the TIBCO Object Service Broker transaction upon sending the end of transaction request, provided no updates are requested. The next transaction can then be scheduled before the previous transaction is completed. ASYNC is recommended for online Gateways.SYNC – Causes the Data Object Broker to wait for the Gateway to complete end of transaction processing. The length of time a connection to the external DBMS is held between the Gateway and an external DBMS. Valid values are TRANSACTION or SESSION, which maintain the connection for the life of a TIBCO Object Service Broker transaction or server session respectively. When the connection ends, the locks are released. The library search environment for the rules to be executed by the Gateway. Set the value to L (for local). Refer to the note at the end of this section for more information. The level of authorization to use when accessing external DBMS data. The default is 0. Valid values:0 – Access the external DBMS using the TIBCO Object Service Broker Gateway user ID and password as the connection ID and its password.1 – Access the Gateway based on the user’s TIBCO Object Service Broker session ID or group name, or externally defined user ID. Use an external security interface. Identifies a pool of Gateways with common characteristics (for example, SLKID1). If you start up a pool of multiple Gateways with the same server ID, all members of the pool have the same values for all parameters. Identifies the type of Gateway. Specify SLK for TIBCO Service Gateway for ODBC. Specify ORS for TIBCO Service Gateway for Oracle. SESSIONPASSWORD (SPWD) Specifies a valid level‑7 TIBCO Object Service Broker user ID (used internally by the Gateway to connect to TIBCO Object Service Broker). Specifies the transaction database (data source for TIBCO Service Gateway for ODBC or Oracle SID for TIBCO Service Gateway for Oracle) that can be updated. All the SLK tables within a transaction used to update SLK data using the Gateway should make reference to this data source or Oracle SID. Required only if Fail Safe Level=1. The type of user that can connect to this server. When allocating a Gateway, the Data Object Broker first tries to allocate an online user to an online server. If it cannot, it allocates the user to a Gateway with USERTYPE=ANY. For use only with a Data Object Broker on z/OS. See the note at the end of this section for more information. Valid entries:LOCAL – Reserves the server for user sessions executing in a Batch or CICS Execution Environment. Not valid for online users.
An ODBC or Oracle Gateway can be run with SEARCH=L, LIBRARY=@SLK settings or, alternatively, the INSTLIB parameter in mon.prm file can be set to @SLK and the search parameter for the Gateway set to “I” for “installation” in session.prm. The latter way is preferable, because it reduces the startup time for a Gateway.The RESPONSEMODE and USERTYPE parameters have no effect on processing when the Data Object Broker runs on open systems. However, a z/OS Data Object Broker rejects a Gateway’s attempt to connect in case an attribute mismatch is detected. Refer to Startup Prerequisites.TIBCO Object Service Broker Managing Security about TIBCO Object Service Broker security.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |