Use this page to register a remote computer as a target with the job manager. To register a target with the job manager, you must be authorized for the administrator role.
To view this administrative console page, click
.Specifies the name of the computer that you want to register as a target with the job manager. The target host must be a remote computer.
Specifies the operating system of the target host. The default value is Any for any operating system. Other supported values are AIX, HPUX, IBM i, IBM zOS, Linux, Solaris, and Windows. Specifying the correct operating system value enables operations to run faster.
Specifies a user name that provides access to the target host. The user must have the authority to log in to the target host.
Specifies the password for the user name on the target host. Specify the same password for the Password and Confirm password fields.
If the target host does not require a password, leave the fields blank.
Specifies the full path to the keystore and, if required for the keystore, the passphrase.
To use public-private key authentication, first generate a pair of keys using a key generation tool such as ssh-keygen. Next, add the public key to the authorized_keys file of the user on the target host. Then, on this page, specify the user name, fully qualified private key file, and optionally the fully qualified passphase.
Specifies whether to save the security information that is entered on this page. The host uses any saved properties as defaults for subsequent job submissions to the host.
The default is not to save security information.
Specifies one or more paths on the host to use as the Installation Manager data location. The default is not to specify a data location path.
Enter the fully qualified path of the Installation Manager data locations. You can enter multiple paths separated by a semi-colon. This property is useful if you have non-default Installation Manager data locations on your targets. For example, if you specified data locations when installing Installation Manager, the inventory job might not find the non-default data locations. Therefore, you might need to specify additional data locations when registering a host. If an unsupported data location is specified, it is not saved. If the specified data location can be detected by the inventory job, it is not saved.
AdminTask.registerHost('[-host hostname -hostProps [[imDataLocations datalocation1; datalocation2][password ****][saveSecurity true][username username]]]')