The SAS Event Stream Processing (ESP) XML server can use multiple TCP ports. The XML server does not have any well-known ports or default ports defined. The ports that are used are based on the configuration of the XML server. If the XML server is behind a firewall, the ports need to be configured in the firewall to allow outside clients to connect. The following ports can be configured:
Port | Description | Configuration |
Publish/Subscribe (pubsub) port | This port is used to accept pubsub connections. |
dfesp_xml_server -pubsub 39095
<engine port="39095" name="DemoEngine">
|
Publish/Subscribe project port | By default, the pubsub API uses an ephemeral port that is discovered by the pubsub client. The pubsub client uses this port for sending and receiving event data. Each project that is loaded to the XML server uses a unique port. |
To force the project to use a specific port, configure the port attribute on the project element:
<project name="DemoProject1" pubsub="manual" port="29095">
|
HTTP Publish/Subscribe port | This port receives HTTP requests for pubsub services. It is used by the streamviewer and ESP studio. | To configure this port:
dfesp_xml_server -http-pubsub 49095
<http-servers>
<http-pubsub-server port="49095"/>
</http-servers> |
HTTP admin port | This port receives HTTP administration requests, such as loading a project. | To configure this port:
dfesp_xml_server -http-admin 59095
<http-servers>
<http-admin-server port="59095"/>
</http-servers> |