Introduction

With an installation of WebSphere Business Monitor, there are a variety of logs generated by the product installer as well as the prerequisite products, such as WebSphere Application Server, WebSphere Portal and DB2 AlphaBlox. Not every log is created directly by the WebSphere Business Monitor product installer. This article explores the logs that help you identify problems that could occur during installation. Learn:

• What logs are available and where they are located.
• How to use the logs to determine the underlying problems.
• How to determine if a problem is related to WebSphere Business Monitor or to one of the prerequisite products.
• How to find the source of a problem and where to focus your attention to resolve the problem.

This article does not try to give answers to specific problems. Rather, it is a guide to the process of discovering the underlying issues. You will get a general understanding of the information that is available and guidelines for finding that information. This article is intended for the average user or administrator who will install WebSphere Business Monitor and wants to know what's available to help identify installation problems.

Version-specific differences

This article covers WebSphere Business Monitor 6.1, 6.1.1 and 6.1.2. You can apply an understanding of log analysis to all three versions. However, the locations of some logs were modified for WebSphere Business Monitor 6.1.2. Web-based dashboards created on 6.1 and 6.1.1 were replaced with business space dashboards on 6.1.2. The different locations will be specified when necessary.

Back to top

Logs, logs, and more logs

There are many different logs associated with WebSphere Business Monitor and the prerequisite products. Searching for information in these logs can be a challenge. Before you dive into a log, you need to know which log to start from. This article shows you where to start and how to proceed to diagnose installation problems for WebSphere Business Monitor.

The following is basic information that will be used throughout this article.

• Product root directories
  
  

  Filename	Description
  <WAS_ROOT>	WebSphere Application Server root directory
  <WP_ROOT>	WebSphere Portal root directory
  <WPWAS_ROOT>	WebSphere Application Server root directory for WebSphere Portal
  <WBM_ROOT>	WebSphere Business Monitor root directory

  
  
  
• File name notation
  
  

  Filename	Description
  <WP_PROFILE_NAME>	WebSphere Portal profile name
  <WBM_PROFILE_NAME>	WebSphere Business Monitor profile name
  <WP_PROFILE_PATH>	WebSphere Portal profile path name
  <WBM_PROFILE_PATH>	WebSphere Business Monitor profile path name

  
  
  
• File path formats

  The file paths where you can find the logs are identified using nomenclature like <WAS_ROOT> to designate the root directory and generic path format, for example, <WAS_ROOT>/logs/install. Ignore the fact that Microsoft® Windowsâ„¢ uses the backslash instead of the forward slash for directory separators.

• Temporary locations for installation logs

  WebSphere Business Monitor and some of the prerequisite products will initially create their installation logs in the user's temporary directory. After the product installation is complete, the logs are moved to the expected location (the product's permanent installed location).

  If something goes drastically wrong with the installation and you cannot find a log file in the expected location, you might be able to find it in the user's temporary location. For Windows, a temporary location could be: C:\Documents and Settings\Administrator\Local Settings\Temp\ for the Administrator user. For Linux®, the location could be /tmp for the root user.

• <WBM_ROOT> location

  <WBM_ROOT> can be located in either <WAS_ROOT> or <WP_ROOT> depending on what WebSphere Business Monitor components are installed. If WebSphere Business Monitor server is installed, then <WBM_ROOT> will be the same as <WAS_ROOT>. If only the portlet-based dashboards components are selected for installation, then <WBM_ROOT> will be the same as <WP_ROOT>.

There are a variety of installation logs, as well as run time logs, to deal with. There are more logs than mentioned in this article. This article tries to cover the logs you will most likely need when diagnosing installation problems.

The next section identifies, by product, the logs that are available.

Back to top

WebSphere Business Monitor logs

For the WebSphere Business Monitor installation, there are several log files that you should understand. There is a single main log where you can always begin. The main log file contains a summary of the system environment and the options chosen for the installation. It also has messages that show the progress of the WebSphere Business Monitor installation. Errors detected during the installation process will be identified in this main log whenever possible. Though you might have to go to other logs for more detailed information about failures, this article tries to point to them wherever possible so you don’t have to guess where to go next.

The following WebSphere Business Monitor product log files are in the <WBM_ROOT>/logs/wbm/ directory. As mentioned, <WBM_ROOT> can be the same as either your WebSphere Application Server 6.1 product root (if you installed the monitor server), or your WebSphere Portal 6.0.1.1 product root (if you installed only portlet-based dashboards).

