![[Note]](images.admon/note.gif) | |
|
The centralized installation manager
The centralized installation manager (CIM) simplifies the installation and maintenance of application servers.
As an administrator, from the Deployment Manager or the Job Manager you can remotely install or uninstall product packages and apply maintenance to specific nodes directly from the administrative console. Use this process to avoid having to log in and repetitively perform these tasks. Using the centralized installation manager, you can reduce the number of steps that are required to create and manage the environment. This reduction can simplify installation and patch management.
The centralized installation manager does not replace the product installation wizard for WebSphere Software. As shown in figure below, the centralized installation manager remotely drives IBM Installation Manager to run installations and maintenance.
Accessing the centralized installation manager
You can access the centralized installation manager in WebSphere Application Server V8.5 releases from the following interfaces:
The job manager console
The deployment manager console
The
AdminTaskobject fromwsadmin.sh
The console for the centralized installation manager tools is available under the Jobs menu and is accessible from the job manager or deployment manager for WebSphere Application Server V8 releases. Figure below shows the following menu options in the job manager or deployment manager console:
Submit: Prepares and submits jobs to one or more targets.
Status: Displays a current status of submitted jobs.
Targets: Lists defined targets and allows you to create new targets.
Target resources: Lists target resources, which is useful when working with target groups.
Target groups: Lists and defines target groups.
Installation Manager installation kits: Configures the Installation Manager installation kit repository.
You can also work with the centralized installation manager using the command line. You can
use the AdminTask object by invoking it from the wsadmin script from the job manager or the
deployment manager host. Example below presents a Jython example of the AdminTask object
usage. In this example, a testConnection job type invokes the target to verify that the
connection between job manager or deployment manager and java.boot.by is active.
AdminTask.submitJob('-jobType testConnection -targetList [java.boot.by]' -username admin -password admin)
Installing Installation Manager on remote targets
With defined targets, you can install the Installation Manager on those targets. Complete the following steps to prepare your Installation Manager installation kit for use on your targets:
Download the compressed Installation Manager copy valid for your target operating system to your local machine.
Click Jobs > Installation Manager installation kits.
Optionally, if you want to change the default local directory where the job manager or deployment manager keeps binaries, enter the path under Installation Manager installation kits location. By default, it is the
profile_home/IMKitsdirectory, whereprofile_homeis your job manager or deployment manager profile directory.Click Add, and point to the Installation Manager compressed file on your local machine. The Installation Manager installation kit is transferred to the job manager or deployment manager and registered in its repository.
After you complete these steps, a view similar to figure below is displayed:
To delete the Installation Manager installation kit, select it from the list shown in figure above and click the Delete button. The compressed file with the Installation Manager will be deleted from the server.
You can install additional versions of Installation Manager for other platforms of your choice that are supported by the Installation Manager. Each of them is kept in the Installation Manager installation kit directory.
Complete the following steps to proceed with the installation of Installation Manager on remote targets:
Click Jobs > Submit from the Jobs navigation section.
From the drop-down menu, choose the Install IBM Installation Manager job, and click Next.
Choose the job targets:
Select a group of targets from the list, or select Target names.
If you selected Target names, specify a target name, and click Add, or click Find, and specify the chosen targets in the Find targets window.
If user authentication is required, specify a user name, password, or any other authentication values as needed:
Click Next.
Because you specified the Installation Manager installation kit in the previous step, you can leave the The path and file name of Installation Manager kit field empty, as shown in figure below. Configuring the Installation Manager installation kit before submitting the job is also useful because when you install the Installation Manager on a group of targets (consisting of different platforms), the Installation Manager automatically uses an appropriate Installation Manager installation kit for each target.The automatic function does require that the Installation Manager has a valid copy for the given platform, so providing a static directory only works for single targets.
You can also leave the Installation Manager agent data location and Installation Manager installation directory empty if you want to use the default Installation Manager install directory.
To proceed to the next step, accept the terms in the license agreements by selecting I accept the terms in the license agreements. To review the license, extract the Installation Manager installation kit and from the extraction point location run the
install.execommand for Windows systems orinstallcommand for AIX, Linux or Solaris operating systems. You can also runinstallc -cto review the license in text mode.Click Next to continue.
If you want to schedule this job to run at a specified time, you can use this step to define specific dates and times. You can also specify the job to run on a given basis, such as daily or weekly. To just install the product, leave the form with its defaults with Availability interval selected to Run once, and click Next.
Figure below shows the available configuration options of this step:
Review the summary and then click Finish to submit the job.
After you submit the job, a unique identifier is allocated to it to track the job status. The administrator can always return to the Jobs > Status view to track the job progress:
If the job is successful or it fails, additional messages and files might be shown. If files are present, you can click them to see the full path to the file on the target. This path can be used to locate the file and obtain it using a Collect file job. In case of an error, investigate the error message or file, correct the condition that caused the error, and submit the job again.
