49 copyright © 2007, oracle. all rights reserved. module 49: section i exploring integration...

49Copyright © 2007, Oracle. All rights reserved.

Module 49: Section IExploring Integration Strategies

Siebel 8.0 Essentials

2 of 35Copyright © 2007, Oracle. All rights reserved.

Module Objectives

After completing this section you will be able to: Explain the business need for application integration Describe Siebel application integration tools Describe the strategies for approaching application

integration

Why you need to know: Being familiar with the Siebel integration tools allows you

to select the tool that satisfies your integration requirements


Need for Application Integration

Enterprises often have: Applications in each domain Applications with different user interfaces Applications using separate data sources

Supply Chain Management

Data

Enterprise Resource Planning

Data

Data

Company Web Site

Partner

Portal

Data

Customer Relationship Management

Data

Employee Relationship Management

Data

Mainframe Applications

DataData

Billing

Data

Desktop/ Email


User Requirements

Users want to: Access all business data quickly Avoid reentering data in multiple systems Work with a consistent user interface (UI)

Data Source

Data Source

Data Source

Data Source

Data Source


Siebel eBusiness Application Integration (EAI)

A configurable and scalable set of tools and components, based on industry standards Enables the building of a consistent view of all customer data

across all channels, applications, mainframes, ERP systems, and custom applications

Enables seamless automation of business process between Siebel applications and others

Enables real-time as well as high-volume, batch-oriented replication of data between Siebel applications and others

• eCommerce applications• Legacy applications (mainframes)• ERP systems• Custom applications

SiebelApplication

External Application

Database DatabaseChannels


Siebel Universal Application Network (UAN)

An integration solution that provides a library of prepackaged, industry-specific business processes that: Span multiple applications Are primarily focused on customer interactions and reflect industry

best practices Are built based on open industry standards such as Extensible

Markup Language (XML) and Web Services-enabling enterprises


Siebel Integration Tools

EAI Connector

Virtual Business Component (VBC)

Integration Workflow Process

Object Interface

0/6

Siebel Business Integration Applications (BIA)

Enterprise Integration Manager (EIM)


Integration Workflow Process

Challenge: To synchronize Siebel account data with customer data on a mainframe

Solution: Integration Workflow Process Is a Siebel workflow process that replicates data

From a Siebel application to an external application From an external application to a Siebel application

Uses standard transports

Siebel Application

Mainframe Application

Account data Customer data

Transport

1/6


EAI Connector

Challenge: To exchange orders between a Siebel application and an SAP R/3 application

Solution: EAI Connector Is a integration workflow that uses prebuilt business services for

ready-to-use integration with popular applications Oracle, SAP R/3, and PeopleSoft Bidirectional integration

Siebel Application

SAP R/3 Application

Order headers

Transport

Order details

2/6


Virtual Business Component (VBC)

Challenge: To display Siebel contact data with contact detailsfrom an external source in the same view

Solution: Virtual Business Component (VBC) Is a business component that displays external data within a

Siebel applet without storing that data in the Siebel database

3/6

Business Object

Regular Business

Component

Virtual Business

Component

Siebel Data

ExternalData



Challenge: To exchange large volumes of data between an external application and the Siebel application

Solution: Enterprise Integration Manager (EIM) Is a server component that exchanges large volumes of data in

batch mode between a Siebel database and another database Using interface tables in the Siebel database

ExternalDatabase

Siebel Database

SiebelInterface Tables

SiebelBase Tables

EIM

SQL Utility

4/6


Object Interface

Challenge: To control a Siebel application or to access Siebel data from an external application

Solution: Object Interface Is an access point that exposes Siebel objects and data to

programmatic access from scripts or external applications Enables an external application to control the Siebel application

or access the Siebel database using: COM Servers: Automation Server, Data Server CORBA Object Manager Java Data Bean

Is an alternative to EIM forloading large data volumes

Database Siebel Application

Siebel COM Data Server

Example: A button in an Excel spreadsheet calls the Siebel COM

Data Server to update Siebel contact data from Excel values

5/6


Siebel Business Integration Applications (BIA)

Challenge: To apply industry-specific business processes across applications and organizational boundaries

Solution: Siebel Business Integration Applications (BIA) Packaged software built on the Universal Application Network

(UAN) architecture Delivers prebuilt, industry specific integration processes, common

objects, and transformations

6/6

Business Process ControllerBusiness Process Controller

TransformationTransformationCRM

Data

Model

ERP

Data

ModelAdapter Transport Layer Adapter

TransformationTransformation

Integration Server

Common ObjectModel

CRM ERP


Approaches to Application Integration

Display external data in Siebel UI Display Siebel data in another application Synchronize Siebel data with external data

SiebelApplication

External

UI UI

Data

ExternalApplication

Siebel


Application Integration Considerations

The following design considerations must be addressed: Usage models

Batch processing Real-time processing

Connection models Peer-to-peer connections Integration servers connections


Batch Processing

Used for periodic uploads or downloads of large amounts of information into the Siebel database

Examples: Uploading a batch of product catalog and item information into a

Siebel application from an external system Downloading a batch of all opportunities from Siebel applications

to another database Uploading legacy data into the Siebel application


Real-Time Processing

Is used when data needs to be updated immediately when changes occur Examples include:

