The trace command displays and sets tracing options for all servers in a farm or specified servers. You can trace various server activity, such as remote procedure calls or log manager processes. You can route this trace information to a trace file.
The TraceOptions.sample file can be found in ..\tools\PE\samples relative to the Content Platform Engine installation directory.
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\traceOptionsThe TraceOptions file is accessed when the server is restarted or reloaded through vwtool trace.
When the trace command is run on a single server, the current trace settings are listed and the trace options that were selected for the server are marked with a double asterisk (**).
http://server:port/FileNet/Enginewhere:
server is the host name of the server where Content Platform Engine is deployed. In a load-balanced environment, server is the name of one of the servers in the farm, not the virtual address of a load balancer.
port is the HTTP port that is used by the application server where Content Platform Engine is deployed.
The following table lists examples of addresses with default port numbers for supported application servers:
| Application server type | Web page address |
|---|---|
| IBM® WebSphere® Application Server | http://myserver:9080/FileNet/Engine |
| Oracle WebLogic Server | http://myserver:7001/FileNet/Engine |
| JBoss Application Server | http://myserver:8080/FileNet/Engine |
c:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\FileNet\server1\pesvr_trace.logIn interactive mode, you are required to set all of the trace options.
trace [server] [change_tracing_options] [from_traceOptions_file] [trace_destination] [trace_options]| Parameter | Description |
|---|---|
| server | Enter s for the trace
to be performed on a single server. You are prompted for the name
of the server. Enter a for the trace to be performed on all of the servers. |
| change_tracing_options | Enter yes to change any of the displayed settings, or no to leave them as they are currently set. |
| from_traceOptions_file | Enter yes if you want the selected trace options from the traceOptions file. Enter no to leave them as they are currently set. |
| trace_destination | Defines the file and location where you want the trace information
to be stored. Enter yes or no for the trace destination. To turn tracing off, enter the trace command with no parameters, and enter no at the trace_destination prompts. Remember: Disabling the trace destination effectively turns
off tracing. However, there is some performance cost from leaving trace options
enabled.
|
| trace_options | The trace activity that you can enable or disable. Enter yes or no for each trace option parameter. The options appear in the order indicated in the trace options parameters table. |
| Parameters | Description |
|---|---|
| Application space | Trace application space changes such as configuration changes or API calls from client applications. |
| Asynchronous tools | Trace the tools that use asynchronous communication to the workflow system such as PELog. |
| Case Analyzer publishing | Trace the Case Analyzer event publishing process. |
| Case Analyzer collection | Trace the event collection process which queries the event logs. |
| Case Analyzer database | Trace the database query statements that are run by Case Analyzer. |
| Case Analyzer RPC | Trace the remote procedure calls from the Administration Console for Content Platform Engine. |
| Case Analyzer upgrade | Trace the Case Analyzer upgrade operation. |
| Case Analyzer OLAP | Trace the interaction with the OLAP database that is conducted through the OLAP connector. |
| Database access | Trace database access. This option outputs the SQL statements that are used by workflow system, along with the values of the substitution variables. Setting this option automatically sets the database time option. |
| Database outputs | Trace the field values and outputs of database statements, such as SELECT, UPDATE, and so on. |
| Database time | Trace database timings. This prompt appears only if you answer no to the database access prompt. |
| Database transaction | Trace an entire database transaction from beginning to end. |
| Environment cache | Trace workflow system interactions with its environment record cache where it keeps track of workflow system user and group membership information. |
| Event exporter | Trace the core framework for Case Analyzer, which drives the Case Analyzer publishing and collection processes. |
| External RPCs | Trace external remote procedure calls (RPCs). The extRPC and intRPC options reflect the number of RPCs going across the network. |
| Farming | Trace activities that are related to a farmed system. |
| Internal RPCs | Trace internal remote procedure calls (RPCs). The extRPC and intRPC options reflect the number of RPCs going across the network. |
| Instruction Sheet Interpreter | Trace Instruction Sheet Interpreter (ISI) process. |
| Log Manager | Trace log manager process. |
| Network Connections | Trace network connections. |
| Email Notification | Trace email notifications. |
| Object Service RPCs | Trace Object Service usage. |
| API RPC | Trace communication RPCs between the API client and workflow server. |
| API RPC input | Trace API input parameters to workflow system RPCs. |
| API RPC output | Trace API output parameters to workflow system RPCs. |
| Rules | Trace workflow system interactions with the Rules Engine and rules processing. |
| Security calls | Trace security calls. |
| Stored Procedure Calls | Trace the execution of database instruction stored procedure calls. |
| Workflow Termination | Trace calls made to the workflow termination process (vwdone). |
| Transfer | Trace all transfer processes. |
| Web Services | Trace workflow system interactions with applications using the Web Services protocol. |