• Primary WebSphere Business Monitor installation log and trace files
  
  

  Filename	Description
  install/wbm_<timestamp>_install_out.log	The main log file for the WebSphere Business Monitor installer. Always start here for a summary of the success or failure of the WebSphere Business Monitor installation and any prerequisite products installed by the WebSphere Business Monitor installer. Error messages may reference other log files for more detail.
  install/wbm_<timestamp>_install_trace.log	The main trace file for the WebSphere Business Monitor installer. Contains much more detailed information about the installation, including data used to install and configure the various components. Sometimes the contents of external logs are copied into the trace file. The trace information can be very useful for the IBM support team to help diagnose installation problems that may arise.

  
  
  
• Common install engine (CIE) log files
  
  

  Filename	Description
  install/log.txt	The summary CIE log file that is generated by the CIE framework. It shows a success or failure summary of each configuration run (or installation step) using the CIE framework. This log file will report the success or failure of each step and provide an overall success or failure indicator at the end.
  installconfig.log	An XML formatted message file generated by the CIE framework. Contains detailed processing messages generated while executing installation scripts within the CIE framework. Will capture exceptions, stack traces, and other detailed information on the problem.

  
  
  
• Other logs under <WBM_ROOT>/logs/wbm
  
  

  Filename	Description
  install/portalinstallresponse.txt	The WebSphere Portal silent installation response file. Contains all of the input options provided to the WebSphere Portal installer.
  install/responsefile.nd.txt	The WebSphere Application Server silent installation response file. Contains all of the input options provided to the WebSphere Application Server installer.

  
  
  
• Profile management tool (PMT) logs

  PMT, which is the user interface for manageprofiles, creates a log for every profile that it creates. During WebSphere Business Monitor installation, if you choose to create a profile, then manageprofile is called. It will generate a log for the corresponding profile that is created. If PMT is called to create a new profile after WebSphere Business Monitor is installed, then a log file (for the new profile) will also be generated in this location.

  The following WebSphere Business Monitor PMT log files are in the <WBM_ROOT>/logs/manageprofiles/ directory.

  
  
  

  Filename	Description
  <WBM_PROFILE_NAME>_create.log	Log created to capture a list of configuration actions executed during creation and setup of profile.
  <WBM_PROFILE_NAME>_augment.log	Log created when a WebSphere Application Server profile already exists and a user runs PMT to augment the profile with WebSphere Business Monitor. This log is generated to capture the augmentation.

  
  
  

  The following WebSphere Business Monitor PMT log files are in the <WBM_ROOT>/logs/wbm/install/ directory.

  
  
  

  Filename	Description
  wbm_<timestamp>_<WBM_PROFILE_NAME>_augment_out.log	This log should be very small and contain only a summary. It is generated when a profile is created or augmented using PMT. WebSphere Business Monitor only augments a WebSphere Application Server profile; the creation portion is done by WebSphere Application Server itself (WebSphere Application Server code). When the profile is created at WebSphere Business Monitor installation run time, this log is not created. All logging is sent to the overall wbm_<timestamp>_install_out.log. For details about this execution, the user must investigate the corresponding trace file (following).
  wbm_<timestamp>_<WBM_PROFILE_NAME>_augment_trace.log	The detailed log file generated when a profile is created or augmented using PMT. Contains much more detailed information about the creation and augmentation of a profile. Error messages may reference other log files.

  
  
  
  • WSAdmin logs

    The following logs capture output messages from the execution of configuration actions. These configuration actions are called during the creation of a profile (through manageprofiles during WebSphere Business Monitor installation) or later, during creation or augmentation of the profile (using PMT).

    Most of the logs had the filename modified for WebSphere Business Monitor 6.1.2, even though the description is still the same. New logs were also created for this version. Web-based dashboards created on 6.1 and 6.1.1 were replaced with business space dashboards on 6.1.2.

    For WebSphere Business Monitor 6.1 and 6.1.1, these log files are in the <WBM_PROFILE_PATH>/logs directory. For WebSphere Business Monitor 6.1.2, these log files are in the <WBM_ROOT>/logs/manageprofiles/<WBM_PROFILE_NAME> directory.

    
    
    

    Filename	Description
    configCEI.log	Messages written during the deployment of CEI and configuration of CEI’s database.
    configWBMSIB.log	Messages written during the creation of monitor service integration bus and the configuration of its security and action services.
    enableIdentityAssertion.log	Messages written during the enabling of identity assertion for both inbound and outbound communication.
    InstallActionManager.log	Messages written during the installation of the action services application and the creation of queues and corresponding Java™ Naming and Directory Interface (JNDI) names.
    InstallDashboard.log	Messages written during the installation of Web-based dashboards application and the setting of security to admin role.
    InstallDMSService.log	Messages written during the creation of MonitorDMSServiceWorkManager and its JNDI name (DB2 or Oracle only).
    InstallRestServices.log	Messages written during the installation of REST services application and the setting of security to monitor user role.
    installVmmService.log	Messages written during the installation of VMM services WIM and WIMWMM system applications.
    installWBMISCPortlet.log	Messages written during the installation of WebSphere Business Monitor welcome and monitor data security ISC portlets.
    MonitorServerResourceInstall.log	Messages written during the creation of the monitor data sources, the variables at cell or node scope, the monitor JDBC providers, the authorization alias, and the enabling of application security.
    InstallABXDashboard.log	Messages written during the installation of AlphaBlox Web-based dashboards application and creation of AlphaBlox data sources.
    createshortcutforabx.log	Messages written during the creation of the start menu shortcut for AlphaBlox.
    createshortcutforprofile.log	Messages written during the creation of the start menu shortcut for the WebSphere Business Monitor profile.

    
    
    
  • General to wsadmin

    These general wsadmin log files are in the <WBM_PROFILE_PATH>/logs directory.

    
    
    

    Filename	Description
    AboutThisProfile.txt	Contains general information about profile, including port numbers and so on.
    ivtClient.log	Contains information created during execution of WebSphere Application Server first steps and installation verification test (IVT).
    wsadmin.traceout	Contains information about current environment and some trace steps.

    
    
    
