On Linux and UNIX platforms: install_root/logs/wbi/log.txt
On Windows platforms: install_root \logs\wbi\log.txt
|
Logs all installation events relating
to WebSphere Process Server. |
- INSTCONFFAILED
- Total installation failure.
- INSTCONFSUCCESS
- Successful installation.
- INSTCONFPARTIALSUCCESS
- Installation errors occurred but the installation is still usable. Additional
information in other log files identifies the errors.
|
On Linux and UNIX platforms: install_root /logs/wbi/instconfig.log
On Windows platforms: install_root\logs\wbi
\instconfig.log
|
Logs configuration actions that run
at the end of the installation process to configure components, install system
applications, and create Windows shortcuts and registry entries. |
Contains a series of <record> elements
that document the configuration actions. If a post-installation configuration
action fails, text like the following appears in the log: <record>
<date>2005-05-26T11:41:17</date>
<millis>1117132877344</millis>
<sequence>742</sequence>
<logger>com.ibm.ws.install.configmanager.
ConfigManager</logger>
<level>WARNING</level>
<class>com.ibm.ws.install.configmanager
.ConfigManager</class>
<method>executeAllActionsFound</method>
<thread>12</thread>
<message>Configuration action failed: com.
ibm.ws.install.configmanager.actionengine.
ANTAction-D:\WBI\AS\properties\version
\install.wbi\6.0.0.0\config\
full\install\90SInstallCEI.ant</message>
</record>
If no actions fail, the following message is the last log entry:<record>
. . .
<message>No errors were encountered while
executing the repository actions</message>
</record>
|
On Linux and UNIX platforms: profile_root/logs
/pcatLog<timestamp>.txt
On Windows platforms: profile_root\logs
\pcatLog<timestamp>.txt
Important: If this file does not exist in this directory
on your system, profile creation failed early in the process. In this case,
review the pcatLog.txt file in the user_home directory,
where user_home represents the directory /root on Linux and
UNIX platforms or C:\Documents and Settings\Administrator on Windows
platforms.
Important:  Draft comment: Text
to cover defect 281508.
When you create the first profile for
an installation and no WebSphere Application Server, WebSphere Application
Server Network Deployment, or WebSphere Process Server profile
exists, warning messages are generated in this log file about a missing profileRegistry.xml file.
The profileRegistry.xml file exists only after the first
profile has been created. These warning messages are normal and can be ignored. 
|
Logs all events that occur when a default
profile is created during a Complete installation, when the Profile Wizard
is run, or when the wasprofile command is used.
|
- INSTCONFFAILED
- Total profile creation failure.
- INSTCONFSUCCESS
- Successful profile creation.
- INSTCONFPARTIALSUCCESS
- Profile creation errors occurred but the profile is still functional.
Additional information in other log files identifies the errors.
|
On Linux and UNIX platforms: install_root/logs/wasprofile
/wasprofile_create_ profile_name.log
On Windows platforms: install_root\logs
\wasprofile \wasprofile_create_ profile_name.log
|
- Traces all events that occur during the creation of the named profile.
- Created during a Complete installation, when using the Profile Wizard,
or when using the wasprofile command.
|
- INSTCONFFAILED
- Total profile creation failure.
- INSTCONFSUCCESS
- Successful profile creation.
- INSTCONFPARTIALSUCCESS
- Profile creation errors occurred but the profile is still functional.
Additional information in other log files identifies the errors.
|
Important: This file name might also appear as wasprofile_augment_ profile_name_<timestamp>.log
|
- Traces all events that occur during the augmentation of the named profile.
- Created during a Complete installation, when using the Profile Wizard,
or when using the wasprofile command.
|
- INSTCONFFAILED
- Total profile augmentation failure.
- INSTCONFSUCCESS
- Successful profile augmentation.
- INSTCONFPARTIALSUCCESS
- Profile augmentation errors occurred but the profile is still functional.
Additional information in other log files identifies the errors.
|
|
- Traces all events that occur during the unaugmentation of the named profile.
- Created when:
- Using the uninstaller to uninstall WebSphere Process Server. The uninstaller
unaugments all WebSphere Process Server profiles. Each profile unaugmented
will have one of these log files created.
- Manually unaugmenting a profile (for example, when manually deleting a
profile).
|
- INSTCONFFAILED
- A failure has occurred, but the augmentation is still considered removed
from the profile (the template is no longer considered to be augmented to
the profile).
- INSTCONFSUCCESS
- Successful profile unaugmentation (the template is no longer considered
to be augmented to the profile).
- INSTCONFPARTIALSUCCESS
- Profile unaugmentation errors occurred but the profile is still unaugmented
(the template is no longer considered to be augmented to the profile).
|
|
|
|
 On Linux and UNIX platforms: install_root/logs/wasprofile
