This chapter includes the following sections:
This section provides an overview of the changes you must make to the Oracle Tuxedo and Oracle WebLogic Server environments before you can start using the Oracle WebLogic Tuxedo Connector.
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 an Oracle 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 Oracle WebLogic Tuxedo Connector instantiation.
Oracle WebLogic Tuxedo Connector requires that the Oracle Tuxedo domain always have encoding turned on.
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
For more information on Oracle Tuxedo domains, see "Using the Tuxedo Domains Component."
The following sections describe WebLogic Server changes required to use the Oracle WebLogic Tuxedo Connector:
WebLogic Server users need to make the following environment changes:
Create Java clients or servers. For more information on creating Oracle WebLogic Tuxedo Connector clients or servers, see the Developing Oracle WebLogic Tuxedo Connector Applications for Oracle WebLogic Server.
Configure the Oracle WebLogic Tuxedo Connector using the WebLogic Server Administration Console, command-line interface, or WLST. For more information on how to configure the Oracle WebLogic Tuxedo Connector, see Configuring Oracle WebLogic Tuxedo Connector for Your Applications.
If the Oracle 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.
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.
Note:AWTC server uses three threads plus one thread for every local access point defined.
This section provides information on how to configure the Oracle WebLogic Tuxedo Connector to allow WebLogic Server applications and Tuxedo applications to interoperate.
Note:Deciding when to target a WTC Server 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.
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. Table 2-1 lists the MBean types used to configure Oracle WebLogic Tuxedo Connector:
Parent MBean containing the interoperability attributes required for a connection between WebLogic Server and Tuxedo. Defines your WTC server when configured using the WebLogic Server Administration Console.
Provides configuration information to connect available remote Tuxedo domains to a WTC server. You must configure at least one local Tuxedo access point. Defines your local Tuxedo access points when configured using the WebLogic Server Administration Console.
Note: Because of dynamic configuration, you can create and deploy an empty WTC server.
Provides configuration information to connect a WTC server to available remote Tuxedo domains. You may configure multiple remote domains. Defines your remote Tuxedo access points when configured using the WebLogic Server Administration Console.
Provides information on services exported by a local Tuxedo access point. Defines your exported services when configured using the WebLogic Server Administration Console.
Provides information on services imported and available on remote domains. Defines your imported services when configured using the WebLogic Server Administration Console.
Specifies global field table classes, view table classes, and application passwords for domains. Defines your resources when configured using the WebLogic Server Administration Console.
Support for MBSTRING is provided using
Specifies the configuration information for inter-domain authentication. Defines your Passwords when configured using the WebLogic Server Administration Console.
Specifies global configuration information for the transfer of messages between WebLogic Server and Tuxedo. Defines your Tuxedo queuing bridge when configured using the WebLogic Server Administration Console.
Specifies the source, target, direction, and transport of messages between WebLogic Server and Tuxedo. Defines your Tuxedo queuing bridge redirects when configured using the WebLogic Server Administration Console.
For more information on the Oracle WebLogic Server management and the
config.xml file, see MBean Reference for Oracle WebLogic Server.
The WebLogic Server Administration Console allows you to configure, manage, and monitor Oracle WebLogic Tuxedo Connector connectivity. To display the pages that you use to perform these tasks, complete the following procedure:
Start the WebLogic Server Administration Console.
Locate the Interoperability node in the left pane, then expand WTC Servers.
Create or modify the WTC server you want to configure.
Follow the instructions in the Oracle WebLogic Server Administration Console Online Help. For links to the Oracle WebLogic Server Administration Console Online Help, see Table 2-2.
Table 2-2 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.
Set the Name attribute.
Set the attributes that describe your local Tuxedo access point on the General, Connections, and Security pages. You must configure at least one local Tuxedo access point.
Note: Because of dynamic configuration, you can create and deploy an empty WTC server.
Set the attributes that describe your remote Tuxedo domains on the Remote APs page.
Set the attributes that describe your exported WebLogic Server services on the Exported page.
Set the attributes that describe your imported Tuxedo services on the Imported page.
Set the attributes that describe your passwords on the Passwords page.
Set the attributes that describe your Oracle WebLogic Tuxedo Connector resources on the Resources page.
Set the global configuration information for the transfer of messages between WebLogic Server and Tuxedo.
Sets the attributes used to specify the source, target, direction, and transport of a message between WebLogic Server and Tuxedo
Select a target server instance for your WTC server.
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 Understanding the WebLogic Scripting Tool.
You need to set the environment of your WebLogic Server application by running the
setExamplesEnv script located at
ORACLE_HOME is the directory you specified as the Oracle Home when you installed Oracle WebLogic.
Windows users: run
UNIX users: run
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
/user_projects/domains/wl_server to your application directory.
setExamplesEnv script with a text editor, such as
Windows users: edit
UNIX users: edit
Save the file.
encoding are WebLogic Server Properties. If you need to set these properties, update the
JAVA_OPTIONS variable in your server start script. Example:
PasswordKey to specify the key used by the
weblogic.wtc.gwt.genpasswd utility to encrypt passwords:
mykey is the key value.
For more information on
PasswordKey, see Configuring a Password Configuration.
To transfer non-ascii (multibyte) strings between WebLogic Server and Tuxedo applications, you must 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:
codesetname is the name of a supported codeset used by a remote Tuxedo domain. See Supported Encodings at
http://docs.oracle.com/javase/7/docs/technotes/guides/intl/encoding.doc.html 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.
The Supported Encoding list includes
The remote domain is supported by a Solaris operating system using
Although the names don't match exactly,
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
To enable dumping of user data, add the following line to the
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 outbound messages
Outbound UDATA: buffer type (<type>, <subtype>) +++++ User Data(size) +++++ ......
For inbound messages
Inbound UDATA: buffer type (<type>, <subtype>) +++++ User Data(size) +++++ ......
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 +++++
To use Socket Direct Protocol (SDP), set the system property
-Djava.net.preferIPv4Stack=true in the
JAVA_OPTIONS variable in your server start script.
For detailed information on how to configure WTC to use SDP to interoperate with Tuxedo, see the Oracle Tuxedo/Oracle Exalogic Environment Deployment Guide, 11gR1PS2.
TraceLevel is deprecated, use system debugging. By default all the debug tracing is off. Use the following settings to turn debug trace on.
For tracing WTC-CORBA runtime
For tracing WTC-GWT runtime
For tracing WTC-JATMI runtime
For tracing WTC-tBridge runtime
For tracing WTC Configuration runtime
Use the following guidelines when configuring Oracle WebLogic Tuxedo Connector:
You may have more than one WTC server in your configuration.
You cannot target two or more WTC servers to the same server instance. A server instance can only be a target for one WTC server.
Some configuration changes implemented in a WTC server after a target server instance is selected will not be updated in the target server instance. You must remove the WTC server from the server instance and then add the updated WTC server to the target server instance.
For example, changes to tBridge requires you to undeploy and then deploy the WTC server to make configuration changes effective. However, some configuration changes, such as
RetryInterval, take effect when you activate the change. For more information on selecting a target server, see "Target WTC servers" in the Oracle WebLogic Server Administration Console Online Help.