Troubleshooting with logs

Edit online

Logging information in AS4 Microservice includes separately logged information for member activity, commands, and other activities.

Use logging information to troubleshoot issues when unexpected results occur during the operation of AS4 Microservice or the running of a command.

For example, if there is a problem with an AS4 transaction, you can troubleshoot the problem by examining the log files in <install directory>/Members/Operational/usr/servers/Operational/logs. The log files are in this location because AS4 communications are managed by the operational member of a node of AS4 Microservice.

Use logging information in conjunction with the exchange and event details information that you access from the home page of AS4 Microservice.

Logging is enabled by default in AS4 Microservice.

Logging information includes the following types of information:
  • Member activity like transactions and provisioning
  • Command activity from the start of the command to its completion
  • WebSphere® MQ logging
  • IBM Installation Manager activities like installing, updating, and uninstalling

Use the following guidelines when working with logging:

  • You can gather logs for IBM® Customer Support using the collect_logs command.
  • You can also gather logs across all nodes in the system with System Management > System Diagnostics. Click Collect System Diagnostics to trigger the system to collect the most recent logs across all nodes. Click Download to download the most recently collected diagnostics.
  • You cannot use the purge set command to delete log files. You must manually delete log files.
  • You can view log information only by looking at the log text files in your installation file system.
  • You can archive log files only by manually saving them from the installation file system.