Oracle WebLogic Tuxedo Connector Administration Guide

      

Configuring Oracle WebLogic Tuxedo Connector

The following sections describe how to configure the Oracle WebLogic Tuxedo Connector.

 

Summary of Environment Changes and Considerations

This section provides an overview of the changes make to the Oracle Tuxedo and Oracle WebLogic Server environments before you can start using the Oracle WebLogic Tuxedo Connector.

 

Oracle Tuxedo Changes

For more information on Oracle Tuxedo domains, see the Using the Tuxedo Domains Component.

Tuxedo users need to make the following environment changes:

 

WebLogic Server Changes

The following sections describe WebLogic Server changes required to use the Oracle WebLogic Tuxedo Connector:

Administration and Programming

WebLogic Server users need to make the following environment changes:

WebLogic Server Threads

The number of client threads available when dispatching services from the gateway may limit the number of concurrent services running. For this release of Oracle WebLogic Tuxedo Connector, there is no Oracle 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.

A WTC server uses three threads plus one thread for every Local Access Point defined.

 

Configuring Oracle WebLogic Tuxedo Connector for Your Applications

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 Oracle WebLogic Tuxedo Connector to allow WebLogic Server applications and Tuxedo applications to interoperate.

 

Oracle WebLogic Tuxedo Connector MBean Classes

For more information on the Oracle WebLogic Server management and the config.xml file, see WebLogic Server MBean Reference.

The Oracle 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 Oracle WebLogic Tuxedo Connector:

MBean Type Description
WTCServer Parent MBean containing the interoperability attributes required for a connection between WebLogic Server and Tuxedo. Defines your WTC Service when configured using the Administration Console.
WTCLocalTuxDom Provides configuration information to connect available remote Tuxedo domains to a WTC Service. You must configure at least one local Tuxedo access point. Defines your Local Tuxedo Access Points when configured using the Administration Console.

Because of dynamic configuration, you can create and deploy an empty WTC Service.

WTCRemoteTuxDom Provides configuration information to connect a WTC Service to available remote Tuxedo domains. You may configure multiple remote domains. Defines your Remote Tuxedo Access Points when configured using the Administration Console. WTCExport Provides information on services exported by a local Tuxedo access point. Defines your Exported Services when configured using the Administration Console. WTCImport Provides information on services imported and available on remote domains. Defines your Imported Services when configured using the Administration Console. WTCResources Specifies global field table classes, view table classes, and application passwords for domains. Defines your Resources when configured using the Administration Console. Support for MBSTRING is provided using RemoteMBEncoding and MBEncodingMapFile attributes WTCPassword Specifies the configuration information for inter-domain authentication. Defines your Passwords when configured using the Administration Console. WTCtBridgeGlobal Specifies global configuration information for the transfer of messages between WebLogic Server and Tuxedo. Defines your Tuxedo Queuing Bridge when configured using the Administration Console. WTCtBridgeRedirect Specifies the source, target, direction, and transport of messages between WebLogic Server and Tuxedo. Defines your Tuxedo Queuing Bridge Redirects when configured using the Administration Console.

 

Configuring Oracle WebLogic Tuxedo Connector Using the Administration Console

The Administration Console allows you to configure, manage, and monitor Oracle WebLogic Tuxedo Connector connectivity. To display the tabs that you use to perform these tasks, complete the following procedure:

  1. Start the Administration Console.

  2. Locate the Interoperability node in the left pane, then expand the WTC Service.

  3. Create or modify the WTC Server you want to configure.

  4. Follow the instructions in the Online Help. For links to the Online Help, see Table 2-1.

The following table shows the connectivity tasks, listed in typical order in which you perform them. You may change the order; just remember configure an object before associating or assigning it.

 

Configuring Oracle WebLogic Tuxedo Connector Using the Command-Line Interface

The command-line interface provides a way to create and manage Oracle WebLogic Tuxedo Connector connections. For information on how to use the command-line interface, see WebLogic Server Scripting Tool.

 

Set the WebLogic Server Environment

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:

  1. From the command line, change directories to the location of the WebLogic Server application. Copy the setExamplesEnv script located at WL_HOME\samples\domains\examples to your application directory.

  2. Edit the setExamplesEnv script with a text editor, such as vi.

    - Windows users: edit setExamplesEnv.cmd

    - UNIX users: edit setExamplesEnv.sh

  3. Save the file.

 

How to Set Oracle WebLogic Tuxedo Connector Properties

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

Set PasswordKey

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=mykey

where mykey is the key value.

Set encoding

To transfer non-ascii (multibyte) strings between WebLogic Server and Tuxedo applications, configure Oracle WebLogic Tuxedo Connector to provide character set translation. Oracle WebLogic Tuxedo Connector uses an Oracle WebLogic Server property to match the encoding used by all the Tuxedo remote domains specified in an Oracle WebLogic Tuxedo Connector service. If you require more than one coding set running simultaneously, you will require Oracle 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.

Example:

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

Set Dumping of User Data

To enable dumping of user data, add the following line to the java.weblogic.Server command. 

JAVA_OPTIONS=-Dweblogic.debug.DebugWTCUData=true

Enabling 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 +++++

 

System Level Debug Settings

Because TraceLevel is deprecated, use system debugging. By default all the debug tracing is off. Use the following settings to turn debug trace on.

 

Oracle WebLogic Tuxedo Connector Configuration Guidelines

Use the following guidelines when configuring Oracle WebLogic Tuxedo Connector: