2.6. Utilize Centralized Installation Manager (CIM) in WebSphere Application Server Network Deployment V8.0.

2.6. Utilize Centralized Installation Manager (CIM) in WebSphere Application Server Network Deployment V8.0.
Prev	Chapter 2. Installation, Configuration and Maintenance	Next


	[WAS_8.0_INFOCENTER]

Centralized Installation Manager provides an easy, repeatable, centralized user interface for installing IBM WebSphere Application Server to a large number of remote target machines, all without requiring the administrator to log in to each machine and repeat the same install operation.

Centralized Installation Manager (CIM) has been available in WebSphere Application Server Network Deployment since Version 7.0. A number of major improvements were made to CIM for WebSphere Application Server V8.0. Beginning with WebSphere Application Server V8.0, CIM drives remote installation of WebSphere Application Server and its supplementary products using IBM Installation Manager, which provides a single user interface for managing the product lifecycle. CIM also enables you to install the product and apply maintenance (fixpacks and ifixes) — separately or together in one operation.

Because CIM is now integrated with the Job Manager, you can submit installation jobs from both the Job Manager administrative console and wsadmin.sh command line.

The table below lists the available CIM jobs and their functions:

Table 2.1. Centralized Installation Manager jobs

Job	Name	Description
`inventory`	Inventory	Use to collect what has been installed on remote targets, it will be run automatically right after you register a host. The inventory information is a snapshot of what has been installed on a remote target at that moment. Rerun this job to get the most updated inventory information as needed.
`installIM`	Install IBM Installation Manager	Use to install IBM Installation Manager on remote targets.
`updateIM`	Update IBM Installation Manager	Use to update IBM Installation Manager on remote targets to a newer version.
`uninstallIM`	Uninstall IBM Installation Manager	Use to uninstall IBM Installation Manager on remote targets.
`manageOfferings`	Manage offerings	Use to install or uninstall WebSphere Application Server and its supplementary products. Can also be used to install or uninstall fixpacks and interim fixes.
`manageprofiles`	Manage profiles	Use to create or delete WebSphere Application Server profiles on remote targets.
`collectFile`	Collect file	Use to remotely retrieve files from remote targets to the Job Manager machine.
`distributeFile`	Distribute file	Use to transfer files from the Job Manager machine to remote targets.
`removeFile`	Remove file	Use to delete a file on remote targets.
`runCommand`	Run command on remote host	Use to run an operating system command or shell script on remote targets.
`testConnection`	Test connection	Test the connection between the Job Manager and remote targets.
`installSSHPublicKey`	Install SSH public key	Before you can use the SSH public and private key authentication, you need to install the public key to remote targets first. Use this job to install the pubic key to remote targets.
`findDataLocation`	Add or search for Installation Manager agent data locations	Use to find additional Installation Manager agent data locations on remote targets. This is for advanced users who need to use more than one agent data locations.

Initial Centralized Installation Manager setup

Install IBM Installation Manager.
Use IBM Installation Manager to install IBM WebSphere Application Server V8.0.

Create a Job Manager profile using the Profile Management Tool or manageprofiles.sh command:

test317:/opt/IBM/WebSphere/AppServer/bin # ./manageprofiles.sh -create -templatePath ../profileTemplates/management -serverType JOB_MANAGER

INSTCONFSUCCESS: Success: Profile JobMgr01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/JobMgr01/logs/AboutThisProfile.txt
for more information about this profile.

Start the Job Manager.

test317:/opt/IBM/WebSphere/AppServer/bin # ./startServer.sh jobmgr -profileName JobMgr01
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/JobMgr01/logs/jobmgr/startServer.log
ADMU0128I: Starting tool with the JobMgr01 profile
ADMU3100I: Reading configuration for server: jobmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server jobmgr open for e-business; process id is 34056

Open the Job Manager administrative console.

Figure 2.30. Job Manager administrative console

Locating Centralized Installation Manager

You can access CIM from several places:

CIM was integrated with the Job Manager in WebSphere Application Server V8.0. Installation functions are implemented as jobs in the Job Manager.
The figure below shows the Jobs section in the Job Manager's navigation panel. All of the CIM functions for installing WebSphere Application Server V8.0 or later are located in the Jobs section (Submit, Status, Targets, and so on).

Figure 2.31. Job Manager administrative console
The Job Manager functions are also available in the Deployment Manager (since V8.0). You can access the Job Manager functions by creating either a Deployment Manager profile or Job Manager profile.

Figure 2.32. Deployment Manager administrative console
There is also a Centralized Installation Manager group under the System Administration section in the Deployment Manager, which is where you find the CIM functions for managing V6.1 and V7.0 nodes. These functions are not available in the Job Manager profile.

Figure 2.33. Deployment Manager administrative console

Using Centralized Installation Manager

In order for CIM to perform operations on a remote host, you must register it with its credential:

From the console, expand the Jobs section and click Targets. Click the New Host button:

Figure 2.34.
Enter the Host name of the remote Linux machine; for example, test317.java.boot.by.
Enter a username for the Administrative user with installation authority field; for example, ilcbuild.
Select Password authentication and then enter and confirm your password.
[Optional] If the user does not have superuser authorities, you may want to configure sudo user.
To save the credential, check the Save security information checkbox. (If you choose to save the security information now, you will not need to enter it again during future job submission.)
Click OK.

Figure 2.35.

The hostname will be displayed in the table of the Targets panel.

Figure 2.36.

Prev	Up	Next
2.5. Perform pre-installation verification and troubleshoot the installation (e.g., identify and analyze log files, Installation Verification Tool (IVT)).	Home	2.7. Backup and restore a configuration.