The INTERFACE_TO_CONNECTOR element

The INTERFACE_TO_CONNECTOR element specifies the interface to the Genero Application Server (GAS) Connector. It specifies the connection between the GAS and the GAS Connector (located with the Web Server).

The GAS Connector is either:

The INTERFACE_TO_CONNECTOR element defines the port on which the Genero Application Server listens for incoming requests. This applies for the httpdispatcher (stand-alone GAS) as well as the GAS Connectors.

Syntax

<INTERFACE_TO_CONNECTOR>
  <TCP_BASE_PORT> base </TCP_BASE_PORT> 
  <TCP_PORT_OFFSET> offset </TCP_PORT_OFFSET>
  <LIMIT_REQUEST_SIZE>  </LIMIT_REQUEST_SIZE>
  <DOCUMENT_ROOT> root </DOCUMENT_ROOT>
  <TEMPORARY_DIRECTORY> dir </TEMPORARY_DIRECTORY>
  [ <SESSION_DIRECTORY> dir </SESSION_DIRECTORY> ]
  <SOCKET_FAMILY> dir </SOCKET_FAMILY>
  <SOCKET_PATH> dir </SOCKET_PATH>
  [ <ERROR_DOCUMENT Code="code"> path </ERROR_DOCUMENT> ]
</INTERFACE_TO_CONNECTOR>

Child elements

The INTERFACE_TO_CONNECTOR element may contain the following child elements.

  1. One TCP_BASE_PORT element.
  2. One TCP_PORT_OFFSET element.
  3. One LIMIT_REQUEST_SIZE element.
  4. One DOCUMENT_ROOT element.
  5. One TEMPORARY_DIRECTORY.
  6. Zero or one SESSION_DIRECTORY element.
  7. One SOCKET_FAMILY element.
  8. One SOCKET_PATH element.
  9. Zero or more ERROR_DOCUMENT element.

Example

<INTERFACE_TO_CONNECTOR>
  <TCP_BASE_PORT>6300</TCP_BASE_PORT>
  <TCP_PORT_OFFSET>94</TCP_PORT_OFFSET>
  <LIMIT_REQUEST_SIZE>0</LIMIT_REQUEST_SIZE>
  <DOCUMENT_ROOT>$(res.path.docroot)</DOCUMENT_ROOT>
  <TEMPORARY_DIRECTORY>$(res.path.tmp)</TEMPORARY_DIRECTORY>
  <SOCKET_FAMILY>$(res.dispatcher.socket.family)</SOCKET_FAMILY>
  <SOCKET_PATH>$(res.dispatcher.socket.path)</SOCKET_PATH>
  <SESSION_DIRECTORY>/var/tmp</SESSION_DIRECTORY>
</INTERFACE_TO_CONNECTOR>

In this example, the application server is listening on port 6394 (TCP_BASE_PORT + TCP_PORT_OFFSET), the application server web site root is specified as the resource $(res.path.docroot).

To have several instances of the Genero Application Server run concurrently on the same host, you create several application server configuration files with different offsets. Once started, each application server listens at the offset specified.

Important: If you create multiple application configuration files (one for each instance of the application server), take care to ensure that the port values are unique for each application server started. If two application server configuration files both specify the same TCP_BASE_PORT and TCP_BASE_OFFSET, a port conflict exists. The second application server will not start, an error message displays (Application Server startup........[fail]) and the message "Address already in use" is written to the log file.