INTERFACE_TO_CONNECTOR

The INTERFACE_TO_CONNECTOR element specifies the connection between the GAS and the GAS Connector located with the Web server.

Syntax

<INTERFACE_TO_CONNECTOR>
   [<ROOT_URL_PREFIX>...</ROOT_URL_PREFIX>] [...]
   [<LISTEN>...</LISTEN>] 
   <TCP_BASE_PORT>...</TCP_BASE_PORT>
   <TCP_PORT_OFFSET>...</TCP_PORT_OFFSET>
   <DOCUMENT_ROOT>...</DOCUMENT_ROOT>
   <GBC_LOOKUP_PATH>...</GBC_LOOKUP_PATH>
   <TEMPORARY_DIRECTORY>...</TEMPORARY_DIRECTORY> 
   <SESSION_DIRECTORY>...</SESSION_DIRECTORY>
   <REPORT_VIEWER_DIRECTORY>...</REPORT_VIEWER_DIRECTORY>
   [<REPORT_REMOTE_URL_PREFIX>...</REPORT_REMOTE_URL_PREFIX>]
   <SOCKET_FAMILY>...</SOCKET_FAMILY>
   <SOCKET_PATH>...</SOCKET_PATH>
   [<HTTP> ... </HTTP>]
</INTERFACE_TO_CONNECTOR>

Child elements

The INTERFACE_TO_CONNECTOR element may contain the following child elements.

  1. Zero or more ROOT_URL_PREFIX element.
  2. Zero or one LISTEN element.
  3. One TCP_BASE_PORT element.
  4. One TCP_PORT_OFFSET element.
  5. One DOCUMENT_ROOT element.
  6. One GBC_LOOKUP_PATH element.
  7. One TEMPORARY_DIRECTORY.
  8. One SESSION_DIRECTORY element.
  9. One REPORT_VIEWER_DIRECTORY element.
  10. Zero or one REPORT_REMOTE_URL_PREFIX element.
  11. One SOCKET_FAMILY element.
  12. One SOCKET_PATH element.
  13. Zero or one HTTP element.

Usage

You use the INTERFACE_TO_CONNECTOR element to define various configurations for the Genero Application Server, such as the port it listens to for incoming requests. This configuration applies for all GAS connectors including the standalone GAS (httpdispatch).

You can have several instances of the GAS running concurrently on the same host, but you need to make sure that each has a separate GAS configuration file with different connection configurations including port offsets. Once started, each application server listens at the offset specified.

Important: If you create multiple GAS configuration files, ensure that the port values are unique for each application server started. If two GAS 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.

Usage example

<INTERFACE_TO_CONNECTOR>
  <ROOT_URL_PREFIX></ROOT_URL_PREFIX>
  <LISTEN></LISTEN>
  <TCP_BASE_PORT>6300</TCP_BASE_PORT>
  <TCP_PORT_OFFSET>94</TCP_PORT_OFFSET>
  <DOCUMENT_ROOT>$(res.path.docroot)</DOCUMENT_ROOT>
  <GBC_LOOKUP_PATH>$(res.path.gwcjs.user);$(res.path.docroot)</GBC_LOOKUP_PATH>
  <TEMPORARY_DIRECTORY>$(res.path.tmp)</TEMPORARY_DIRECTORY>
  <SESSION_DIRECTORY>$(res.appdata.path)/session</SESSION_DIRECTORY>
  <REPORT_VIEWER_DIRECTORY>$(res.gredir)/viewer</REPORT_VIEWER_DIRECTORY>
  <SOCKET_FAMILY>$(res.dispatcher.socket.family)</SOCKET_FAMILY>
  <SOCKET_PATH>$(res.dispatcher.socket.path)</SOCKET_PATH>
  <HTTP/>
</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).

Parent elements

This element is a child of the APPLICATION_SERVER element.