- Are you reinstalling with an INSTCONFSUCCESS message but no
files are being installed?
If you do not use the Web server
Plug-ins uninstaller program to uninstall the plug-ins, a reinstall can fail
with an INSTCONFSUCCESS message.
The Web server Plug-ins installer
is an Install Shield for Multiplatforms (ISMP) wizard. The wizard uses the vpd.properties file
or the operating system registry to determine if the plug-ins are installed.
If you do not use the uninstaller program for the plug-ins, neither the vpd.properties file
nor the operating system registry is updated properly. You might see a plugins_root /logs/install/log.txt with
content similar to the following example:
Plugin.Install, com.installshield.product.service.product.
PureJavaProductServiceImpl$InstallProduct, msg1,
Did not replace installed object (IBM WebSphere Application
Server - Plugins) with object (IBM WebSphere Application
Server - Plugins)
Plugin.Install, ... msg1, Did not replace installed object
(WebServer Plugin Binaries and Configurations) with
object (WebServer Plugin Binaries and Configurations)
Plugin.Install... Did not replace installed object (GSKit) with object (GSKit)
Plugin.Install... Did not replace installed object (LAP Component) with
object (LAP Component)
Plugin.Install...Did not replace installed object (WebServer Plugin
Binaries) with object (WebServer Plugin Binaries)
Plugin.Install... Did not replace installed object (Additional Bytes
for non-HP) with object (Additional Bytes for non-HP)
Plugin.Install... Did not replace installed object (GSKit) with object (GSKit)
Plugin.Install... Did not replace installed object (Standalone JDK)
with object (Standalone JDK)
Use the uninstaller program in the plugins_root/uninstPlugin directory to uninstall the Web server Plug-ins. For example, do not delete
the plugins_root directory
to uninstall the plug-ins without running the installer program first.
If
you have this problem, follow the uninstall procedure and the manual uninstall
procedure to clean up your system before reinstalling the Web server Plug-ins.
See Uninstalling the Web server plug-ins for WebSphere Application Server for more information.
- Does the installation image have the proper directories?
The following directories are present on the installation image of
the full product. The directories in bold are required for a successful installation
of the plug-ins:
- parent_directory/WAS
- parent_directory/IHS
- parent_directory/plugin
- parent_directory/AppClient
- parent_directory/JDK
- parent_directory/GSKit
Remember: The parent_directory variable
is the directory where you can unpack the images. All of the directories in
the list must have the same parent directory.
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.
Symptoms that can occur when the JDK directory
is missing or is not used: If the
plugins_root/logs/install/log.txt log file records the following errors, the installer program did not use
the correct Java 2 SDK, which is in the
JDK directory
on the installation image:
Plugin.Install, com.ibm.ws.install.ni.ismp.actions.
ISMPComponentizedFileRepositoryDeployAction, msg1,
Processing component: prereq.jdk
Plugin.Install, com.ibm.ws.install.ni.ismp.actions.
ISMPComponentizedFileRepositoryDeployAction, err,
Component not found: prereq.jdk
Plugin.Install, com.ibm.ws.install.ni.ismp.actions.
ISMPComponentizedFileRepositoryDeployAction, err,
ComponentNotFoundException.message
The installation
program can pick up another Java 2 SDK 1.4 on the system when running from
the command prompt in terminal window that already has set the Java 2 SDK
for the environment. Another way to point the installation program to a particular
SDK is with the -is:javahome option for the Install Shield for Multiplatforms
(ISMP) wizard.
In either case, the JDK directory
on the installation image is not being used. When the installation attempts
to install the prereq.jdk component, the wizard cannot
find the JDK directory and throws the error in the plugins_root/logs/install/log.txt file.
Verify
the cause of the error by examining the CURRENT_WORKING_DIRECTORY value and
the JAVA_INSTALL_PATH value in the log.txt file. The
working directory value is typically the CD_root/plugin
directory. An erroneous Java path might be non_CD_root/java/jre.
The correct Java path is the CD_root/JDK/repository/prereq.jdk/java/jre directory.
In such a case:
- Verify that the JDK directory is on the product disc.
- Close the current command window.
- Open a new command window.
- Change directories to the plugin directory on the
product disc.
- Restart the installation: ./install
Symptoms that occur when the GSKit directory is missing: If
the JDK directory is present, but the GSKit directory
is not present, the installation is only partially successful, as shown in
the logs by the INSTCONFPARTIALSUCCESS indicator.
The plugins_root/logs/install/masterConfigurationLog.txt log file shows that the 99SGSKitInstall.ant script
failed to run. Complete the full installation by manually installing GSKit.
The plugins_root/logs/install/installGSKit.log file
shows the command to use for the manual installation in the GSKIT 7 entry.
- Is there any sign that the installation occurred?
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 system such as AIX
or Linux.
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.
- Does a local installation attempt result
in an INSTCONFPARTIALSUCCESS status, reporting a 98SConfigureWebserverDefinition failure
in log.txt?
The plugin installation log file shows a code of
INSTCONFPARTIALSUCCESS, and the following error message is found in
plugins_root/logs/install/log.txt.
This message states that the installation process was successful, but one
of the configuration scripts responsible for configuring the plug-ins failed
to complete. In this case, the name of the script which failed to complete
is 98SConfigureWebserverDefinition.
Config action failed: 98SConfigureWebserverDefinition -
install_root\properties\version\nif\config\install\
98SConfigureWebserverDefinition.ant
Current install/uninstall process is successful. Process type is: install
This
issue occurs under the following conditions:
- WebSphere Application Server is installed on the same system on which
the plugin is being installed.
- The plug-ins are being installed in local configuration mode.
- The existing application server profile, specified in the installation
options for the plug-ins, is installed to a location outside of the application
server. In other words, the specified profile is not in the default profile
location in app_server_root/profiles/profile_name.
This might occur in IBM products which extend the application server as part
of their installation, like WebSphere Portal Server for example.
Although the plug-ins installation is intact, the existing application
server is not automatically configured to use the new plug-ins. There are
two options to resolve the problem:
- Uninstall and reinstall the plug-ins in remote mode, then manually invoke
the configuration script. Even though the application server is on the same
machine as the plug-ins, you can still run the installation in remote mode.
Read the remote configuration topic,Configuring a Web server and an application server on separate machines (remote) ,
for more information.
- Keep the existing plug-ins, and manually invoke the configuration script
as indicated on step 20 and afterwards in the remote configuration topic.
- Does the installation result in an INSTCONFPARTIALSUCCESS status?
- Look for errors in the plugins_root/logs/install/log.txt file.
- Look for an entry in the log.txt file that shows
the location of the masterConfigurationLog.txt file.
- Open the masterConfigurationLog.txt file.
- Starting at the end of the file, scan towards the beginning of the file
looking for configuration scripts that could not run.
For example, the
following stanza shows a configuration script that could not run:
<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>
- A configuration script that fails to run is likely the cause of a partially
successful installation status. To debug the example, look at the installGSKit.log,
which is the log file for GSKit. Look for signs of a failed installation to
determine if you can correct the problem.
Configuration script log files and recovery procedures: The
following configuration scripts run during the configuration of supported
Web servers.
Configuration script: 98SConfigureWebserverDefinition.ant
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.
|
- If the Web server definition partially exists, delete the Web server definition.
- Run the Web server definition script manually. The Web server definition
is referenced in the script. The script is in the plugins_root/bin directory,
with a name similar to the following convention:
configureWeb_server_definition_name.sh
configureWeb_server_definition_name.bat
|
Configuration script: 99SBootStrapPluginsSunOne.ant
Log file to investigate for error |
Recovery |
installSunOnePlugin.logInvestigate
the log file to determine what failed:
- If the error is due to plugin-cfg.xml not existing,
investigate why this file is not present.
- If the error is due to the Web server definition creation failing, address
this as discussed under the 98SConfigureWebserverDefinition.ant description.
- If the Web server configuration files do not update, investigate the files
to verify that they exist and that the file permissions are correct.
|
- You can manually configure the Web server by following
the procedure documented in Configuring the Sun Java System Web Server.
- You can rerun the Plug-ins installation wizard. Select the existing plug-ins
installation root directory. Doing so results in the Web server being configured
to use the existing binaries.
|
Configuration script: 99SBootStrapPluginsDomino6.ant
Log file to investigate for error |
Recovery |
installDomino6Plugin.logInvestigate
the log file to determine what failed:
- If the error is due to plugin-cfg.xml not existing,
investigate why this file is not present.
- If the error is due to the Web server definition creation failing, address
this as discussed under the 98SConfigureWebserverDefinition.ant description.
- If the Web server configuration files do not update, investigate the files
to verify that they exist and that the file permissions are correct.
|
- You can manually configure the Web server by following
the procedure documented in Configuring Lotus Domino.
- You can rerun the Plug-ins installation wizard. Select the existing plug-ins
installation root directory. Doing so results in the Web server being configured
to use the existing binaries.
|
Configuration script: 99SBootStrapPluginsDomino5.ant
Log file to investigate for error |
Recovery |
installDomino5Plugin.logInvestigate
the log file to determine what failed:
- If the error is due to plugin-cfg.xml not existing,
investigate why this file is not present.
- If the error is due to the Web server definition creation failing, address
this as discussed under the 98SConfigureWebserverDefinition.ant description.
- If the Web server configuration files do not update, investigate the files
to verify that they exist and that the file permissions are correct.
|
- You can manually configure the Web server by following
the procedure documented in Configuring Lotus Domino.
- You can rerun the Plug-ins installation wizard. Select the existing plug-ins
installation root directory. Doing so results in the Web server being configured
to use the existing binaries.
|
Configuration script: 99SBootStrapPluginsIIS6.ant
Log file to investigate for error |
Recovery |
installIIS6Plugin.logInvestigate
the log file to determine what failed:
- If the error is due to plugin-cfg.xml not existing,
investigate why this file is not present.
- If the error is due to the Web server definition creation failing, address
this as discussed under the 98SConfigureWebserverDefinition.ant description.
- Start the Internet Information Services (IIS) application and investigate
the IIS configuration.
|
- You can manually configure the Web server by following
the procedure documented in Configuring Microsoft Internet Information Services (IIS).
- You can rerun the Plug-ins installation wizard. Select the existing plug-ins
installation root directory. Doing so results in the Web server being configured
to use the existing binaries.
|
Configuration script: 99SBootStrapPluginsIIS5.ant
Log file to investigate for error |
Recovery |
installIIS5Plugin.logInvestigate
the log file to determine what failed:
- If the error is due to plugin-cfg.xml not existing,
investigate why this file is not present.
- If the error is due to the Web server definition creation failing, address
this as discussed under the 98SConfigureWebserverDefinition.ant description.
- Start the IIS application and investigate the IIS configuration.
|
- You can manually configure the Web server by following
the procedure that is documented in Configuring Microsoft Internet Information Services (IIS).
- You can rerun the Plug-ins installation wizard. Select the existing plug-ins
installation root directory. Doing so results in the Web server being configured
to use the existing binaries.
|
Configuration script: 99SBootStrapPluginsApache.ant
Log file to investigate for error |
Recovery |
installApachePlugin.logInvestigate
the log file to determine what failed:
- If the error is due to plugin-cfg.xml not existing,
investigate why this file is not present.
- If the error is due to the Web server definition creation failing, address
this as discussed under the 98SConfigureWebserverDefinition.ant description.
- If the Web server configuration files do not update, investigate the files
to verify that they exist and that the file permissions are correct.
|
- You can manually configure the Web server by following
the procedure documented in Configuring Apache HTTP Server Version 2.0.
- You can rerun the Plug-ins installation wizard. Select the existing plug-ins
installation root directory. Doing so results in the Web server being configured
to use the existing binaries.
|
Configuration script: 99SBootStrapPluginsIHS.ant
Log file to investigate for error |
Recovery |
installIHSPlugin.log Investigate
the log file to determine what failed:
- If the error is due to plugin-cfg.xml not existing,
investigate why this file is not present.
- If the error is due to the Web server definition creation failing, address
this as discussed under the 98SConfigureWebserverDefinition.ant description.
- If the Web server configuration files do not update, investigate the files
to verify that they exist and that the file permissions are correct.
|
- You can manually configure the Web server by following
the procedure documented in Configuring IBM HTTP Server Version 6.x.
- You can rerun the Plug-ins installation wizard. Select the existing plug-ins
installation root directory. Doing so results in the Web server being configured
to use the existing binaries.
|
Configuration script: 99SGSKitInstall.ant
Log file to investigate for error |
Recovery |
installGSKit.logInvestigate
the log file to determine what failed:
- In cases where the CD layout is not correct, then the gskit installer
program cannot be found. GSKit fails to install.
- In cases where GSKit is already installed, the installation might incorrectly
report a failure. If the logs show that an installation already existed, you
can safely ignore the error.
|
Manually install GSKit by running the installer
program. The installGSKit.log file shows the installer
program that runs to install GSKit.
![[Windows]](../../windows.gif) Run the following command from the "E:\GSKit\ directory,
assuming the E drive is the CD-ROM drive:
- "E:\GSKit\Setup.exe" WASPLUGIN60_041008085014 "C:\Program Files" -s -z
-f1"E:\GSKit\setup.iss"
|
Configuration script: 99SSolarisGSKitInstall4.ant
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:
- In cases where the CD layout is not correct, then the gskit installer
program cannot be found. GSKit fails to install.
- In cases where GSKit is already installed, the installation might incorrectly
report a failure. If the logs show that an installation already existed, you
can safely ignore the error.
|
Manually install GSKit by running the installer
program.
![[Solaris]](../../solaris.gif) Run the following command from the /cdrom/GSKit directory:
|
Configuration script: 90SCreateWinRegPlugin.ant
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:
|
Configuration script: 99SModifySetupCmdLine.ant
Log file to investigate for error |
Recovery |
This script does not have an associated log file.
Investigate
the plugins_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 systems such as AIX or Linux.
|
|
If you do not find the cause of the problem, open the plugins_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.
- Does the installation result in a INSTCONFFAILED status?
- This is a serious failure of the installation.
- Analyze the log files to determine the problem.
- Uninstall the plug-ins.
- Delete the plug-ins installation root directory.
- Install the plug-ins again.
- Do errors occur when you start the snoop application?
See "Start
the Snoop servlet" in the installation troubleshooting file.
If
errors occur, look at the plugins_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.
Do you have the correct file
permissions for the configureWeb_server_definition_name script?
On operating systems such as AIX or Linux, 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 systems such as AIX or Linux.
Are you using the configureWeb_server_definition_name script
when the Web server machine is running dynamic host configuration protocol
(DHCP)? The configureweb_server_name.sh script
can contain null values for the name of the host machine of the Web server
when using DHCP. Examine the script to see if the last few parameters include
the word null. If so, you have this problem.
The plugins.install log
file might also have an entry for the problem:
(MMM DD, YYYY HH:MM:SS AM|PM),
Plugin.Install,
com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction,
msg1, WEB_SERVER_HOSTNAME : null
If the Network Deployment product cannot resolve the host name
of the server, problems can occur with such situations as adding or administering
nodes, or the node agent contacting the application server. To resolve the
host name, the product opens a port, or queries for an IP address. The product
then waits for the operating system to return the correct information. The
operating system might go to multiple places to find the IP address, but the
product does not care about the order in which the operating system does
this, if the correct information is returned. If the host name of the server
cannot be resolved, refer to your network administration documentation to
resolve the problem. The following additional information might help you ensure
that the host name is resolved.
Perform the following steps to successfully create the configuration
script for creating and configuring the Web server definition in the application
server node:
- Uninstall the Web server plug-ins.
- Perform the suggested edits based on your operating system.
- Install the Web server plug-ins again.