|
|
The following sections describe how to configure the WebLogic Tuxedo Connector.
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 Using the Tuxedo Domains Component. |
Tuxedo users need to make the following environment changes:
MTYPE should always be unset, or set to NULL, or set to a value different from the MTYPE in the DM_LOCAL_DOMAINS section in the DMCONFIG file.The following sections describe WebLogic Server changes required to use the WebLogic Tuxedo Connector:
WebLogic Server users need to make the following environment changes:
Local, access to local services does not depend on the CredentialPolicy. The Tuxedo remote domain DOMAINID must be authenticated as a local WebLogic Server user. For more information, see User Authentication.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.
| Note: | A WTC server uses three threads plus one thread for every Local Access Point defined. |
| Note: | Deciding when to target a WTC Service is very important. Support for runtime MBean exists, so the configuration can be modified after deployment. There is an exception in tBridge. Both tBridge Globals and tBridge Redirect changes will not be in effect until WTC is undeployed and redeployed. |
This section provides information on how to configure the WebLogic Tuxedo Connector to allow WebLogic Server applications and Tuxedo applications to interoperate.
| Note: | For more information on the WebLogic Server management and the config.xml file, see
WebLogic Server MBean Reference. |
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:
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.
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 WebLogic Server Scripting Tool.
You need to set the environment of your WebLogic Server application by running the setExamplesEnv script located at WL_HOME\samples\domains\examples.
- Windows users: run setExamplesEnv.cmd
- UNIX users: run setExamplesEnv.sh
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:
setExamplesEnv script located at WL_HOME\samples\domains\examples to your application directory.setExamplesEnv script with a text editor, such as vi.
- Windows users: edit setExamplesEnv.cmd
- UNIX users: edit setExamplesEnv.sh
PasswordKey, and encoding are WebLogic Server Properties. If you need to set these properties, update the JAVA_OPTIONS variable in your server start script. Example:
JAVA_OPTIONS=-Dweblogic.wtc.PasswordKey=mykey| Note: | For more information on PasswordKey, see Configuring a Password Configuration. |
Use PasswordKey to specify the key used by the weblogic.wtc.gwt.genpasswd utility to encrypt passwords:
JAVA_OPTIONS=-Dweblogic.wtc.PasswordKey=mykeyTo transfer non-ascii (multibyte) strings between WebLogic Server and Tuxedo applications, you must configure WebLogic Tuxedo Connector to provide character 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 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
To enable dumping of user data, add the following line to the java.weblogic.Server command.
JAVA_OPTIONS=-Dweblogic.debug.DebugWTCUData=trueEnabling this causes user data to be dumped after the connection is connected. If no other debugging properties are enabled, then this will be the only WTC information dumped, except normal WTC error/informational messages. The dump is available in the WLS server log file.
The dump has the following format.
For example, a WLS client sends data “strings” in a STRING typed buffer and the Tuxedo TOUPPER service converts it to “STRINGS”. The WLS server log shows the following dump.
Outbound UDATA: buffer type (STRING, null)
+++++ User Data(16) +++++
00 00 00 07 73 74 72 69 6E 67 73 00 00 00 00 00 ....strings.....
+++++ END +++++
Outbound UDATA: buffer type (String, null)
+++++ User Data(12) +++++
00 00 00 07 53 54 52 49 4E 47 53 00 ....STRINGS.
+++++ END +++++
Because TraceLevel is deprecated, use system debugging. By default all the debug tracing is off. Use the following settings to turn debug trace on.
-Dweblogic.debug.DebugWTCCorbaEx=true-Dweblogic.debug.DebugWTCGwtEx=true-Dweblogic.debug.DebugWTCJatmiEx=true-Dweblogic.debug.DebugWTCtBridgeEx=true-Dweblogic.debug.DebugWTCConfig=trueUse the following guidelines when configuring WebLogic Tuxedo Connector:
KeepAlive, KeepAliveWait and RetryInterval, take effect when you activate the change. For more information on selecting a target server, see Assign a WTC Service to a Server.
|