Displaying Communications Process and Listener Information

You can see the communications processes and listeners for a specific enterprise server region by clicking GENERAL > Listeners.

The information for a communications process is as follows:

• Auto Start - whether or not the communications process is started automatically when the enterprise server instance starts.
• Listeners - list of listeners owned by this communications process.
• Process ID - the process ID of this communications process. This is present only when the communications process is running.
• Actual Address - displays the network address or addresses used by the communications process to accept incoming client requests. The format is:

  protocol:hostname or ip-address:port

  where:

  protocol

  This can be tcp or tcpssl.

  hostname or ip-address

  This can be a single hostname or multiple IP addresses that can be either IPv4 or IPv6.

  port

  This must be a valid port or an asterisk * which indicates that the address is dynamically assigned for the communications process when it starts.

• Status - you can see the current status and the time of the last status change.
• Status Log - this supplies information about the most recent event that occurred for this communications process.

Communications processes do not have names; instead they have sequence numbers. The communications process that is automatically created when you add a new enterprise server instance is Communications Process 1, and any further communications processes that you create are numbered in ascending order of creation. When you delete a communications process, existing communications processes are not renumbered, however, the next communications process you create will use the same number as the process that was deleted - the lowest available number.

The information for a listener is as follows:

• Name
• Actual Address - displays the network address or addresses used by the listener to accept incoming client requests. The format is:

  protocol:hostname or ip-address:port

  where:

  protocol

  This can be tcp or tcpssl.

  hostname or ip-address

  This can be a single hostname or multiple IP addresses that can be either IPv4 or IPv6.

  port

  This must be a valid port or an asterisk * which indicates that the address is dynamically assigned for the listener when it starts.

• Status - you can see the current status and the time of the last status change
• Status Log - this supplies information about the most recent event that occurred for this listener
• Conversation Type - this indicates what type of client requests the listener handles. Possible values are:
  • Web Services and J2EE for SOAP or J2EE requests
  • Web for World Wide Web (HTTP) requests; Enterprise Server uses a Web listener for service deployment
  • Fileshare for Fileshare client requests
  • TN3270 for requests from TN3270 terminals
  • MSS Inter-System Communication, MSS Inter-System Communication (inbound only) and CICS Transaction Gateway for CICS Intersystem Communication (peer-to-peer) and for requests for CICS transactions from non-CICS programs
  • Custom for any other type of requests

  TN3270 and the MSS ISC types are only available for use with MSS.

• Custom Configuration - See Configuration Information for more information.
• Description

See Listeners for more information.