Configure the SOAP and WLP Servers

The Data Management Server manages client connections using multiple threads. By default, a SOAP server communicates with clients. To enhance performance, you can enable a second server that listens for client connections at a separate port. The two servers run as separate threads in a single process. Both servers spawn new threads to connect to clients, using a shared thread pool. The two servers are defined as follows.

The SOAP server uses a SOAP interface, as defined in the DataFlux Web Service Definition Language (WSDL) file. For more information about the WSDL file, see Customize the Server’s WSDL File.

The Wire-Level Protocol (WLP) server uses a proprietary WLP client library. WLP offers a significant performance increase over SOAP, especially for real-time data services that require significant amounts of data transfer. The WLP server is disabled by default. When it is enabled, the WLP server is used with the SAS programs that include the procedure DMSRVDATASVC, and all functions. In SAS programs, WLP is enabled by setting the system option DQOPTIONS=(DQSRVPROTOCOL=WIRELINE). WLP is used primarily in the z/OS operating environment, where it is a required replacement for SOAP.

The Data Management Server processes a single SOAP request per client connection. After the server returns a response, the connection is closed. This is true even if the client attempts to make a persistent connection by including Connection: Keep-Alive (for HTTP 1.0) or by omitting Connection: close (for HTTP 1.1). The connection parameters are specified in the HTTP header of the SOAP request.

To manage the configuration of the SOAP and the WLP servers, set the following configuration options.

Configuration Option	Description
DMSERVER/SOAP/LISTEN_HOST	Specifies the host name or IP address to which the SOAP server must bind. A machine running Data Management Server might be available on the network under different host names or IP addresses. Different machines on the network might have access to this machine via one host name or IP address, but not via others. By binding to a particular host name or IP address, the server hears only requests addressed specifically to that host name or IP address. A pair of host names and IP addresses can be used interchangeably. For example, if this option is set to localhost, local clients sending requests to 127.0.0.1 will still be heard. However, requests to public IP address or the host name of the machine (or requests coming from external clients to the machine) will not be heard. By default, this option is left blank. That means Data Management Server is not bound to any specific host name or the IP address of the machine and receives all requests that are coming to the machine, on the correct port. Note: If the value for this option originates from the Metadata Server (when DMSERVER/NAME is configured), and you want to change the setting for that value, then add this option to dmserver.cfg file. This is necessary when you want the DMServer to start and listen for all available interfaces (as if there were+ no value set for this option). In addition, leave the value empty after the `=` symbol.
DMSERVER/SOAP/LISTEN_PORT	Specifies the port on which the SOAP server listens for connections. The default value is 21036 when you use a DataFlux Authentication Server for security. When you use a SAS Metadata Server for security, the DataFlux Data Management Server uses the DMSERVER/NAME option to retrieve from metadata the values of three configuration options, including LISTEN_PORT. If the SAS Metadata Server does not return a value for LISTEN_PORT, then the DataFlux Data Management Server does not start. If a value is returned, and if dmserver.cfg also contains a value for LISTEN_PORT, then the local value overrides the metadata value. For this reason, it is recommended that you not set LISTEN_PORT in dmserver.cfg when using a SAS Metadata Server. For further information, see DMSERVER/NAME and DMSERVER/SOAP/SSL.
DMSERVER/WLP	Enables or disables the WLP server. When the value is YES, the WLP server is started and uses its own listen port. When the value is NO, the WLP server is bypassed during start-up of Data Management Server. This means that WLP clients cannot connect to the DataFlux Data Management Server, but SOAP clients can. The DataFlux Data Management Server log receives entries for the status of WLP server.
DMSERVER/WLP/LISTEN_PORT	Specifies the port on which the WLP server listens for connections from WLP clients. If you are running multiple instances of the server on the same machine, each instance must have a unique port configured for it. The default port is 21037.
DMSERVER/WLP/LISTEN_HOST	Specifies the host name or IP address to which the WLP server must bind. By default, this option is left blank. For more information, see DMSERVER/SOAP/LISTEN_HOST.