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 in this topic,
then follow the recovery instructions described, depending on the situation.
Log files
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.
- The log file created by the Profile wizard.
Note: If you used the manageprofiles command
and experienced failure, do not look for this file.
The name of the
file is partially based on a timestamp and is in the form
pcatLogNNNNNNNNNNNNN.txt,
where
NNNNNNNNNNNNN is a number. This file can be found
in the directory
profile_root/logs on Linux and UNIX systems
and
profile_root\logs on Microsoft Windows systems (where
profile_root
is the installation location of the profile). If you cannot determine the
cause of the failure, review the log files described in the following options.
Note: If
you ran the Profile wizard multiple times for a profile, more than one of
these files might exist. Always refer to the newest file.
- The log file wasprofile_create_profile_name.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.
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.
Note: There can be multiple occurrences of "false".
Investigate and remedy each one. Also review the log files described in the
following options, if the profile was created.
- Log file wasprofile_augment_profile_name.log (where profile_name is
the name of the profile).
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.
Note: There can be multiple occurrences
of "false". Investigate and remedy each one.
- 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 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, each is the name of the .ant script
that failed followed by .log. For example, suppose 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.
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 Process Server profile
templates to create a WebSphere Process Server profile.
Even if you encountered a profile creation failure, a profile can exist that
does not have all the needed augmentations (presumably because of the failure).
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 Recovery for augmentation failure.
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.
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 Process Server profile
by following these steps:
- Start the Profile wizard and, instead of creating a new profile, choose
to augment an existing profile.
- 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 wizard. 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 wizard detects which remaining augmentations must
be completed and displays only the necessary panels.
Attention: If
you choose to manually delete the profile before trying again, you must remove
all augmentations from the profile before deleting it, or problems might occur.
This includes both augmentations to the original WebSphere Application Server
or WebSphere Application Server Network Deployment profile that were made
by the
WebSphere Process Server Profile
wizard to augment it into a
WebSphere Process Server profile,
and augmentations that were made by other profile templates. Refer to
Deleting augmentations for more information.
Deleting augmentations
To remove augmentations
from a
WebSphere Process Server profile
that were made originally by the
WebSphere Process Server Profile
wizard, follow these steps:
- Verify that no servers are running for the profile.
- Find the entry for the profile in the file install_root/properties/profileRegistry.xml (on
Linux and UNIX platforms) or install_root\properties\profileRegistry.xml (on
Windows platforms) and determine how many WebSphere Process Server augmentations
it has.
- Unaugment each WebSphere Process Server augmentation
for the profile using the wasprofile -unaugment command.
- Each call removes the last template augmented to the profile. Verify
that each unaugmentation command you ran completed successfully.
- Delete the profile using the wasprofile -delete command.
Note: Do not change the contents of the profileRegistry.xml file in any
way other than through using the wasprofile command.
For removing
augmentations caused by profile templates for products other than
WebSphere Process Server, refer to
documentation for those other products to ensure you are unaugmenting the
templates properly.
For more information about manually deleting augmentations,
refer to IBM Technical Note 1218704, "Remove augmentations before
manually deleting a profile using command line utility wasprofile."
Last updated: Tue 31 Oct 2006 09:53:28
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)