|
Problem(Abstract) |
You can have multiple instances of the IBM® WebSphere®
Application Server installed on your machine. If you need to manually
uninstall a particular instance, it might not be immediately obvious which
of the various unique package instances is associated with the individual
Application Server instance you want to uninstall. |
|
|
|
Cause |
With multiple instances of WebSphere Application Server
installed on a Solaris machine, all of the packages installed as part of
the Application Server will have unique package names. |
|
|
Resolving the
problem |
On Solaris, you can use the following command to generate
a list of installed packages. This list includes information about the
base directory with which each package is associated.
Use your favorite editor (for example: VI) to open this file. Locate the
package name associated with the Application Server. For example:
ISWSBJD9A
On this particular machine, you will see the following:
-------------------------------------------------------------------
PKGINST: ISWSBJD9A
NAME: javaCommonConfigComponent
CATEGORY: application
ARCH: sparc
VERSION: 1.3..1.DSP=
BASEDIR: /opt/WebSphere51/AppServer
VENDOR:
STATUS: completely installed
PKGINST: ISWSBJD9A.2
NAME: javaCommonConfigComponent
CATEGORY: application
ARCH: sparc
VERSION: 1.3..1.DSP=
BASEDIR: /opt/WebSphere/DeploymentManager
VENDOR:
STATUS: completely installed
PKGINST: ISWSBJD9A.3
NAME: javaCommonConfigComponent
CATEGORY: application
ARCH: sparc
VERSION: 1.3..1.DSP=
BASEDIR: /opt/JccSphere/AppServer
VENDOR:
STATUS: completely installed
------------------------------------------------------------------- |
Use the BASEDIR value to determine which of these package
instances (for example: PKGINST values) need to be removed. All of the
package instances will have the same BASEDIR value. Locate and remove
these packages.
Question:
Is the PKGINST code for WebSphere Application Server always
ISWSBJD9A?
Answer:
Do not assume that this will always be the case. It is quite reasonable
to presume that different versions of the product might very well change
the package instance name. This is why you should use the value of
BASEDIR to determine all of the unique package names to be
removed. |
|
|
|