e-docs > WebLogic Server > WebLogic Tuxedo Connector Administration Guide > Configuring WebLogic Tuxedo Connector |
WebLogic Tuxedo Connector Administration Guide |
Configuring WebLogic Tuxedo Connector
The following sections describe how to configure the WebLogic Tuxedo Connector.
Summary of Environment Changes and Considerations
This section provides an overview of the changes you must make to the Tuxedo and WebLogic Server environments before you can start using the WebLogic Tuxedo Connector.
Note: For more information on Tuxedo domains, see the BEA TUXEDO Domains Guide.
Tuxedo users need to make the following environment changes:
The following sections describe WebLogic Server changes required to use the WebLogic Tuxedo Connector:
Administration and Programming
WebLogic Server users need to make the following environment changes:
Note: For more information on WebLogic Server performance and tuning, see BEA WebLogic Server Performance and Tuning.
The number of client threads available when dispatching services from the gateway may limit the number of concurrent services running. For this release of WebLogic Tuxedo Connector, there is no WebLogic Tuxedo Connector attribute to increase the number of available threads. Use a reasonable thread model when invoking service EJBs.You may need to increase the number of WebLogic Server threads available to a larger value.
Optional Dedicated WTC Thread Pool
If an EJB application executed by InboundEJBRequest is slow compared to the rate at which input requests are arriving from the remote Tuxedo domain, thread starvation can occur. The result of such a thread starvation can cause a backlog in default execute requests and possibly a loss of input requests.
In WebLogic Server 7.0 SP6 and higher service packs, you can use the applicationQueueSize property to create a weblogic.wtc.applicationQueue at WTC boot time. Once configured, all EJB applications are executed in this queue rather than the default execute queue. To configure the applicationQueueSize property, see applicationQueueSize.
Configuring WebLogic Tuxedo Connector for Your Applications
Note: This release of the WebLogic Tuxedo Connector provides only static configuration. If you need to change any parameters used to configure the WebLogic Tuxedo Connector, the WebLogic Server must be restarted for the changes to take effect. For example, you can not add or remove domain network links, change network addresses, or import or export new services.
This section provides information on how to configure the WebLogic Tuxedo Connector to allow WebLogic Server applications and Tuxedo applications to interoperate.
WebLogic Tuxedo Connector MBean Classes
Note: For more information on MBean parameters, see WebLogic Tuxedo Connector MBean Attributes.
The WebLogic Tuxedo Connector uses MBeans to describe connectivity information and security protocols to process service requests between WebLogic Server and Tuxedo. These configuration parameters are analogous to the interoperability attributes required for communication between Tuxedo domains. The configuration parameters are stored in the WebLogic Server config.xml file. The following table lists the MBean types used to configure WebLogic Tuxedo Connector:
Configuring WebLogic Tuxedo Connector Using the Administration Console
The Administration Console allows you to configure, manage, and monitor WebLogic Tuxedo Connector connectivity. To display the tabs that you use to perform these tasks, complete the following procedure:
The following table shows the connectivity tasks, listed in typical order in which you perform them. You may change the order; just remember you must configure an object before associating or assigning it.
Configuring WebLogic Tuxedo Connector Using the Command-Line Interface
The command-line interface provides a way to create and manage WebLogic Tuxedo Connector connections. For information on how to use the command-line interface, see the Mbean Management Command Reference.
Set the WebLogic Server Environment
You need to set the environment of your WebLogic Server application by running the setEnv script.
If you are setting the environment for the first time, you will need to review the settings in the script. If necessary, use the following steps to modify the settings for your application environment:
Note: The setExamplesEnv file is used to set the environment for the WebLogic Server examples provided with your distribution.
How to Set WebLogic Tuxedo Connector Properties
Note: For more information about setting WebLogic Server properties, see Starting and Stopping WebLogic Servers.
If you need to set properties, update the JAVA_OPTIONS variable in your server start script. Example:
JAVA_OPTIONS=-Dweblogic.wtc.TraceLevel=100000
Note: For more information on TraceLevel, see Monitoring the WebLogic Tuxedo Connector.
Use TraceLevel to specify the level of message tracing WebLogic Tuxedo Connector will send to your log files:
JAVA_OPTIONS= -Dweblogic.wtc.TraceLevel=tracelevel
where tracelevel is a number between 10,000 and 100,000 that specifies the level of WebLogic Tuxedo Connector tracing.
Note: For more information on PasswordKey, see Configuring a WTCPassword MBean.
Use PasswordKey to specify the key used by the weblogic.wtc.gwt.genpassword utility to encrypt passwords:
JAVA_OPTIONS=-Dweblogic.wtc.PasswordKey=mykey
To transfer non-ascii (multibyte) strings between WebLogic Server and Tuxedo applications, you must configure WebLogic Tuxedo Connector to provide characer set translation. WebLogic Tuxedo Connector uses a WebLogic Server property to match the encoding used by all the Tuxedo remote domains specified in a WebLogic Tuxedo Connector service. If you require more than one coding set running simultaneously, you will require WebLogic Tuxedo Connector services running in separate WebLogic Server instances.
To enable character set translation, update the JAVA_OPTIONS variable in your server start script. Example:
JAVA_OPTIONS=-Dweblogic.wtc.encoding=codesetname
where codesetname is the name of a supported codeset used by a remote Tuxedo domain. See Supported Encodings for list of supported supported base and extended coding sets.
You may not be able to select the exact encoding name to match the encoding used by the remote domain. In this situation, you should select an encoding name that is equivalent to the remote domain.
Although the names don't match exactly, EUC_JP and eucJP are equivalent encoding sets and provide the correct string translation between WebLogic Server and your remote domain. You should set the encoding property to EUC_JP:
JAVA_OPTIONS=-Dweblogic.wtc.encoding=EUC_JP
In WebLogic Server 7.0 SP6 and higher service packs, you can improve the performance of slow executing EJB applications by processing threads in a dedicated thread pool.
JAVA_OPTIONS=-Dweblogic.wtc.applicationQueueSize=threads
where threads is the number of threads to be assigned to the dedicated pool.
WebLogic Tuxedo Connector Configuration Guidelines
Use the following guidelines when configuring WebLogic Tuxedo Connector: