Profile-specific log files

There are log files detailing the characteristics and runtime activities of individual profiles. This topic applies only to the Distributed platforms 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 installation_root represents the installation directory of IBM® Business Process Manager. The variable profile_root represents the root location of a profile.

This topic applies only to the Distributed platforms For more information, see Installation directories for the product and profiles.

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: 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. 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 (deployment manager 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 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 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 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 (managed-node 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 (managed-node 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/`server_name` 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-deployment manager 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 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. 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): 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 `profile_root`/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 Installation Verification Tool log file is listed here (only for deployment manager 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 Quick start 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.