WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Profile-specific log files

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

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.

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 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.
  • Managed node 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 SystemErr.log and SystemOut.log are found in deployment manager job logs unless customized to write to a file. The start and stop server logs are found in profile_root/logs/dmgr if started in USS.

You will work primarily with two 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.

Node agent logs SystemErr.log and SystemOut.log are found in node agent job logs unless customized to write to a file. The start and stop server logs are found in profile_root/logs/nodeagent if started in USS.

You will work primarily with two 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.

Server logs SystemErr.log and SystemOut.log are found in server job logs unless customized to write to a file. The start and stop server logs are found in profile_root/logs/<servername> if started in USS.

You will work primarily with two 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.

Node federation log files are found in the profile_root/logs/ directory.
Two log files are generated when you attempt to federate a node 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):The location of the Integrated Solutions Console application deployment log file is in the <profilepath>/logs directory.

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 log files for a profile creation is the install_root/logs/ directory.

These files contain the output from profile creation. 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.zseries.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).