Integration Objects

Август 21, 2022

Содержание

2. Module Objectives After completing this module you should be able to: Explain the role of internal
3. Integration Object Defines the structure of data being exchanged between a Siebel and an external application
4. Integration Object Continued Is designed to represent hierarchical data structures Consists of multiple integration components Each
5. Types of Integration Objects Internal integration object Specifies the structure of the data extracted from or
6. Internal Integration Object Represents a subset of a Siebel business object Integration components represent business components
7. Integration Components An integration object includes the following: One parent integration component corresponding to the primary
8. Integration Components Continued In addition, a child integration component represents the business component for each MVG
9. Integration Component Key Is a field or set of fields that uniquely identify a record being
10. Status Key Is a special type of integration component key that is used to return the
11. Creating an Internal Integration Object 1. Identify the Siebel Data to Be Exchanged 2. Specify the
12. 1. Identify the Siebel Data to Be Exchanged Identify the data in the Siebel UI to
13. 2. Specify the Business Object Use the Integration Object Builder to create an integration object based
14. 2. Specify the Business Object Continued Select the business object Provide a name for the integration
15. 3. Select the Integration Components Select components to include in the integration object
16. 3. Select the Integration Components Continued Review messages about fields made inactive Click Finish to configure
17. 3. Select the Integration Components Continued Integration Object Wizard: Finds all links, business components, and underlying
18. 4. Inactivate Unneeded Integration Component Fields Set unneeded fields to inactive in each integration component to
19. 5. Inactivate Unneeded Integration Component Keys Make sure that the fields in the integration component keys
20. Synchronizing Integration Objects When business objects are modified or updated, it is necessary to make sure
21. Creating an External Integration Object 1. Obtain a Schema of the External Data 2. Create the
22. 1. Obtain a Schema of the External Data Use the schema if published by the external
23. 2. Create the External Integration Object Use the Integration Object Builder to create an integration object
24. 2. Create the External Integration Object Continued Specify the source object to serve as the root-level
25. 3. Select Integration Components Select integration components
26. 4. Verify the Integration Object Examine the configured integration object that contains the desired components and
27. Module Highlights Integration objects define the structure of data being exchanged between a Siebel and an
29. Скачать презентацию

Слайд 2

Module Objectives
After completing this module you should be able to:
Explain the

role of internal and external integration objects
Create an internal integration object
Create an external integration object based on an XML schema definition (XSD)
Why you need to know:
Integration objects provide the templates for importing and exporting data from a Siebel application

Слайд 3

Integration Object
Defines the structure of data being exchanged between a Siebel

and an external application
Is used as a template to create memory-resident instances of data for processing by business services

Слайд 4

Integration Object Continued
Is designed to represent hierarchical data structures
Consists of multiple

integration components
Each integration component consists of multiple integration component fields

Integration Object

Integration Component

Integration Component Field

Слайд 5

Types of Integration Objects
Internal integration object
Specifies the structure of the data

extracted from or inserted into the Siebel application
External integration object
Specifies the structure of the data that is transported between the Siebel and the external application
Is required only when the external application is not able to handle data in Siebel format (“Siebel data”)
Additional processing is required within the Siebel application to convert the integration object instance

Слайд 6

Internal Integration Object
Represents a subset of a Siebel business object
Integration components

represent business components
Integration component fields represent business component fields

Contact

First Name

Contact_Business Address

Last Name

Job Title

Business
Component

Business
Object

Field

Integration
Component

Integration
Object

Integration
Component
Field

Слайд 7

Integration Components
An integration object includes the following:
One parent integration component corresponding

to the primary business component in a business object
Zero or more child integration components corresponding to other business components in the business object

Слайд 8

Integration Components Continued
In addition, a child integration component represents the business

component for each MVG in the primary and child business components

State MVF in Employee points to State MVF in Position

State MVF in Position points to State MVF in Business Address

In the integration object, these expand into Position and Position_Business Address

Слайд 9

Integration Component Key
Is a field or set of fields that uniquely

identify a record being exchanged
Is based on user keys for the tables referenced by the business components
Is constructed by the Integration Object Wizard

Слайд 10

Status Key
Is a special type of integration component key that is

used to return the result of an operation, such as insert or update
Type is Status Key
Can be used to indicate:
Success or failure of an operation
Actual operation performed (for example during an upsert)
ROW_ID for a newly created record
Integration component key fields specify data to be returned when status is requested

Слайд 11

Creating an Internal Integration Object
1. Identify the Siebel Data to Be

Exchanged

2. Specify the Business Object

3. Select the Integration Components

4. Inactivate Unneeded Integration Component Fields

5. Inactivate Unneeded Integration Component Keys

Слайд 12

1. Identify the Siebel Data to Be Exchanged
Identify the data in

