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

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

To work with the centralized installation manager through the command line, you can use the

AdminTask object by invoking it from the wsadmin script from the deployment manager host.

Example 29-2 presents a Jython example of AdminTask object usage. In this example, a

connection test is made with target host yourhost.com from the deployment manager to check

if the connection is active.

Example 29-2 AdminTask command used for connection test on WebSphere Application Server V7

AdminTask.testConnectionToHost ('[-hostName yourhost.com

-platformType linux -adminName root -adminPassword password]')

29.5 Managing V8 release environments with the centralized

installation manager

Managing the full lifecycle of WebSphere Application Server V8 release environment using

the centralized installation manager consists of the following steps:

1. Define your targets.

2. Install Installation Managers on targets.

3. Install the product.

4. Create profiles.

5. Register with job manager.

6. Work with environment.

29.5.1 Adding new targets

To register a new target:

1. Start the job manager or deployment manager and the targets. In the web console, click

Jobs  Targets  New Host.

2. Supply the form presented in Figure 29-4 on page 1013 with the host name of your target

and its operation type. Specify the user that will be used for product installation and

management, or select to use a public/private key pair to authenticate to the target. If you

select a non-root user, be sure that this account allows you to install the product. Refer to

29.1.4, “Additional requirements” on page 1003 for more information about this topic.

3. You can also select the Save security information option to save the credentials together

with the host. This action eliminates supplying the credentials each time you submit a job

to that host.

4. In the

Installation Manager data location path(s) field, you can also supply paths on the

target host to the Installation Manager installation directory. If there is no Installation

Manager on that host, leave this field blank. If the Installation Manager was not installed in

the standard location (during installation, a custom path was given), use the custom path

in this field. This action helps the centralized installation manager to obtain which

Note: The AdminTask object uses different methods and parameters when working with the

centralized installation manager for WebSphere Application Server V8 releases than for

V6.1 or V7. For more information about the available methods, refer to 29.6.11, “The

centralized installation manager AdminTask commands” on page 1053.

Note: Not every step is required when working with the centralized installation manager. It

depends on your WebSphere Application Server environment and if you are working with

existing installations or creating a new environment.

Chapter 29. Managing an environment with the centralized installation manager 1013

Installation Manager it must use on the target. Path information helps because the

inventory job that the centralized installation manager uses to detect the installed

WebSphere software, might not be able to locate the Installation Manager product.

Figure 29-4 shows the window used to create a new target.

5. Click OK to save the target.

Figure 29-4 New target definition

Complete the following steps to list the available resources discovered by the centralized

installation manager on the target:

1. Click Jobs  Targets.

2. Select the check boxes next to your targets, and click the Display Resources button.

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

3. In the pop-up menu, select All to see all available resources, as shown in Figure 29-5.

Note that not all targets contain the version information. Targets that have versions are

managed nodes registered in the job manager, such as deployment manager or

administrative agent servers, and the version is their product version level. Targets that are

just added as new targets do not contain this information.

Figure 29-5 Listing resources on targets

Discovered resources are displayed (Figure 29-6 on page 1015). If your target does not

contain any WebSphere Application Server or Installation Manager products, the list is empty.

You can also filter the resources you want to see by selecting a different Display Resources

option, for example, limited only to Applications.