Target Introducing EBM Header Concepts

Working with Message Transformations 23-21 – ID - Identifies the object type of the sender system, for example, Order. ReqABCSImpl has this information and populates this value – NAME - Identifies the description of the sender system, for example, Purchase Order. ReqABCSImpl has this information and populates this value. – ContextID - Identifies the sender systems object identifiers. If the senders object has multiple values then repeat this as many times. Use the attribute SchemeID to set the key name and store the key value in the element itself. ReqABCSImpl has this value and populates the value.

23.6.2.11 WS Address

This element holds all WS-Addressing elements and transports WS-Addressing elements and exchanges WS-Addressing elements between the requester and target system. A local version of WS-Address schema is stored in a specified directory and ReqABCSImpl populates this. This element must be populated in the request EBM only when the provider application sends the response in an asynchronous mode. The provider application sending an asynchronous response leverages the value of this element to identify the callback address.

23.6.2.12 Custom

This element is the complex type that you can extend to add your own elements. For more information about specific usage of this element, see Section 10.6, Implementing the Fire-and-Forget Message Exchange Pattern.

23.6.3 Target

The Target section is populated only when there is a need to override the routing rules for the target system defined in Oracle Mediator. For bulk processing it is assumed that all objects reach the same target system defined in a routing rule. In that scenario you must define the appropriate target system information in this element if you need to override the routing rule. The overriding target system information is applicable to all the objects in the data area. Note that the requester ABCS should never populate the target system. The Enterprise Business Flow EBF or an EBS alone can populate the details. The Target element contains information regarding the target or receiving system and has the elements shown in Figure 23–10 . Figure 23–10 Structure of the Target Element 23-22 Developers Guide for Oracle Application Integration Architecture Foundation Pack

23.6.3.1 ID

Use this element, shown in Example 23–17 , to identify target systems to route to when the routing rules are overridden. It is populated by the EBS when the target system must be overridden with the value of the participating application instance code.

23.6.3.2 ApplicationTypeCode

This element identifies the type of application. An identifier for the application type where multiple instances of the same application type may be registered in the integration platform. The application type may contain the version number of the application if more than one version is supported on the system. This field, as seen in Example 23–17 , should be populated at the same time as the TargetID field is populated in the EBS or in an EBF, usually in the ABCS. The value of this field should come from the function aia:getSystemTypeID, where ID is the system ID value that is populated in TargetID. EBS routing rules almost always check this field for a value or lack of value when determining the routing target.

23.6.3.3 Custom

This is the complex type that you can extend to add your own elements when needed. Example 23–17 shows an example of target element code. Example 23–17 Target Element Code Sample corecom:Target corecom:IDPORTAL_01corecom:ID corecom:ApplicationTypeCodePORTAL_01corecom:ApplicationTypeCode corecom:Target

23.6.4 BusinessScope