|
TCP/IP Services |
|
|
One or more TCP/IP Service may be defined, with the add tcpipservice directive. When XCICS region is alive, TCP/IP services may be controlled using xcicsadm. Syntax
name Name of the TCP service. port Number of the TCP port, where the service waiting for connections. terminal (Optional) Name of the virtual terminal where the task is to be started. server_pool If set to yes, the service forwards the transaction directly on the engines pool, instead of forking as every normal background process; protocol defines the protocol handled by the tcpip service. The protocol may be one of the following:
enabled If specified the service is automatically activated at XCICS start up time. This is the default behaviour. disabled If specified the service is not automatically activated at XCICS start up time. urm For HTTP and USER protocol only. Defines the name of the analyzer program to be started to handle HTTP and non-HTTP requests. ssl For HTTP and USER protocol only. If set to yes, the communication with the service will be encrypted over SSL (Secure Socket Layer) close_connection For HTTP and USER protocol only. Controls the usage of permanent connection. By default XCICS uses permanent connections. close_timeout For HTTP and USER protocol only. Defines the close timeout, in seconds, for permanent connections. auth For HTTP and USER protocol only. Defines the authorization method for the service.
For further information about the EZA-like and SOAP TCP services modes, please refer to the TCP Services. For further information about XCICS Web Interface, HTTP and user protocols, please refer to the XCICS Internet Guide. If no mode is specified, the BASIC mode is assumed by default. Example: add tcpipservice name=DEFAULT, port=8023; |