Monitoring the WebLogic Tuxedo Connector

来源：百度文库编辑：神马文学网时间：2024/04/30 21:02:11

The WebLogic Tuxedo Connector uses the WebLogic Server log file to record log information.
Setting Trace Levels
Use the TraceLevel parameter to set the tracing level of the WebLogic Tuxedo Connector on a server node. To enable tracing, add the keyword TraceLevel and with the desired trace value in the Arguments field of the startup class window. Use a comma to separate arguments in the Arguments field.
Example: Arguments=BDMCONFIG=.\mydomain\wtc_config.xml,TraceLevel=100000
Use the following values to set the TraceLevel:
Value
Components Traced
Description
10000
TBRIDGE_IO
tBridge input and output
15000
TBRIDGE_EX
more tBridge information
20000
GWT_IO
Gateway input and output, including the ATMI verbs
25000
GWT_EX
more Gateway information
50000
JAMTI_IO
JAMTI input and output, including low-level JAMTI calls
55000
JAMTI_EX
more JAMTI information
60000
CORBA_IO
CORBA input and output
65000
CORBA_EX
more CORBA information
100000
All Components
information on all WebLogic Tuxedo Connector components

Console Settings
To ensure that the all the necessary trace information is written to the log file, verify that server logging settings specify the following:
Debug to Stdout is selected.

Stdout severity threshold is set to Info.

Frequently Asked Questions
This section provides solutions to common user questions.
Cannot Find Configuration File
The error log displays the message Can not find the XML configuration file. What am I doing wrong?
Make sure that the Startup class is configured properly. SeeCreate a StartUp Class for the WebLogic Tuxedo Connector.

Check the WebLogic Server configuration file, config.xml. Check the Startup Class entry and edit if necessary. An example of a StartUp class follows:
EJB Deployment Message
When I build the simpserv example, I get the following error:

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.
Connection Problems
I‘m having trouble getting a connection established between WebLogic Tuxedo Connector and Tuxedo. What should I do?
Check the WebLogic Tuxedo Connector configuration against the Tuxedo remote domain. The remote domain must match the name of a remote domain configured in 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 the WebLogic Tuxedo Connector configuration file field.

Check the WebLogic Tuxedo Connector and Tuxedo log files for error messages.

Enable the WebLogic Tuxedo Connector trace and repeat the connectivity test.

Request assistance from BEA Customer Support.
_xyz

Monitoring the WebLogic Tuxedo Connector Monitoring the WebLogic Tuxedo Connector 配置WebLogic Tuxedo Connector 配置WebLogic Tuxedo Connector tuxedo How WebLogic Portal Uses the WebLogic Server Security Framework Leveraging the Unified User Profile @ WEBLOGIC JOURNAL 结束饥饿必须是所有人的重点-FAO - Monitoring Progress and Action in the F... 粮农组织的举措-FAO - Monitoring Progress and Action in the F... AD MP: The script 'AD Replication Monitoring' encountered a permissions error. Tuxedo杂记 Tuxedo----------------->CMDTUX_CAT:873 BEA Tuxedo 10.0 Documentation weblogic portal weblogic是什么？ weblogic优化 WebLogic教程 weblogic 概述射频同轴连接器 (RF CONNECTOR) mmcx Coaxial Connector--From Amphenol BCB客户端tuxedo开发实例 Huihoo Power! - 技术文档 - Tuxedo BCB客户端tuxedo开发实例 [Mullins02] Section 10.3. System Monitoring