Because TraceLevel is no longer supported, use system debugging. By default all the debug tracing is off. See System Level Debug Settings for information on how to develop applications that use RMI-IIOP to call a Tuxedo service using a WebLogic Server EJB.

See How to Set Oracle WebLogic Tuxedo Connector Properties.

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 outbound messages

  Outbound UDATA: buffer type (<type>, <subtype>)
  +++++ User Data(size) +++++
  ......
  

• For inbound messages

  Inbound UDATA: buffer type (<type>, <subtype>)
  +++++ User Data(size) +++++
  ......
  

When I build the simpserv example, I get the following error:

<date> <Error> <EJB> <EJB Deployment: Tolower has a class weblogic.wtc.jatmi.tpserviceHome which is in the classpath. This class should only be located in the ejb-jar file.>

This error message can be ignored for this release of the WebLogic Tuxedo Connector. The EJB wants all of the interfaces for an EJB call in the EJB jar file. However, some interfaces for the WebLogic Tuxedo Connector are implemented through the CLASSPATH, and the compiler throws an exception. When the EJB is deployed, the compiler complains that the EJB cannot be redeployed because some of its classes are found in the CLASSPATH.

Releases prior to WebLogic Server 7.0 used a WebLogic Server Startup class to start a WebLogic Tuxedo Connector session and a WebLogic Server Shutdown class to end a session. In WebLogic Server 8.1 and later, WebLogic Tuxedo Connector sessions are managed using a WTC server.

• A WebLogic Tuxedo Connector session is started when a configured WTC server is assigned to a selected server instance.

• A WebLogic Tuxedo Connector session is ended by removing a WTC server from the WebLogic server instance or when you shut down the WebLogic server instance.

The Tuxedo queuing bridge is started if the Tuxedo queuing bridge and redirections configurations exist in your WTC server and the WTC server is assigned to a selected server

The WebLogic Remote Console displays an exception when I try to assign my WTC server to a server instance. What should I do?

Make sure you have a valid WTC server configured. Each WTC server must have one or more local Tuxedo access points configured before it can be assigned to a server instance. Your server log will display the following:

<Apr 22, 2002 4:21:35 PM EDT> <Error> <WTC> <180101> <At least one local domain has to be defined.>

I'm having trouble getting a connection established between Oracle WebLogic Tuxedo Connector and Tuxedo. What should I do?

• Make sure you have started your Tuxedo server.

• Set the TraceLevel and enable Debug mode. Repeat the connectivity test and check the WebLogic Tuxedo Connector and Tuxedo log files for error messages.

• Avoid using machine names or localhost. Always use an IP address when specifying a network location.

• Check your AclPolicy and CredentialPolicy attributes. If your AclPolicy is LOCAL, you must register the remote domain DOMAINID as a WebLogic Server user. For more information, see Section 3.5, User Authentication.

• If you are migrating from WebLogic Server 6.x and your applications use security, you need to set PasswordKey as a WebLogic Server property. For more information, see How to Set Oracle WebLogic Tuxedo Connector Properties.

• Check the WebLogic Tuxedo Connector configuration against the Tuxedo remote domain. The remote domain must match the name of a remote domain configured in Oracle WebLogic Tuxedo Connector.

  For example: If the name simpapp is configured in the Tuxedo DMCONFIG *DM_LOCAL_DOMAINS section, then this name must match the name in your remote Tuxedo access point Access Point Id attribute.

• Request assistance from BEA Customer Support.

See Upgrading Oracle WebLogic Server.