Defining a UPIC connection for outbound communication between the UTM partner and BeanConnect

From the UTM partner point of view, the BeanConnect resource adapter is seen as a UPIC client.

A UPIC connection from BeanConnect to an UTM partner requires a TPOOL statement within the KDCDEF generation of UTM partner application. The Management Console does not generate this statement.

The configuration enables non-transactional UPIC outbound communication.

The UTM connection is configured as follows:

BCAMAPPL UTMSERV
   ,T-PROT=RFC1006
  [,LISTENER-PORT = 11111] // only required for Unix/Linux/Windows systems
  [,TSEL-FORMAT=T|A|E]     // only required for Unix/Linux/Windows systems
 
TPOOL NUMBER=99
   ,PTYPE=UPIC-R
   ,LTERM=UPIC#R
   ,BCAMAPPL=UTMSERV
   ,PRONAM=*ANY
   ,Connect-Mode=MULTI

Please note the following:

• TSEL-FORMAT must match the configuration property connectionURL, parameter TSEL, attribute rt (see "connectionURL" in Defining configuration properties for OSI-TP / LU6.2 ).

• UTMSERV and the port number must match the values which are specified in the configuration property connectionURL parameters remote and port or in the program.

Example 11 Example of an URL

The UTM partner application configured above can be addressed as follows with the configuration property connectionURL:

<config-property name="connectionURL" value="upic://host:11111/UTMSERV?rt=t"/> (for Unix/Linux/Windows systems)