2.12.2 Prerequisites, restrictions, and estimation of required system resources for installing JP1/AJS3 - Agent in containers
This section shows the prerequisites and restrictions that apply when installing JP1/AJS3 - Agent in containers and describes how to estimate the system resources required for the installation.
- Organization of this subsection
(1) Prerequisites for installing JP1/AJS3 - Agent in containers
(a) Supported OSs
For the requirements for the container host machine used when JP1/AJS3 - Agent is installed in a container and the OSs supported within the containers, see the Release Notes.
(b) Supported container management software
The following software products can manage containers in which JP1/AJS3 - Agent can be installed:
-
Docker
-
Podman
(c) Network environment
If a container in which JP1/AJS3 - Agent is installed needs to link with a host other than the container host machine, make sure that TCP/IP communication can be performed between the container and host in both directions. For details about the setup procedure for a container to communicate with a host other than the host machine via TCP/IP communication, see the JP1/Base User's Guide.
If each container requires a different port number for communication, you must use the destination port mapping function of JP1/Base. For details about destination port mapping function, see (4) Destination port mapping function.
(2) Restrictions when JP1/AJS3 - Agent is installed in containers
The following shows the restrictions that apply when JP1/AJS3 - Agent is installed in containers:
-
JP1/AJS3 services can start on either the physical host only or logical host only in a single container.
-
JP1/AJS3 can be installed in containers and on the container host machine.
Note, however, that in this case, the version of JP1/AJS3 installed on the container host machine must be 12-60 or later.
-
In containers, only the following jobs can be used:
-
Unix job#
-
QUEUE job
-
Flexible job
-
HTTP connection job
-
Receive JP1 Event job
-
Monitoring Files job
-
Receive Mail job
-
Monitoring Log Files job
-
Interval Control job
-
Send JP1 Event job#
-
Send Mail job#
- #
-
Queueless Agent can also be specified for Exec. Service.
-
(3) Estimating the system resources required to install JP1/AJS3 - Agent in containers
Before you install JP1/AJS3 - Agent in a container, estimate the system resources that will be used on the agent host that will operate inside the container. Then, add the estimated system resources to the system resources that are used on the container host machine. The values to be added are the same as the values of the system resources on the physical host. If you create multiple containers on one host machine, you must add the estimated system resources for each container. For details about the system resources used by JP1/AJS3 - Agent, see the Release Notes.
(4) Destination port mapping function
The destination port mapping function allows the user to specify the numbers of ports that are used for communications from the manager host to agent hosts and for communications between agent hosts (by using a flexible job). If this function is used, hosts outside containers become able to communicate with hosts inside the containers even in an environment in which each container requires a different port number for communication.
The following figure shows an overview of connections by using the destination port mapping function in an environment in which each container requires a different port number for communication.
|
|
![[Figure]](GRAPHICS/ZH020720.GIF)
As the example in the preceding figure shows, use the destination port mapping function to specify a different port used for communication from the manager host for each container. Then, in the container management software or container orchestration system, specify the port forwarding settings so that the communication to each specified port is forwarded to the JP1/AJS3 - Agent reception port in the corresponding container.
For details about how to specify the settings of the destination port mapping function, see 21.8.3 Environment in which each container requires a different port number for communication in the JP1/Automatic Job Management System 3 Configuration Guide. For details about how to enable the destination port mapping function, see 21.8.6 Settings for using the destination port mapping function in the JP1/Automatic Job Management System 3 Configuration Guide.