For Gen Java & .NET environments, how can the destination directory for the CMIDEBUG trace file be customised?

Document ID : KB000025837
Last Modified Date : 14/02/2018
Show Technical Document Details

Summary:

The CMIDEBUG trace file destination directory can be customised within the following files:

  • commcfg.properties for Java environments (Java proxy, Java web client)

  • commcfg.txt for .NET environments (.NET proxy, ASP.NET client).

 

Instructions:

Java environments:

Method 1:

Edit the commcfg.properties file (%IEF% directory). Locate the CMIDEBUG section & see comments:

# To turn tracing on and write to user specifiled file. Please make sure
# that the you have read/write permission for the same.
# CMIDEBUG=ON FILENAME

Uncomment the line 'CMIDEBUG=ON FILENAME' and replace FILENAME with a valid string. When specifying the FILENAME it is important to remember that under the Java Virtual Machine (JVM) the forward slash character ('/') can be used as a directory limiter for all underlying OS platforms (irrespective of whether they be Unix or Windows). For example on Windows, the FILENAME can be specified as follows:

CMIDEBUG=ON d:/temp/trace.out

The modified commcfg.properties file then needs to be redeployed with your Java proxy or Java web client application.

Using this method for creating the trace file, a very small initial trace file named trace.out (~8 lines) will still be created in the Application Server root directory. The main trace file will be created as per the CMIDEBUG directive in the commcfg.properties file.

Method 2:

To generate a single combined trace file the following method can be used.

Edit the commcfg.properties file (%IEF% directory).

As per Method 1, locate the CMIDEBUG section. However in this case, ensure that all CMIDEBUG lines are commented out. The modified commcfg.properties file then needs to be redeployed with your Java proxy or Java web client application.

The java command that starts the JVM for the Application Server needs to have the following additional property added to it's options list:

-D"CMIDEBUG=ON d:/temp/trace.out"

Restart the Application Server.

All trace information should be created in a single file as per the CMIDEBUG property above.

.NET environments:

Edit the commcfg.txt file (%IEF%\.net directory).

Locate the CMIDEBUG section & see comments:

# To turn tracing on and write to user specified file. Please make sure
# that the you have read/write permission for the same.
# CMIDEBUG=ON FILENAME

The FILENAME can be specified in standard format (no double '\' required) e.g.
CMIDEBUG=ON D:\TEMP\trace.out
The modified commcfg.txt file then needs to be redeployed with your .NET proxy or ASP.NET application.