Use this page to add a new service listener to the selected communications process.
To access this page:
Specify the unique name of the new service listener, up to 255 characters in length. You cannot include angle brackets (<>) or ampersands (&) in the name.
Specify the communications protocol used by the listener to accept incoming client requests. TCP is the only option.
Specify the network address used by the listener to accept incoming client requests. The format is:
If this network address is not unique in the repository, this may cause listener startup problems.
The server certificate proves your identity to people you communicate with online and enables them to send you data in encrypted form. If the server certificate file is not in the default directory (which is the certs directory in the location defined by the SSLDIR environment variable), you must also specify the full path to the file.
If this file is not in the default directory (which is the keys directory in the location defined by the SSLDIR environment variable), you must also specify the full path to the file.
Check this if you want the listener to handle non-standard TCP/IP flows, for example, for Fileshare clients.
Choose a status from the list. The possible statuses are:
|The listener is started when the server starts, but it does not accept client requests. One use for this status is where you want to allow requests from only one client, perhaps for debugging purposes. You could amend the client code to ignore a status of "Blocked"and allow requests through.
|The listener is not started when the server starts and is therefore not available to any client
|The listener is available but stopped. This is the default. To start a listener use the Edit Listener page. When you add a stopped listener to a server that has a status of "Started", the server will attempt to start the listener immediately. If you add a stopped listener to a server that has a status of "Stopped", when the server is started it will attempt to start the listener.
if you chose TCP in Endpoint Protocol, click one button to choose a conversation type:
Specify textual configuration information that determines the startup and run-time behavior of the listener. Optional. For details of the valid entries, see the section Configuration Information in the chapter Communications Processes and Service Listeners in your Configuration and Administration Guide.
Specify an optional text description of the listener, for example, its purpose and owner. Optional.
Click this to add the listener to the current server.