Run the Feature Pack for Web Services installation program
to silently install the feature pack on an existing installation of
a WebSphere Application Server Version
6.1 product.
Before you begin
The WebSphere Application Server Version 6.1 Feature Pack
for Web Services extends the capabilities of WebSphere Application
Server Version 6.1 to enable Web services messages to be sent asynchronously,
reliably, and securely, focusing on interoperability with other vendors
and to provide support for the Java API for XML Web Services (JAX-WS)
2.0 programming model.
Before starting this installation, do the
following:
- Read Planning to install the Feature Pack for Web Services.
- Install a Version 6.1 WebSphere Application Server product if you
have not done so already.
- Download and extract the Feature Pack for Web Services.
For
example, create two directories, wssrv_download and wsssrv_installation_image.
Then, download the feature pack to the wssrv_download directory
and then extract the downloaded file to the wsssrv_installation_image directory.
Do not move any files out of the wsssrv_installation_image directory.
- The operating system requirements for a feature pack are the same
as for a Version 6.1 application server installation. However, you
need to ensure that you have enough free disk space to install the
feature pack and the included maintenance onto the application server
installation.
- 1450 MB of free space available in your target installation directory
for the feature pack and included maintenance. This is in addition
to the required Version 6.1 application server product.
- 600 MB of free space available in your temporary directory
Avoid trouble: If you are planning to install multiple
feature packs on the application server product, then there might
be other steps to consider based on your topology. See
Installing and configuring multiple feature packs for more information.
gotcha
About this task
This topic describes how to install the Feature Pack for
Web Services silently using a response file.
The installation
program installs the following program files if they are not already
installed:
- WebSphere Application Server V6.1 Fix Pack 9 (6.1.0.9)
- Java SDK 1.5 SR5 Cumulative Fix for WebSphere Application Server
(6.1.0.9)
- Feature pack enablement extensions
- WebSphere Application Server Version
6.1 Feature Pack for Web Services
Consider your current product topography before installing
the feature pack because it installs maintenance packages that may
affect the version of your application server product. If the application
server is already at or above the levels of maintenance included with
the feature pack, then the installation of these maintenance packages
is skipped. If the application server is at a higher level than what
the feature pack requires, then the feature pack installer will prompt
you to upgrade the feature pack to the same version as the application
server.
Procedure
- Log on as the user who installed the Version 6.1 WebSphere Application Server product.
- Extract the downloaded product files. The WEBSV directory
is the main directory of the Feature Pack for Web Services installation
image. Save a backup copy of the response file responsefile.WEBSV.txt somewhere on your system.
- Edit responsefile.WEBSV.txt and customize
it for your environment.
Set values for the following
options:
Option |
Description |
-OPT silentInstallLicenseAcceptance="true" |
Accept the enclosed license agreement.
|
-OPT disableNonBlockingPrereqChecking="true" |
This will notify the installer to continue
with the installation and log the warnings even though the prerequisite
checking has failed. This will also allow the installation to proceed
if you are below the required level of maintenance. The feature pack
installer will install the included maintenance packages.
|
-OPT installLocation=app_server_root |
Set app_server_root to
the root directory of your application server product.
|
-OPT allowNonRootSilentInstall="true" |
You must uncomment this line if you are installing
the product with a non-root or non-administrator ID.
|
To override any option in the response file with
command-line options, include the following option in the response
file:
-OPT overrideResponsefileOptions=true
- Optional:
You can set values
to create new application server and deployment manager profiles which
are already augmented with the feature pack, or you can augment existing
deployment manager profiles. You can also choose to create and augment
profiles after installation. See "What to do next" on this page for
more information. Change the following values in the response file
to work with profiles during installation:
Restriction: For the Feature
Pack for Web Services you can only augment an existing deployment
manager profile. It is recommended that you create a new deployment
manager profile or a new application server profile that is already
enabled with the feature pack functionality. Use the profile creation
tasks to create these profiles. The deployment manager and application
server are the only profile types which can be created with the feature
pack functionality.
- Stop all processes for the Version 6.1 product on which
you are installing the feature pack.
For example, for
the Network Deployment product, stop all application server processes,
the node agent, and the deployment manager. The installation will
fail if the installer detects running Java processes associated with
the target application server directory.
- Run the Feature Pack for Web Services installation program
using the -silent option.
At a command
prompt for the WEBSV directory, enter the following
command:
install -options responsefile.WEBSV.txt -silent
The
installation program runs silently in the background.
Results
The installation wizard installs the feature pack and records
installation events in the installation log files in the
app_server_root/logs/install/webservices directory.
Tip: If you are logged in as non-root or non-admin user, you
might not always find a log in the application server directory after
a failed installation or uninstallation attempt. When the installer
runs, a log file is created in your user home directory. If the installation
fails, an attempt is made to move the log to the
app_server_root directory;
however, without the necessary permission to move the file to the
app_server_root directory,
the attempt to move fails and the log remains in your home directory.
Look for the following log files in the
user_home/webserviceslogs directory:
- log.txt
- trace.txt.gz
- trace.xml.gz
Troubleshooting
If the
installation program is interrupted for any reason while feature pack
files are being installed, examine the messages that the installation
program displays and the information in the installation logs. Correct
the problems identified and try installing the product again. Since
the feature pack installation contains the feature pack and various
fix packs, an installation failure might occur at different points
in the process.
- If you use the silent install option to install the Feature Pack
for Web Services, you might receive a RequireSamePakversionForFEPPrereqPlugin error
in the log files. The feature pack requires WebSphere Application
Server Version 6.1.0.9. However, if you attempt to install the feature
pack on a version later than Version 6.1.0.9, the error occurs. To
address this issue, complete the following steps:
- Install WebSphere Application Server Version 6.1.0.9.
- Install the Feature Pack for Web Services.
- Install updates to Version 6.1.0.9 and updates to the feature
pack.
- If the installation program is interrupted while the fix pack
files are being installed, a later attempt to install the feature
pack might fail with an error similar to the following message:
A failure from a previous installation or uninstallation attempt has been
detected. The failed package is 6.1.0-WS-WASSDK-WinX32-FP0000009. Click Next to
initiate automated recovery.
Because the failure
occurred during the fix pack installation, the Update Installer must
be used to recover after the failure. The feature pack installer cannot
automatically recover the installation. Cancel the automated recovery
process and perform the following actions to recover the installation.
- Install the Update Installer and launch the wizard.
- On the product selection panel, select or enter the location of
the application server product directory which you used in part d
of step 4 in the Procedure.
- The Update Installer will detect that there was an update failure.
- Click Next to start the automated recovery
process.
- If the installation program is interrupted while feature pack
files are being installed, a later attempt to install the feature
pack might fail with the following message:
Failure Recovery Complete
Failure recovery unsuccessful: The failed installation or uninstallation
of maintenance package fep.websv.primary.pak was not recovered.
Click Cancel to exit the installation wizard.
Exit the installer and then perform the following
manual steps:
- Remove the fep.websv.primary.pak file from the app_server_root/properties/version/nif/backup/ directory
- Remove the app_server_root/properties/version/nif/backup/legal.websv directory.
- Remove the app_server_root/lafiles/websv directory.
- Make a backup copy of app_server_root/properties/version/nif/backup/updateStatus.xml.
Look for the section beginning with the <package> entry
associated with fep.websv.primary.pak and ending
with </package>, remove it, and save the file:
<package MaintenanceNamesOfPackagesToBeCleaned=""
URIsOfPackagesToBeCleaned=""
URIsOfPackagesToBeExecuted="zip:///home/<user_name>/IBM/WebSphere/WASND0405/properties/version/nif/backup/fep.websv.primary.pak"
isprimary="true"
maintenancefilename="fep.websv.primary.pak"
maintenancename="fep.websv.primary.pak" mode="installconfig" modified="true"
timestamp="2007-04-05 19:16:22-0400"
uritoreinstall=""
uritouninstall="zip:///home/<user_name>/IBM/WebSphere/WASND0405/properties/version/nif/backup/fep.websv.primary.pak">
...
</package>
- Remove the WEBSERVICES entries from the WebSphere
registry with the installRegistryUtils command in
the app_server_root/bin directory:
- For a root user or adminstrator:
./installRegistryUtils.bat|sh -cleanProduct
-offering WEBSERVICES
-installLocation app_server_root
- For a non-root or non administrator user, where user_home is
the home directory of the current user:
./installRegistryUtils.bat|sh -cleanProduct
-offering WEBSERVICES
-installLocation app_server_root
-userHome user_home
- Run the install executable file in the WEBSV directory
of the Feature Pack for Web Services installation image and install
the feature pack.
Avoid trouble: Certain events can prevent
ISMP from starting the installation wizard. Such an event is not enough
disk space to launch the installation wizard for example. If your
installation fails and there is no information in the installation
logs, use the
-is:javaconsole parameter to record
entries for events that cause the ISMP program to fail to start the
installation wizard. The syntax of the
install command
for observing such events is:
./install -is:javaconsole
install.exe -is:javaconsole
Avoid trouble: Although the usage of
-is:javaconsole is
supported, the usage of
-console, for example
install
-console, is not supported.
gotcha
gotcha
What to do next
Applying Maintenance
Use the Update Installer
to install maintenance packages for any of the installable WebSphere
software components in the product package. See Applying maintenance for the Feature Pack for Web Services with the Update Installer for more information.
Apply
the current feature pack fix pack to Feature Pack for Web Services.
You must synchronize the versions of any installed feature pack with
the application server. For example, if your application server is
at Version 6.1.0.9, then you must upgrade to 6.1.0.13 if you wish
to upgrade the feature pack to 6.1.0.13.
If you have already
installed Feature Pack for EJB 3.0, then you must apply the PK53084
interim fix before applying any feature pack fix packs to Feature
Pack for Web Services, unless you originally installed Feature
Pack for Web Services using a CIP created with the Installation
Factory. See Installing and configuring multiple feature packs for
more information.
Profiles
In order to use the
feature pack functionality, you must first create a new profile enabled
with the feature pack, or augment an existing deployment manager profile
using the Profile Management tool.
For the Feature Pack for
Web Services you can only augment an existing deployment manager profile.
It is recommended that you create a new deployment manager profile
or a new application server profile that is already enabled with the
feature pack functionality. Use the profile creation tasks to create
these profiles. The deployment manager and application server are
the only profile types which can be created with the feature pack
functionality. See Profile augmentation rules and limitations for feature packs for more
information.
Samples
The Feature Pack for Web Services
provides several sample applications that you can install onto an
application server profile that has been created with the feature
pack functionality. See Installing Web Services Samples with the console.