New target settings (deprecated)

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 Jobs > Targets > New Host.

Host name

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.

Specify the host name value in one of the following formats:
  • Fully qualified domain name system (DNS) server host name string, such as xmachine.manhattan.ibm.com
  • Default short DNS host name string, such as xmachine
  • Numeric IP address, such as 127.1.255.3

Operating system

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.

Administrative user with install authority

Specifies a user name that provides access to the target host. The user must have the authority to log in to the target host.

Password authentication

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.

Use sudo

Specifies whether a substitute user can perform commands on the target host. sudo means substitute user do. Select this option to change users before a job runs. If you select Use sudo, specify the user name and password for the substitute user as needed. The following selection combinations are valid:
  • Select Use sudo, and leave the user name and sudo password blank. These selections use the default user that is set in the /etc/sudoers file and use the password of the connection user.
  • Select Use sudo, specify a user name, and leave the sudo password blank. These selections use the specified user and use the password of the connection user.
  • Select Use sudo, specify a user name, and specify a sudo password. These selection use the specified user and sudo password.
  • Use the same password for the Sudo password and Confirm sudo password fields. If the target host does not require a password, leave the password fields blank.
The default is not to use sudo. The sudo option is supported on AIX, HP-UX, Linux®, and Solaris operating systems only.

Public-private key authentication

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.

Save security information

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.

Installation Manager data location path(s)

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.

Avoid trouble: Ensure that the path is not longer than 256 characters. If the path is longer than 256 characters, the product truncates the path. The product does not warn you if the path is longer than 256 characters. You must check the length of the path. Truncated paths are not valid and, after validation checking, are removed from this field.
You can use the find data location job to search for data locations on the system. The find data location job automatically updates this property. For example:
AdminTask.registerHost('[-host hostname -hostProps [[imDataLocations datalocation1; datalocation2]
[password ****][saveSecurity true][username username]]]')