top 10 ways to integrate with oracle enterprise content management (ecm)

Download Top 10 Ways To Integrate With Oracle Enterprise Content Management (ECM)

Post on 13-Jan-2015

22.890 views

Category:

Technology

3 download

Embed Size (px)

DESCRIPTION

Oracle Enterprise Content Management (ECM) can manage your unstructured content, no matter where it exists. As a result, there are well over 50 different ways to integrate it with your system. This presentation lists the top 10, and a few others as \"honorable mention.\"

TRANSCRIPT

  • 1. Top 10 Ways To Integrate With Oracle ECM Brian Bex Huff Chief Software Architect

2. Agenda

  • ECM integration basics
    • Whats involved, why its useful
  • The Top 10 ways to integrate
    • Out-of-the-box tools
    • Frameworks
    • Web services
  • Some honorable mentions
    • Less common, but still important!
  • Recommendations

3. Integration Basics

  • UCM is a service-oriented architecture
    • Easy to consume services from remote applications
    • Easy to customize services for your needs
  • Integrations come in several forms
    • Pre-built integrations
      • Just install, and configure.
    • Framework integrations
      • Lets you easily create content-rich applications and interfaces
    • Web-service integrations
      • Direct APIs for the most options and power.
    • Customizations to the applications
      • Integrate the back-end with your systems.

4. The Top Ten

  • Secure Enterprise Search
  • SOAP
  • Content Integration Suite (CIS/CPS)
  • Open WCM
  • JCR Adapter and WebCenter
  • AJAX / Mashups
  • AquaLogic Ensemble (WebCenter Services)
  • Records Management Adapters
  • BPEL Workflows
  • Custom components and security integrations

5. Secure Enterprise Search

  • Enables you to search across multiple systems
    • Content Manage Systems: Stellent, Documentum, FileNet
    • Legacy system: shared file systems, web sites, Lotus Notes
    • Enterprise Applications: Siebel
    • Generic database table search
  • Multiple security options
    • Global security policy, application specific policy
    • Can oranize results differently based on user context
      • Department, location, language, etc.
  • Easy to set up
    • Multiple connectors, generic spiders, plus integration API

6. Secure Enterprise Search screen Find information wherever it lives in your organization. Browse content hierarchy from your search results. Sort results by relevance, date or other criteria. Login to enable secure access to any application you are authorized to see. Filter results by topics or metadata values such as record type, author, or other criteria. See search term highlighted in context in your hit results. 7. SOAP

  • Open XML-based protocol for application integration
    • Typically over the web (HTTP), or in messages
    • Fundamental part of Microsofts .NET framework
    • Toolkits exist for almost every language and platform
  • Built into Content Server
    • SOAP support built into Content Server (7.5 and above)
    • WSDLGeneratorcomponent bundled with Content Server (10gR3 and above); separate extra for 7.5.x
    • AddIsSoap=1to any content server URL
  • Web Services Description Language (WSDL)
    • Helps SOAP toolkits parse XML into easy to use objects
    • One object to execute the service
    • Binds the XML request and response into data objects

8. SOAP Benefits

  • All UCM services available through SOAP
    • Can create XML request manually, or use WSDL
    • 7.5.x and later passIsSoap=1into any URL or request to get back SOAP
  • All the benefits of XML and HTTP
    • Simple, extensible, used almost everywhere
    • Most developers comfortable with the technology
  • Toolkits available for nearly every language
    • Java, C, C++, C#
    • Python, Perl, PHP, Ruby
    • JavaScript, Flash, Flex

9. SOAP Challenges

  • All the drawbacks of XML and HTTP
    • Stateless requests both good and bad
    • Standard security challenges with HTTP
    • Verbosity presents performance challenges
  • SOAP (and WSDL) considered needlessly complex
    • Some prefer ReST-based approach
    • UCM is mostly, but not entirely, ReST-ful
  • SOAP with ReST-like simplicity
    • Use theIsSoap=1flag
    • Use the URL Mapping feature built-in to 10gr3

10. SOAP vs. ReST

  • Fewer tools available for security, auto configuration, etc.
    • No WSDLs
    • Although it usually is simple enough to not need these tools
  • HTTP is kind of broken: sometimes it needs help
    • Messaging, polling, encoding, quality of service.
    • HTTP not good for all use cases.
  • Difficult to separate the good ideas from ReST dogma

11. Content Integration Suite (CIS/CPS)

  • Standards compliant JEE application for UCM
    • Client connector, plus service cache
  • Supported on all major Java app servers
    • Oracle App Server, Websphere, WebLogic, JBoss, Tomcat
    • Plain Old Java Objects
  • Complete coverage of UCM API
    • Common services available as objects-oriented API
    • Can execute any UCM service
    • Can also interface with IPM

12. CIS/CPS Continued

  • CIS allows Java apps to communicate with UCM
    • CIS server connects to Content Server
    • CIS client is used in your app to connect to CIS server
    • CIS server caches results for faster performance in peak hours
    • Server supports multiple interfaces: JMS, JCA, EJB, RMI
  • Content Portal Suite (CPS) for J2EE Portal Server
    • Uses CIS to connect to UCM
    • Contains sample portlets for interacting with UCM
    • Search, Library, Contribution, Workflow, Admin
    • Federated Search (Combined search over I/BPM and UCM)

13. Open Web Content Management

  • Distributed model for web content management
  • Manage web content in containers outside the repository
    • Display images, text, converted Word docs
  • Alter content in-context with the application!
    • Standard Site Studio contributor editor
    • Launch in remote portal or web app
    • Uses standard workflows, conversion, subscription, etc.
  • Change it in one portal, see it change in them all!

14. Open WCM Architecture 15. Java Content Repository (JCR) Adapter

  • Java Content Repository
    • Java standard for content management
    • Formerly known as JSR170 and JSR283
  • Oracles JCR adapter connects to UCM through CIS
    • Achieves Level 1 compliance with JCR
  • Easy integration with WebCenter ADF components
    • Create a JCRData Control
    • Bind to ADF Tables and Trees
    • Show thumbnails, content, and limited metadatas

16. JCR Adapter Limitations

  • Only works with Java
    • Cannot connect to SharePoint with JCR connectors
  • Less powerful than SOAP or CIS alone
    • Very limited feature set
    • Gives an awkward view of the content repository
  • Limited ECM vendor adoption; not a popular standard
  • IBM, EMC, and Microsoft have dropped it in favor of CMIS
    • Oracle and others will likely follow suit

17. Asynchronous JavaScript and XML (AJAX)

  • Several AJAX options
  • Use semi-ReSTful SOAP int

Recommended

View more >