Non-SSL communication host configuration file
- Organization of this page
Format
|
[NO_SSL_HOST] non-SSL communication host name-1 non-SSL communication host name-2 : |
Parameters by type
- Required parameters:
-
None
- Custom parameters:
-
Non-SSL communication host name
File name
jp1bs_nosslhost.conf (non-SSL communication host configuration file)
jp1bs_nosslhost.conf.model (model file of a non-SSL communication host configuration file)
Storage destination directory
- In Windows:
-
installation-folder\conf\
- In UNIX:
-
/etc/opt/jp1base/conf/
Description
This file is used to set destination and originating hosts that do not perform SSL communication in an environment where the communication encryption function (SSL communication) is enabled. The settings specified in this file are applicable to physical hosts, logical hosts, and event services.
In an environment where SSL communication is enabled, SSL communication is used to access hosts not specified in this file. Even when this file does not exist, SSL communication is used between the destination host and the originating host.
Application of settings
After editing the non-SSL communication host configuration file, start or restart JP1/Base services and event services to apply the settings specified in the file.
Definition details
Specify the names of the destination and originating hosts that do not perform SSL communication. The following rules apply to the non-SSL communication host configuration file:
-
A hash mark (#) (code 0x23) at the start of a line indicates a comment.
-
Each line must end with a linefeed character.
-
You can use ASCII characters only.
-
You cannot use the following characters:
" / \ [ ] ; : | = , + ? < >
-
Define one host name in each line.
The host names are case-insensitive and must be 255 bytes or less.
Single-byte spaces or tabs specified at the beginning or end of a host name are ignored.
-
You can define a maximum of 100 hosts.
-
If you specify the same host name multiple times, only the first value specified becomes valid.
Note
The non-SSL communication host configuration file is referenced by physical hosts, logical hosts, and any event services. It is therefore important to ensure that reliable communication can be maintained even when the non-SSL communication host configuration file is edited by mistake while it is in use. To this end, three generations of non-SSL communication host configuration file with a generation number assigned to each one of them as well as the non-SSL communication host configuration file with all errors removed from it are saved upon the startup of JP1/Base and event services. Do not delete the saved files.
|
For Windows |
For UNIX |
|
|---|---|---|
|
When JP1/Base is started |
|
|
|
When event services are started |
|
|
When the non-SSL communication host configuration file contains an error, JP1/Base services and event services ignore the line containing the error and start up after outputting only the KAVB3920-W or KAJP1510-W message to the log.
Definition examples
Examples of a definition (or definitions) in a non-SSL communication host configuration file are provided below.
- When SSL communication takes place during communication with all hosts:
-
To use encrypted communication during communication with all hosts, define only the [NO_SSL_HOST] line.
[NO_SSL_HOST]
- When both non-SSL communication and SSL communication take place during communication with a specific host:
-
Non-SSL communication takes place during communication with hostA and SSL communication takes place during communication with all the other hosts.
[NO_SSL_HOST] hostA