1.12 Managing Connection Destinations
In JP1/AO, the host to which a service connects to perform operations is called a Connection Destination. By registering Connection Destination definitions in JP1/AO, when services are submitted for execution, you can restrict access to Connection Destinations based on the service group to which a task belongs.
Note that you need to specify the following to agentless remote connections:
-
Operation targets of general command plug-ins
-
Operation targets of file-transfer plug-ins
-
Operation targets of terminal-connection plug-ins
-
Execution target server of content plug-ins
- Important
At installation, JP1/AO provides a Connection Destination definition that allows services in the DefaultServiceGroup service group to connect to all connection destination hosts. This means that the connection destinations of services in the DefaultServiceGroup group are not restricted in any way.
To restrict the hosts to which tasks can connect, you need to edit or delete the Connection Destination definition created at installation, and register new definitions that permit connections only to specific hosts.
To use the features for managing Connection Destinations, register the Connection Destinations to which you want to allow access in the Connection Destination(s) area. You can then edit the registered Connection Destinations as needed.
Connection Destination management in JP1/AO involves the following:
- Creating Connection Destination definitions
You can create and register Connection Destination definitions.
The definition of a Connection Destination consists of connection information such as a host name or IP address, and authentication information such as the user ID and password used to log in to the host.
- Editing Connection Destination definitions
You can edit the contents of Connection Destination definitions registered in JP1/AO.
- Deleting Connection Destinations
You can delete registered Connection Destinations.