WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Profile-specific log files

There are log files detailing the characteristics and runtime activities of individual profiles. These log files are located within the profile directory for each profile.

There are a number of log files that are created for each profile. Some of these logs describe the parameters used for the creation of the profile. These types of log files generally remain unchanged once the profile is fully configured. Other profile-specific logs are continually updated to capture error, warning, and information messages emitted during runtime. Some of these log files are also used to capture a Common Base Event (that may include business object data) that is selected for monitoring.

The table below specifies the different types of profile-specific log files and the locations where you can find them within the product. Within the table, the variable install_root represents the installation directory of WebSphere® ESB. The variable profile_root represents the root location of a profile.

For i5/OS operating system The variable user_data_root represents the default user data directory.

For more information see Default installation directories for the product, profiles, and tools.

Table 1. Profile-specific log files updated during runtime
Log Contents
First failure data capture (ffdc) log and exception files (common to all profile types) are found in these directories:
  • For Linux operating systemFor UNIX operating system profile_root/logs/ffdc
  • For Windows operating system profile_root\logs\ffdc
  • For i5/OS operating system profile_root/logs/ffdc

Contains the ffdc log and exception files for individual profiles. There are two types of ffdc logs: a single log file with a compilation of all the errors encountered during the profile runtime, and numerous text files with details such as stack traces and other information. The naming conventions for the different types of profiles are given for both files, as follows:

  • Deployment manager profile:
    • Log file: deployment_manager_name_exception.log.
    • Text files: deployment_manager_name_hex_id_date_time.txt.
  • Custom profile:
    • Log files:node_agent_name_exception.log and server_name_exception.log
    • Text files: node_agent_name_hex_id_date_time.txt or server_name_hex_id_date_time.txt.
  • Stand-alone profile:
    • Log file: server_name_exception.log.
    • Text files: server_name_hex_id_date_time.txt.
Deployment manager logs (deployment manager profiles only) are found in these directories:
  • For Linux operating systemFor UNIX operating system profile_root/logs/deployment_manager_name
  • For Windows operating system profile_root\logs\deployment_manager_name
  • For i5/OS operating system profile_root/logs/deployment_manager_name

You will work primarily with four log files in this directory:

  • startServer.log

    Contains the system parameters detected on the system and the messages emitted by the deployment manager during the start process

  • stopServer.log

    Contains the system parameters detected on the system and the messages emitted when the deployment manager is shut down.

  • SystemErr.log

    Contains error and exception messages generated by the deployment manager during runtime. Continually updated while server is running.

  • SystemOut.log

    Contains all messages, including error, warning, and information messages generated by the deployment manager during runtime. Continually updated while server is running.

Node agent logs (custom profiles only) are found in these directories:
  • For Linux operating systemFor UNIX operating system profile_root/logs/node_agent_name
  • For Windows operating system profile_root\logs\node_agent_name
  • For i5/OS operating system profile_root/logs/node_agent_name

You will work primarily with four log files in this directory:

  • startServer.log

    Contains the system parameters detected on the system and the messages emitted by the node agent during the start process

  • stopServer.log

    Contains the system parameters detected on the system and the messages emitted when the node agent is shut down.

  • SystemErr.log

    Contains error and exception messages generated by the node agent during runtime. Continually updated while node agent is running.

  • SystemOut.log

    Contains all messages, including error, warning, and information messages generated by the node agent during runtime. Continually updated while the node agent is running.

Server logs (custom and stand-alone profiles only) are found in these directories:
  • For Linux operating systemFor UNIX operating system profile_root/logs/server_name
  • For Windows operating system profile_root\logs\server_name
  • For i5/OS operating system profile_root/logs/server_name

You will work primarily with four log files in this directory:

  • startServer.log

    Contains the system parameters detected on the system and the messages emitted by the server during the start process

  • stopServer.log

    Contains the system parameters detected on the system and the messages emitted when the server is shut down.

  • SystemErr.log

    Contains error and exception messages generated by the server during runtime. Continually updated while server is running.

  • SystemOut.log

    Contains all messages, including error, warning, and information messages generated by the server during runtime. Also contains any events being monitoring that are emitted from the Common Event Infrastructure (CEI), in Common Base Event format. These events may also include the level of business object data (FINE, FINER, or FINEST) that is specified for the monitor. Continually updated while the server is running.

Node federation log files are found in these directories (only applies to non-deployment manager profiles):
  • For Linux operating systemFor UNIX operating system On Linux® and UNIX® platforms: profile_root/logs
  • For Windows operating system On Windows platforms: profile_root\logs
  • For i5/OS operating system On i5/OS® platforms: profile_root/logs
Two log files are generated when you attempt to federate a custom, augmented, or stand-alone profile to a deployment manager:
  • addNode.log

    contains the pertinent server environment information and messages generated when you attempt to federate the profile.

  • isFederated.log

    lists the commands used by the deployment manager to federate the profile.

The location of the Integrated Solutions Console application deployment log file is listed here (only for deployment manager and stand-alone profiles):
  • For Linux operating systemFor UNIX operating system profile_root/logs/iscinstall.log
  • For Windows operating system profile_root\logs\iscinstall.log
  • For i5/OS operating system profile_root/logs/iscinstall.log

The iscinstall.log file contains information regarding the deployment of the administrative console application in a deployment manager or stand-alone profile.

The location of the Installation Verification Tool log file is listed here (only for deployment manager and stand-alone profiles):
  • For Linux operating systemFor UNIX operating system profile_root/logs/ivtClient.log
  • For Windows operating system profile_root\logs\ivtClient.log
  • For i5/OS operating system profile_root/logs/ivtClient.log

This log file contains the output generated by the Installation Verification Tool. You can start this program from the First Steps console after you create a deployment manager or stand-alone profile. The log contains basic configuration information and the messages that are displayed when you run the tool.

The location of the log file detailing the commands generated for a profile creation is listed here:
  • For Linux operating systemFor UNIX operating system profile_root/logs/updateserverpolicy.log
  • For Windows operating system profile_root\logs\updateserverpolicy.log
  • For i5/OS operating system profile_root/logs/updateserverpolicy.log

This file contains the sequence of commands used by the product to set server environment variables and create a profile. All profile types will contain this file.


concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/cadm_log_files.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).