1.12.3 List of definition parameters for connection destinations
Connection destination definitions consist of the following two types of information:
-
Connection destination information
Permits connection to the connection destination. You must specify this setting if you intend to submit a service belonging to a resource group other than All Resources to connect to the connection destination.
-
Authentication information
This information is used for authentication of connection destinations. You do not need to specify this setting if you do not specify authentication information as connection destination definitions.
The following table shows the parameters you can set when creating a definition for a connection destination.
Category |
Item |
Description |
---|---|---|
Connection destination information |
Resource Group for Service |
Specify the resource group name to associate with the connection destination. Services in this resource group only have access to connection destinations specified in the Destination field. If you specify All Resources, all services in All Resources will have access to all connection destinations. |
Type |
Select one of the following:
|
|
Destination |
Specify connection destinations in a format that matches the destination type. You can specify connection destinations in three ways:
|
|
Authentication information#2 |
Protocol |
Select one of the following authentication protocols to use when communicating with the connection destination host:
|
SSH authentication method |
Specify the authentication method to use when communicating with the connection destination host. Specify one of the following methods if you select SSH as the protocol:
|
|
User ID |
Specify the user ID of a user capable of remote login to the connection destination host. Specify domain user accounts in one of the following formats:
|
|
Password |
Specify the password corresponding to the user ID. You must specify the password if one of the following conditions applies:
|
|
Superuser password#3 |
Specify the password for the superuser account at the connection destination host when you select SSH or Telnet for the protocol. Specification of the password for the superuser account varies depending on the definitions for the service template (whether to execute the command line or file transfer processing as a user with root privileges). Check the specifications of the service template and plug-ins to use. |
- #1
-
If the host name resolves to more than one IP address, JP1/AO allocates uses all of the IP addresses as the connection destination.
- #2
-
Set only one authentication information item for each connection destination. If you specify more than one authentication information item for the same connection destination, the authentication might fail.
- #3
-
-
For the General command plug-in, file-forwarding plug-in, and content plug-in, if the device to use runs on UNIX, use SSH for connection. To use SSH for connection, log in as the user specified for the user ID of authentication information. After the login, if you are prompted to elevate to a root user, edit authentication information (superuser password). The method for specifying whether to elevate to a root user varies depending on plug-ins.
-
For the General command plug-in and file-forwarding plug-in
Specify either true (elevate to a root user) or false (do not elevate to a root user) for the elevatePrivileges plug-in property.
-
For the content plug-in
To elevate to a root user, open the Create Plug-in or Edit Plug-in dialog box, and then select the Execute by using root privileges (for SSH connections). or Enabled check box. Do not select either check box if you do not want to elevate.
-
-
For the terminal command plug-in, if you specify the reserved.terminal.suPassword reserved property as the command value of the commandLine plug-in property, specify the superuser password.
-
For the General command plug-in, file-forwarding plug-in, and content plug-in, if you want to use SSH as the protocol for the connection with the connection destination, conditions exist for the shell specified as the default of the connection destination. The condition varies depending on whether to elevate to a root user. Specify as follows:
-
When elevating to a root user
Set the default shell of the connection user and the root user to sh, bash, ksh, csh, or tcsh.
-
When you do not want to elevate to a root user
Set the default shell of the connection user to sh, bash, ksh, csh, or tcsh.
-
-
Related topics
-
General command plug-in, File-forwarding plug-in, and Terminal command plug-in in the manual Job Management Partner 1/Automatic Operation Service Template Reference