C Gateway Initialization Parameters

LOG_DESTINATION

The following table describes the LOG_DESTINATION parameter:

LOG_DESTINATION specifies the full path name of the gateway log file.

AUTHORIZATION_MODEL

The following table describes how to use the AUTHORIZATION_MODEL parameter:

AUTHORIZATION_MODEL defines the authorization model for the gateway user. The relaxed model specifies that authorizations that are granted to the effective user ID of the gateway by the queue manager are the only associations that an Oracle application has.

The strict model specifies that the Oracle user ID and password (that are provided when a database link is created), or the current user ID and password (when the Oracle user ID and password are not provided), should be checked against the local or network password file.

Refer to Security Models for more information about effective user IDs.

QUEUE_MANAGER

The following table describes how to use the QUEUE_MANAGER parameter:

QUEUE_MANAGER, a required parameter, specifies the name of the queue manager that the gateway connects to at logon. The effective user ID of the gateway should have the correct user privileges or should be authorized to connect to this queue manager. Specify manager_name by using the following rules:

• 1 to 48 alphanumeric characters in length

• No leading or embedded blank characters

• Trailing blank characters are permitted

Refer to Security Models for more information about effective user IDs.

TRACE_LEVEL

The following table describes how to use the TRACE_LEVEL parameter:

TRACE_LEVEL controls whether tracing information is collected as the gateway runs. When set to collect information, the trace data is written to the log file that is specified by the LOG_DESTINATION parameter. Specify level as an integer from 0 to 3, which is the sum of the desired trace values. The following table describes the significance of these values:

TRANSACTION_LOG_QUEUE

The following table describes how to use TRANSACTION_LOG_QUEUE.

TRANSACTION_LOG_QUEUE specifies the name of the queue for logging transaction IDs. Specify tx_queue_name using the following rules:

• 1 to 48 alphanumeric characters in length

• No leading or embedded blank characters

• Trailing blank characters are permitted

Refer to Creating a Transaction Log Queue for more information.

TRANSACTION_MODEL

The following table describes how to use TRANSACTION_MODEL.

TRANSACTION_MODEL defines the transaction mode of the gateway. Specify a value for TRANSACTION_MODEL as described in the following table:

TRANSACTION_RECOVERY_PASSWORD

The following table describes how to use TRANSACTION_RECOVERY_PASSWORD:

TRANSACTION_RECOVERY_PASSWORD specifies the password of the user that the gateway uses to start recovery of a transaction. The default value is set to an asterisk (*), and this asterisk indicates that the value of this parameter is stored in an encrypted form in a separate password file. To specify or change a valid password for encrypted gateway parameters, you need to use the tg4pwd gateway utility to do the work. For more information, refer to Using the tg4pwd Utility.

The TRANSACTION_RECOVERY_PASSWORD parameter is required only when TRANSACTION_MODEL is set to COMMIT_CONFIRM. Refer to Creating a Transaction Log Queue for more information.

Passwords in the gateway initialization file

The gateway uses user IDs and passwords to access the information in the remote database on the WebSphere MQ server. Some user IDs and passwords must be defined in the gateway initialization file to handle functions such as resource recovery. In a security conscious environment, plain-text passwords are regarded as insecure when they are accessible in the Initialization File.

A new encryption feature has been added to the gateway to make such passwords more secure. The tg4pwd utility can be used to encrypt passwords that would normally be stored in the gateway initialization file. Using this feature is optional, but highly recommended by Oracle. With this feature, passwords are no longer stored in the initialization file but are stored in a password file in an encrypted form. This makes the password information more secure. The following section describes how to use this feature.

Using the tg4pwd Utility

The tg4pwd utility is used to encrypt passwords that would normally be stored in the gateway initialization file. The utility works by reading the Initialization File and looks for parameters with a special value. This value is the asterisk (*). The asterisk indicates that the value of this parameter is stored in an encrypted form in another file. The following sample is a section of the initialization file with this value.

TRANSACTION_RECOVERY_PASSWORD=*

The initialization file is first edited to set the value of the parameter to the asterisk (*). Then the tg4pwd utility is run, specifying the gateway SID on the command line. The utility reads the initialization file and prompts the user to enter the values to be encrypted.

The syntax of this command is:

tg4pwd gateway_sid

In this command gateway_sid is the SID of the gateway.

The following is an example, assuming gateway SID is pg4mqs:

% tg4pwd pg4mqs
ORACLE Gateway Password Utility Constructing password file for
Gateway SID pg4mqs
Enter the value for TRANSACTION_RECOVERY_PASSWORD
welcome
%

In this example, the TRANSACTION_RECOVERY_PASSWORD parameter is identified as requiring encryption. The user enters the value (for example, welcome) and presses the Enter key. If more parameters require encryption, then you are prompted for their values. The encrypted data is stored in the pg4mq\admin ORACLE_HOME\pg4mq\admin directory.

TRANSACTION_RECOVERY_USER

The following table describes how to use the TRANSACTION_RECOVERY_USER parameter:

TRANSACTION_RECOVERY_USER specifies the user name that the gateway uses to start the recovery of a transaction. This parameter is required only when AUTHORIZATION_MODEL is set to STRICT, and TRANSACTION_MODEL is set to COMMIT_CONFIRM. Refer to Creating a Transaction Log Queue for more information.