Profile-specific log files

IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting administration tasks and tools
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.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 run time. Some of these log files are also used to capture a Common Base Event (that might 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 IBM BPM. The variable profile_root represents the root location of a profile.
See Installation directories for the product and profiles.

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:

On Linux and UNIX platforms: profile_root/logs/ffdc
On Windows platforms: profile_root\logs\ffdc
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.

Custom profile:

Log file(s) — node_agent_name_exception.log and server_name_exception.log.
Text files — node_agent_name(or) server_name_ hex_id_ date_ time.txt.

Managed node profile:

Log file(s) — node_agent_name_exception.log and server_name_exception.log .
Text files — node_agent_name(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 (dmgr profiles only) are found in these directories:

On Linux and UNIX platforms: profile_root/logs/ deployment_manager_name
On Windows platforms: profile_root\logs\ deployment_manager_name
Deployment manager logs SystemErr.log and SystemOut.log are found in dmgr 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 UNIX System Services.
You will work primarily with four log files in this directory: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 dmgr during the start process
stopServer.log —
Contains the system parameters detected on the system and the messages emitted when the dmgr is shut down.
SystemErr.log —
Contains error and exception messages generated by the dmgr during runtime. Continually updated while server is running.
SystemOut.log —
Contains all messages, including error, warning, and information messages generated by the dmgr during runtime. Continually updated while server is running.

Node agent logs (custom profiles only) are found in these directories:

On Linux and UNIX platforms: profile_root/logs/ node_agent_name
On Windows platforms: profile_root\logs\ node_agent_name
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 UNIX System Services.
You will work primarily with four log files in this directory: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.
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:

On Linux and UNIX platforms: profile_root/logs/ server_name
On Windows platforms: profile_root\logs\ server_name
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 UNIX System Services.
You will work primarily with four log files in this directory: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.
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-dmgr profiles):

On Linux and UNIX platforms: profile_root/logs
On Windows platforms: profile_root\logs
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 dmgr:

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 dmgr to federate the profile.
Two log files are generated when you attempt to federate a custom, augmented, or stand-alone profile to a dmgr:

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 dmgr to federate the profile.

The location of the Integrated Solutions Console application deployment log file is listed here (only for dmgr and stand-alone profiles):

On Linux and UNIX platforms: profile_root/logs/iscinstall.log
On Windows platforms: profile_root\logs\iscinstall.log
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 dmgr or stand-alone profile.
The location of the Installation Verification Tool log file is listed here (only for dmgr and stand-alone profiles):

On Linux and UNIX platforms: profile_root/logs/ivtClient.log
On Windows platforms: 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 dmgr 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:

On Linux and UNIX platforms: profile_root/logs/updateserverpolicy.log
On Windows platforms: profile_root\logs\updateserverpolicy.log
The location of the log files for a profile creation is the INSTALL_ROOT/logs/ directory.
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.These files contain the output from profile creation. All profile types will contain this file.

Troubleshooting IT administration
Troubleshooting administration tasks and tools

Related concepts:
IBM BPM log files

Related information:

Installation and profile creation log files

Log	Contents
First failure data capture (ffdc) log and exception files (common to all profile types) are found in these directories: On Linux and UNIX platforms: profile_root/logs/ffdc On Windows platforms: profile_root\logs\ffdc 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. Custom profile: Log file(s) — node_agent_name_exception.log and server_name_exception.log. Text files — node_agent_name(or) server_name_ hex_id_ date_ time.txt. Managed node profile: Log file(s) — node_agent_name_exception.log and server_name_exception.log . Text files — node_agent_name(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 (dmgr profiles only) are found in these directories: On Linux and UNIX platforms: profile_root/logs/ deployment_manager_name On Windows platforms: profile_root\logs\ deployment_manager_name Deployment manager logs SystemErr.log and SystemOut.log are found in dmgr 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 UNIX System Services.	You will work primarily with four log files in this directory: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 dmgr during the start process stopServer.log — Contains the system parameters detected on the system and the messages emitted when the dmgr is shut down. SystemErr.log — Contains error and exception messages generated by the dmgr during runtime. Continually updated while server is running. SystemOut.log — Contains all messages, including error, warning, and information messages generated by the dmgr during runtime. Continually updated while server is running.
Node agent logs (custom profiles only) are found in these directories: On Linux and UNIX platforms: profile_root/logs/ node_agent_name On Windows platforms: profile_root\logs\ node_agent_name 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 UNIX System Services.	You will work primarily with four log files in this directory: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. 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: On Linux and UNIX platforms: profile_root/logs/ server_name On Windows platforms: profile_root\logs\ server_name 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 UNIX System Services.	You will work primarily with four log files in this directory: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. 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-dmgr profiles): On Linux and UNIX platforms: profile_root/logs On Windows platforms: profile_root\logs 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 dmgr: 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 dmgr to federate the profile. Two log files are generated when you attempt to federate a custom, augmented, or stand-alone profile to a dmgr: 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 dmgr to federate the profile.
The location of the Integrated Solutions Console application deployment log file is listed here (only for dmgr and stand-alone profiles): On Linux and UNIX platforms: profile_root/logs/iscinstall.log On Windows platforms: profile_root\logs\iscinstall.log 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 dmgr or stand-alone profile.
The location of the Installation Verification Tool log file is listed here (only for dmgr and stand-alone profiles): On Linux and UNIX platforms: profile_root/logs/ivtClient.log On Windows platforms: 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 dmgr 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: On Linux and UNIX platforms: profile_root/logs/updateserverpolicy.log On Windows platforms: profile_root\logs\updateserverpolicy.log The location of the log files for a profile creation is the INSTALL_ROOT/logs/ directory.	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.These files contain the output from profile creation. All profile types will contain this file.