Add Listener

Add Configuration Information Description Endpoint Address Endpoint Protocol Initial Status | Legacy Micro Focus Application Format Name Secure Sockets Layer Supported Conversation Type

Add Listener

  Use this page to add a new service listener to the selected communications process.

  Top

Name

  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.

  Top

Endpoint Protocol

  Specify the communications protocol used by the listener to accept incoming client requests. TCP is the only option.

  Top

Endpoint Address

  Specify the network address used by the listener to accept incoming client requests. The format is:

  ip-address:port

  where:

  - ip-address is either the text host name or IP address of the server listener. An asterisk (*) indicates that the address is the IP address of the current machine.
  - port is the port value. An asterisk (*) indicates that the port is dynamically assigned for the listener when it starts.

  If this network address is not unique in the repository, this may cause listener startup problems.

  Top

Secure Sockets Layer

  Not currently used.

  Top

Legacy Micro Focus Application Format

  Check this if you want the listener to handle non-standard TCP/IP flows, for example, for Fileshare clients.

  Top

Initial Status

  Choose a status from the list. The possible statuses are:

  Blocked | 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.
  Disabled | The listener is not started when the server starts and is therefore not available to any client
  Stopped | 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.

  Top

Supported Conversation Type

  if you chose TCP in Endpoint Protocol, click one button to choose a conversation type:

  - Web Services / J2EE for client requests that use a conversation protocol supported by the request handlers provided by Micro Focus, MFRHBINP and MFRHSOAP.
  - Web for World Wide Web (HTTP) client requests. Enterprise Server uses a Web listener for service deployment.
  - Fileshare for Fileshare client requests.
  - TN3270 for client requests for CICS transations that use the TN3270 protocol. You can only use TN3270 listeners with Mainframe Transaction Option.
  - MTO ISC for client requests from non-CICS programs for CICS transactions. You can only use MTO Inter System Communications listeners with Mainframe Transaction Option.
  - Custom for other kinds of client requests. Specify the name of the connector module in the entry field next to Custom.

  Top

Configuration Information

  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.

  Top

Description

  Specify an optional text description of the listener, for example, its purpose and owner. Optional.

  Top

Add

  Click this to add the listener to the current server.

  Top