H.11 Differences between communication protocols of JP1/Base 06-51 or earlier and JP1/Base 06-71 or later
You can check which of the communication protocols is used, JP1/Base 06-51 or earlier or JP1/Base 06-71 or later, by referring to the JP1_COM_VERSION value in the common definition information. If JP1_COM_VERSION is set to 0, the system uses the communication protocol of JP1/Base 06-51 or earlier. If JP1_COM_VERSION is set to 1, the system uses the communication protocol of JP1/Base 06-71 or later.
For details on how to check the JP1/Base communication protocol, see 6.3.4 Checking the JP1/Base communication protocol.
Depending on the JP1_COM_VERSION setting, during communication, JP1/Base functionalities behave differently according to the value specified in each communication setting item.
The following table shows the behavior of each function during communication when the communication protocol of JP1/Base 06-51 or earlier is used.
|
Functionality |
Communication setting item |
|||||
|---|---|---|---|---|---|---|
|
JP1_BIND_ADDR |
JP1_CLIENT_BIND_ADDR |
COM_LISTEN_ALL_ADDR |
COM_MAX_LISTEN_NUM |
jp1hosts information |
jp1hosts2 information |
|
|
Configuration management |
Yes |
--#1 |
--#2 |
--#3 |
Yes |
Yes |
|
Command execution |
Yes |
--#1 |
--#2 |
--#3 |
Yes |
Yes |
|
User management |
Yes |
--#1 |
-- |
-- |
Yes |
Yes |
|
Collecting and distributing definitions |
Yes |
--#1 |
-- |
-- |
Yes |
Yes |
|
Health check |
Yes |
--#1 |
-- |
-- |
Yes |
Yes |
|
Service management control |
Yes |
--#1 |
-- |
-- |
Yes |
Yes |
|
Inter-process communication |
Yes |
--#1 |
-- |
-- |
Yes |
Yes |
|
Event service#4 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Event API (client)#5 |
-- |
--#6 |
-- |
-- |
-- |
Yes |
- Legend:
-
Yes: The value of the setting item is referenced.
--: The value of the setting item is not referenced.
#1: The functionality depends on the value specified in JP1_BIND_ADDR.
#2: The value 1 (bind to multiple IP addresses) is assumed.
#3: The value 16 (bind to 16 IP addresses) is assumed.
#4: The value of the setting item shown in the above table is referenced when <jp1hosts2> is specified in the address component of the ports and remote-server parameters of the event server settings file (conf).
#5: This functionality is used when registering and obtaining JP1 events to and from JP1/Base and other products such as JP1/IM. The value of the setting item shown in the above table is referenced when <jp1hosts2> is specified in the address component of the server parameter of the API settings file (api).
#6: The source IP address can by specified by using only the client parameter in the API settings file (api).
The following table shows the behavior of each function during communication when the communication protocol of JP1/Base 06-71 or later is used.
|
Functionality |
Communication setting item |
|||||
|---|---|---|---|---|---|---|
|
JP1_BIND_ADDR |
JP1_CLIENT_BIND_ADDR |
COM_LISTEN_ALL_ADDR |
COM_MAX_LISTEN_NUM |
jp1hosts information |
jp1hosts2 information |
|
|
Configuration management |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Command execution |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
User management |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Collecting and distributing definitions |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Health check |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Service management control |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Inter-process communication |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Event service#1 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Event API (client)#2 |
-- |
--#3 |
-- |
-- |
-- |
Yes |
- Legend:
-
Yes: Setting is referenced.
--: Setting is not referenced.
#1: The value of the setting item shown in the above table is referenced when <jp1hosts2> is specified in the address component of the ports and remote-server parameters of the event server settings file (conf).
#2: This functionality is used when registering and obtaining JP1 events to and from JP1/Base and other products such as JP1/IM. The value of the setting item shown in the above table is referenced when <jp1hosts2> is specified in the address component of the server parameter of the API settings file (api).
#3: The source IP address can by specified by using only the client parameter in the API settings file (api).