Content Integration Architectures

1. Content Integration Architectures November 16, 2005

2. Agenda • Enterprise Content Integration Intro • Definitions • Standardized Content Clients • Content Caching • Content Bridge • Enterprise Services Bus • Case Study • Summary

3. WHY Enterprise Content Integration • Enterprise Application Integration (EAI) + • Voluminous Enterprise Content Repositories __________________________________ • Enterprise Content Integration (ECI)

4. ECI Defining continued • Web 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.

5. Content Clients Ways to access Content Repositories • JSR-170 • WEB-DAV • XML-RPC • JDBC/ODBC • RMI/COM+

6. Content Caching • 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.

7. Content Bridge • Pluggable repositories • Loosely coupled • Business Change Management • Content Monitoring • Workflow • Federated Views • Metadata Warehouse

8. 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

9. ESB

10. ESB Use Case • A partnering company sends an order to the ESB. • The ESB’s Event Endpoint receives it and decrypts the message • The endpoint’s pipe then authenticates the message producer via WS-Security policies • Then a filter inspects the content and figures out there is a registered pipeline for this type message and forwards the message. • The second pipeline’s first filter translates customer supply codes to out companies supply codes • The pipe’s next filter adds metadata to the message • The pipe’s last filter sends the message to the order fulfillment endpoint and consequently in the order fulfillment application

11. 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

12. Case Study – ECI Solution

13. Summary • Variety 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

14. Summary • This presentation is available at www.anexinet.com/events/kmworld05 Thanks for having Us! Any Questions?