AS4 Microservice log files
You can access and view several types kinds of log files to troubleshoot and diagnose different issues inAS4 Microservice.
There are several types of log files in AS4 Microservice, member log files, console (command) log files, Installation Manager log files, and WebSphere® MQ log files. Member log files contain the message for the components that run on each member. Console (command) log files contain details of when and who ran commands. Installation Manager log files contain information about operations done with the Installation Manager. The WebSphere MQ libraries create log and trace in response to certain error conditions.
Collecting logs with System Diagnostics
You can gather logs across all nodes in the system with Collect System Diagnostics to collect the most recent log information across all nodes. Log collections are saved until you delete them on the System Diagnostics page. Click the Collection Identifier of a particular log collection to download it to your system.
. ClickFor more information about managing system diagnostics, see Monitoring system diagnostics.
Member log file locations
Log files are written to the following folders, which are based on the member and the components that are running on that member. For example, all communication messages are written to the Operational.log because the communications component runs in the Operational member. Each host that has an Operational member has its own Operational.log file. If you have more than one host in your installation, you might need to check log files on several hosts before you find the message that you are looking for.
Member Type | Components | Default Location | AUDIT, INFO, WARNING, and ERROR messages log | TRACE messages log |
---|---|---|---|---|
Operational | Includes the communications, storage (server and client), and identity components; and the visibility receiver (exchange tracking service). Optionally, it includes a perimeter server configuration for use by communications connections. | <install directory/Members/Operational/usr/servers/Operational/logs | Operational.log | Operational_trace.log |
Informational | Includes the user interface, the trading partner repository, and visibility database and user interface services. | <install directory/Members/Informational/usr/servers/Informational/logs | Informational.log | Informational_trace.log |
WebSphere eXtreme Scale catalog | Runs one catalog server in support of the data grid. A catalog member acts as an index to the information stored in the container member. | <install directory/Members/WXSCatalog/usr/servers/WXSCatalog/logs | WXSCatalog.log | WXSCatalog_trace.log |
WebSphere eXtreme Scale container | Runs one container server in support of the data grid. A container member stores the data grid information. | <install directory/Members/WXSContainer/usr/servers/WXSContainer/logs | WXSContainer.log | WXSContainer_trace.log |
Console log file for command line interface commands
The console log file is in the <install directory/Members/logs directory and is called console_cmd_0.log. As The log file rolls over as needed, from console_cmd_0.log to console_cmd_0.log.1 to console_cmd_0.log.2, and so on. The log file with the highest number is the most recent.
The console log file logs error and audit information for AS4 Microservice commands. Any errors that occur when you run a command are logged in the console log file. Modification to the system, such as configuration changes and member start and stop commands, are logged with the user name that changed it for troubleshooting purposes and not security auditing.
Log files for the Installation Manager
Every operation of the IBM® Installation Manager generates a log file.
When you run the Installation Manager, log files are generated in XML format in the following directories:
- (Windows) C:\ProgramData\IBM\Installation Manager\logs
- (Linux®) /var/ibm/InstallationManager/logs
WebSphere MQ log file location
The directories that contain the log files for WebSphere MQ are specified in the jms.config file in the /<install directory>/Members/resources directory.