Host access operation concentrates all configurations related to the host connection processing into a UDTT operation through the tooling editor, which is convenient for users to develop host related transactions. By defining the host access operation in UDTT tooling, users improve their development efficiency by using a zero-code method.
To create a full host access operation, the related configurations include UDTT operation, context, data, format and service.
▪ Operation configuration To create a host access operation, please open the UDTT operation wizard of UDTT eclipse tooling and set the properties as shown in following example:
In addition to the original standard attribute definition of UDTT operation, the following operation attributes are added to the host access operation:
▪ Hostconnector This is the name of the host connector, which can be defined globally in service.xml or in this operation.
▪ Implclass For MQ or SNA lu0, lu62 type connections, the messages sent are plain string. For these types, the implementation class provided by the product is HostPlainMsgAccessOp. It’s full name is com.unicom.dtt.host.operation.HostPlainMsgAccessOp.
▪ Input format Input format is used to format the UDTT context data in a plain text message which is to be sent to the host. If the format name of the data sent to the host is empty, the default name "hostSentFormat" will be used (in this case, a user needs to select "hostSentFormat" as the relevant format name in refFormat).
▪ Output format Output format is used to parse and convert the host reply message string into UDTT context data. If the format name of the data returned from the host is empty, the default name "hostReceiveFormat" will be used (in this case, you need to select the relevant format name as "hostReceiveFormat " in refFormat).
▪ Timeout The timeout of waiting for the host to receive data, in MS.
▪ HFaultEvent Exit event name when the operation flow fails to execute.
▪ HSuccessEvent The exit event name for the successful execution of the operation flow.
Connector service configuration
Please refer to topic 2 (see Interface API and Configuration) and 3 (see Connection Pool) for relevant properties of the host connector. The connector service definition can be embedded in the local operation or comes from the global service definition.
Context configuration
In the context definition, the refRecord is defined to refer to the data definition. If the connector service is not defined globally, then the refService should be defined to add the reference of the local host connector service. In this case, the alias will be used by the API as connector id.
Format configuration
Format defines the formatting and parsing of UDTT context data and host messages. In general, an input and an output format should be defined for a specific host transaction. Input format is used to format the UDTT context data into a host string, and output format is to convert a host string into context data.
After all operation, connector service, context, and format configurations are defined, the application transaction to access the host is defined. In this case, the user does not need to write any code. The UDTT platform will perform the runtime code automatically according to the definitions created by UDTT tooling as shown above.