• Portlet-based dashboards installation and configuration

  Portlet-based dashboards can be installed by itself or as part of the WebSphere Business Monitor server installation. In either case, the following logs are created during specific portions of the portlet-based dashboards installation. The logs are always in subdirectories under the WebSphere Portal root directory (<WP_ROOT>).

  • WebSphere Business Monitor AlphaBlox theme log

    The log is in the <WP_ROOT>/wbmonitor/install/logs directory.

    
    
    

    Filename	Description
    Set_ABXTheme.out	Created by WebSphere Business Monitor during installation of the WebSphere Business Monitor theme for AlphaBlox.

    
    
    
  • XMLAccess logs

    The following logs are created by WebSphere Business Monitor installation during the portlet-based dashboards installation and configuration steps. The logs are written by XMLAccess, which is the WebSphere Portal tool for installing and configuring portlets.

    These logs are in the <WP_ROOT>/wbmonitor/logs directory.

    
    
    

    Filename	Description
    abxinst_CreateABXPalette.out	Messages written during creation of the AlphaBlox palette (only during AlphaBlox feature installation).
    abxinst_CreateAllDashboards.out	Messages written during creation of all the dashboards (only during AlphaBlox feature installation).
    abxinst_CreateMonitorCategory.out	Messages written during creation of the WebSphere Business Monitor category (only during AlphaBlox feature installation).
    abxinst_CreateUtilities.out	Messages written during creation of the utilities tab (only during AlphaBlox feature installation).
    abxinst_Deploy_ABXPortlet.out	Messages written during deployment of the AlphaBlox portlet (only during AlphaBlox feature installation).
    abxinst_Deploy_Theme.out	Messages written during deployment of the WebSphere Business Monitor theme (only during AlphaBlox feature installation).
    abxinst_SetWelcomePage.out	Messages written during setting of the portlet-based dashboards welcome page (only during AlphaBlox feature installation).
    abxinst_Set_WPSTheme.out	Messages written during setting of the IBM WebSphere Process Server theme (only during AlphaBlox feature installation).
    CreateMonitorCategory.out	Messages written during creation of the WebSphere Business Monitor category.
    CreateSampleDashboards.out	Messages written during creation of sample dashboards.
    CreateUtilities.out	Messages written during creation of the utilities tab.
    Deploy_Theme.out	Messages written during deployment of the WebSphere Business Monitor theme.
    Deploy_WBIMon.out	Messages written during deployment of the portlet-based dashboards.
    SetWelcomePage.out	Messages written during setting of the portlet-based dashboards welcome page.
    Set_WPSTheme.out	Messages written during setting of the WebSphere Process Server theme.

    
    
    
  • wsadmin logs

    The following logs are generated when using wsadmin to install and configure components needed by the portlet-based dashboards. wsadmin is a WebSphere Application Server tool used for installing and configuring applications in WebSphere Application Server. You can find the logs in the <WP_PROFILE_PATH>/logs directory.

    
    
    

    Filename	Description
    installABXPortalDashboard.log	Log written during configuration of the data source for the AlphaBlox portlet.
    installHumanTask.log	Log written during configuration of human task for WebSphere Process Server.
    installPortalDashboardRestProxy.log	Log written during installation of the REST service proxy application.
    wsadmin.traceout	Log written when installations scripts are run with wsadmin. This file is overwritten each time wsadmin is called, so information tends to get lost. It's useful for getting information about the last script executed.

    
    
    
  • wasprofile logs

    The following logs are generated when using wasprofile to create or augment a profile. wasprofile is a WebSphere Application Server 6.0 tool used for installing, modifying, and deleting WebSphere Application Server profiles. This tool is the equivalent of the manageprofile tool used in WebSphere Application Server 6.1.

    The profile defines a WebSphere Application Server run time environment with applications that will run in that environment. For portlet-based dashboards, the WebSphere Portal profile (wp_profile) is only augmented. The creation of the profile is done during the WebSphere Portal installation.

    The following is created during portlet-based dashboards installation, and is located in the <WPWAS_ROOT>/logs/wasprofile directory.

    
    
    

    Filename	Description
    wasprofile_augment_wp_profile.log	Created during portlet-based dashboards installation by WebSphere Business Monitor installer.

    
    
    
