21.8.3 Environment in which each container requires a different port number for communication

There might be an environment in which JP1/AJS3 - Agent is deployed for each container of the container orchestration system or container management software and communication to each container is performed with a different port number from external hosts. In such an environment, the destination port mapping function of JP1/Base must be used on the external hosts that communicate to the containers. For details about the destination port mapping function, see 2.12.2(4) Destination port mapping function in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

The procedure for setting up the destination port mapping function is as follows:

Edit the destination communications port settings file (jp1_destport.conf).

Create the destination communications port settings file by editing its model file (jp1_destport.conf.model). In the initial settings of the model file, all lines are commented out by prefixing a hash mark (#). If necessary, delete the hash marks (#) and change the port numbers from the default values. A port number specification is required for each container. An example of editing the file is as follows:

Before the change:
```
#
# jp1_destport.conf
#
#[container1]
#jp1ajs2qagt    20242     # To send job execution requests to JP1/AJS3 - Agent
#jp1ajs2eaagt   20247     # JP1/AJS3 - Agent event job execution
#jp1ajs2chkagt  23139     # To use the definition pre-check function
#jp1ajs2qlagt   20300     # To use queueless jobs(For queueless job execution by JP1/AJS3 - Agent)
#jp1ajs2atmsg   22251     # Flexible job execution
#jp1ajs3sysctla 22257     # To use the Web GUI (Management Portal)
#jp1imevt       20098     # Transferring JP1 events to another host
```
After the change:
```
#
# jp1_destport.conf
#
[container1]
jp1ajs2qagt    30242     # To send job execution requests to JP1/AJS3 - Agent
jp1ajs2eaagt   30247     # JP1/AJS3 - Agent event job execution
jp1ajs2chkagt  33139     # To use the definition pre-check function
jp1ajs2qlagt    30300     # To use queueless jobs(For queueless job execution by JP1/AJS3 - Agent)
jp1ajs2atmsg   32251     # Flexible job execution
jp1ajs3sysctla  32257     # To use the Web GUI (Management Portal)
jp1imevt       30098     # Transferring JP1 events to another host
 
[container2]
jp1ajs2qagt    31242
jp1ajs2eaagt   31247
jp1ajs2chkagt  34139
jp1ajs2qlagt   31300
jp1ajs2atmsg  33251
jp1ajs3sysctla  33257
jp1imevt       31098
```
For details about how to edit the destination communications port settings file, see the JP1/Base User's Guide.

Cautionary note:

When defining a destination communication port by using the jbsdestpimport command, ensure that no jobs are being executed on the target container. Defining the destination port while jobs are running can cause communication failures with the target container, resulting in jobs ending abnormally or command execution failures.

Additionally, it may take up to 30 seconds for the definition of the destination port for services used by queueless jobs (jp1ajs2qlagt) to take effect. Therefore, avoid executing queueless jobs on the target container immediately after defining the destination port.
Execute the jbsdestpimport command.

For details about the jbsdestpimport command, see the JP1/Base User's Guide.

To check the information registered by the jbsdestpimport command, execute the jbsdestpexport command. For details about the jbsdestpexport command, see the JP1/Base User's Guide.
Enable the destination port mapping function (if it has not been enabled).

For details about how to enable the destination port mapping function, see 21.8.6 Settings for using the destination port mapping function.

To Page Top