Configuring WebLogic Tuxedo Connector
The following sections describe how to configure the WebLogic Tuxedo Connector.
- Summary of Environment Changes and Considerations
- Configuring WebLogic Tuxedo Connector for Your Applications
Summary of Environment Changes and Considerations
This section provides an overview of the changes make to the Tuxedo and WebLogic Server environments before you can start using the WebLogic Tuxedo Connector.
Tuxedo Changes
Note: For more information on Tuxedo domains, see the BEA TUXEDO Domains Guide.
Tuxedo users need to make the following environment changes:
- If an existing Tuxedo application is already using Tuxedo /T DOMAINS, then a new domain must be added to the domains configuration file for each connection to a WebLogic Tuxedo Connector instantiation.
- If the existing Tuxedo application does not use domains, then the domain servers must be added to the TUXCONFIG of the application. A new DMCONFIG must be created with a Tuxedo /T Domain entry corresponding to the WebLogic Tuxedo Connector instantiation.
- WebLogic Tuxedo Connector requires that the Tuxedo domain always have encoding turned on. MTYPE should always be unset or set to NULL in the DMCONFIG file.
WebLogic Server 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:
- Create Java clients or servers. For more information on creating WebLogic Tuxedo Connector clients or servers, see the WebLogic Tuxedo Connector Programmer's Guide.
- Configure the WebLogic Tuxedo Connector using the WebLogic Server console or command-line interface. For more information on how to configure the WebLogic Tuxedo Connector, see Configuring WebLogic Tuxedo Connector for Your Applications.
- If the WebLogic Tuxedo Connector ACL Policy is set to 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.
WebLogic Server Threads
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.
Configuring WebLogic Tuxedo Connector for Your Applications
Note: Deciding when to target a WTC Service is very important. Once a WTC Service is targeted, the configuration deployed to the selected server is static. Although you can continue to make changes in your WTC Service configuration, any changes made after the configuration is deployed will not be reflected in the selected server. You will need to remove the service from the server and target the service to the server for these changes to take effect.
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
- Configuring WebLogic Tuxedo Connector Using the Administration Console
- Configuring WebLogic Tuxedo Connector Using the Command-Line Interface
- Set the WebLogic Server Environment
- How to Set WebLogic Tuxedo Connector Properties
- WebLogic Tuxedo Connector Configuration Guidelines
WebLogic Tuxedo Connector MBean Classes
Note: For more information on the WebLogic Server management and the config.xml file, see WebLogic Server Configuration 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:
|
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. |
| 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. |
| 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 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:
- Start the Administration Console.
- Locate the Services node in the left pane, then expand the WebLogic Tuxedo Connector node.
- Create or modify the node in the tree specific to the component you want to configure.
- 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.
|
Task # |
Task |
Description |
|---|---|---|
| 1 | Creating a WTC Service | On the General tab in the right pane, you set the attributes for Name and Deployment Order. |
| 2 | Creating a Local Tuxedo Access Point | Set the attributes that describe your local Tuxedo access point in the General, Connections, and Security tabs. You must configure at least one local Tuxedo access point. |
| 3 | Creating a Remote Tuxedo Access Point | Set the attributes that describe your remote Tuxedo domains in the General, Connections, and Security tabs. |
| 4 | Creating Exported Services | Set the attributes that describe your exported WebLogic Server services in the General tab. |
| 5 | Creating Imported Services | Set the attributes that describe your imported Tuxedo services in the General tab. |
| 6 | Creating a Password Configuration | Set the attributes that describe your passwords in the Configuration tab. |
| 7 | Creating a Resource | Set the attributes that describe your WebLogic Tuxedo Connector resources in the Configuration tab. |
| 8 | Creating a Tuxedo Queuing Bridge Connection | Set the global configuration information for the transfer of messages between WebLogic Server and Tuxedo. |
| 9 | Creating a tBridge Redirection | Sets the attributes used to specify the source, target, direction, and transport of a message between WebLogic Server and Tuxedo |
| 10 | Assign a WTC Service to a Server | Select a target server for your WTC Service. |
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 Commands for Managing WebLogic Server MBeans.
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.
- NT/2000 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:
- 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.
- Edit the setExamplesEnv script with a text editor, such as vi.
- NT/2000 users: edit setExamplesEnv.cmd
- UNIX users: edit setExamplesEnv.sh
- Save the file.
How to Set WebLogic Tuxedo Connector Properties
TraceLevel, 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.TraceLevel=100000
Set TraceLevel
Note: For more information on how to record log information, 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.
Set PasswordKey
Note: For more information on PasswordKey, see Configuring a Password Configuration.
Use PasswordKey to specify the key used by the weblogic.wtc.gwt.genpassword 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 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.
Example:
- The Supported Encoding list includes EUC_JP
- The remote domain is supported by a Solaris operating system using eucJP
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
WebLogic Tuxedo Connector Configuration Guidelines
Use the following guidelines when configuring WebLogic Tuxedo Connector:
- You must have at least one local Tuxedo access point in your configuration.
- You may have more than one WTC Service in your configuration.
- You can not target 2 or more WTC Services to the same server. A server can only be a target for one WTC Service.
- Any configuration changes implemented in a WTC Service after a target server is selected will not be updated in the target server instance. You must remove the WTC Service from the server and then add the updated WTC Service add to the target server. For more information on selecting a target server, see Assign a WTC Service to a Server.
|
|
|