• IVT logs

  Logs are created when a user launches IVT under <WBM_PROFILE_PATH>/firststeps.wbm. The log files are in the <WBM_PROFILE_PATH>/logs directory.

  
  
  

  Filename	Description
  wbm_<timestamp>_<profile_type>_ivt_out.log	Output log for IVT. <timestamp> captures the time when this file was created. <profile_type> describes the type of profiles that could be created: custom, default (application server), dmgr (deploy manager), and federated.
  wbm_<timestamp>_ivu_out.log	Output log for installation verification utility (IVU), which checks a list of WebSphere Business Monitor components and verifies that components were installed properly. <timestamp> captures the time when this file was created.

  
  
  

Back to top

WebSphere Application Server logs

You need to know about several types of logs for WebSphere Application Server 6.1, including installation logs, run time logs, profile management logs, and the wsadmin logs. The installation logs are written to during the WebSphere Application Server product installation and provide valuable information in the event of a WebSphere Application Server installation failure. The run time logs are written during the course of WebSphere Business Monitor product installation and configuration, as are the PMT and wsadmin logs. The PMT and wsadmin logs are also described in WebSphere Business Monitor logs.

• Installation logs

  The installation logs are written to by the WebSphere Application Server installer during the course of the WebSphere Application Server product installation. If you choose to install WebSphere Business Monitor using the basic installation option, then a new copy of WebSphere Application Server will be installed on your system and you'll need to know about the installation logs. The WebSphere Application Server installation logs are originally generated in the users temporary directory and then moved to <WAS_ROOT>/logs/ (for the user).

  
  
  

  Filename	Description
  install/log.txt	The summary CIE log file that is generated by the CIE framework during WebSphere Application Server product installation. It shows a success and failure summary of each configuration (or install step) run using the CIE framework. This log file will report the success or failure of each step, and an overall success or failure indicator at the end.
  update/tmp/updateconfig.log	Generated during the WebSphere Application Server update (or fix pack) part of the installation. In XML format, it shows a success and failure summary of each configuration (or install step) run using the CIE framework. This log file will report the success or failure of each step, and an overall success or failure indicator at the end.

  
  
  
• run time logs

  The following logs are written when the server (Java Virtual Machine (JVM) for server named server1) is running for the WebSphere Business Monitor profile named WBMon01. These logs are in the logs/server1 subdirectory under the profile path for WebSphere Business Monitor— <WBM_PROFILE_PATH>/logs/server1.

  
  
  

  Filename	Description
  startServer.log	Messages written during server startup.
  stopServer.log	Messages written during server shutdown or stop.
  SystemErr.log	Error and exception conditions output during startup, shutdown, and operation of the server.
  SystemOut.log	Messages written during startup, shutdown, and operation of the server.
  native_stderr.log	Standard error output written by any native code running under the server.
  native_stdout.log	Standard output written by any native code running under the server.

  
  
  
• First failure data capture

  There are logs in the <WBM_PROFILE_PATH>/logs/ffdc directory for what is defined by WebSphere Application Server as first failure data capture (ffdc). The logs contain information generated at run time from a WebSphere Application Server processing failure. The information is primarily useful for an IBM service representative when analyzing a failure.

Back to top

WebSphere Portal logs

WebSphere Portal, like WebSphere Application Server, has several different types of logs that warrant mentioning, including installation, run time, wasprofile, wsadmin, and XMLAccess logs. This section discusses the installation and run time logs.

