Use this page to change configurable attributes of a listener.
To access this page:
Click this to return to the list of all the servers on this Directory Server, on the Home page.
Click this to view a list of all the service listeners registered with the current server.
Click this to view a list of all the services registered with the current server.
Click this to view a list of all the request handlers registered with the current server.
Click this to view a list of all the packages registered with the current server.
Specify the unique name of the listener, up to 255 characters in length. You cannot include angle brackets (<>) or ampersands (&) in the name.
Specify the network address used by the listener to accept incoming client requests. The format is:
protocol:ip-address:port
where:
If this network address is not unique in the repository, this may cause listener start-up problems.
Check this to make the communications process SSL-enabled. See To Create a Secure Listener for more information.
Check this if you want the listener to handle non-standard TCP/IP flows, for example, for Fileshare clients.
Shows the current status of the listener:
| Blocked | The listener is started when the server starts, but it does not accept client requests. |
| Disabled | The listener is stopped and is therefore not available to any client |
| Invalid | An error has occurred such that it has not been possible to set the status to any other value |
| Not responding | The listener status is unknown because the server it is registered with is not responding to the server monitor |
| Started | The server listener is running. |
| Stopped | The listener is stopped. |
Choose a status from the list. If the status of the server is "Started", the possible listener statuses are:
| Blocked | The listener is still running but will not be found by clients searching for this listener in a "Started" state. 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 "Blocked" status and allow requests through. |
| Disabled | The listener is stopped and will not be started. |
| Started | The server listener is started. |
| Stopped | The listener is stopped. |
If the status of the server is "Stopped", the possible statuses are:
| Blocked | The listener is stopped. The listener is started when the server starts, but will not be found by clients searching for this listener in a "Started" state. 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 "Blocked" status and allow requests through. |
| Disabled | The listener is stopped and it will not be started when the server starts. |
| Stopped | The listener is stopped. It will be started when the server starts. |
Shows the conversation type of the listener.
Specify textual configuration information that determines the start-up and run-time behavior of the listener. Optional.
Specify a text description of the listener, for example, its purpose and owner. Optional.
Click this to apply your changes to the listener.
Click this to delete the listener. You cannot delete a listener if it is registered for use with a service.