Updating a service request Updating an account’s contacts Updating an order status

Deploying Siebel applications as a client or as a service Client: Siebel applications access another program or initiate a

transaction on an external system Service: Siebel applications are accessed by an external

program without any initiation from the Siebel application


Peer-to-Peer Connections

Each application-to-application connection is custom

CUSTOM WEB CUSTOM WEB APPLICATION APPLICATION

CRMCRM

BILLINGBILLING ERPERP

LEGACYLEGACY

PROVISIONINGPROVISIONING

Possible total custom connections

n=number of connections

n n-12( )


Integration Server Connections

Provide an information bus or a hub-and-spoke architecture to tie disparate applications together

Allow each application to connect only to the integration server through an adapter

PROVISIONINGPROVISIONING

LEGACYLEGACY CUSTOM WEB CUSTOM WEB APPLICATION APPLICATION

CRMCRM

BILLINGBILLING ERPERP

X


Summary

This section showed you how to: Explain the business need for application integration Describe Siebel application integration tools Describe the strategies for approaching application

integration

49Copyright © 2007, Oracle. All rights reserved.

Module 49: Section IIIntroducing Enterprise Integration Manager

Siebel 8.0 Essentials


Module Objectives

After completing this module you will be able to: Describe the features of Enterprise Integration Manager (EIM) Describe how EIM supports referential integrity Describe why direct SQL statements must not be used to insert

user data

Why you need to know: EIM enables you to properly import external data into the Siebel

database



Business Challenge: To exchange large volumes of data between an external application and the Siebel database Implementation project challenge: To perform an initial data load

for a Siebel application Business Solution: Enterprise Integration Manager (EIM)

Is a server component that moves large volumes of data in batch mode between Siebel interface tables and Siebel base tables Interface tables act as a staging area for external data

ExternalDatabase

Siebel Database

SiebelInterface Tables

SiebelBase Tables

EIM

SQL Utility


User Data

The Siebel database contains several types of data: Seed data: application data populated during product installation Repository data: metadata initialized at installation and modified

during application configuration User data: user-supplied data, such as account records, contacts,

price lists, or assignment rules EIM is only used to move user data

Siebel Database

User-supplied data such as account information,

contacts, or price lists

Seed data

Repository data

User data


Populating and Managing User Data

Use the client application to enter, update, or delete small amounts of user data directly in the base tables

Use EIM to: Import large amounts of data from external sources

through interface tables Delete large amounts of data


Siebel Database

Components of EIM

Important components of EIM are:

Base table

Interface table

Prepared and cleansed

external data

Server component

Non-Siebel loading tool

Siebel client

Base Tables

Interface Tables

EIM Server Component

EIM Configuration File

0/4


Base Tables

User data is stored in one or more base tables in the Siebel database Relationships between base tables (referential integrity) rely upon

primary keys (PKs) and foreign keys (FKs) based on ROW_IDs ROW_ID is the system primary key for every base table ROW_ID is a system-generated value

PK

S_ORG_EXT S_ADDR_ORG

FKFKPK

S_BU

FK

1/4


Interface Tables

Interface tables store external data inside the Siebel database Staging area for data to be imported, updated, or merged into

base tables by EIM Staging area for data exported by EIM Staging area for data to be deleted in the base table by EIM

EIM_ACCOUNT S_ORG_EXT

S_ADDR_ORG

External data

Interface Tables

Base Tables

External database

2/4



Interface Tables Continued

Are meant to represent typical business “entities” Typically map to multiple Siebel base tables

Are denormalized Example: EIM_ACCOUNT interface table maps to eight base

tables

2/4



Manages the exchange of data between interface tables and user data in base tables

Belongs to Enterprise Application Integration (EAI) component group

S_ORG_EXT

S_ADDR_ORG

EIM_ACCOUNT

External data

3/4



EIM Configuration File

EIM server component reads a configuration file (.ifb) to determine: Whether data should be imported, merged, deleted, or exported Which interface table(s) and base table(s) are used and affected

Import, merge, delete, or export


4/4

Configuration file (.ifb)


User Keys

Based on multiple columns, user keys are used to uniquely identify a row for EIM

Primary and foreign keys based on ROW_ID are used for system-wide referential integrity

S_ORG_EXT

ROW_ID NAME LOC BU_ID

S_BU

User KeyPK FK


Referential Integrity

User key column mappings in interface tables are used to resolve ROW_IDs for base tables, maintaining referential integrity

PK (ROW_ID)

Acme

1-8D

User key

1-8DInterface Table

Base Tables

FK (ROW_ID)


SQL

You must not use SQL to populate user data in base tables Relationships between tables are complex Referential integrity is maintained programmatically through

ROW_IDs, not using constraints on the database SQL statements cannot generate Siebel ROW_IDs

FK PK

S_ORG_EXT S_ADDR_ORG

SQL


Module Highlights

Enterprise Integration Manager (EIM) is a server component that supports bulk imports and exports to and from a Siebel database Useful for initial data loads

The main components of EIM are: Base tables Interface tables EIM server component EIM configuration files (.ifb)

You must not insert user data into Siebel base tables using SQL!

49 copyright © 2007, oracle. all rights reserved. module 49: section i exploring integration...

Documents