Installation logs are written during the WebSphere Portal product installation, and provide valuable information in the event of a WebSphere Portal installation failure. The run time logs are written during the course of WebSphere Business Monitor product installation and configuration, as are the wasprofile, wsadmin, and XMLAccess logs. The wasprofile, wsadmin, and XMLAccess logs are written during the installation and configuration of Portlet-based dashboards, and are also described in the section about Portlet-based dashboards logs.

The WebSphere Portal run time and installation logs are in the <WP_ROOT>/log directory in the WebSphere Portal product root directory.

The main installation logs for WebSphere Portal are shown below.

The main run time logs for WebSphere Portal are shown below.

The WebSphere Portal start and stop logs are in the <WP_PROFILE_PATH>/logs/WebSphere_Portal directory, as follows.

WebSphere Application Server 6.0 logs (for WebSphere Portal)

A copy of WebSphere Application Server 6.0.2 is installed by WebSphere Portal. WebSphere Application Server 6.0.2 serves as the base run time server for WebSphere Portal. So, you need to be aware of some of the WebSphere Application Server 6.0 logs that are generated during the installation of WebSphere Portal.

Similar to WebSphere Application Server 6.1, there are several types of logs to understand, including installation, run time, WebSphere Application Server profile logs, and the wsadmin logs.

The installation logs are written to during the WebSphere Application Server product installation, and provide valuable information in the event of a WebSphere Application Server installation failure. The run time logs are written during the course of WebSphere Portal and WebSphere Business Monitor Portlet-based dashboards installation and configuration. The wasprofile and wsadmin logs are written both during wp_profile creation by WebSphere Portal and by profile augmentation for Portlet-based dashboards. The wasprofile logs are mentioned in this section. The wasprofile and wsadmin logs are also described in WebSphere Business Monitor logs.

WebSphere Application Server 6.0 installation logs

WebSphere Application Server is installed using the CIE. The logs generated during WebSphere Application Server installation are in the <WPWAS_ROOT>/logs directory.

wasprofile logs

The following logs are generated when using wasprofile to create or augment a profile. wasprofile is a WebSphere Application Server tool used for installing, modifying, and deleting WebSphere Application Server profiles. The profile defines a WebSphere Application Server run time environment with applications that will run in that environment. For WebSphere Portal installation, the WebSphere Portal profile (wp_profile) is created during the WebSphere Portal installation.

The wasprofile logs are in the <WPWAS_ROOT>/logs/wasprofile directory.

run time logs

There are some run time logs in the profile directory structure, but the main run time logs for WebSphere Portal are in <WP_ROOT>/logs, as mentioned above. The run time logs found here are primarily for the WebSphere Portal administrative server (server1) run time and exception logs. These logs are in subdirectories under the wp_profile path: <WP_PROFILE_PATH>/logs.

First failure data capture

There are logs in the <WP_PROFILE_PATH>/logs/ffdc directory for what is defined by WebSphere Application Server as first failure data capture (ffdc). These logs contain information generated at run time from a WebSphere Application Server processing failure. The information is useful for an IBM service representative who is analyzing a failure.

server1 run time logs

The <WP_PROFILE_PATH>/logs/server1 directory contains run time logs for the WebSphere Portal administrative server. These logs are written during WebSphere Portal product installation. They are not typically useful for WebSphere Business Monitor related install problems. However, it is good to understand what they are.

WebSphere_Portal run time logs

WebSphere_Portal is the default name for the server created for WebSphere Portal to run on. There are only two logs in the <WP_PROFILE_PATH>/logs/WebSphere_Portal directory. The main run time log (SystemOut.log) is maintained in the WebSphere Portal logs directory.

Back to top

DB2 AlphaBlox logs

If AlphaBlox has been installed, it will either be installed with Web-based dashboards (or business space dashboards, in the case of WebSphere Business Monitor V6.1.2), or with portlet-based dashboards, in one of the following locations.

• For Web-based dashboards or business space dashboards, the AlphaBlox logs for Web-based (or business space) dashboards can be found in the <WBM_PROFILE_PATH>/AlphaBlox_server1 directory.
• For Portlet-based dashboards, the AlphaBlox logs for portlet-based dashboards can be found in the <WP_PROFILE_PATH>/AlphaBlox directory.

The AlphaBlox installation logs are shown below.

Back to top

Putting it all together

Now that you're familiar with logs and where to find them, it's time to think about problem determination when the WebSphere Business Monitor installer reports that something failed. The primary indicator of success or failure is the result code. The result code is reported to you by the installer when it's running interactively and will appear in a message at the bottom of the main install log. The result code will be set to one of the following values.

