Configure logging to write to separate log files for separate JVM instances

Technote (FAQ)

This document applies only to the following language version(s):

Language Independent


How can logs be written to separate files when a vertical cluster is implemented using a common EAR file?


Not documented


Maximo 6 uses Log4j Java logging to generate log information. By default, the file is set to use the Apache appender class that will write to a common log file for all applications running on the same physical server.

In some cases it is helpful to separate log files so that each Maximo application server has it’s own log. To do this, the log4j.appender must be modified to include an IBM supplied appender class.

The default setting in the file is set as follows:

# A2 is set to be a RollingFileAppender which outputs to maximo.log file

To enable separate logs for each Maximo application server, modify the file as follows:

# A2 is set to be a RollingFileAppender which outputs to maximo.log file

After completing the changes in the file, the maximo.ear file must be rebuilt and redeployed.

See the following link for more information on Apache Log4j logging

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Tivoli Change and Configuration Management Database
Systems and Asset Management Tivoli Asset Management for IT
Systems and Asset Management Tivoli Service Request Manager

Document information

More support for:

Maximo Asset Management
System Related

Software version:

6.0, 6.1, 6.2, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:


Modified date:


Translate my page

Content navigation