Previous Topic: Security User ExitsNext Topic: Conversion User Exit


Communications User Exits

The following user exit classes are invoked by Java Proxies flowing to their target DPSs using a supported communications type. The user exit source code is located in a directory under classes/com/ca/genxx/exits/coopflow in the CA Gen installation directory. These classes are installed as part of the specific communications runtime (for example: classes/com/ca/genxx/exits/coopflow/tcpip).

Note: xx refers to the current release of CA Gen. For the current release number, see the Release Notes.

User Exit Class

Purpose

TCPIPDynamicCoopFlowExit

The methods in this class let you override the host name and the port number. Additionally, this class contains a method that exposes that a TCP/IP processing exception has occurred. This user exit method indicates if the processing of the flow should be retried. For example, retry in the event of a Connection Reset by Peer error.

MQSDynamicCoopFlowExit

The methods in this class let you override the following MQSeries processing data items:

Local Queue Manager name

Remote Queue Manager name

Put Queue name

Reply to Queue name

Local Queue Manager name

Remote Queue Manager name

Put Queue name

Reply to Queue name

ECIDynamicCoopFlowExit

The methods in this class let you override the following CICS Transaction Gateway processing data items:

The ECI client security class name

The port address of the CICS Transaction Gateway

The protocol to be used to communicate with the CICS Transaction Gateway (example: local, TCP, auto, http, https, and SSL)

The ECI server security class name

The CICS system name, as known within the Transaction Gateway (or supporting Universal Client), to which the cooperative request should be sent.

EJBRMIDynamicCoopFlowExit

The methods in this class lets you to override the following EJB RMI processing data items:

The provider URL

Additionally, this class has a method that permits an optional User object to be sent as part of the EJB RMI flow to the EJB server.

This class has a method for handling exceptions that occur when performing an EJB RMI operation (open, read, write, and so on). This method lets the failed request to be retried.

TUXDynamicCoopFlowExit

This class contains two methods that expose the data flowing to and from the server. The OutData method provides the ability to examine or modify the request data being sent to the server. The InData method provides the ability to examine or modify the response data received from the server.

WSDynamicCoopFlowExit

This class has methods that let you manipulate the target Web Service endpoint URL by modifying the following members:

baseURL

contextType

This class has a method for handling exceptions that occur when performing a Web Service operation. This method lets the failed request to be retried.

Note: If you specified the server address by name, try entering the decimal IPv4 address instead (for example, 1.1.1.1) or hexidecimal IPv6 address (for example FE80:0:0:1::1). Your machine may not be configured properly to work with your local name server