Options for turning on trace during install

If the installation is failing and the error logs do not contain sufficient information to determine the cause of the problem then you can enable additional log by using these steps

• Report the stdout and sterr logs to the console window by executing install.sh -is:javaconsole command, you can redirect output to a file


• Capture additional information to a log of your choice by executing install.sh -is:log file_name command.


• Turn on additional installation logging by executing the command install.sh -W Setup.product.install.logAllEvents="true" command

Trouble shooting errors during profile creation

The successful installation of the Network Deployment product is a two-part process:

• The first step is using the installation wizard to install a shared set of core product files.


• The second step is to create a deployment manager profile, an application server profile, or a custom profile.

If the installation failed during the creation of profile then check app_server_root/logs/manageprofiles/<profilename>_create.log for further information on what went wrong. The <profilename>_create.log file is an XML file that contains a record of the events that occur during the creation of the last profile.

In addition to the logs created within the core product files, the following logs are created in the app_server_root/logs/manageprofiles/profile_name directory.

• activity.log: Compiled activity log from various installation activities


• amjrte_config.log: Tivoli Access Manager configuration log for its Java Runtime Environment


• collect_metadata.log: Collects metadata information about managed objects in the system to evaluate and prevent potential installation conflicts


• createDefaultServer.log: A log from wsadmin recording the creation of the server1 process in the default profile


• createshortcutforprofile.log:Windows tool log for creating menu entries and shortcuts


• defaultapp_config.log:JACL script log from configuring default application resources


• defaultapp_deploy.log:Application DefaultApplication installation log


• node_name Service.log:Start and stop events for server1


• filetransfer_config.log:Application filetransfer installation log


• hamanager_config.log: Configuration log for the high availability application


• ivt_config.log:Application ivtApp installation log


• mejb_config.log: Application ManagementEJB installation log


• query_config.log: Application Query installation log


• samples_config.log: Configuration log for the PlantsByWebSphere Samples application


• samples_install.log: Installation log for the SamplesGallery and PlantsByWebSphere Samples applications


• scheduler.cal_config.log: Application SchedulerCalendars installation log


• SIBDefineChains.log: Creation log for service integration bus endpoints, inbound channels and channel chains, outbound thread pool, and outbound channel and channel chains


• SIBDeployRA.log: Deployment log for the service integration bus function


• webui_config.log: Application administrative console installation log

The no. and logs that get created might vary based on the profile that your creating. The same set of logs get created irrespective of how your creating profile, i.e. either at the time of installation, using Profile Management tool or using the manageprofile command.

Log files for error during product binary files installation

After installing WAS 6.1 check the app_server_root/logs/install/log.txt file to verify that there were no file or other ununsal error while installaing. If there were errors correct them and reinstall product. If the WAS installation was successful the last line in log.txt should be something like this


(Sep 5, 2009 10:48:42 PM), Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=0
(Sep 5, 2009 10:48:42 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS


If the status was either INSTCONFPARTIALSUCCESS or INSTCONFFAILED, then that means the installation was not successful.

If the installation was not successful then take a look at log files.

• app_server_root/logs/install/log.txt: Logs all installation events.


• app_server_root/logs/install/installconfig.log.gz: Logs the activities of ANT configuration scripts that run at the end of installation procedure. If there was error in ant script configuration you should see Configuration action failed message.


• app_server_root/logs/install/trace.log.gz: Contains trace information generated during the install. If the product was installed successfully, the last few lines should look like this
  
2009.09.05 22:48:42.012 EDT I Current install/uninstall process is successful. Process type is: install
2009.09.05 22:48:42.121 EDT I CWUPI0000I: EXITCODE=0
2009.09.05 22:48:42.122 EDT I INSTCONFSUCCESS

  


• app_server_root/logs/install/trace.xml.gz: Contains trace information generated during the installation in xml format

If the installation of the core product files fails, fix the error and reinstall the product

Important Note: If the error happens early in the installation, look for the log.txt file in the system temporary area. The installation program copies the log from the temporary area to the logs directory at the end of the installation.

During installation, a single entry in the app_server_root/logs/install/log.txt file points to the temporary log file, either %TEMP%\log.txt on Windows platforms, or /tmp/log.txt on platforms such as AIX or Linux. The installation program copies the file from the temporary directory to the app_server_root/logs/install/log.txt location at the end of the installation.

If the installation fails and the log.txt file has only this one pointer to the temporary directory, open the log.txt file in the temporary directory. The log might have clues to the installation failure.