/manageProfiles-create- profile_name.log
On Windows platforms: install_root\logs
\wasprofile \manageProfiles-create- profile_name.log
|
- Traces all events that occur during the creation of the named profile.
- Created when using the manageprofiles command.
|
Provides output similar to the following: Prereq base template found in file:
e:\o0540.17_mod1\profileTemplates\
default.wbiserver\
prereqMetadata.xml
Creating the prereq base profile : default
Return code : 0
Adding prereq default.wbicore to prereq list
Adding prereq default.bfm to prereq list
Adding prereq default.wbicore to prereq list
Augmenting default with the prereq profile
template: default.wbicore
Return code : 0
Augmenting default with the prereq profile
template: default.bfm
Return code : 0
Augmenting with the user specified template:
e:\o0540.17_mod1/profileTemplates/
default.wbiserver
Return code : 0
Profile actions completed
|
|
- Traces all events that occur during the augmentation of the named profile.
- Created when using the manageprofiles command.
|
Provides output similar to the following: Adding prereq managed.wbicore to prereq list
Adding prereq managed.bfm to prereq list
Adding prereq managed.wbicore to prereq list
Template 'managed.wbicore' is an existing
applied augment for profile : Custom01
Template 'managed.bfm' is an existing
applied augment for profile : Custom01
Augmenting with the user specified
template:
E:\o0540.17_mod1/profileTemplates/
managed.wbiserver
Return code : 0
Profile actions completed
|
|
- Traces all events that occur during the unaugmentation of the named profile.
- Created when using the manageprofiles command.
|
Draft comment: We'll need to get content for this in March.
|
On Linux and UNIX platforms: install_root/logs/wasprofile
/wasprofile_delete_ profile_name.log
On Windows platforms: install_root\logs\wasprofile
\wasprofile_delete_ profile_name.log
|
- Traces all events that occur during the deletion of the named profile.
- Created when profile deletion is performed with the wasprofile command.
|
- INSTCONFFAILED
- Total profile deletion failure.
- INSTCONFSUCCESS
- Successful profile deletion.
- INSTCONFPARTIALSUCCESS
- Profile deletion errors occurred but the profile is still deleted. Additional
information in other log files identifies the errors.
|
 On Linux and UNIX platforms: install_root/logs/wasprofile
/manageProfiles-delete- profile_name.log
On Windows platforms: install_root\logs\wasprofile
\manageProfiles-delete- profile_name.log
|
- Traces all events that occur during the deletion of the named profile.
- Created when profile deletion is performed with the manageprofiles command.
|
Draft comment: We'll need to get content for this in March.
|
On Linux and UNIX platforms: install_root/logs
/wasprofile.log
On Windows platforms: install_root\logs
\wasprofile.log
|
- Traces all events that occur during the deletion of profiles.
- Created during uninstallation if you choose to uninstall the underlying
WebSphere Application Server Network Deployment.
|
- INSTCONFFAILED
- Total profile deletion failure.
- INSTCONFSUCCESS
- Successful profile deletion.
- INSTCONFPARTIALSUCCESS
- Profile deletion errors occurred but the profile is still deleted. Additional
information in other log files identifies the errors.
|
On Linux and UNIX platforms: install_root/logs/log.txt
On Windows platforms: install_root\logs\log.txt
|
- Logs all installation events relating to WebSphere Application Server
Network Deployment.
- Created when WebSphere Application Server Network Deployment is silently
installed.
|
- INSTCONFFAILED
- Total installation failure.
- INSTCONFSUCCESS
- Successful installation.
- INSTCONFPARTIALSUCCESS
- Installation errors occurred but the installation is still usable. Additional
information in other log files identifies the errors.
|
On Linux and UNIX platforms: install_root /logs/instconfig.log
On Windows platforms: install_root \logs\instconfig.log
|
- Logs configuration actions that run at the end of the installation process
to configure components, install system applications, and create Windows shortcuts
and registry entries.
- Created when WebSphere Application Server Network Deployment is silently
installed.
|
Contains a series of <record> elements that
document the configuration actions. |
On Linux and UNIX platforms: install_root /logs/wbi/uninstlog.txt
On Windows platforms: install_root \logs\wbi\uninstlog.txt
|
Logs all uninstallation events relating
to WebSphere Process Server. |
- INSTCONFFAILED
- Total uninstallation failure.
- INSTCONFSUCCESS
- Successful uninstallation.
- INSTCONFPARTIALSUCCESS
- The Uninstallation Wizard successfully removed the core product files,
but errors occurred during configuration. Additional information in other
log files identifies the errors.
|
On Linux and UNIX platforms: install_root /logs/wbi/uninstconfig.log
On Windows platforms: install_root \logs\wbi\uninstconfig.log
|
Logs configuration actions that run at the
end of the uninstallation process. |
Contains a series of <record> elements that
document the configuration actions. |