This subsection describes the changes in the output destination of trace files, the number of files, and entries of Cosminexus TPBroker.

The default output destination of the trace files of Cosminexus TPBroker is as follows:

For trace information of a J2EE server

• In Windows
  working-directory\ejb\server-name\logs\TPB\logj
  
• In UNIX
  working-directory/ejb/server-name/logs/TPB/logj
  

For trace information of server management commands

• In Windows
  Cosminexus-installation-directory\CC\admin\logs\TPB\logj
  
• In UNIX
  /opt/Cosminexus/CC/admin/logs/TPB/logj
  

For the trace information of the EJB client applications

• In Windows
  EJB-client-log-output-directory^#\system\TPB\logj
  
• In UNIX
  EJB-client-log-output-directory^#/system/TPB/logj
  

#: For details on the output destination of the EJB client log output directory, see 4.5.2 Output Destination of the EJB Client Application System Log.

For the CTM trace information

• In Windows
  Product-installation-directory\TPB\log
  Product-installation-directory\TPB\logj
  
• In UNIX
  /opt/Cosminexus/TPB/log
  /opt/Cosminexus/TPB/logj
  

The following table describes the items that can be changed, the corresponding parameters of the Easy Setup definition file or the corresponding user definition files and keys.

Table 3-19 Settings for acquiring Cosminexus TPBroker log

Items	Category	Corresponding parameters of the Easy Setup definition file or user definition files and keys
Output destination of trace file	J2EE server	ejb.server.log.directory in the <configuration> tag on a logical J2EE server (j2ee-server) or vbroker.orb.htc.tracePath in the <configuration> tag on a logical J2EE server (j2ee-server)
	Server management commands	-Dejbserver.log.directory option of the USRCONF_JVM_ARGS key of usrconf.bat (in Windows), or usrconf (in UNIX) or vbroker.orb.htc.tracePath key# of usrconf.properties for server management commands
	EJB client applications	For the cjclstartap command, the vbroker.orb.htc.tracePath key in usrconf.properties for the Java applications For the vbj command, the vbroker.orb.htc.tracePath key in the JavaVM system properties specified with the vbj command
	CTM	For the global CORBA Naming Service, set up the environment variable HVI_TRACEPATH at the location where the logical server type of adminagent.xml (Administration Agent configuration file) is Naming Service. For the CTM domain manager, set up the environment variable HVI_TRACEPATH in user.env.variable in the <configuration> tag of the logical CTM domain manager (ctm-domain-manager). For CTM, set up the environment variable HVI_TRACEPATH in user.env.variable in the <configuration> tag of the logical CTM (component-transaction-monitor).
Number of trace files	J2EE server	vbroker.orb.htc.comt.fileCount in the <configuration> tag on a logical J2EE server (j2ee-server)
	EJB client applications	For the cjclstartap command, the vbroker.orb.htc.comt.fileCount key in usrconf.properties for the Java applications For the vbj command, the vbroker.orb.htc.comt.fileCount key in the JavaVM system properties specified with the vbj command
	CTM	For the global CORBA Naming Service, set up the environment variable HVI_COMTFILECOUNT at the location where the logical server type of adminagent.xml (Administration Agent configuration file) is Naming Service. For the CTM domain manager, set up the environment variable HVI_COMTFILECOUNT in user.env.variable in the <configuration> tag of the logical CTM domain manager (ctm-domain-manager). For CTM, set up the environment variable HVI_COMTFILECOUNT in user.env.variable in the <configuration> tag of the logical CTM (component-transaction-monitor).
Number of trace file entries	J2EE server	vbroker.orb.htc.comt.entryCount in the <configuration> tag on a logical J2EE server (j2ee-server)
	EJB client applications	For the cjclstartap command, the vbroker.orb.htc.comt.entryCount key in usrconf.properties for the Java applications For the vbj command, the vbroker.orb.htc.comt.entryCount key in the JavaVM system properties specified with the vbj command
	CTM	For the global CORBA Naming Service, set up the environment variable HVI_COMTENTRYCOUNT at the location where the logical server type of adminagent.xml (Administration Agent setup file) is Naming Service. For the CTM domain manager, set up the environment variable HVI_COMTENTRYCOUNT in user.env.variable in the <configuration> tag of the logical CTM domain manager (ctm-domain-manager). For CTM, set up the environment variable HVI_COMTENTRYCOUNT in user.env.variable in the <configuration> tag of the logical CTM (component-transaction-monitor).

#

For details about the usrconf.bat file (in Windows) or usrconf file (in UNIX), and usrconf.properties, see 3.3 Customizing operation settings of server management commands in the uCosminexus Application Server Application Setup Guide. For details about each file and key for the server management commands see the following sections in the uCosminexus Application Server Definition Reference Guide:

• 5.1 List of files used in server management commands
• 5.2 usrconf (Option definition file for server management commands for UNIX)
• 5.3 usrconf.bat (Option definition file for server management commands for Windows)
• 5.4 usrconf.properties (System property file for server management commands)

For the details on the Easy Setup definition file, see 4.6 Easy Setup definition file in the uCosminexus Application Server Definition Reference Guide.

For details on the usrconf.properties file and keys for the Java applications, see 14.3 usrconf.properties (User property file for Java applications) in the uCosminexus Application Server Definition Reference Guide.

For details on the JavaVM system properties specified with the vbj command, see 14.4 System properties specified in the Java application in the uCosminexus Application Server Definition Reference Guide.

For details on adminagent.xml (Administration Agent setup file), see 10.5 adminagent.xml (Administration Agent settings file) in the uCosminexus Application Server Definition Reference Guide.

For details on the communication trace, see the TPBroker Operation Guide.

Notes

• To change the output destination of a trace file, you need to create comtrc and mdltrc in advance as the subdirectory of the changed output destination directory of the trace file. If you change the output destination, the trace file is output to comtrc and mdltrc under the changed log output destination directory.
• If you specify both the ejb.server.log.directory and vbroker.orb.htc.tracePath for <param-name> in the <configuration> tag on a logical J2EE server (j2ee-server) in the Easy Setup definition file, the settings of the vbroker.orb.htc.tracePath are given priority.
• If you specify both the -Dejbserver.log.directory option of the USRCONF_JVM_ARGS key of usrconf.bat (in Windows) or usrconf (in UNIX) and the vbroker.orb.htc.tracePath key of usrconf.properties for the server management commands, the settings of the vbroker.orb.htc.tracePath key of usrconf.properties is given priority.
• You cannot change the output destination of the server management commands when operating from the Management Server Remote Management.
• If you specify the number of trace files and entries with the CTM domain manager and CTM, these values are valid not only in the CTM domain manager and the CTM daemon, but also in the processes of the CTM regulator and the ctmstart command. When you increase the number of trace files and entries, note the increase in the disk usage.
• When you increase the number of trace file entries of the communication trace file, note the increase in the memory usage.