This example describes how to create and install an integrated
installation package (IIP) composed of the application server and a feature
pack using the IBM WebSphere Application Server Installation Factory. Later
examples will describe how to install the IIP created here.
Before you begin
You must first install the Installation Factory before you use
it to create an installation package. See Getting Started with the Installation
Factory for more information about downloading and installing the product.
You should also familiarize yourself with customized installation packages (CIPs)
and IIPs before following this example.
About this task
With IIPs you can install multiple products in a single installation
session instead of having to install them independently one at a time. The
installation packages within an IIP are invoked one after the other by the
IIP in order to complete the end-to-end installation. The release of WebSphere
feature packs is one of the main reasons why creating a repeatable installation
package makes more sense than ever.
This example will describe how to create
two CIPs, one containing the application server and one containing a feature
pack. The CIPs will also include any fixes or customizations which need to
be applied to that product into the same package. See Developing and installing
customized installation packages for more information. The CIPs are then included
into the overall IIP resulting in an installation solution which can be reused
on more than one machine.
This example will step through the following
with a non-root user on a Linux operating system:
- Create a WebSphere Application Server CIP
- Create a Feature Pack for Web Services CIP
- Create an IIP containing the two CIP contributions
- Install the IIP, installing both contributions in GUI mode
- Verify the installation
Procedure
- Create a WebSphere Application Server
CIP at fix pack level 6.1.0.16, including SDK fix pack and one WebSphere Application
Server interim fix.
- Download the IBM Installation Factory for WebSphere Application Server
V6.1 and unpack it into /newdisk/IF.
- Launch the Installation Factory in GUI mode using the /newdisk/IIP/bin/ifgui.sh script.
- On the IBM Installation Factory panel, select Create a New
Customized Installation Package.
- On the Product, Package, and Edition Selection panel, choose "WebSphere
Application Server" and "Network Deployment" edition. Click Finish.
- On the Mode Selection panel, choose the default “Connected mode” and “Linux
IA32” platform. Click Next.
- On the Package Identification panel, change the Identifier to something
like com.ibm.samplewascip and take the default value for
Version (1.0.0.0). Click Next.
- On the Build Information panel, leave the defaults for the Build definition
file name and CIP build directory path. Note that the location of the CIP
build directory path is where the CIP will be generated. Click Next.
- On the Product Installation Image panel, browse to the WebSphere Application
Server Version 6.1 installation image location. Note that this image is the
installable image from a CD or download location which can be used to install
WebSphere Application Server. It is not any image that might have already
been installed on a system. Click Next.
- On the Feature Selection panel, take the default values and click Next.
- On the Maintenance Packages panel, Input the WebSphere Application Server
fix pack 6.1.0.16, SDK fix pack 6.1.0.9 (which actually comes with the Feature
Pack for Web Services installation image later in this example), and any WebSphere
Application Server interim fix that you might have available. You may want
to click Verify Maintenance Packages to make sure the
input on this panel is good. Click Next.
- On the Install and Uninstall Scripts panel, click Next.
- On the Profile Customization panel, take the default and click Next.
- On the Additional Files panel, click Next.
- On the Authorship panel, enter a name for your organization and input
a description. Click Next.
- On the Customized Installation Package Preview panel, click Save
build definition file and generate customized installation package.
Click Estimated Size and Available Space to check disk
space. Click Finish.
- The Installation Factory will generate the CIP based on the information
you entered. The CIP build can be found under CIP_directory/ifpackage
where CIP_directory is the directory path you entered in
part f.
- After the CIP has been created successfully, click OK in
the confirmation window. Leave the Installation Factory main panel open to
create a Feature Pack for Web Services CIP in Step 2.
- Create a Feature Pack for Web Services
CIP at fix pack level 6.1.0.16, including feature pack interim fixes
- If the main Installation Factory panel is still open, select Create
a New Customized Installation Package. Otherwise, launch the main
panel again using the /newdisk/IIP/bin/ifgui.sh script.
- On the Product, Package, and Edition Selection panel, choose “IBM WebSphere
Application Server Version 6.1 Feature Pack for Web Services”. By default,
all product editions will be preselected. This is due to the fact that feature
pack applies to all WebSphere Application Server editions. Click Finish.
- On the Mode Selection panel, choose the default “Connected mode” and “Linux
IA32” platform. Click Next.
- On the Package Identification panel, fill in an Identifier and Version.
Click Next.
- On the Build Information panel, leave the defaults for the Build definition
file name and CIP build directory path. Note that the location of the CIP
build directory path is where the CIP will be generated. Click Next.
- On the Product Installation Image panel, browse to the Feature Pack for
Web Services product image location. Click Remove the bundled maintenance
packages from the CIP. The reason for this is that the bundled
packs are at a lower level included with the feature pack. Since we are installing
the WebSphere Application Server CIP at 6.1.0.16 level, the minimum bundle
here is not needed. This will save the disk space for Feature Pack for Web
Services CIP. Click Next.
- On the Maintenance Packages panel, input the Feature Pack for Web Services
fix pack 6.1.0.16 and any Feature Pack for Web Services interim fixes. You
may want to click Verify Maintenance Packages to make
sure the input on this panel is good. Click Next.
- On the Install and Uninstall Scripts panel, click Next.
- On the Profile Customization panel, take the default and click Next.
- On the Additional Files panel, click Next.
- On the Authorship panel, enter a name for your organization and input
a description. Click Next.
- On the Customized Installation Package Preview panel, click Save
build definition file and generate customized installation package.
Click Estimated Size and Available Space to check disk
space. Click Finish.
- The Installation Factory will generate the CIP based on the information
you entered. The CIP build can be found under CIP_directory/wsif
where CIP_directory is the directory path you entered in
part e.
- After the CIP has been created successfully, click OK in
the confirmation window. Leave the Installation Factory main panel open to
create the IIP in Step 3.
- Create the IIP containing the two CIP
contributions
- If the main Installation Factory panel is still open, select Create
a New Integrated Installation Package. Otherwise, launch the main
panel again using the /newdisk/IIP/bin/ifgui.sh script.
- On the Mode Selection panel, choose the default “Connected mode” and “Linux
IA32” platform. Click Next.
- On the Package Identification panel, change the Identifier tocom.ibm.sampiip and
leave the default value for Version. Click Next.
- On the Build Information panel, leave the defaults for the Build definition
file name and IIP build directory path. Note that the location of the IIP
build directory path is where the IIP will be generated. Make sure that you
have enough space in the target directory if you are going to generate the
IIP in addition to building the build definition. You may see an error indicating
a non-empty directory if the default IIP directory is not empty and the Warn
if the target location is not empty checkbox is selected. Click Next.
- On the Integrated Installation Wizard Settings panel, accept the defaults
which will display the IIP installation wizard at startup, and will allow
the installing user to override whether to display the IIP installation wizard.
If you prefer to run the IIP silently you can run the installer using the –iipNoGUI option.
Click Next.
- The Construct the Integrated Installation Package panel is displayed.
This is the main panel where you will select, add, and modify the properties
of the packages you want to include in the IIP. Since we want to create a
package which includes both the Network Deployment CIP and the feature pack
CIP, we will begin with the Network Deployment product. Select “IBM WebSphere
Application Server Network Deployment 6.1” from the list, then click Add
Installer.
- On the new Add Installation Package panel, click Modify to
input the location of first contribution, which is the WebSphere Application
Server CIP you created in Step 1.
- On the new Modify Installation Package Properties panel, browse to the
location of the WebSphere Application Server CIP, then click Retrieve
Package Size to estimate the size of that package. Click OK.
- You are returned to the Add Installation Package panel. You can see that
the Directory path to the package and the Package size fields are filled out.
Click OK.
- You are returned to the Construct the Integrated Installation Package
panel. You can now see your package listed in the Installation packages used
in this IIP field, and an invocation of that package has been created and
listed in the Installation package invocations field. Make sure your package
invocation is selected and click the Modify button
next to the Installation package invocations field.
- In the new Installation Package Invocation Properties panel, you will
be able to change several properties of the current contribution. You might
notice that Make this installation invocation the primary installation
invocation checkbox is selected, the default installation mode
is “interactive” (wizard) mode, and users can override the installation mode
to be silent at IIP installation time. There are two sets of values for “Default
installation directory paths”, “Response files”, and “Exit code actions”.
One set is for a non root user type and the other is for a root user type.
The default “Installation directory path” for non root user is $JP{user.home}/IBM/WebSphere/AppServer.
For root user, it is /opt/IBM/WebSphere/AppServer. $JP{user.home} is
a macro which will be resolved to /home/nonroot in this case.
Accept the default values for now and you will see that they can be changed
at installation time. Click OK.
- You are again returned to the Construct the Integrated Installation Package
panel. Add the Feature Pack for Web Services CIP to this IIP . Select IBM
WebSphere Application Server Version 6.1 Feature Pack for Web Services from
the list, then click Add Installer. Follow steps i-iii
in the application server section, changing only the product directory path
to the location of your feature pack CIP. Click OK twice
to return to the main Construct the Integrated Installation Package panel.
- You can now see your feature pack CIP listed in the Installation
packages used in this IIP field, and an invocation of that package
has been created and listed in the Installation package invocations field.
To view the properties of the second invocation, make sure the feature pack
invocation is selected and click the Modify button
next to the Installation package invocations field.
- Change the Display name of this invocation to
be CIP WS16. Users may find that the Installation
directory path is set to the WebSphere Application Server CIP
installation location through the use of the$RESV{} macro.
See IIP macro replacement for more information. Click OK to
close this window and return to the Construct the Integrated Installation
Package panel. Click Next.
- On the Additional Files and Directories panel, click Next.
- On the Authorship panel, enter a name for your organization and input
a description. Click Next.
- On the Integrated Installation Package Preview panel, click Save
build definition file and generate integrated installation package.
Click Finish.
- The Installation Factory will generate the IIP based on the information
you entered. The IIP build can be found under IIP_root/iip
where IIP_root is the directory path you entered in part
d. The two CIP contributions are located in theIIP_root/iip/contrib directory.
- When the IIP is generated successfully, click OK in
the confirmation window. At this point, the main Installation Factory panel
can be closed.
- Install the IIP.
- Launch the IIP installer wizard fromIIP_root/iip/bin using
the command ./install.sh –iipUserType=nonroot The reason
to have –iipUserType is to pick up the right set of values
from the IIP build definition, either for a non-root user type (nonroot) or
root user type (root). On the Welcome panel, click Next.
- On the Installation Selection panel you will see the two CIP invocations
that were created Steps 2 and 3. Click About if you
want to view the IIP information.
- Click Install to start installing the first invocation,
which is the WebSphere Application Server CIP. The CIP installer will appear
and will look similar to the non-CIP application server installation wizard.
- On the Installation directory panel, the default Product installation
location is /home/nonroot/IBM/WebSphere/AppServer. /home/nonroot
is the resolved value for $JP{user.home} displayed in step
3.g.i. Change the default to /newdisk/IBM/WebSphere/AppServer.
The IIP will automatically take whatever location you specify here for WebSphere
Application Server and will use it as the installation location for the Feature
Pack for Web Services CIP later on because of the $RESV macro
in step 3.j. Click Next.
- On the WebSphere Application server environments panel, choose None from
the list for this sample. We would like to have a profile created later after
the Feature Pack for Web Services CIP installation. Click Next.
You will see a warning panel asking whether you want to proceed without creating
a profile. Click Yes.
- On the Summary panel, click Next to start the installation
of the application server CIP. Click Finish on the
Installation Results panel when the installer completes.
- The IIP installation wizard shows that the invocation has installed successfully,
and triggers the second installation automatically.
- Follow a similar procedure to install the Feature Pack for Web Services
CIP to the same location as the WebSphere Application Server CIP. You will
find the default installation location is correctly pre-filled with /newdisk/IBM/WebSphere/AppServer which
you set during the previous CIP invocation.
- On the Summary panel, click Next to start the installation
of the feature pack CIP. Click Finish on the Installation
Results panel when the installer completes.
- You are returned to the IIP installation wizard, where it shows both invocations
have installed successfully. Click Finish to exit the
IIP installer wizard.
- Create a profile by launching the Profile Management tool in GUI mode.
Go to /newdisk/IBM/WebSphere/AppServer/bin/ProfileManagement,
and run the./pmt.sh command. Click Next.
- On the Environment Selection panel, highlight Feature Pack
for Web Services and click Next.
- On the Profile Type Selection panel, select either the Application server
or the Deployment manager type and click Finish.
- Verify the installation
- Verify the product version using the versionInfo command
which can be found in the /newdisk/IBM/WebSphere/AppServer/bin directory.
You should find both WebSphere Application Server and Feature Pack for Web
Services are installed at the 6.1.0.16 level.
- To view interim fixes that are installed, use the ./versionInfo.sh
–long > version_long.txt. You should find that interim fixes for
both the WebSphere Application Server and feature pack products have been
installed.
- You can also review the logs for each product in the /newdisk/IBM/WebSphere/AppServer/logs directory.