Interface Mappings 

Use

Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time (see: Defining Interface Determinations). The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.

See also: Overview.

Activities

...

       1.      Create an interface mapping on the design maintenance screen of the Integration Builder (also see: Creating a New Object).

You can also create multiple interface mappings for the same interface pair.

       2.      Enter the source and target interfaces that require a mapping of the request message, the response message, the fault message, or all three, in the table of the same name. To map several messages to one another using multi-mappings, you must specify asynchronous abstract message interfaces (multi-mappings are only supported for integration processes). You can also create message interfaces by using the function Create New Object ().

If the interface cannot be imported or cannot be created in the Integration Repository (in the case of an external adapter, for example), you must enter the interface names manually. However, it is not possible to check the technical name in this case.

       3.      To import the properties of the interfaces, choose Read Interfaces. The table in the lower area displays tab pages for the request message, response message, and if available, for the fault message, for each mode of the interfaces (either synchronous or asynchronous).

       4.      To develop an external mapping program, export the XSD schema of the respective request or response message as a zip file after you have imported the interfaces. The zip file can contain multiple schema files that reference each other, for example in a multi-mapping. In this case, the schema with the global message element has the name MainSchema.

       5.      To reference a mapping program for the respective message, you have the following options:

¡        Select an existing mapping program from the Integration Repository by using the input help (). If this is a message mapping, the default setting of the input help only displays those message mappings that are found using the source and target message in the Integration Repository (in multi-mappings, the first source and target messages are used as the search criteria). However, you can also display any number of message mappings, for example, because you are constructing a mapping from several mapping programs with intermediate instances which have no message types.

¡        You can create message mappings directly from the interface mapping. To do this, select the mapping type message mapping in the Type column. Position the cursor in the Name column and choose the function Create New Message Mapping () in the Mapping Program frame. The Integration Builder copies the specifications of the messages and their occurrence directly from the interface mapping.

An interface mapping can only reference mapping programs that belong to the same or an underlying software component version of the interface mapping. This ensures that the mapping programs can be shipped together with the interface mapping (see: Software Logistics).

       6.      If you are not using a multi-mapping or a mapping for a fault message, you can execute multiple mapping programs in succession for request and response messages:

¡        To insert an additional line for a mapping program, choose .

¡        To delete the registration for a mapping program, choose .

At runtime, the mapping programs are executed from top to bottom.

       7.      Save the interface mapping.