Viewing Installation Manager log files

The IBM® Installation Manager application creates log files during the installation process. These logs can be viewed through a browser.

Before you begin

You must have a browser available to view the log files. If you are on a server that does not have a browser, copy the logs to a workstation.

To enable enhanced debug logging in ./InstallationManager/logs, copy STARTUPKIT_INSTALL_HOME/InstallationManagerDebug/log.properties into ./InstallationManager/logs before starting IBM Installation Manager to begin installing InfoSphere® MDM.

Important: After you have enabled enhanced debug logging, the logged information in ./InstallationManager/logs can include password details entered by the user during the installation. Ensure that these logs are stored in a secure place to avoid password exposure.

About this task

The logs contain messages with INFO, DEBUG, WARNING, or ERROR labels. If the installation is successful, all messages have an INFO or DEBUG label. Messages that are identified as WARNING or ERROR must be reviewed.
Tip: For more information about using IBM Installation Manager logs to troubleshoot an installation, see the related links at the end of this topic.

Procedure

  1. Go to the ./InstallationManager/logs directory.
  2. Open the index.xml file.
  3. From the All Log Files table, click a link that corresponds to the IBM Installation Manager session that installed InfoSphere MDM.
  4. Locate the following link: Custom operation MDM Operational Server, verifying install location in unit mdmv.app.set.install.location.

    That link, and subsequent links, show installation process messages.

  5. Look for messages that are identified as WARNING or ERROR. The messages must be reviewed to identify potential problems with your installation.
  6. Click a link to view native log file representations of an installation process segment.

    Such processes can include running custom Java™ code to manage InfoSphere MDMfiles, to run the madconfig utility Ant-based tool that in turn runs SQL scripts, and to implement the WebSphere® Application Server MBean API that deploys InfoSphere MDM deployment archives like EBA and EAR files, and other actions.

Results

If you have messages that are identified as WARNING or ERROR, try to determine the cause of the issue by searching for Java or Ant exception errors. If you locate a workaround for the WARNING or ERROR, attempt to fix the installation or contact IBM Software Support.