WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

108 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

Repository topologies can be generalized into these categories:

 A public repository that is accessible to the general public at an IBM-hosted site, such as

IBM Passport Advantage

 A local repository that is used by a single user and not shared with others

 An enterprise repository that is located behind the firewall and is accessed by multiple

machines within the enterprise

4.3.3 Updating Installation Manager

To update Installation Manager, you must update the installation kit. Refer to 4.2.2, “Obtaining

an Installation Manager installation kit” on page 104 for more information.

After you obtain the updated installation kit, refresh the Installation Manager installation using

the same commands that you used for the initial installation (installc, userinstc, or

groupinstc). For details about these commands, refer to 4.2.3, “Installing Installation

Manager on the system” on page 105.

4.3.4 Installing the WebSphere Application Server initial repository

WebSphere Application Server V8.5 has FMID HBBO850 and can be obtained in one of the

following ways:

 Through a ServerPac or SystemPac: Follow the instructions in the Installing Your Order

guide to create the repository file system <high level qualifier (HLQ)>.SBBOIMR and the

<HLQ>.SBBOJCL library.

 Through a Custom-Built Product Delivery Offering (CBPDO): Run the jobs to install the

WebSphere Application Server repository following the instructions that are available at

Program Directory to create the repository file system <high level qualifier

(HLQ)>.SBBOIMR and the <HLQ>.SBBOJCL library.

Run the following jobs to create the WebSphere Application Server repository:

 BBORECEV to receive the deliverables

 BBOISMKD to allocate the system paths

 BBODDDEF to define de SMP/E DDDEFs

 BBOAPPLY to apply product repository

 BBOACCEP to accept product repository

4.4 Using Installation Manager

Before you begin using Installation Manager, consider in which mode it is going to be used

and what actions are going to be performed in the software that is going to be maintained.

The following options are available:

Command-line mode Use the Installation Manager command line (imcl) to manage

installations from the /eclipse/tools subdirectory.

Silent mode Use this mode to install software easily to multiple systems. Silent

mode uses the imcl command in conjunction with response files.

You can use all of the commands that we demonstrate in this chapter in z/OS jobs using

BPXBATCH.

Chapter 4. Installing WebSphere Application Server on z/OS systems 109

4.4.1 Key features of Installation Manager

In addition to installing packages, Installation Manager can be used to perform maintenance

operations, such as updating, modifying, or rolling back packages. These operations differ

slightly from how they are performed on a distributed platform.

Installing packages

When the specific version of a package is not specified in the installation command,

Installation Manager checks the designated repository and picks the highest version that is

available there. For example, the WebSphere package name for z/OS is

com.ibm.websphere.zOS.v85.

Due to this approach, if a repository shows more than one WebSphere version and the

installation needs to be done at a level that is

not the highest, you must specify the complete

package name, such as com.ibm.websphere.zOS.v85_8.5.0.20120501_1118, in your

command.

Updating packages

You can update a package as soon as the updates are available in an Installation Manager

repository. You can apply the following types of updates:

 A

fix pack is a new product level. Each fix pack repository is a delta on top of the previous

fix pack level. Fix packs have the same package name but a different version level. A fix

pack can be delivered as an SMP/E program temporary fix (PTF) to the initial product

repository.

 An

interim fix is also known as a patch. Interim fixes use the package name, and they are

not available as SMP/E PTF.

You can obtain fix packs and interim fixes by downloading them from the IBM Fix Central

website:

http://www.ibm.com/support/fixcentral/

When you need to verify the fixes that are available for maintenance, use the imcl

listAvailableFixes command, as shown in Example 4-4, with the following parameters:

<package name> The package to be installed with the version

-repositories The repository location

Example 4-4 Listing available fixes in a repository

/InstallationManager/bin/eclipse/tools $ imcl listAvailableFixes

com.ibm.websphere.zOS.v85_8.5.0.20120501_1118 -repositories

/usr/lpp/InstallationManagerRepository/HBBO850

Modifying packages

A package can have features, languages, and functions added or removed by Installation

Manager. To modify a package, run imcl install. To add sample applications to WebSphere

Application Server, as shown in Example 4-5 on page 110, run imcl install with the

following parameters:

<package name>,<feature name> The package and feature name to be installed

-installationDirectory The directory where the package is installed

-repositories The repository location