Socket clients and servers must run locally or remotely in a TCP/IP network environment.

A potential server must have a TCP/IP port available on which to listen for connections.

A socket server can have only one server socket object enabled to listen for connections.

AppServer and WebSpeed procedures cannot function as socket servers—they can only function as socket clients.

A potential client must:

Know the hostname or IP address of the machine where the server it wants to connect to is running.

Know the TCP/IP port where the server is listening for connections.

For SSL sessions, have access to a public key certificate store as maintained by the OpenEdge features for managing certificate stores. For more information, see OpenEdge Getting Started: Core Business Services - Security and Auditing.