Integrated Configuration

You find the Web service description for an integrated configuration in the data types below. You find the data types in the Integrated Configuration folder.

Data Type	Description
MessageHeaderID (in Common folder)	Specifies object key. The same data structure is used for the object key for receiver determinations, interface determinations, sender agreements, receiver agreements, integrated configurations, and direct connections. For more information, see Receiver Determination
IntegratedConfiguration (or RestrictedIntegratedConfiguration)	Defines the integrated configuration with all attributes. MasterLanguage, AdministrativeData, and Description; more information: Cross-Object-Type Elements InterfaceDeterminationID: Object Key PrefixNamespaceMapping: Specifies the mapping of a namespace in a prefix (Example: `p1 := http://sap.com/xi`). This parameter is relevant when you use XPath expressions in the condition. QualityOfService: Specifies the quality of service. This parameter is relevant when you have assigned several inbound interfaces. The quality of service sets the order in which messages are delivered to the inbound interface (obligatory entry). Here you specify whether the message delivery order is to be adhered to at runtime or not. The possible values for this parameter are therefore: `EOIO`: for Exactly Once In Order `EO`: for Exactly Once Choose `EOIO` if the message delivery order is to be adhered to.
InboundProcessing	Defines attributes for the inbound processing of the message. The data type consists of the following elements: CommunicationChannel: Specifies the sender communication channel. AdapterSpecificAttribute: The adapter-specific attributes are dependent on the adapter type of the assigned communication channel. AdapterSpecificTableAttribute for table-type attributes. AssignedUser: Assigned service user If you have restricted the access to the runtime to particular service users for a sender component, you can refine these restrictions with respect to the sender interface. Assign the authorized users to the Integrated Configuration that contains the communication component and the interface in the object key.
Receivers	Defines attributes for determining receiver components. The data type consists of the following elements: Rule: Specifies the condition and receiver in a standard receiver determination. More information: See element`IntegratedConfigurationReceiverRule`. DynamicReceiverRule: Specifies reference to a mapping in the ES Repository (enhanced receiver determination). More information: See element `ReceiverDeterminationMapping`. NoReceiverBehavior: Specifies what happens if no receiver can be determined at runtime. Possible values: Error Message: Message processing is terminated with an error. Ignore: Message processing is ended as defined by your configurations settings. Specified Receiver: The message is sent to a fixed predefined receiver. NoReceiverReceiver: Specifies a fixed receiver (party/service) when receiver cannot be determined at runtime. Specify this parameter when you have entered the value Specified Receiver for the element NoReceiverBehaviour. If you have entered the valuesIgnore orError Message for the Element NoReceiverBehaviour then the element NoReceiverReceiver is ignored.
OutboundProcessing	Defines attributes for the outbound processing of the message. Note the following notes for the selected elements: HeaderMapping: Defines the header mapping. You enter the sender and receiver for the header mapping. AdapterSpecificAttribute/AdapterSpecificTableAttribute: For more information, see the description of the data type InboundProcessing.
IntegratedConfigurationReceiverRule	Specifies the routing rule for an Integrated Configuration with standard receiver determination. The rule contains the following elements: Operation: Specifies the service interface operation in the case you want to define the receiver determination operation-dependently. Condition: Specifies the condition for forwarding a message to a specific receiver. For more information see element AtomicCondition Receiver: Specifies the receiver of the message.
ReceiverDeterminationMapping	Specifies the routing rule for an Integrated Configuration with extended receiver determination. The routing rule consists of the following elements: Operation: If the sender interface has operations, the mappings are assigned according to these operations. Mapping: Specifies a link to a mapping in the Integration Repository. Mapping Parameters: Parameter specifies a mapping program if you reference an operation mapping with a parameterized mapping program in the interface determination. For more information on the parameterized mapping programs, see the Process Integration overview documentation on the SAP Help Portal under SAP NetWeaver Process Integration Special Development Tasks Develop and Configure Mappings Apply Enhanced Mapping Techniques Developing and Configure Parameterized Mapping Programs .
IntegratedConfigurationReceiverInterfaceRule	Defines attributes for determining the receiver interfaces and mappings. The rule contains the following elements: Condition: Specifies the condition for forwarding a message to the specific receiver interface. A Condition consists of the following elements: Operator: Specifies the operator to link left and right operands. You can enter the following values: EQ for equal, NE for not equal, CP for contains pattern, EX for exist. LeftExtractor/RightExtractor:Specifies the expression for left/right operand. More information, see Structuring Conditions below and the description of the Extractor element. Mapping: Specifies a link to a mapping in the Integration Repository (optional field). Mapping Parameters: Specifies a mapping program if you reference an operation mapping with a parameterized mapping program in the integrated configuration. For more information on the parameterized mapping programs, see the Process Integration documentation on the SAP Help Portal under SAP NetWeaver Process Integration Special Development Tasks Develop and Configure Mappings Apply Enhanced Mapping Techniques Developing and Configure Parameterized Mapping Programs Interface: Specifies a link to a service interface in the ES Repository (obligatory entry). Use this parameter to specify the receiver interface.
Extractor	Describes the data structure for the entry of an expression in a condition. An expression consists of the following elements: TypeID: Specifies whether an expression is displayed as an `XPath` expression or by entering a context object. Possible values: `XPath`, `Context Object`, `Technical Context Object`, `Constant`, `Message Header Field`. The parameter that you specify depends on the specification of the output type. Value: You can specify a simple value with this parameter. Data Type: You can specify an XSD data type with this parameter. This is useful when a particular format is needed for the expression (for example the entry of a date in a fixed predefined date format). Possible values: `xsd:string`, `xsd:integer`, `xsd:date`, `xsd:time` ContextObjectName/ContextObjectNamespace: Specifies the name and namespace of the context object.

