Communications processes handle communications between clients and the enterprise server instance, and consist of a number
of service listeners.
To create a new communication process, click
ADD COMMS SERVER.
To view the listeners associated with a communications process, click the communications process in the communications process
list.
To display all the configurable properties of the communication process, click
CONFIGURE.
To create a new listener:
- Click
ADD LISTENER.
- Modify the listener properties as required.
- Click
APPLY.
The properties for a listener are:
- Name
- Specify the unique name of the listener, up to 255 characters in length. You cannot include angle brackets (<>) or ampersands
(&) in the name.
- Legacy Micro Focus Application Format
- Check this if you want the listener to handle non-standard TCP/IP flows, for example, for Fileshare clients.
- Protocol
- This can be set to TCP or SMEM for shared memory protocols.
- Requested Endpoint
- Specify the network address used by the listener to accept incoming client requests. The format is:
protocol:ip-address:port
where:
- protocol
- This is tcp.
- ip-address
- This is either the text host name or IP address of the server listener. An asterisk (*) indicates that the address is dynamically
assigned for the listener when it starts.
- port
- This 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 start-up problems.
- Status
- Displays 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.
- Requested Status
- The status the listener has been requested to change to:
- Started
- Stopped
- Blocked
- Disabled
- Conversation Type
- Displays the conversation types that are supported:
- Web Services and J2EE
- For client requests that use either of the conversation protocols supported by the Micro Focus request handlers, MFRHBINP
and MFRHSOAP.
- SOAP and J2EE (legacy)
- This is a legacy conversation type.
- 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
- For CICS Intersystem Communication (peer-to-peer) and for requests for CICS transactions from non-CICS programs. This conversation
type handles both inbound and outbound calls. Only one listener of this type can be used with an enterprise server. The corresponding
conversation type in previous Enterprise Server software releases is
Micro Focus MTO Inter-System Communication.
Note: This conversation type uses Legacy Micro Focus Application Format.
- MSS Inter-System Communication (inbound only)
- For CICS Intersystem Communication (peer-to-peer) and for requests for CICS transactions from non-CICS programs. This conversation
type handles inbound calls only. Only one listener of this type can be used with an enterprise server. The corresponding conversation
type in previous Enterprise Server software releases is
Micro Focus MTO Inter-System Communication.
Note: This conversation type uses Legacy Micro Focus Application Format.
- CICS Transaction Gateway
- Is similar in functionality to the previous two conversation types, except that it does not use Legacy Micro Focus Application
Format.
- Custom
- Can be used for any other type of requests. You can select whether or not to use Legacy Micro Focus Application Format.
- Custom Configuration
- Specify optional textual configuration information that determines the start-up and run-time behavior of the listener.
- Description
- Specify an optional text description of the listener, for example, its function and owner.