For some of the mws commands, My webMethods Server creates a log file with information from the command execution in addition to logging the command output to the console. The log file name takes this form:

command-name_server-name.log

where:

For example, if you issue this command:

The resulting log file has the name create-osgi-profile_alpha.log.

The log files for mws commands are written to this location:

Software AG_directory \MWS\bin

If the mws command is unsuccessful, one quick way to check the log file is to search for the existence of this exit code:

Following that code, you should find the missing requirement, possibly a missing bundle or feature ID. If you cannot find an obvious reason for the failure, be prepared to make a copy of the log file available to Software AG Global Support.

When My webMethods Server is running inside a container, only certain actions, such as applying a test patch or a third-party library at the time of container startup can result in writing a log file to the bin directory for the instance. If you want to keep these log files, and you have not specified a volume for log files, create a backup copy before shutting down the container.