NonStop Server for Java 7.0 Programmer's Reference
Mapping file
When the JI library is loaded, it searches for a mapping file to determine what sockets and channels
need to use NonStop IPC. The mapping file contains key value pairs delimited by <space>.
The JI library searches for the mapping file in the following sequence:
1. Java System Property: The JI library searches for a system property by name
ji.mapping.file. For example,
java -Dji.mapping.file=/usr/home/ji.prop
2. Environment variable JI_MAPPING_FILEFor example, export
JI_MAPPING_FILE=/usr/home/ji.prop
The value can either be an absolute path to the mapping file or it can be a relative path. The path
is relative to the current working directory (CWD).
Key
The key in the mapping file contains three parts and is of the format
{client_socket|server_socket}-<host name>:<port number>
where,
client_socket|server_socket
indicates if the entry is for a client socket or a server socket.
If the key begins with the string client_socket, the JI library assumes that the
mapping is for a client socket.
If the key begins with the string server_socket, the JI library assumes the mapping
is for a server socket.
hostname
In case of a client_socket, the host name indicates the destination address
where the socket is intended to connect.
In case of a server_socket, the host name indicates the address on which the
socket is intended to bind.
The value of the host name is the output of
address.getAddress().getHostName(), where address is an instance of
the class java.net.InetSocketAddress.
port number
In case of a client_socket, this is the port number the client socket connects
to.
In case of a server_socket, this is the port on which the server sockets bind.
Value
The value in the mapping file contains information on where (a standalone process or a TS/MP
server class) the client socket must connect to, and the conditions that the server socket evaluates
to accept new connections and modes of communication. While the key in the mapping has a
common format for both client and server sockets, the format of the value differs. The value is a
set of name=value pairs delimited by a : (colon).
Table 11 (page 77) lists all the attributes relevant for a client socket. Some attributes are relevant
for Pathsend IPC, while some others are relevant for File System IPC. All attribute names and values
are case sensitive.
76 Java infrastructure










