2.9 Destination communications port specification function
You can change the destination communications port information for the destination container in order for JP1/Base to run JP1/AJS-Agent on Kubernetes, OpenShift, and other port forwarded environments. However, destination communications port information can only be set for the following services.
|
No. |
Product name |
Service name |
Purpose |
|---|---|---|---|
|
1 |
JP1/AJS3 - Agent |
jp1ajs2qagt |
To accept job execution requests To accept requests to confirm the operating status of jobs To accept requests to check the status of jobs |
|
2 |
jp1ajs2eaagt |
JP1/AJS3 - Agent event job execution |
|
|
3 |
jp1ajs2chkagt |
To use the definition pre-check function Used by the definition pre-check function |
|
|
4 |
jp1ajs2qlagt |
To use queueless jobs For queueless job execution by JP1/AJS3 - Agent |
|
|
5 |
jp1ajs2atmsg |
Flexible job execution |
|
|
6 |
jp1ajs3sysctla |
To use the Web GUI (Management Portal) For accepting communications from the JP1/AJS3 System Control Manager service |
|
|
7 |
JP1/Base |
jp1imevt |
To use when forwarding JP1 events to other hosts |
Commands related to destination communications port information set to the destination container include the following:
-
jbsdestpimport (Setting the destination communications port)
-
jbsdestpexport (Outputs of destination communications port setting information)
For details on these commands, see jbsdestpimportand jbsdestpexport in 15. Commands.
For details on the Kubernetes container system configuration and how to use the destination communications port specification function, see the manual JP1/Automatic Job Management System 3 System Design (Configuration) Guide or JP1/Automatic Job Management System 3 Configuration Guide.
- Organization of this section