IBM HTTP Server 1.3.28 and WebSphere Application Server 5.1 defect description

greasyservantInternet και Εφαρμογές Web

30 Ιουλ 2012 (πριν από 5 χρόνια και 16 μέρες)

406 εμφανίσεις


Defect description/Abstract:

If IBM Http Server (IHS) and WebSphere (WAS) or WebSphere Plugin are installed on a
machine, and if you invoke iKeyMan of IHS, iKeyMan of WebSphere gets invoked
instead.

In the particular customer situation where both IBM Http

Server 1.3.28 and the
WebSphere Application Server 5.1 plugin exist on the same system, two versions of the
ikeyman utility are installed: the
JDK iKeyman for Java
-
only users

(shipped with IBM
JDK 1.4.1 in WebSphere)
and
GSKit iKeyman for GSKit users
. I
n this configuration the
IBM JDK iKeyman will be loaded, and this package does not have the option to create
the CMS database needed by IHS. Therefore, we need to replace the JDK iKeyman with
a newer version (so that CMS key databases can be handled).


Fix applies to:


The following two scenarios if you are using IHS:

1.

IKeyMan on IHS if IHS+plugin and WAS are on the same machine.

2.

IKeyMan on IHS if IHS+plugin is on a separate machine than WAS.


Apply the PQ80440 interim fix (or ifix) after installing WA
S and IHS+plugin on the
same machine; or after installing IHS+plugin on a machine. This ifix corrects the
conditions listed in the defect by
providing the latest SSL toolkit, GSKit (7a), which has
the option to create the CMS database needed by IHS. This

ifix applies to the following
operating systems:
Linux, AIX, Solaris, Windows and HP
-
UX.


Note: On UNX, you will have to be root or a user that runs WebSphere to install this iFix.
On Windows install this iFix as a user that is part of Administrative gr
oup.


Steps for installing an ifix on the base WebSphere Application Server product:


1.

Create a read/write installation directory on your system for the downloaded software,
if one does not already exist. For example create: /tmp/updateInstaller Make sure

that you have enough disk space to extract the updateInstaller.


2.

Download the update installer application tar or ZIP file to the installation directory
you created. These files contains the update installer and ifix.


3.

Extract the contents of the tar or
ZIP file to the installation directory.


On Windows platforms, the pkunzip utility might not decompress the download
image correctly. Use another utility (such as WinZip) to unzip the image.


4.

Stop each server process on the base WebSphere Application Ser
ver node with the
stopServer

command. Stop each server process on the IHS node with the
apachectl

stop

command. If any processes are not stopped by this command, do the
following: On a Windows platform, use the task manager to stop these Java processes.

On a UNIX
-
based platform, use the kill command to stop Java processes.


5.

Set up the Java environment for the update installer. (Note that if you use a non
-
standard installation root, it is possible that the update installer cannot set the
JAVA_HOME enviro
nment variable). In the following, the WAS_HOME variable is
the installation directory of WAS 5.1 (e.g., /usr/WebSphere51/AppServer) if WAS is
installed with IHS. If only IHS is installed, then WAS_HOME is the installation
directory of the IHS plugin (e.
g., /usr/IBMHTTPServer/plugin or
/user/WebSphere51/IBMHttpServerPlugin).


You can set up the Java environment by exporting or seting JAVA_HOME to
WAS_HOME/java on UNIX and Windows respectively as follow:


$ export JAVA_HOME=WAS_HOME/java ( UNIX )

C:> set

JAVA_HOME=WAS_HOME/java ( Windows )


6.

Use updateWizard.sh for Unix (updateWizard.bat for Windows) script interface to the
update installer to apply the ifix as follows:


A.

Type the command:
updateWizard.sh
. This will bring up the following panel.
Click O
K.




B.

On the Welcome panel, click Next.





C.

On the WebSphere Application Server panel, go to Browse and locate the
WebSphere installation directory or type it in the bar. Note: If both WAS 5.1 and
IHS+plugin are installed on a machine, the installation

directory would be
something like /usr/WebSphere51/AppServer. If only IHS+plugin is installed on
a machine, then the installation directory would be something like
/usr/IBMHTTPServer/plugin.


Then Click Next.





D.

On the install/uninstall panel, click
the Install fixes radio button. Click Next.





E.

On the Specify directory where fixes are located, type the location where the ifix
is located (the directory where you have placed the UpdateInstaller software).



F.

On this panel, click on the ifix (PQ80440
) that appears. Click Next. This will
begin the installation of this ifix.





G.

This next panel will verify the previously selected ifix. Click Next to begin the
installation of the ifix.





H.

After the ifix has installed, this next panel will display t
he installation results.
Make sure that it displays that the ifix (PQ80440) has been successfully installed.
Click Finish to exit the wizard.





Note:

The updateWizard.sh script may be used to both install and uninstall ifixes.


To uninstall an ifi
x, the steps are basically the same, but the final message will
indicate that the ifix has been uninstalled.


7.

If this is an IHS node, restart IHS:


apachectl start



8.

Restart the node agent for the base node with the startNode command if this a
WebSphere no
de and is part of a cell.



startnode



9.

Restart each server on the node with the startServer command if this is a WebSphere
node.


startserver server1