IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting installation and configuration

Recovering from profile creation or augmentation failure

The Profile Management Tool can experience failures when creating new or when augmenting existing profiles. The same can occur using manageprofiles.sh.

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).

    Look at this file only if you were creating a new profile, not augmenting an existing one.

    • INSTALL_ROOT/logs/manageprofiles/ profile_name_create_error.log

    • INSTALL_ROOT\logs\wbi\update\ profile_name_create_error.log

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

    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.

    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 PMT.

  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:

    • INSTALL_ROOT/logs/manageprofiles/ profile_name_augment_error.log

    • INSTALL_ROOT\logs\wbi\update\ profile_name_augment_error.log

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

    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.

    If you want to know the status of a profile you created during installations:

    • INSTALL_ROOT/bin/logProfileErrors.sh

    • INSTALL_ROOT\bin\logProfileErrors.bat

  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:

    • INSTALL_ROOT/logs/manageprofiles/ profile_name on Linux and UNIX systems

    • 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 have addressed the cause of the failure, you can try to create the profile again.

When you create a profile, it first creates a WebSphere Application Server profile and then augments it with IBM BPM profile templates to create the IBM BPM 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

For recovery from a profile augmentation failure follow the steps below:

: Troubleshooting installation and configuration