This topic describes troubleshooting the installation and removal of the Web server plug-ins for WebSphere Application Server.
Before you begin
Why and when to perform this task
Log files for Web server plug-ins for WebSphere Application Server
Steps for this task (dependent on configuration)
If the directories are not present, or if the directories are empty, download a new installation image or discuss the product CD that you are using with someone who is knowledgeable about its creation. The IBM product discs are certified.
Reinstall using the IBM product disc.
If not, look for the temporaryPluginInstallLog.txt file in the temporary directory of the user who installed the plug-ins.
For example, the /tmp/temporaryPluginInstallLog.txt file might exist if the root user installed the plug-ins on a Linux or UNIX system.
This log is of particular interest after a silent installation. Suppose that the silent installation responsefile.txt file has incorrect entries. The installation cannot succeed. The cause of the problem is recorded in the temporaryPluginInstallLog.txt file.
If the responsefile.txt does not pass validation, the failure is logged as an INSTCONFFAILED entry. The installation does not occur. Correct the failure and run the silent installation again.
See responsefile.txt for information about editing the file properly. You might have to start with a new copy of the file that is on the product disc if you cannot get your copy to work.
<record> <date>2004-10-08T10:31:43</date> <millis>1097245903200</millis> <sequence>189</sequence> <logger>com.ibm.ws.install.configmanager.ConfigManager</logger> <level>INFO</level> <class>com.ibm.ws.install.configmanager.ConfigManager</class> <method>dumpNonFatalFailedActionsInfoToLogFile</method> <thread>10</thread> <message>This action failed to execute: C:\Plugins\properties\version\install\plugin\6.0.0.0\ config\full\install\99SGSKitInstall.ant</message> </record>
Configuration script log files and recovery procedures: The following configuration scripts run during the configuration of supported Web servers.
Log file to investigate for error | Recovery |
---|---|
configureWeb_server_type_webserver.log For example, the file might be named: configure_IHS_webserver.log Logs the Web server definition creation. |
|
Log file to investigate for error | Recovery |
---|---|
installSunOnePlugin.log Investigate the log
file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installDomino6Plugin.log Investigate the
log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installDomino5Plugin.log Investigate the
log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installIIS6Plugin.log Investigate the log
file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installIIS5Plugin.log Investigate the log
file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installApachePlugin.log Investigate the log
file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installIHSPlugin.log Investigate the log
file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installGSKit.log Investigate the log file
to determine what failed:
|
Manually install GSKit by running the installer program. The installGSKit.log file shows the installer program that runs to install GSKit. ![]() ![]()
![]()
|
Log file to investigate for error | Recovery |
---|---|
On Solaris, the installation is logged to the installGSKit.log file. Investigate
the log file to determine what failed:
|
Manually install GSKit by running the installer program. ![]()
|
Log file to investigate for error | Recovery |
---|---|
This script does not have an associated log file. The script creates the Windows registry entry for the Web server plug-ins for WebSphere Application Server. HKEY_LOCAL_MACHINE > Software > IBM > Web server Plug-ins for IBM WebSphere Application Server > 6.0.0.0 |
Add the HKEY_LOCAL_MACHINE > Software > IBM > Web
server Plug-ins for IBM WebSphere Application Server > 6.0.0.0 key manually
with the actual value of the installation location. Set the following registry
values under this key:
|
Log file to investigate for error | Recovery |
---|---|
This script does not have an associated log file. Investigate the plug-ins_install_root/bin/setupCmdLine.sh script to verify that the PLUGIN_HOME variable is set to the Web server plug-ins installation root directory. Verify that file permissions are 755 (rwxr-xr-x) on Linux and UNIX systems. |
|
If you do not find the cause of the problem, open the plug-ins_install_root/logs/Web_server_name directory. The directory is empty until the Web server loads the plug-in and errors occur. The plug-in then creates the http_plugin.log file to record the errors. If no errors occur, the directory is empty. Examine any relevant files for error entries. Correct any errors and reinstall.
See "Start the Snoop servlet" in the installation troubleshooting file.
If errors occur, look at the plug-ins_install_root/logs/Web_server_name/http_plugin.log file for causes.
Also investigate the WebSphere Application Server installation logs and the logs for your supported Web server.
On Linux and UNIX systems, copying the configureWeb_server_definition_name.sh script from one operating system, such as AIX, to another, such as HP-UX, can cause the file permissions of the script to be invalid for running the script.
Verify that file permissions are 755 (rwxr-xr-x) on Linux and UNIX systems.
If log files exist, examine them, correct the errors, and reinstall.
If not, look for the temporaryPluginUnInstallLog.txt file in the temporary directory of the user who installed the plug-ins.
For example, the /tmp/temporaryPluginUnInstallLog.txt file might exist if the root user uninstalled the plug-ins on a Linux or UNIX system.
<record> <date>2004-10-08T10:31:43</date> <millis>1097245903200</millis> <sequence>189</sequence> <logger>com.ibm.ws.install.configmanager.ConfigManager</logger> <level>INFO</level> <class>com.ibm.ws.install.configmanager.ConfigManager</class> <method>dumpNonFatalFailedActionsInfoToLogFile</method> <thread>10</thread> <message>This action failed to execute: C:\Plugins\properties\version\install\plugin\6.0.0.0\ config\full\uninstall\99SGSKitUnInstall.ant</message> </record>
Configuration script | Log file to investigate for error |
---|---|
99SBootStrapPluginsSunOneUninstalluniqueID.ant 99SBootStrapPluginsDomino6UninstalluniqueID.ant 99SBootStrapPluginsDomino5UninstalluniqueID.ant 99SBootStrapPluginsIIS6UninstalluniqueID.ant 99SBootStrapPluginsIIS5UninstalluniqueID.ant 99SBootStrapPluginsApacheUninstalluniqueID.ant 99SBootStrapPluginsIHSUninstalluniqueID.ant |
uninstallWeb_server_typePlugin.log For example, the file might be named: uninstallIHSPlugin.log Logs the Web server deconfiguration events for the Web server. |
![]() |
uninstallGSKit.log On Windows only, the Web server plugins GSKit key will be unregistered. GSKit is uninstalled if no other product is registered to use GSKit. On Linux and UNIX, it is your responsibility to uninstall GSKit when no other products are using it. |
90SDeleteWinRegPlugin.ant | This script does not have an associated log file. The script deletes the Windows registry entry for the Web server plug-ins for WebSphere Application Server. HKEY_LOCAL_MACHINE > Software > IBM > Web server Plug-ins for IBM WebSphere Application Server > 6.0.0.0 |
If the uninstall failed in any way, follow the manual uninstall steps to verify the system is clean and if necessary, remove Web server plug-in entries.
Result
This procedure results in troubleshooting the installation or removal of the Web server plug-ins for WebSphere Application Server.
What to do next
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering the information that you need to resolve a problem. Before opening a PMR, see the IBM Support page.