If the product did not install successfully you'll need to find out why. The place to start looking is in the WebSphere Business Monitor main log. Recall that this main log file is named with a date and time stamp (for example, wbm_07.12.04_11.20.54.876_install_out.log) and is in the monitor installation root directory under the logs/wbm/install subdirectory. It's usually best to start at the top the log and work your way down to locate the first error. More often than not, one error will lead to another. It's best to solve the first problem before journeying into the weeds with errors discovered further into the installation process.

The WebSphere Business Monitor main log file is a simple text file that you can open in your favorite text viewer, and scan down through the messages in the log. The messages are formatted for relatively easy reading.

The general format is:

<TIMESTAMP> space THREAD-ID space COMPONENT-ID space(s) MSG-LEVEL space 
	MSG-CODE: space MSG-TEXT

For example:

	   
[07/12/10 14:18:51:935 EST] Runnable PORTDASH    
 E CWMLP2135E: Completed configuration action: 30S_StartPortalServer with error(s)!! 
Details can be found in log file:
 /usr/IBM/WebSphere/PortalServer/logs/WebSphere_Portal/SystemOut.log

An easy way to search for errors in the log is to start at the top and search for the string " E " (space E space).

Determining where to go next

Your search through the WebSphere Business Monitor main log file is going to yield one of the following results:

