eClient 101 Customization and Integration

440 eClient 101 Customization and Integration

[LOC] Provides the class name and the method name within which the error

occurs. In our example, it is

com.ibm.mm.sdk.server.DKDatastoreICM:logon.

[MSG] Provides the Content Manager return code and the exception type

whenever applicable. It is ICM7172 in our example.

18.4 Additional trace information

Since eClient is a WebSphere application server, you can obtain additional

information through the WebSphere logging mechanism. By default, the

WebSphere log files for eClient are in the

C:\WebSphere\AppServer\logs\eClient_Server directory.

If you have problems displaying the eClient logon window, it is possible that the

Web server has problems or has not even started. In this case, the Web server

log files and Web server plug-in log files may present tips for you to identify the

problem. By default, these log files reside in both the C:\IBMHttpServer\logs and

C:\WebSphere\AppServer\logs directories. In the C:\WebSphere\AppServer\logs

directory, pay special attention to the activity.log and http_plugin.log files.

18.5 Debugging your application

In addition to tracing, you can debug your applications using programming and

external third-party tools.

18.5.1 Debugging Java code using stdout

One way of debugging your Java source code, whether it is in a custom servlet, a

custom Java file, or Java code in a JSP, is by writing messages to the stdout file

using the System.out.println() method. For example:

String myVariable = “test”;

System.out.println(“The value of test is ‘” + myVariable + “‘”);

The output from this code will go to the stdout file.

If you use WebSphere Studio Application Developer, the stdout output goes to

the console that can be viewed in the WebSphere Studio Application Developer

Web perspective.

If you are running in the standard eClient, the location of the stdout file is

controlled by WebSphere. The default location is C:\Program

Files\IBM\CMeClient\logs\eClient_Server_stdout.log.