The Profile Wizard 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 here, then follow the recovery instructions below depending on the situation.
This log file is located in the directory install_root/logs/wasprofile on Linux and UNIX systems and install_root\logs\wasprofile on Windows systems (where install_root is the WebSphere Process Server installation root location). Search for the text "Result of executing" and verify that each occurrence ends with "true." Each true or false value results from the execution of a profile template configuration action .ant script. For example:
<message>Result of executing E:\o0536.15\profileTemplates\default\actions\first was: true</messages>
A value of false in this file can indicate the source of the failure.
This log file is located in the directory install_root/logs/wasprofile on Linux and UNIX systems and install_root\logs\wasprofile on Windows systems (where install_root is the WebSphere Process Server installation root location). Search for the text "Result of executing" and verify that each occurrence ends with "true." Each true or false value results from the execution of a profile template configuration action .ant script. For example:
<messages>Result of executing E:\o0536.15\profileTemplates\default.wbicore\actions\saveParamsWbiCore.ant was:true</messages>
A value of false in this file can indicate the source of the failure. Also review the log files described in the following option.
If you discovered false values in the log files described in the preceding options, review the log files in the directory profile_root/logs on Linux and UNIX systems and profile_root\logs on Windows systems (where profile_root is the installation location of the profile). These log files do not follow a consistent naming convention, but typically, it is the name of the .ant script that failed followed by .log. For example, if the following entry is in the wasprofile_augment_profile_name.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 wasprofile_augment_profile_name.log file. 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.
To determine if the profile exists, run the install root/bin/wasprofile.sh -listProfiles command on Linux and UNIX systems or the install_root\bin\wasprofile.bat -listProfiles command on Windows systems (where install_root is the WebSphere Process Server installation root location). 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 the following section.
In the event the profile was created but augmentations
failed when using the manageprofiles command, it is
recommended that you finish the remaining augmentations with the Profile Wizard.
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 Process Server profile by following the steps below.
Last updated: Thu Apr 27 15:20:08 2006
(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)