Job Management Partner 1/Base User's Guide

1.10.1 Recommended communication protocol

On JP1/Base, the following binding methods are recommended for communication:

When running JP1/Base on a physical host only: ANY binding method.

In the ANY binding method, JP1/Base performs communication using only the port number without recognizing an IP address. The communication wait process ensures that data sent to all IP addresses assigned to the host are received. When handling connections, you can send data to hosts on all subnets even if the host uses several subnets.

JP1/Base might not be able to communicate with hosts properly if it is activated using the ANY binding method in a cluster system. For example, a logical host might receive data addressed to a physical host, or vice versa.

When using a logical host (using a cluster):IP binding method

In the IP binding method, if the host uses several IP addresses when two or more IP addresses are assigned to one NIC (Network Interface Card) or one host has more than one NIC, JP1/Base receives only data addressed to a particular IP address. When handling connections, JP1/Base sends data via only an NIC that uses a particular IP address.

When JP1/Base runs in a cluster system, physical and logical hosts might coexist on a single host or two or more logical hosts might be started simultaneously. In such a case, the IP binding method ensures that physical hosts receive only data destined to their IP addresses, and logical hosts receive only data destined to their IP addresses.

By default, the ANY binding method is selected as the communication protocol. The IP-binding method is applied to both physical and logical hosts when you set up JP1/Base for a cluster system as shown below:

In Windows, configure JP1/Base for the cluster system by using the GUI (jp1bshasetup.exe) or the command jbs_setup_cluster.

In UNIX, configure JP1/Base for the cluster system by using the command jp1base_setup_cluster.

Note

Once a host is set up for a cluster system, the communication protocol of physical hosts does not return to the ANY binding method even when all logical hosts are removed. To restore operation using physical hosts only, modify the communication protocol back to the ANY binding method as described in 4.3.3 Changing communication settings.

As an example, the illustrations below show how the communication waiting process changes when the JP1/Base communication protocol is the ANY or the IP binding method.

First, the following figure shows the communication waiting process when the communication protocol of JP1/Base is the ANY binding method.

Figure 1-27 Communication waiting process when JP1/Base is activated in the ANY binding method on hostA

hostA has an NIC to which IP addresses 10.0.0.10 and 10.0.0.11 are assigned. This host is assumed to be able to resolve its own host name only into IP address 10.0.0.10. (In fact, depending on the OS, the host might only be able to resolve one host name into one IP address.) hostX assumes that hostA is resolved by using IP address 10.0.0.10, and hostY assumes that hostA is resolved by using IP address 10.0.0.11.

When JP1/Base is activated in the ANY binding method on hostA, it can receive data from both hosts X and Y. In the ANY binding method, JP1/Base can receive data addressed to either 10.0.0.10 or 10.0.0.11 since it communicates with hosts by using only port numbers without considering IP addresses.

Next, the following figure shows the communication waiting process when the communication protocol of JP1/Base is the IP binding method.

Figure 1-28 Communication waiting process when JP1/Base is activated in the IP binding method on hostA

When JP1/Base is activated in the IP binding method on hostA, it receives only data addressed to 10.0.0.10, and cannot recognize data addressed to 10.0.0.11. This is because hostA does not accept data whose IP address is different from its own, even when the port numbers are the same.

[Contents][Back][Next]

[Trademarks]