Structuring Conditions

The core of a condition is the connection of an expression (Extractor) with another expression by using an operator. In an elementary condition (AtomicCondition), you connect exactly two expressions together, a left expression and a right expression (LeftExtractor/RightExtractor).

You can connect elementary conditions to blocks (AtomicConditionBlock) using the AND operator. You can then connect this to a condition using the OR operator.

The figure shows how complex conditions are fundamentally set up when they are made up of several blocks of elementary conditions.

This graphic is explained in the accompanying text.

Structuring Conditions

Structuring Expressions

You have several options for formulating an elementary condition in an expression.

Note Note

Using TypeID element you specify how you want to define the expression.

End of the note.

Entering Expressions
Expression Type	Description
Entering a constant (TypeID = `Constant`)	Enter the value in the Value parameter.
Entering an XPath expression (TypeID = `XPath`)	Enter the XPath expression in the Value parameter.
Entering a Context Object (TypeID = `Context Object`)	Enter the name and namespace of the (technical) context object or the header field from the ES Repository in the ContextObjectName and ContextObjectNamespace parameters.
Entering a Technical Context Object (TypeID = `Technical Context Object`)
Entering a field from the message header (TypeID = `Message Header Field`)

Example of a Condition

If the AirlineID field in the message payload has the value LH, then the message is forwarded to the receiver business system BUS_100. A context object of the same name from the ES Repository is used to access the AirlineID field in the message.

The receiver determination (in the dual stack) or integrated configuration contains just one block with an elementary condition (AtomicCondition) and the assignment to the receiver.

The elementary condition is expressed using the following elements (XML presentation).

Syntax Syntax

```
<AtomicCondition>
```
```
      <Operator>EQ</Operator>
```
```
      <LeftExtractor>
```

           <TypeID>Context Object</TypeID>

           <Value>/p1:BookingOrderRequest/FlightID/AirlineID</Value>

```
           <Datatype></Datatype>
```

           <ContextObjectName>AirlineID</ContextObjectName>

           <ContextObjectNamespace>http://sap.com/xi/XI/Demo/Agency

```
           </ContextObjectNamespace>
```
```
      </LeftExtractor>
```
```
      <RightExtractor>
```
```
           <TypeID>Constant</TypeID>
```
```
           <Value>LH</Value>
```

           <Datatype>xsd:string</Datatype>

```
           <ContextObjectName>
```
```
           </ContextObjectName>
```
```
           <ContextObjectNamespace>
```
```
           </ContextObjectNamespace>
```
```
      </RightExtractor>
```
```
</AtomicCondition>
```

End of the code.

Example of Expressions

Entering a Field from the Message Header

Syntax Syntax

```
<TypeID>Message Header Field</TypeID>
```
```
<Value></Value>
```
```
<Datatype>xsd:string</Datatype>
```

<ContextObjectName>SenderPartyAgency</ContextObjectName>

<ContextObjectNamespace>http://sap.com/xi/XI/System</ContextObjectNamespace>

End of the code.

Entering a Technical Context Object

Syntax Syntax

<TypeID>Technical Context Object</TypeID>

```
<Value></Value>
```
```
<Datatype>xsd:string</Datatype>
```

<ContextObjectName>ProcessStep</ContextObjectName>

<ContextObjectNamespace>http://sap.com/xi/XI/System</ContextObjectNamespace>

End of the code.

Entering a Context Object

Syntax Syntax

```
<TypeID>Context Object</TypeID>
```
```
<Value></Value>
```
```
<Datatype>xsd:string</Datatype>
```

<ContextObjectName>ConvContent</ContextObjectName>

<ContextObjectNamespace>http://xi.com/gr/conv</ContextObjectNamespace>

End of the code.