Install a feature pack customized installation package (CIP) using
the installation wizard on distributed operating system platforms.
Before you begin
You can install a customized installation package (CIP) that includes
a feature pack and one or more maintenance packages and other customizations.
You must first create a CIP with the Installation Factory before you can
install the CIP. See
Developing and installing customized installation packages for
more information about creating a CIP.
Avoid trouble: As
of Version 6.1.0.13 you must keep the version levels of the application server
and any installed feature packs synchronized to the same maintenance level.
If you have any feature packs installed, then it is recommended that you use
the Update Installer to synchronize your environment before installing any
additional Installation Factory packages. In fact, you will either be blocked
from installing or prompted to upgrade during the installation of a feature
pack CIP if your versions are not the same. If you are prompted and do not
provide the proper maintenance packages you will be blocked from installing
the CIP.
You can slip install, or update, an existing
application server that contains one or more feature packs with an IIP as
long as all packages in the IIP are at the same maintenance level. You can
alsoscratch install an IIP containing the application server
and one or more feature packs onto a machine with no existing application
server as long as all included packages are at the same maintenance level.
Read the Working with feature packs topic for more information.
You must use Installation Factory version 6.1.0.17 or later if you want to
use an IIP to update a feature pack environment.
If you are installing
the Feature Pack for Web Services for the first time, then it is recommended
that you create a CIP containing the feature pack and the most recent fix
pack. Otherwise if you have already installed the Feature Pack for Web Services
with the regular installer, you need to include a mandatory interim fix before
installing a CIP containing any feature pack fix packs. See
Installing and configuring multiple feature packs for additional information regarding
feature pack installation and other considerations.
gotcha
About this task
Use the following installation procedure to install a feature
pack CIP using the installation wizard GUI. You can also install a CIP silently.
See Installing a CIP silently.
Select
available features and characteristics for the feature pack and the profile
that you can create.
Procedure
- Log on to the operating system.
![[Windows]](../../windows.gif)
When installing on a Windows system, a Windows
service is automatically created to autostart the application server if your
installer user account has the following advanced user rights:
- Act as part of the operating system
- Log on as a service
For example, on some Windows systems, click
Administrative
Tools > Local Security Policy > User Rights Assignments to set
the advanced options. See your Windows documentation for more information.
If you plan to run the application server as a Windows
service, do not install from a user ID that contains spaces. A user ID with
spaces cannot be validated. Such a user ID is not allowed to continue the
installation. To work around this problem, install with a user ID that does
not contain spaces.
- Insert the CD or DVD with the CIP into the disc drive, or access
the directory where the CIP is located.
Mount
the drive if necessary as described in Mounting disc drives on operating systems such as AIX or Linux.
- Start the installation directly with the install command,
where cip_root is the root directory of your CIP.
If a problem occurs with the Java Runtime Environment (JRE), use
the WebSphere Application Server JRE in the /java/jre/bin directory
of an installation image to start the installation.
After launching
the installation wizard from the command line, the installer wizard initializes
and then displays the Welcome panel. Click Next.
- Read the license agreement and accept its terms.
Click the radio button beside the message I accept
both the IBM and the non-IBM terms to agree to the license agreement.
Click Next to continue.
After you accept the
licensing terms, the installation wizard checks for a supported operating
system and prerequisite patches. If you encounter a problem such as not having
the right prerequisite updates on your system, cancel the installation, make
the required changes, and restart the installation. Since you are installing
the feature pack, you should already have an existing application server installed
and should already have met the system requirements.
- The Systems prerequisite check panel is displayed. The installer
program checks for required space before calling the installation wizard.
If you do not have enough space, stop the installation program, free space
by deleting unused files and emptying the recycle bin, and restart the installation.
See Installing Feature Pack for Web Services on distributed operating systems or Installing Feature Pack for Web Services on i5/OS for
more information on the feature pack installation requirements.
Click Next to
continue.
- The installation wizard looks for an existing Version 6.1 application
server installation and displays the Installation directory panel.
If
the wizard detects an existing installation, it will populate the Product
installation location field with the root directories of all the
WebSphere application server products it detects. If for some reason the filed
is not populated, specify the installation root directory manually, or click Browse to
browse the file system for the directory. Click Next.
Note: If
an existing installation is at a lower level than the CIP or at the same level
as the CIP, the core product will be updated to the CIP level automatically.
If an existing installation is at a higher level than the CIP, the core product
will not be down leveled.
Restriction: Deleting the default
target location and leaving the installation location field empty prevents
you from continuing.
- The Customization panel will be displayed if the feature pack is
already installed on the target application server you specified and you only
want to apply maintenance. This is called a slip install of the
feature pack CIP. Depending on the content of the CIP, you may have options
to install maintenance only, or install maintenance and profile customizations.
- Review the summary information, then click Next to
install the product code or Back to change your specifications.
The installation wizard creates the uninstaller program
and then displays a progress panel that shows which components are being installed.
At the end of the installation, the wizard displays the Installation completion
panel.
- If you want to create a feature pack profile immediately after
installation, then select the Launch the Profile management tool (PMT)
checkbox, then click Finish to exit the installation
wizard and launch the PMT.
- The installation wizard records installation events in the installation
log files in the app_server_root/logs/install/webservicesdirectory.
Results
The installation wizard installs the feature pack product files onto
the specified application server.
Example
This example describes how to create and install several customized
installation packages containing the application server and two feature packs.
All feature pack CIPs must raise the installed feature pack to the same version
as the application server and other feature packs to ensure version synchronization.
See
Installing and configuring multiple feature packs for more details.
Table 1. Installing the application server and multiple feature packs at or
above version 6.1.0.13
Step |
Task |
1 |
Download Installation Factory at or above version 6.1.0.13. |
2 |
Download Feature Pack for EJB 3.0, Feature Pack for
Web Services, a Feature Pack for EJB 3.0 fix pack at or above version 6.1.0.13,
and a Feature Pack for Web Services fix pack at or above version 6.1.0.13 |
3 |
Build a CIP containing WebSphere Application Server
6.1 and include an application server fix pack at or above version 6.1.0.13 |
4 |
Build a CIP containing Feature Pack for EJB 3.0 and
include a Feature Pack for EJB 3.0 fix pack at or above version 6.1.0.13 |
5 |
Build a CIP containing Feature Pack for Web Services
and include a Feature Pack for Web Services fix pack at or above version 6.1.0.13 |
6 |
Include the CIPs into an Integrated installation package
(IIP) or install them one after the other. |
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 using the Profile Management tool.
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.
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.
If
the profile is correctly enabled with the feature pack, a Services option
is displayed in the administrative console navigation tree. Your applications
can now use the functionality provided by the Feature Pack for Web Services.