12Property Set Representation of Integration Objects
Property Set Representation of Integration Objects
This chapter describes the relationship between property sets and integration objects. Property sets are in-memory representations of integration objects. For an overview of property sets, see Using Siebel Tools. It includes the following topics:
Property Sets and Integration Objects
Many EAI business services operate on integration object instances. Because business services take property sets as inputs and outputs, it is necessary to represent integration objects as property sets. The mapping of integration objects, components, and fields to property sets is known as the Integration Object Hierarchy.
Using this representation, you can pass a set of integration object instances of a specified type to an EAI business service. You pass the integration object instances as a child property set of the business service method arguments. This property set always has a type of SiebelMessage. You can pass the SiebelMessage property set from one business service to another in a workflow without knowing the internal representation of the integration objects.
Property Set Node Types
When passing integration object instances as the input or output of a business service, you can use property sets to represent different node types, as presented in the following table.
Table Property Set Node Types
| Name | Parent | Value of Type Attribute | Properties | Description |
|---|---|---|---|---|
Service Method Arguments |
Not applicable |
Ignored |
The properties of this property set contain the service specific parameters, such as PrimaryRowId for the EAI Siebel Adapter. |
This is the top-level (highest-level) property set of a business service’s input or output. The properties of this property set contain the service-specific parameters (for example, PrimaryRowId for the EAI Siebel Adapter). |
SiebelMessage |
Service Method Arguments |
SiebelMessage |
The properties of this property set contain header attributes associated with the integration object, for example, IntObjectName. |
This property set is a wrapper around a set of integration object instances of a specified type. To pass integration objects between two business services in a workflow, this property set is copied to and from a workflow process property of type Hierarchy. |
Object List |
SiebelMessage |
ListOfObjectType |
Not used. |
This property set identifies the object type that is being represented. The root components of the object instances are children of this property set. |
Root Component |
Object List |
Root Component Name |
The property names of the property set represent the field names of the component, and the property values are the field values. |
This property set represents the root component of an integration object instance. |
Child Component Type |
Root Component or Component |
ListOfComponent Name |
Not used. |
An integration component can have a number of child component types, each of which can have zero or more instances. The Integration Object Hierarchy format groups the child components of a given type under a single property set. This means that child components are actually grandchildren of their parent component’s property set. |
Child Components |
Child Component Type |
Component Name |
The property names of the property set represent the field names of the component, and the property values are the field values. |
This property set represents a component instance. It is a grandchild of the parent component’s property set. |
Example Instance of an Account Integration Object
This example shows an Account integration object in which the object has two component types: Account and Business Address (which is a child of Account). The hierarchy of component types, from the perspective of Oracle’s Siebel Tools, looks like that shown in the following figure.
The following figure shows an example instance of this object type, using the Integration Object Hierarchy representation. There are two Sample Account instances. The first object instance has an Account component and two Business Address child components. The second object instance has only an Account component with no child components.
