WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Recovering from profile creation or augmentation failure

The Profile Management Tool can experience failures when creating new or augmenting existing profiles. The same can occur using the manageprofiles command. If such a failure occurs, first check the log files as described in this topic, then follow the recovery instructions described, depending on the situation.

Log files

All manageprofiles log files are in install_root/logs/manageprofiles. Look at the following log files in the order given. Each log file must contain the entry "INSTCONFSUCCESS." If a file does not include this entry, a failure was detected. Look at the log files to determine why a failure was encountered and to determine a remedy.
  1. The log file profile_name_create_error.log (where profile_name is the name of the profile).
    Note: Look at this file only if you were creating a new profile, not augmenting an existing one.
    • For Linux operating systemFor UNIX operating system install_root/logs/manageprofiles/profile_name_create_error.log
    • For Windows operating system install_root\logs\wbi\update\profile_name_create_error.log
    • For i5/OS operating system install_root/logs/wbi/update/profile_name_create_error.log

    Search for the text Configuration action succeeded or Configuration action failed.

    Note: There can be multiple occurrences of Configuration action failed. Investigate and remedy each one. Also review the log files described in the following options, if the profile was created.
    Note: Additional information is available in the manageprofiles directory in the pmt.log, which logs all events that occur when a default profile is created during a complete installation using the Profile Management Tool.
  2. Log file profile_name_augment_error.log (where profile_name is the name of the profile).
    This log file is located in the following directories:
    • For Linux operating systemFor UNIX operating system install_root/logs/manageprofiles/profile_name_augment_error.log
    • For Windows operating system install_root\logs\wbi\update\profile_name_augment_error.log
    • For i5/OS operating system install_root/logs/wbi/update/profile_name_augment_error.log

    Search for the text Configuration action succeeded or Configuration action failed.

    Note: There can be multiple occurrences of Configuration action failed. Investigate and remedy each one. Also review the log files described in the following options, if the profile was created.
    Note: If you want to know the status of a profile you created during installation, run the following commands:
    • For Linux operating systemFor UNIX operating system install_root/bin/logProfileErrors.sh
    • For Windows operating system install_root\bin\logProfileErrors.bat
    • For i5/OS operating system install_root/logProfileErrors
  3. Individual profile template action log files.
    If you discovered false values in the log files described in the preceding options, review the log files in the following directories:
    • For i5/OS operating system user_data_root/profileregistry/logs on i5/OS® systems
    • For Linux operating systemFor UNIX operating system install_root/logs/manageprofiles/profile_name on Linux® and UNIX® systems
    • For Windows operating system install_root\logs\manageprofiles\profile_name on Windows® systems
    where profile_root or user_data_root is the installation location of the profile.

    These log files do not follow a consistent naming convention, but typically, each is the name of the Apache Ant script that failed followed by .log. For example, suppose the following entry is in the profile_name_augment.log file:

    <messages>Result of executing
    E:\o0536.15\profileTemplates\default.wbicore\actions\saveParamsWbiCore.ant 
    was:false</messages>

    First look at the surrounding entries in the profile_name_augment.log file in the install_root/logs/manageprofiles directory. If you cannot determine the cause of the failure from the surrounding entries, look for the corresponding log file for any failing Ant script entries. In this case, the log file created by the saveParamsWbiCore.ant script is saveParamsWbiCore.ant.log. Look at that file to investigate why the failure occurred.

Recovery for creation failure

After you determine why profile creation failed and address the cause of the failure, you can try to create the profile again.
Note: When you create a profile, it first creates a WebSphere® Application Server profile and then augments it with WebSphere ESB profile templates to create a WebSphere ESB profile. Even if you encountered a profile creation failure, a profile can exist that does not have all the needed augmentations.

To determine if the profile exists, run the install_root/bin/manageprofiles -listProfiles command. If the profile name you used for creation does not exist, you can recreate the profile. If the profile name you used for creation exists, then the profile was created and you have encountered an augmentation failure. For tips on recovering from an augmentation failure, see Recovery for augmentation failure.

Recovery for augmentation failure

After you determine why profile augmentation failed and address the cause of the failure, you can try to augment the existing profile again to successfully create a complete WebSphere ESB profile by following these steps:

  1. Start the Profile Management Tool and, instead of creating a new profile, choose to augment an existing profile.
  2. Choose the profile you were working with, and enter the correct information for it.
Note: Some of the augmentations might have completed successfully the first time you ran the Profile Management Tool. As a result, you might not see all of the panels that you saw the first time you tried to create the profile. This is because the Profile Management Tool detects which remaining augmentations must be completed and displays only the necessary panels.

topic Topic topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_recprofaug.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).