GAS Configuration Reference / Configuration file elements |
The INTERFACE_TO_CONNECTOR element specifies the connection between the GAS and the GAS Connector located with the Web server.
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.
<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>
The INTERFACE_TO_CONNECTOR element may contain the following child elements.
<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.
This element is a child of the APPLICATION_SERVER element.