The WebSphere Application Server Version 6.1
Feature Pack for EJB 3.0 implements the Enterprise JavaBeans (EJB) Version
3.0 and Java Persistence API (JPA) specifications. Run the Feature
Pack for EJB 3.0 installation program to silently install the feature
pack on an existing installation of a WebSphere® Application Server Version
6.1 product.
Before you begin
Before starting this installation, complete the following actions:
- Read Planning to install Feature Pack for EJB 3.0.
- Install a Version 6.1 WebSphere Application Server product
if you have not done so already.
- Download and extract the Feature Pack for EJB 3.0.
For
example, create two directories, ejb3_download and ejb3_installation_image.
Then, download the feature pack to the ejb_download directory
and then extract the downloaded file to the ejb_installation_image directory.
Do not move any files from the ejb_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. The following space
is required
- 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 silently
using a response file.
The installation program installs the following
program files if they are not already installed:
- WebSphere Application Server Version 6.1 Fix Pack 13 (6.1.0.13)
- Java SDK 1.5 SR6 Cumulative Fix for WebSphere Application Server (6.1.0.13)
- Feature pack enablement extensions
- WebSphere Application Server Version 6.1 Feature Pack for EJB 3.0
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 EJB3 directory
is the main directory of the Feature Pack for EJB 3.0 installation
image. Save a backup copy of the response file responsefile.EJB3.txt somewhere
on your system.
- Edit the responsefile.EJB3.txt file and customize
it for your environment.
Set values for the following options:
Table 1. Response file parameters
Option |
Description |
-OPT silentInstallLicenseAcceptance="true" |
Accept the enclosed license agreement.
|
-OPT installLocation=app_server_root |
Set app_server_root to
the root directory of your application server product.
|
-OPT disableNonBlockingPrereqChecking="true" |
Notifies the installer to continue with the installation
and log the warnings even though the prerequisite checking has failed. You
have to specify "true" if your application server is below the level of maintenance
required by the feature pack. In that case the feature pack will install any
included application server maintenance packages.
|
-OPT allowNonRootSilentInstall="true" |
You must uncomment this line if you are installing
the product with a non-root or non-administrator ID.
|
-OPT fepFixpackLocation |
Optional. Specifies the location of any feature pack
fix packs to be applied to the feature pack. The installer will ignore this
option if the application server is below the level of maintenance required
by the feature pack. Make sure that the level of your application server matches
or exceeds the level of the feature pack installer.
|
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 enabled with the
feature pack, or you can augment existing deployment manager and application
server profiles. You can also choose to create and augment profiles after
installation. See the "What to do next" section in this topic for more information.
Restriction: The deployment manager and application server
are the only profile types which can be created or augmented with theFeature
Pack for EJB 3.0 functionality. Use the profile creation tasks to create
these profiles.
- Stop the application server and any other product 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 installation program using the -silent option.
At a command prompt in the EJB3 directory, enter
the following command:
install -options responsefile.EJB3.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/ejb directory.
Tip: If you are logged in as non-root or non-admin
user, you might not always find a log file 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, then an attempt is made to move the file 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 file remains in your home directory. Look
for the following log files in the
user_home/ejb3logs 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 the installation program is interrupted while the fix pack files are
being installed, a later attempt to install the feature pack might fail. This
could occur during the installation of the feature pack enablement fixes or
the fix pack as seen in the following example:
A failure from a previous installation or uninstallation attempt has been
detected. The failed package is 6.1.0-WS-WASSDK-WinX32-FP00000013. Click Next to
initiate automated recovery.
Since 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 detects 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, then 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.ejb3.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.ejb3.primary.pak file from the app_server_root/properties/version/nif/backup/ directory
- Remove the app_server_root/properties/version/nif/backup/legal.ejb3 directory.
- Remove the app_server_root/lafiles/ejb3 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.ejb3.primary.pak and ending with </package>,
remove it, and save the file. The following is an example of such a section:
<package MaintenanceNamesOfPackagesToBeCleaned=""
URIsOfPackagesToBeCleaned=""
URIsOfPackagesToBeExecuted="zip:///home/<user_name>/IBM/WebSphere/WASND0405/properties/version/nif/backup/fep.ejb3.primary.pak"
isprimary="true"
maintenancefilename="fep.ejb3.primary.pak"
maintenancename="fep.ejb3.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.ejb3.primary.pak">
...
</package>
- Remove the EJB3 entries from the product registry with
the installRegistryUtils command in the app_server_root/bin directory:
- For a root user or adminstrator:
./installRegistryUtils.bat|sh -cleanProduct
-offering EJB3
-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 EJB3
-installLocation app_server_root
-userHome user_home
- Run the install executable file in the EJB3 directory
of the Feature Pack for EJB 3.0 installation image
and install the feature pack.
Avoid trouble: Certain events can prevent InstallShield
Multi-Platform 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
Apply the current feature pack
fix pack to the feature pack. 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.15, then you must upgrade to 6.1.0.15 if you wish
to upgrade the feature pack to 6.1.0.15. See Installing and configuring multiple feature packs for
more information.
Use the Update Installer to install maintenance packages
for any of the installable WebSphere software components in the product package.
See Applying maintenance for Feature Pack for EJB 3.0 with the Update Installer 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 or
application server profile using the Profile Management tool. 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 Augmentation rules and limitations for feature packs on non-z/OS operating systems for
more information.
Samples
The Feature Pack for EJB 3.0 provides several
sample applications that you can install onto an application server profile
that has been created with the feature pack functionality. See Installing EJB 3.0 Samples with the console for
more information.