the Siebel UI to integrate
Determine the underlying Siebel business objects, business components, and fields

Слайд 13

2. Specify the Business Object
Use the Integration Object Builder to create

an integration object based on a Siebel business object
Select the EAI Siebel Wizard business service

Слайд 14

2. Specify the Business Object Continued
Select the business object
Provide a name

for the integration object

Слайд 15

3. Select the Integration Components
Select components to include in the integration

object

Слайд 16

3. Select the Integration Components Continued
Review messages about fields made inactive
Click

Finish to configure the integration object

Слайд 17

3. Select the Integration Components Continued
Integration Object Wizard:
Finds all links, business

components, and underlying tables
Identifies all business component fields that map to user keys in tables
Creates integration component user keys based on those fields
Notes any key columns that are not exposed in a business component
Creates calculated fields as integration component fields, but marks them inactive
Such fields cannot be updated

Слайд 18

4. Inactivate Unneeded Integration Component Fields
Set unneeded fields to inactive in

each integration component to improve performance
Do not delete unneeded fields—deleted fields become active when the business object is upgraded

Field will not be included in the integration object

Слайд 19

5. Inactivate Unneeded Integration Component Keys
Make sure that the fields in

the integration component keys are consistent with the component fields
Inactivate unneeded key fields in each integration component
Inactivate a key itself if it has no active fields

Слайд 20

Synchronizing Integration Objects
When business objects are modified or updated, it is

necessary to make sure the integration object is still consistent
If business object changes are minor, click Synchronize to update the integration object
Example: adding a new single value field
If business object changes are extensive, delete and recreate the integration object
Example: creating a new MVG

Слайд 21

Creating an External Integration Object
1. Obtain a Schema of the External

Data

2. Create the External Integration Object

3. Select Integration Components

4. Verify the Integration Object

Слайд 22

1. Obtain a Schema of the External Data
Use the schema if

published by the external application
Alternatively, create a file containing a sample XML file received/sent by the external application
Use a third-party XML utility to generate the schema as an XSD

Слайд 23

2. Create the External Integration Object
Use the Integration Object Builder to

create an integration object
Select the EAI XSD Wizard or EAI DTD Wizard business service
Check Simplify Integration Hierarchy to create an integration object with leaf elements as fields
Otherwise, all leaf elements are converted to integration components

Слайд 24

2. Create the External Integration Object Continued
Specify the source object to

serve as the root-level node

Слайд 25

3. Select Integration Components
Select integration components

Слайд 26

4. Verify the Integration Object
Examine the configured integration object that

contains the desired components and fields
Inactivate unneeded integration component fields as necessary

Слайд 27

Module Highlights
Integration objects define the structure of data being exchanged between

a Siebel and an external application
Integration objects are used as templates to create memory-resident instances of data for processing by business services
Internal integration objects are a subset of Siebel business objects
Use the Siebel Wizard to configure an internal integration object
Requires inactivating multiple fields and user keys
Use the EAI XSD Wizard to build an external integration object based on the schema associated with external data

Integration Objects

Содержание

Module ObjectivesAfter completing this module you should be able to:Explain the

Integration ObjectDefines the structure of data being exchanged between a Siebel

Integration Object ContinuedIs designed to represent hierarchical data structuresConsists of multiple

Types of Integration ObjectsInternal integration objectSpecifies the structure of the data

Internal Integration ObjectRepresents a subset of a Siebel business objectIntegration components

Integration ComponentsAn integration object includes the following:One parent integration component corresponding

Integration Components ContinuedIn addition, a child integration component represents the business

Integration Component KeyIs a field or set of fields that uniquely

Status KeyIs a special type of integration component key that is

Creating an Internal Integration Object1. Identify the Siebel Data to Be

1. Identify the Siebel Data to Be ExchangedIdentify the data in

2. Specify the Business ObjectUse the Integration Object Builder to create

2. Specify the Business Object ContinuedSelect the business objectProvide a name

3. Select the Integration ComponentsSelect components to include in the integration

3. Select the Integration Components ContinuedReview messages about fields made inactiveClick

3. Select the Integration Components ContinuedIntegration Object Wizard:Finds all links, business

4. Inactivate Unneeded Integration Component FieldsSet unneeded fields to inactive in

5. Inactivate Unneeded Integration Component KeysMake sure that the fields in

Synchronizing Integration ObjectsWhen business objects are modified or updated, it is

Creating an External Integration Object1. Obtain a Schema of the External

1. Obtain a Schema of the External DataUse the schema if

2. Create the External Integration ObjectUse the Integration Object Builder to

2. Create the External Integration Object ContinuedSpecify the source object to

3. Select Integration ComponentsSelect integration components

4. Verify the Integration Object Examine the configured integration object that

Module HighlightsIntegration objects define the structure of data being exchanged between

Похожие презентации