Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Concept Proposal A standards based SOA Framework for ...

527 views

Published on

  • Be the first to comment

  • Be the first to like this

Concept Proposal A standards based SOA Framework for ...

  1. 1. Concept Proposal A standards based SOA Framework for Interoperable Enterprise Content Management Mike Connor miconnor@adobe.com Paul Fontaine Paul.Fontaine@ost.dot.gov
  2. 2. What is it? IECM Framework • Vision: – A SOA standards based framework to enable interoperable content / document processes – The framework is registry / repository centric enabling design, development, publishing, discovery and interoperation of document centric work processes – IECM will be developed as an open standard in conjunction with customers, ISV & SI partners and standards organizations • Objective: – Lower the life cycle costs of content intensive business process – Provide a common layer of interoperable services / infrastructure that enable content and content management systems to interoperate with core enterprise applications and work processes.
  3. 3. What do Users get from IECM? “Information - when, where & how it is needed • IECM solves the problem of creating interoperable document / content centric process flows • IECM will connect customers documents, content and related process to their enterprise’s services delivery and back end systems • IECM binds unstructured & semi structured content to emerging SOA, EDA and POA • Key Benefits – Accelerate and reduce the cost of delivery of transformed services in which content is bound to process – Improved Business Effectiveness - Information Sharing / Collaboration – Just in Time, Just Right, My Way Information – Highly adaptive and configurable environment – easily changed to meet new business requirements – Ability to multi purpose / re use existing ECM components
  4. 4. What is ECM? • Real-time information exchange • Content sharing • General Records Schedule (GRS) • Collaborative Document production Processing • Interface with related functions • Archival – eRecords management • Disposal – Online Rulemaking • LOB Applications interface – Web Content Management • E-Government Application – Electronic Publishing Collaboration Interface – Document Management Records • Integration with related functions Management •Correspondence control • Web site management • Lifecycle management •Forms (workflow) •Electronic publishing • Personalization & •Web Content Customization •Archival • Dynamic content delivery Web Electronic •Privacy • Content testing (508, Publishing • Multi-format rendering hyperlink, privacy,security) Content • Archival management – Internet • Digital asset management Management – Intranet • Integration with: – PDA – Content creation tools – Fax – Enterprise portal – Voice – Web applications – Paper Forms • Repurpose Content • Content Creation Document Management •Form Delivery, (HTTP, FTP, Email) • Version control •Electronic Signature/User • Library Services Management Identification • Workflow •Form Management • Lifecycle Management •Populate/Deliver Forms • Attribute-based and full text searching •Workflow - Process control, • Electronic distribution (subscriptions) Approval route • Hard copy printing •Version control • Hard copy distribution (subscriptions) •Archive •Data Mgt. - Insert/extract/route data
  5. 5. Doculab’s ECM Architecture
  6. 6. What is the Deliverable? The IECM Architecture Front End ECM Processes External Systems Processes IECM Web Services / SOA Architecture Process Services Search / Find Format Create / Organize Store / Distribute Archive / Acquire / Process Retrieve / Publish Destroy Service Bus Rules / Event Management Secure / Authenticate / Administer Integrate / Orchestrate Document Back End / Form Desktop Applications
  7. 7. Deliverables Web Service Descriptions / Requirements / Schema Client Layer IECM IECM Services (1). 1 Infrastructure Layer Name Provides a common set of interfaces by which ECM Description systems can interoperate. Allows ECM systems from different organizations and Purpose vendors to interoperate and manage content over its life cycle securely. IECM services provide a standardized approach for content- centric processes that span organizations, in a fashion that What it does is designed to work within a services-oriented architecture (SOA). What it Does not provide end-to-end services for enhancing or providing access to all common functionality found in ECM Directory syncRegistry() doesn't do systems; the focus is to provide access to only those Name Metadata (1.4.2). Inputs services that are part of an interoperable environment. Content, data, rules, processes, etc. in a particular format. [a.k.a. Registry] 1.4 Description Purpose Metadata repository services are one of the most important class of services in an IECM architecture. The repository these services provide access to contain inform ation about where data and content reside throughout a content management solution (even if this solution is a highly distributed and federated complementation of solutions). To help locate information, content, and services across organizational boundaries in a secure manner. <XML Schema & Data>, The metadata registry service should have the ability to interact with other remote metadata directory services in Content, data, rules, processes, etc. in a different (ideally order to find the information being requested. It should allow Outputs a system or users through an application interface t o locate Web Services, What it does information or store information on the location of content. It standardized) format. is also possible that the registry service have a Data synchronization capability to be used with other registries that are commonly consulted. Provides APIs and interfaces to access key functionality What it Does not provide the underlying content management or structured data management solutions in which the content Function within existing content management solutions. Name Directory [a.k.a. Registry] (1.4). doesn't do resides; it simply provides capabilities to store information related to what exists in these registries. Inputs Search criteria or request (store metadata, sync, etc. ) A child services case worker needs to securely access and Directory and location services are used to find information Outputs Acceptable data structure, content, further location information Provides interfaces to query a metadata registry (and Documentation retrieve criminal records for the parents of an abused child. and information about information throughout an Function potentially other external metadata repositories) for the location of information The information resides in the content stores of one or more organization. Most users are not even aware that they are Examples Parents: Directory (1.4) Examples agencies and must be located using a federated search on Description leverage one or more directory services. Managing user IECM parents Children: searchRegistry (1.4.2..1), storeLocationInformation (1.4.2..2), and children synchronizeRegistry (1.4.2.3), addPartnerRegistry both the local and state level. The information contains both profiles, looking up colleagues, participating in a workflow, (1.4.2..4), deletePartnetRegistry (1.4.2.5), getRegistryInformation (1.4.2.6), etc. structured records and unstructured reports and content. and searching for documents all involve some combination Parents: None (except for multiple inheritance from of directory and location services. getRegistryInfo() Layer To help locate information, content, and services across Metadata (1.4.2). general ECM functionality). Purpose Name IECM parents and children Children: Security (1.1), Transaction and Messaging (1.2), Integration (1.3), Directory (1.4), Connectivity What it does organizational boundaries in a secure manner. Allows systems and users to conduct information searches across multiple organizational boundaries. Description Purpose Metadata repository services are one of the most important class of services in an IECM architecture. The repository these services provide access to contain inform ation about where data and content reside throughout a content management solution (even if this solution is a highly distributed and federated complementation of solutions). To help locate information, content, and services across organizational boundaries in a secure manner. <XML Schema & Data>, (1.5), Lifecycle (1.6), Document Retrieval and Storage The metadata registry service should have the ability to interact with other remote metadata directory services in (1.7), Process and Workflow (1.8). Does not provide the underlying content management or What it does order to find the information being requested. It should allow a system or users through an application interface to locate Web Services, information or store information on the location of content. It What it structured data management solutions in which the content is also possible that the registry service have a synchronization capability to be used with other registries that are commonly consulted. doesn't do resides; it simply provides search capabilities across What it Does not provide the underlying content management or structured data management solutions in which the content registries. doesn't do resides; it simply provides capabilities to store information Metadata Inputs related to what exists in these registries. Search criteria or request (store m etadata, sync, etc.) Inputs Registry location information, search criteria. Outputs Acceptable data structure, content, further location 1.4.2 information Documentation Provides interfaces to query a metadata registry (and Function potentially other external metadata repositories) for the location of information Acceptable data structure, content, further location Outputs information. Examples Parents: Directory (1.4) Children: searchRegistry (1.4.2..1), IECM parents storeLocationInformation (1.4.2..2), and children synchronizeRegistry (1.4.2.3), addPartnerRegistry Provides APIs and interfaces to query one or more (1.4.2..4), deletePartnetRegistry (1.4.2.5), Function registries in a federated manner. Metadata (1.4.2). getRegistryInformation (1.4.2.6), etc. Name When sensitive information flows between organizations, Metadata repository services are one of the most important there may be a need to use strong encryption technology class of services in an IECM architecture. The repository Examples before data transmission. To do this the send must locate Description these services provide access to contain information about where data and content reside throughout a content searchRegistry() and retrieve the public key(s) of the person or people they Name Metadata (1.4.2). are sending the content to. This can be made possible management solution (even if this solution is a highly Metadata repository services are one of the most important class of services in an IECM architecture. The repository IECM parents through the use of registry services. Parents: IECM Services (1) Purpose distributed and federated complementation of solutions). To help locate information, content, and services across organizational boundaries in a secure manner. Description Purpose these services provide access to contain information about where data and content reside throughout a content management solution (even if this solution is a highly distributed and federated complementation of solutions). To help locate information, content, and services across organizational boundaries in a secure manner. The metadata registry service should have the ability to <XML Schema & Data> Children: User (1.4.1), Metadata (1.4.2), Services interact with other remote metadata directory services in and children The metadata registry service should have the ability to order to find the information being requested. It should allow a system or users through an application interface to locate (1.4.3), Process/Rules (1.4.4) interact with other remote metadata directory services in What it does information or store information on the location of content. It is also possible that the registry service have a Web Services, synchronization capability to be used with other registries that are commonly consulted. order to find the information being requested. It should allow Does not provide the underlying content management or What it structured data management solutions in which the content a system or users through an application interface to locate doesn't do resides; it simply provides capabilities to store information What it does information or store information on the location of content. It related to what exists in these registries. Search criteria or request (store metadata, sync, etc.) Inputs is also possible that the registry service have a Outputs Acceptable data structure, content, further location information synchronization capability to be used with other registries Function Provides interfaces to query a metadata registry (and potentially other external metadata repositories) for the location of information that are commonly consulted. Documentation Examples Parents: Directory (1.4) Does not provide the underlying content management or IECM parents Children: searchRegistry (1.4.2..1), storeLocationInformation (1.4.2..2), What it structured data management solutions in which the content and children synchronizeRegistry (1.4.2.3), addPartnerRegistry (1.4.2..4), deletePartnetRegistry (1.4.2.5), getRegistryInformation (1.4.2.6), etc. doesn't do resides; it simply provides capabilities to store information related to what exists in these registries. Inputs Search criteria or request (store metadata, sync, etc.) Acceptable data structure, content, further location Outputs information storeLocationInfo() Metadata (1.4.2). Provides interfaces to query a metadata registry (and Name Metadata repository services are one of the most important Function potentially other external metadata repositories) for the Description class of services in an IECM architecture. The repository these services provide access to contain inform ation about where data and content reside throughout a content location of information management solution (even if this solution is a highly <XML Schema & Data> distributed and federated complementation of solutions). To help locate information, content, and services across Purpose Examples organizational boundaries in a secure manner. The metadata registry service should have the ability to interact with other remote metadata directory services in order to find the information being requested. It should allow Parents: Directory (1.4) What it does a system or users through an application interface t o locate information or store information on the location of content. It is also possible that the registry service have a Children: searchRegistry (1.4.2..1), synchronization capability to be used with other registries that are commonly consulted. IECM parents storeLocationInformation (1.4.2..2), Web Services, Does not provide the underlying content management or What it structured data management solutions in which the content and children synchronizeRegistry (1.4.2.3), addPartnerRegistry doesn't do resides; it simply provides capabilities to store information related to what exists in these registries. Search criteria or request (store metadata, sync, etc.) (1.4.2..4), deletePartnetRegistry (1.4.2.5), Inputs Acceptable data structure, content, further location Outputs getRegistryInformation (1.4.2.6), etc. information Provides interfaces to query a metadata registry (and Function potentially other external metadata repositories) for the location of information Documentation Examples Parents: Directory (1.4) Children: searchRegistry (1.4.2..1), IECM parents storeLocationInformation (1.4.2..2), and children synchronizeRegistry (1.4.2.3), addPartnerRegistry (1.4.2..4), deletePartnetRegistry (1.4.2.5), getRegistryInformation (1.4.2.6), etc. Document Meta data & presentation & services Layer
  8. 8. IECM Service Definition - Example Name IECM Services (1). Description Provides a common set of interfaces by which ECM systems can interoperate. Allows ECM systems from different organizations and vendors to interoperate and manage Purpose content over its life cycle securely. IECM services provide a standardized approach for content-centric processes that span What it does organizations, in a fashion that is designed to work within a services-oriented architecture (SOA). Does not provide end-to-end services for enhancing or providing access to all common What it doesn't do functionality found in ECM systems; the focus is to provide access to only those services that are part of an interoperable environment. Inputs Content, data, rules, processes, etc. in a particular format. Outputs Content, data, rules, processes, etc. in a different (ideally standardized) format. Provides APIs and interfaces to access key functionality within existing content management Function solutions. A child services case worker needs to securely access and retrieve criminal records for the parents of an abused child. The information resides in the content stores of one or more Examples agencies and must be located using a federated search on both the local and state level. The information contains both structured records and unstructured reports and content. Parents: None (except for multiple inheritance from general ECM functionality). IECM parents and Children: Security (1.1), Transaction and Messaging (1.2), Integration (1.3), Directory (1.4), children Connectivity (1.5), Lifecycle (1.6), Document Retrieval and Storage (1.7), Process and Workflow (1.8). <<explain what types of services typically call this service within a process, and what types of services it might call as part of a process>> Process fit <add this to the templates> <Mike to provide additional input on this model>
  9. 9. Participation Benefits Interaction with a World Wide IECM Community of Practice Relationships Insight • Government • Real World • Industry Requirements • ISV’s • Thought Leaders • SI’s • Real Projects • Standards • Interoperability Groups Testing • Working Groups • Best Practice Development • Major Project and Program Market Alignment Managers • Whitepapers • Forums • Conferences • Standards
  10. 10. What Do Vendors get? • Projects - Opens doors to major enterprise and cross enterprise projects • Partnering - Opens doors to powerful partnering relationships • Enterprise Scale Deployment - Provides basis for truly enterprise level development, management and deployment of document services • Interoperable Next Generation Architecture - Provides a cross product line interoperability platform • Leadership - Creates a leadership seat at the design table for next generation enterprise environment - SOA, EDA & POA • Next generation products –Can productize and enhance IECM as well as the requirements that emerge from the IECM community
  11. 11. Current Status • AIIM – Standards Group – Formal process to recommend / establish IECM standards working group – Immediate extension to financial, manufacturing, and pharmaceutical industries – Will propose as an ISO standard – potential OASIS partnership – Endorsement from chair & senior members of document & content management interoperability standard working group. • Federal CIO Council – Support / Endorsement from chairs of emerging components groups • They have agreed to host and promote IECM group on web site • To help contribute to creation of the IECM standard • Help develop business case for IECM as top level component in Fed Architecture and to integrate and align with other working groups – Engagement with registry / repository working group • DOT – Seeking support to create an IECM center of excellence lab – will be extending invitation to help fund / staff to other government organizations and vendors as well as other working groups
  12. 12. IECM Development Methodology • Establish IECM Standards Working Group – Organizations with active IECM type projects – Develop and publish work plan and methodology • Review and refine Adobe provided IECM Draft 1 architecture – Review / refine against current real world requirements from working group – Publish V2 for review by market and analysts • Fund, Build & Staff IECM Center of Excellence (US & Europe) – Bring major architectural components together in an interoperability lab – Gather world wide requirements across industries – Gather world wide SOA / Web services components that align with IECM architecture – Begin test and integration of components in lab based on real world requirements – Refine and publish results and services back out for real world test and review • Publish community guidance, services and best practices back out to the world – Establish collaborative community (IBM AlphaWorks) • Publish & release standards in phases – Use a maturity model to evolve the standard – “The first thing we want to is be able to get the phone to ring, we will address electronic switching, failover, call forwarding in later phases.”
  13. 13. IECM 2005 Implementation Plan Q4 Q1 Q2 Q3 Q4 Formal Kick Off Whitepaper on Guidance & 1st Formal IECM 2nd Level of Standards Level Standards Architecture & components Group components Guidance for Effort description description Review Complete Web site & Lab up Publish results preliminary & running architecture work Hold conference Hold conference in DC in Europe Formal approach to vendors Formal approach to government & industry Ongoing –meetings with users, working groups, standards bodies & vendors

×