• You found a message that directly identifies the problem.

  Now you just have to fix it. (Sorry, this article doesn't cover the fix-it part).

• You found a message that identifies a general problem, but you need to look somewhere else for more information.

  You'll need to go to another log file to find the details. Fortunately, the message tries to help you by giving a pointer to the name and location of the next log file that can aid the situation. Many messages contain the text "Details can be found in log file," along with the name and path of the log file that might have exactly what you're looking for. Some problems are easy to find because there is an error message in the referenced log file. For other problems you must do some detective work or get help to find the underlying problem.

• You did not find any error message.

  In this case, you'll need to look at the CIE installation logs for WebSphere Business Monitor.

Following the bread crumb trail

Many messages in the WebSphere Business Monitor main log say "Details can be found in log file," with the name and path of the log file that contains more information. Often you will find the specifics that you need to identify a problem in the referenced log file. However, sometimes that second log file has a message that points to yet another log file. Following this chain of pointers from one log file to another (bread crumb trail) will usually lead you to the critical information you are looking for.

Looking for errors in the CIE log files

As mentioned, there is a summary log file called log.txt in the same directory (<WBM_ROOT>/logs/wbm/) as the main product log that will show which installation step failed. There should also be a message at the bottom of this log that indicates the installation failed. Following are two examples.

(Jan 12, 2008 10:54:59 AM), Process, com.ibm.ws.install.wbmserver.ismp.actions.
   ISMPLogSuccessMessageAction, msg1, INSTCONFFAILED

   
(Jan 12, 2008 10:54:59 AM), Process, com.ibm.ws.install.wbmserver.ismp.actions.
   ISMPLogSuccessMessageAction, msg1, INSTPARTIALSUCCESS

Preceding this message will be one or more messages that indicate an error or configuration failure, similar to:

	   
(Jan 12, 2008 10:54:59 AM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage,
    err, Configuration failed. The configuration action that 
failed was: 60FCreatePortalDashboardProfile.

Note the configuration name 60FCreatePortalDashboardProfile at the end of the example failure message. This same name will be referenced in the detailed CIE log. In addition to the configuration failure message, there might be a stack trace from an exception that was thrown during the failure. The combination of failure messages and stack trace may give you clues about the problem. However, you'll likely need to proceed to the detailed CIE log to get more information.

The detailed log is installconfig.log, and is one directory level up in <WBM_ROOT>/logs/. This log file is in Java logging (XML) format. The raw text of this file is a little cumbersome to read if you are not used to the format. There are log viewers available on the Internet that can format and display these messages nicely for you. If you choose to call someone for help at this point it would be understandable, but read on for help uncovering more clues and gaining insight into the problem.

Searching for errors manually in installconfig.log can be a little awkward, but with some patience you can do it. Since you've already identified the name of the failed configuration step in the log.txt file, you can use this name to help you find where the error information is located. You can also search for the string "failed" or "exception" to find where a problem was detected. All messages are contained within <message> and </message> tags. An easier way is to use a Java log viewer, which can format the messages and highlight error and warning messages in different colors for you.

An example failure message is:

<message>Configuration action failed: com.ibm.ws.install.configmanager.actionengine.
ANTAction-/opt/IBM/WebSphere/MonServer/properties/version/install.wbm/config/install/
   portaldash/40S_InstallDashboardPortlets.ant</message>

An example exception message is:

<message>The translated exception message is: 
resultType=report resultName=40S_InstallDashboardPortlets</message>

followed by:

 
<message>The stack trace follows</message>

followed by a message with the contents of the stack trace.

Helpful hints

• Read the message text. Does the message identify a problem that makes sense to you?
• Does the message refer to another log file for more information?
• Look at the context of the message. Look at the surrounding messages.
• Is the error related to WebSphere Business Monitor or a prerequisite product or database setup?

And sometimes you just have to read between the lines.

Back to top

Example

In this example, there are too many open files on Linux. There is a partial success reported on a WebSphere Business Monitor Basic Install sequence with Portlet-based dashboards. First, you need to look at the main install log for WebSphere Business Monitor. You can verify the partial success by locating the following message at the bottom of the log file (wbm_<timestamp>_install_out.log).

[08/03/04 18:04:36:605 EST] Thread-1 INSTALLER I INSTCONFPARTIALSUCCESS

Next, look for other error messages in the log file that may tell you what the problem is. Starting at the top, you find the following error messages:

 [08/04/08 14:25:05:498 EDT] Runnable PORTDASH     I CWMLP0024I: Begin Portal Dashboard
 Portlet configuration: Deploy_WBIMon.xml  

[08/04/08 14:30:46:448 EDT] Runnable PORTDASH     E CWMLP2160E: An error was detected 
executing: /opt/IBM/WebSphere1/PortalServer/bin/xmlaccess.sh. The result code is: 1 

[08/04/08 14:30:46:476 EDT] Runnable PORTDASH     E CWMLP2137E: Completed 
configuration of: Deploy_WBIMon.xml with error(s). Details can be found in log file:
/opt/IBM/WebSphere1/PortalServer/wbmonitor/logs/Deploy_WBIMon.out

The first error message doesn't really give you much to go on, but the informational message that precedes it gives the idea that the failure is on a portlet-based dashboards configuration step. The second error message points to a log file that might provide some additional clues.

A log file named Deploy_WBIMon.out is in directory /opt/IBM/WebSphere1/PortalServer/wbmonitor/logs. This is a log file generated by the XMLAccess utility, which is used to install and configure portlets on WebSphere Portal. The log file contains XML formatted messages. Many of the messages weren't very helpful, until near the bottom.

<message id=EJPPH0056E">com.ibm.wps.pe.mgr.exceptions.AppServerWarInstallException: 
EJPPH0056E: The installation of portlet application
 /opt/IBM/WebSphere1/PortalServer/deployed/WBMonDashboard.war did not complete 
successfully. Please check the WebSphere Application Server log files for a possible
explanation..</message>

      
<message id="EJPPH0000E">com.ibm.wps.pe.mgr.exceptions.AppServerWarInstallException: 
EJPPH0000E: ADMA5016I: Installation of Dashboard_12kbgyxk started.

ADMA5058I: Application and module versions validated with versions of deployment targets.

ADMA5005I: The application Dashboard_12kbgyxk is configured in the WebSphere Application 
   Server repository.

ADMA5053I: The library references for the installed optional package are created.
    

ADMA5006E: An error occurred configuring Dashboard_12kbgyxk in WebSphere Application
Server repository: 
java.io.FileNotFoundException: /opt/IBM/WebSphere1/AppServer/profiles/wp_profile/wstemp
   /wp_1192f48faf2/workspace/cells/ DefaultCell/applications/Dashboard_12kbgyxk.ear/
   deployments/Dashboard_12kbgyxk/META-INF/MANIFEST.MF (Too many open files)
ADMA5011I: The cleanup of the temp directory for application Dashboard_12kbgyxk is 
   complete.

ADMA5014E: The installation of application Dashboard_12kbgyxk failed.

</message>

Notice the error message
ADMA5006E: An error occurred configuring Dashboard_12kbgyxk in WebSphere Application Server repository
shows a java.io.FileNotFoundException, and then it provides a long path to a manifest file. At the end there is a note in parentheses: "(Too many open files)." It looks like the system opened more than the maximum number of files allowed during installation. This is a known issue on Linux systems, and it is documented in the WebSphere Business Monitor Information Center. This is easily fixed by increasing the open file limit.

Back to top

Summary

In this article, you learned about the logs that can help you identify problems encountered during WebSphere Business Monitor installation. You learned what the installation logs are for, their locations for WebSphere Business Monitor and the prerequisite products, and where to start looking in the event of an installation problem. You also learned some strategies for searching for the cause of a problem.

Acknowledgments

The authors would like to thank the WebSphere Business Monitor 6.1 installation team for all of their hard work, creativity, and dedication: Nick Metianu, Paritosh Patel, Soonthorn Ativanichayaphong, Yan Li, Jerry McCobb, Aimee Silva, Miriam Celi, Xiaoming Wang and Larissa Guerrero.

We would also like to thank all of the developers of WebSphere Business Monitor for the tremendous efforts they put into delivering the product.

Resources

Learn

• Check out the other parts of this series:
  • Part 1, "What's new in WebSphere Business Monitor 6.1" (developerWorks, Dec 2007)
  • Part 2, "WebSphere Business Monitor 6.1 installation improvements" (developerWorks, Jan 2008)
  • Part 3, "Improved Unit Test Environment in IBM WebSphere Business Monitor Development Toolkit V6.1" (developerWorks, Feb 2008)
  • Part 4, "Use the Integrated Test Client to improve iterative development with WebSphere Business Monitor V6.1" (developerWorks, Mar 2008)
  • Part 5, "Managing failed and unrecoverable events In IBM WebSphere Business Monitor V6.1" (developerWorks, Apr 2008)
  • Part 6, "Combine high-level monitor models from IBM WebSphere Business Modeler with low-level monitor models from IBM WebSphere Integration Developer" (developerWorks, Apr 2008)
  • Part 7, "Creating user-defined XPath functions for IBM WebSphere Business Monitor V6.1" (developerWorks, Apr 08)
  • Part 8, "Enabling IBM WebSphere Business Monitor V6.1 to receive events from WebSphere MQ" (developerWorks, Apr 08)
  • Part 9, "Empowered authoring of monitor models with IBM WebSphere Business Monitor development toolkit for 6.1" (developerWorks, May 08)
  • Part 10, "Improved data handling with IBM WebSphere Business Monitor 6.1" (developerWorks, Jun 08)
  • Part 11, "Advanced installation of IBM WebSphere Business Monitor 6.1" (developerWorks, Jul 08)
  
  
• Browse the IBM WebSphere Business Process Management information center.
  
  
• Learn about WebSphere Business Monitor features and benefits, system requirements, library, services, news items, and more.
  
  
• WebSphere Education lists IBM WebSphere Business Monitor classes.
  
  
• The IBM AlphaBlox Library has more information about clustering AlphaBlox.
  
  
• Learn more about IBM WebSphere Application Server V6.1 and IBM WebSphere Portal V6.0.
  
  
• Visit the WebSphere zone on developerWorks for more information about business process management.
  
  
• In the Architecture area on developerWorks, get the resources you need to advance your skills in the architecture arena.
  
  
• Get an RSS feed for the series Put new capabilities of business activity monitoring (BAM) to work.
  
  
• Browse the technology bookstore for books on these and other technical topics.
  
  
• Browse the Jump-start business activity monitoring (BAM) series for a wealth of how-to information and samples.
  
  

Get products and technologies

• Download IBM product evaluation versions and get your hands on application development tools and middleware products from IBM® DB2®, Lotus®, Rational®, Tivoli®, and WebSphere®.
  
  

Discuss

• Participate in the discussion forum.
  
  
• Get involved in the developerWorks community by participating in developerWorks blogs.
  
  

About the authors

Ron is a senior software engineer who develops installation solutions for IBM WebSphere Business Monitor. Ron has been with IBM since 1984 and has developed a variety of software for laboratory and manufacturing systems, Internet applications and services, and IBM ViaVoice® and IBM WebSphere Voice Server middleware products.

Lea Leite is a staff software engineer with IBM. She joined the company in 2001 and has worked on a variety of IBM products. Lea is the Development Verification Test Lead for the WebSphere Business Monitor installation team, where she has been since April 2007.

Comments

Back to top

Trademarks  |  My developerWorks terms and conditions

Table of contents

• Introduction
• Logs, logs, and more logs
• WebSphere Business Monitor logs
• WebSphere Application Server logs
• WebSphere Portal logs
• DB2 AlphaBlox logs
• Putting it all together
• Example
• Summary
• Resources
• About the authors
• Comments

Next steps from IBM

• Try: DB2 Enterprise
• Demo: DB2 serving ATOM feed
• Webcast: A smarter way to successful SOA - Information as a trusted strategic asset
• Briefing: Information on Demand
• Buy: DB2 Enterprise

My developerWorks community