Install a feature pack directly from your iSeries server on an
existing installation of the IBM Application Client for the WebSphere Application
Server Version 6.1 product.
Before you begin
The Feature Pack for EJB 3.0 implements
the Enterprise JavaBeans (EJB) Version 3.0 and Java Persistence API (JPA)
specifications.
Before starting this installation, do the following:
- Read Planning to install Feature Pack for EJB 3.0.
- Ensure that your user profile has *ALLOBJ and *SECADM special authorities.
- Determine if the IBM Application Client for WebSphere Application Server
is already installed on your server. The feature pack must be installed on
an existing IBM Application Client for WebSphere Application Server Version
6.1 installation.
- Enter the Display Software Resources (DSPSFWRSC) command
on a CL command line.
- Look for an entry with the product Resource ID 5733W61.
- If you do not find the product Resource ID, then this product has not
been installed on your iSeries server.
- If you find the product Resources ID, ensure that the following entry
displays: 5733W61 6 5106 WebSphere Application Server V6.1 Client.
- Install the IBM Application Client for WebSphere Application Server Version
6.1 product if you have not done so already.
- Download the feature pack and extract the contents to an Integrated File
System (IFS) directory on the iSeries system you will install to.
For example,
create two directories, appclient_download and appclient_installation_image.
Then, download the feature pack to the appclient_download directory
and extract the downloaded file to the appclient_installation_image directory.
Do not move any files out of the appclient_installation_image directory.
- The operating system requirements for a feature pack are the same as for
a Version 6.1 application client 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 client 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 client product.
- 600 MB of free space available in your temporary directory
About this task
This topic describes how to install the Feature Pack for
EJB 3.0 silently using the installation
program. You can install the feature pack from Qshell using the
INSTALL command.
You can also use the
RUNJVA command to invoke the installation
wizard.
The installation program installs the following program files if
they are not already installed:
- IBM Application Client for WebSphere Application Server Version 6.1 Fix
Pack 13 (6.1.0.13)
- Feature pack enablement extensions
- IBM Application Client for WebSphere Application Server Version 6.1 Feature
Pack for EJB 3.0
Procedure
- Sign on the iSeries system with a user profile that has *ALLOBJ
and *SECADM special authorities.
- Copy the responsefile.EJB3.txt file located
in the EJB3 subdirectory
of the extracted install image.
- Edit the copy of the responsefile.EJB3Client.txt file.
You can edit the file using a mapped drive and a text editor or by using the EDTF
CL command from the i5/OS command line.
Set values
for the following options where app_client_root is
the directory path to your IBM Application Client for WebSphere Application
Server Version 6.1 installation:
-OPT silentInstallLicenseAcceptance="true"
-OPT installLocation=app_client_root
To
override any option in the response file with command-line options, include
the following option in the response file:
-OPT overrideResponsefileOptions=true
- Stop all processes for the Version 6.1 product on which you are
installing the feature pack.
Stop the application server and
any other product processes. For example, for the Network Deployment product,
stop the deployment manager, the node agent, and all application server processes.
- Verify that the host server jobs have started on your iSeries server.
The host server jobs allow the installation code to run on iSeries.
On a CL command line, enter the following command:
STRHOSTSVR SERVER(*ALL)
- If you have not already done so, read the IBM International Program
License Agreement located in the lafiles directory.
If you agree to the terms of the agreement, continue with the installation
process.
- Invoke the installation program for the feature pack.
Run
the INSTALL command from Qshell or use the RUNJVA command
from the CL command line.
In the following example commands, path/responsefile represents
the fully-qualified path of the responsefile.EJB3.txt file that
you edited.
- Run the INSTALL command from Qshell.
- On a CL command line, issue the STRQSH command to start
the Qshell command shell.
- Issue the install command from the EJB3 subdirectory of the directory
containing the extracted install image to start the installation program:
install -options path/responsefile
Important: Do not exit the Qshell session (PF3) until the installation
has completed. Doing so might cause the installation to stop prematurely.
- Issue the RUNJVA command from the CL command line:
At
the CL command line, change to the EJB3 subdirectory of the directory
containing the extracted install image before issuing the following commands:
chdir ‘/pathToExtractedImage/EJB3’
Enter
the RUNJVA command on one line. The command is shown on more
lines for formatting clarity:
RUNJVA
CLASS(run) PARM('-options' 'path/responsefile')
CLASSPATH('setup.jar')
PROP(
('Xbootclasspath/p' 'java/endorsed/xml.jar')
(java.version 1.5)
(is.debug 1)
)
- For security purposes, if the host servers were not running prior
to installation, it is recommended that you run the End Host Server (ENDHOSTSVR)
command after the installation is complete.
Results
The installation program records events in the log files and installs
the feature pack.
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 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.clt.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.clt.ejb3.primary.pak file from the app_client_root/properties/version/nif/backup/ directory
- Remove the app_client_root/properties/version/nif/backup/legal.ejb3 directory.
- Remove the app_client_root/lafiles/ejb3 directory.
- Make a backup copy of app_client_root/properties/version/nif/backup/updateStatus.xml. Look for the section beginning with the <package> entry
associated with fep.clt.ejb3.primary.pak and ending with </package>,
remove it, and save the file:
<package MaintenanceNamesOfPackagesToBeCleaned=""
URIsOfPackagesToBeCleaned=""
URIsOfPackagesToBeExecuted="zip:///home/<user_name>/IBM/WebSphere/AppClient/properties/version/nif/backup/fep.clt.ejb3.primary.pak"
isprimary="true"
maintenancefilename="fep.clt.ejb3.primary.pak"
maintenancename="fep.clt.ejb3.primary.pak" mode="installconfig" modified="true"
timestamp="2007-04-05 19:16:22-0400"
uritoreinstall=""
uritouninstall="zip:///home/<user_name>/IBM/WebSphere/AppClient/properties/version/nif/backup/fep.clt.ebj3.primary.pak">
...
</package>
- Remove the EJB3 entries from the WebSphere registry with
the InstallRegistryUtils utility in the app_client_root/bin directory.
- Run the install executable file in the EJB3 directory
of the feature pack installation image and install the feature pack.
What to do next
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.