Content Integration Architectures November 16, 2005.

14
Content Integration Architectures November 16, 2005

Transcript of Content Integration Architectures November 16, 2005.

Page 1: Content Integration Architectures November 16, 2005.

Content Integration Architectures

November 16, 2005

Page 2: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

AgendaEnterprise Content Integration Intro

Definitions

Standardized Content Clients

Content Caching

Content Bridge

Enterprise Services Bus

Case Study

Summary

Page 3: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

WHY Enterprise Content IntegrationEnterprise Application Integration (EAI)

+

Voluminous Enterprise Content Repositories

__________________________________

Enterprise Content Integration (ECI)

Page 4: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

ECI Defining continuedWeb Services – Open standards UDDI, WSDL, SOAP, and HTTP. All are managed by standard bodies like W3C and OASIS.

Enterprise Information Integration (EII) Enterprise Content Integration is practically interchangeable with

EII but when we refer to ECI know that the solution is content driven not just Information driven.

Page 5: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

Content ClientsWays to access Content

Repositories

JSR-170

WEB-DAV

XML-RPC

JDBC/ODBC

RMI/COM+Content Cache

orContent Repository

Internet SiteSearch Engine

PC Based Application

RMI

WEB-DAV

XML-RPC

Page 6: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

Content Caching

Content StorageArea 1

Content StorageArea 2

Mainframe Storage

Content Cache

File system

Internet Site Search EnginePC Based Application

Centralized copy of content

Content is usually pushed to the cache. ETL Synchronized (i.e.. rsync) FTP

Not the data source of record for the content that it serves

Focus’s on high performance production delivery of content.

Page 7: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

Content Bridge

Pluggable repositories

Loosely coupled

Business Change Management

Content Bridge

Content StorageArea 1

Content StorageArea 2

Mainframe Storage File system

MetadataWarehouse

Bridge Rules

Content Monitoring

Workflow

Federated Views

Metadata Warehouse

Internet Site Search EnginePC Based Application

Page 8: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

Enterprise Service Bus (ESB)Features

Content Based Routing

Content Enricher

Guaranteed Delivery

Message Brokering

Service Registry

Event-Driven Consumers

Message Channels

Message Translator

Governance Features

Reporting

Control Bus

Wire Tap

Smart Proxy

Versioning

Security

Page 9: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

ESB

Controller

Reporting

J2EEApp

J2EEApp

ContentStorageArea 1

ContentStorageArea 2 Mainframe Storage File system

Enterprise Service Bus

SAP J2EEApp

CRM / SiebelJ2EEApp

.NETApp

.NETApp

.NETApp

.NETApp

WS-Policy

ServiceMonitoring

SLA Security

MetadataWarehouse

Page 10: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

ESB Use Case1. A partnering company sends an order to the ESB.

2. The ESB’s Event Endpoint receives it and decrypts the message

3. The endpoint’s pipe then authenticates the message producer via WS-Security policies

4. Then a filter inspects the content and figures out there is a registered pipeline for this type message and forwards the message.

5. The second pipeline’s first filter translates customer supply codes to out companies supply codes

6. The pipe’s next filter adds metadata to the message

7. The pipe’s last filter sends the message to the order fulfillment endpoint and consequently in the order fulfillment application

Page 11: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

Case Study – Unnamed Government Department

For many years several dispersant agencies have provided interrelated very detailed information.

Congress mandates to give the citizen a single website to view all the content.

50k + publications are released a year by these Agencies.

7 different websites contain silo’d query mechanism Utilizing similar but not the same search criteria values

Page 12: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

Content Cache

Case Study – ECI Solution

Agency1

Agency 2Mainframe Store

Agency3

Agency4

Agency5

Agency 4

Agency6

Agency 2

MetadataWharehouseContent Bridge Enterprise Service Bus

Citizen

Page 13: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

SummaryVariety of Connectors to Content Repositories

Finer grain control of Content

Caching Content abstracted from the repositories to extend capabilities of

content production

Bridging Unifying content repositories to the enterprise

Enterprise Service Bus Connecting your Enterprise Application to your Enterprise Content

Page 14: Content Integration Architectures November 16, 2005.

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

SummaryThis presentation is available at www.anexinet.com/events/kmworld05

Any Questions?

Thanks for having Us!