To invoke a service an EIS and the SNA JCA LU62 Connector must provide the following information:
<definitions ...> <binding ...> <connector:binding /> <format:typeMapping encoding="..." style="..."> <format:typeMap typeName="..." formatType="..."/> </format:typeMapping> <operation ...> <connector: operation functionName="name" ...interaction attributes... /> <input>...</input> <output>...</output> <fault>...</fault> </operation> </binding> <port...> <connector: address hostName="uri" portNumber="..." ...connection attributes... /> </port> </definitions>
connector:binding - Identifies the type of connector being bound. The connector in the tag is the short name that identifies the particular connector such as lu62 in the <lu62:binding/> tag.
format:typeMapping - Identifies the formatters used to convert data between Branch Transformation Toolkit data structures and native EIS formats and styles. The typeMapping contains formatter typeMaps that associate a logical format such as an XML schema with the native format. The formatType attribute identifies the native format. The following is an example in which the native format type is COBOL:
<format:typeMapping encoding="COBOL" style="COBOL"> <format: typeMap typename="Customer" formatType="/CustomerInfo.ccp: CUSTINF"/ > </format:typeMapping>
connector:operation - Identifies the service to be invoked in the EIS. The attributes also contains the LU62InteractionSpec data required to run the service on the EIS side. An example of the tag is <lu62:operation functionName="GETCUST"/ >. The subtags identify the input data for the service and the data resulting from a successful or failed execution of the service.
connector:address - Identifies the location of the connector. It also contains the LU62ManagedConnectionFactory attributes required to configure the connection factory. An example of the tag is <lu62:address TPName= ". . . " / >
See WSDL definition example for an example of the binding extension and where it fits within the definition of an SNA JCA LU62 Connector.