INTERFACE_TO_CONNECTOR

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

The GAS Connector is either:
  • The FastCGI extension
  • The ISAPI extension
  • User agent through direct connection

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

Syntax

<INTERFACE_TO_CONNECTOR>
  [<ROOT_URL_PREFIX>URL_Web_Server_behind_proxy</ROOT_URL_PREFIX>] [...]
  <TCP_BASE_PORT> base </TCP_BASE_PORT>
  <TCP_PORT_OFFSET> offset </TCP_PORT_OFFSET>
  <DOCUMENT_ROOT> [docroot [;...] </DOCUMENT_ROOT>
  <GBC_LOOKUP_PATH> [path [;...] </GBC_LOOKUP_PATH>
  <TEMPORARY_DIRECTORY> dir </TEMPORARY_DIRECTORY> 
  <SESSION_DIRECTORY> dir </SESSION_DIRECTORY>
  <REPORT_VIEWER_DIRECTORY>dir</REPORT_VIEWER_DIRECTORY>
  [<REPORT_REMOTE_URL_PREFIX>URL_GRE_server</REPORT_REMOTE_URL_PREFIX>]
  <SOCKET_FAMILY> dir </SOCKET_FAMILY>
  <SOCKET_PATH> dir </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. One TCP_BASE_PORT element.
  3. One TCP_PORT_OFFSET element.
  4. One DOCUMENT_ROOT element.
  5. One GWC_JS_LOOKUP_PATH element.
  6. One TEMPORARY_DIRECTORY.
  7. One SESSION_DIRECTORY element.
  8. One REPORT_VIEWER_DIRECTORY element.
  9. One SOCKET_FAMILY element.
  10. One SOCKET_PATH element.
  11. Zero or one HTTP element.

Example

<INTERFACE_TO_CONNECTOR>
  <ROOT_URL_PREFIX></ROOT_URL_PREFIX>
  <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).

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

Important: If you create multiple GAS 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.

Parent elements

This element is a child of the APPLICATION_SERVER element.