Oracle - The following is intended to outline our …...The following is intended to outline our general product direction. It is intended for information purposes only, and may not

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

<Insert Picture Here>

The Wait is Over:Standards-Based Content IntegrationPhilipp WeckerleProduct Manager / Strategy

Agenda

<Insert Picture Here>• What About All That Content ?• Standards-Based Content Access• Oracle’s Path to JCR• Your Path to JCR• How to Get There

What About All That Content ?Fragmented, all over the enterprise

Did someone send them an email?When did that price

change? Who has access to those files?

Is this the latest version of the

contract?Where is that Powerpoint

Presentation?

What About All That Content ? The Problem

<Insert Picture Here>• Cumbersome discovery and retrieval• Unnecessary duplication• Missed revenue opportunities• Difficulty in distribution and access control• Difficulty in aggregation• Usage tracking and reporting

What About All That Content ? The Problems that drive Content Integration


What About All That Content ? Content Integration – Why bother ?

RepositoryRepositoryAA

ApplicationApplicationAA

API AAPI A

RepositoryRepositoryBB

ApplicationApplicationBB

API BAPI B

RepositoryRepositoryCC

ApplicationApplicationCC

API CAPI C

RepositoryRepositoryDD

ApplicationApplicationDD

API DAPI D

What About All That Content ? Content Integration – Why bother ?

JDBC DOM/SAX FS ??? ??? Standardized Repository Access API

RDBMS XML BLOBS Config Users

Your currentApplication!

Content Repository

Your nextApplication?

Agenda



The Solution

Java Content Repository

Standards-Based Content AccessWhat is JCR ?

Level1

Read onlySimple & Covers a large number of usecases

StructuredStrong typed information

HierarchicalParent child relationships, Sort order

PropertyTypesString, Binary, Numbers, Calendar, ...

NodeTypesIntrospect complex Content Structures

Query (XPath)Search and query the Repository

ExportStandardized XML Content Export

Fine & CoarsegrainedContent Items Small to Large

Standards-Based Content Access What is JCR ?

WriteSave changes to a repository

UnstructuredSupport for weakly or unstructured Content

ImportStandardized Finegrained Content Import

Referencial IntegrityReference Tracking and Integrity

AccessControlIntrospection

Level 2

Standards-Based Content Access What is JCR ?

VersioningWorkspaces, Merge, Update, Label, ...

JTA Support(XA) Transactions

ObservationMonitor changes in the Repository

Query (SQL)Search the Content Repeository using SQL

LockingSession based and persistant

Optional

Standards-Based Content Access The Goal?

J2EE App-Servers

RDBMS

WebServerOS

Content Repository

Enterprise Software

Standards-Based Content Access Why JCR?

Silos, Point-to-point, Needs API Knowledge



API AAPI A



API BAPI B



API CAPI C



API DAPI D


Unify access through use of Standards



API AAPI A



API DAPI D



API BAPI B



API CAPI C


Unify content without application impact



API AAPI A



API BAPI B



API CAPI C



API DAPI D

Centralized Centralized RepositoryRepository

Agenda



Oracle’s Path to


Oracle’s Path to JCRContent Centric Applications

Repository

API

Application

Oracle ContentDB &Oracle Portal

or 3rd party repositories

Content Adapters

Oracle ADF &Content Data Control

GUI, Workflow, Delivery, …

JSR 170CompliantRepository

JSR 170 API

Oracle’s Path to JCRWhy JCR?

• Standards-based content access through JCR• Open connectivity through repository-independent

API• Out-of-the-box support for:

• Content DB• Portal

• 3rd -party adapters available

Oracle’s Path to JCRWhy ADF and Data Controls?

• Development Framework following the MVC design-pattern

• Content Data Control (JSR-227)• Drag-and-Drop development• Repository independent

Oracle’s Path to JCRData Control Facts

• Browse content (= getItems)• Get direct access URL for content (= getURL)• Retrieve attributes (= getAttributes)• Search by:

• Keyword or name pattern (= search)• Any attribute or combination of attributes

(= advancedSearch)

Agenda



Your Path to


DEMONSTRATION


Live Demonstration

Agenda


How To Get ThereBundling/Packaging

• Oracle WebCenter Suite 10gR3• Oracle WebCenter Framework• Oracle WebCenter Services

• Content Management (Oracle Content DB)• Search (Oracle Secure Enterprise Search)• Discussionforums (Jives)• VoIP• Wiki/Notes• Presence & Instant Messaging

Oracle Fusion Middleware

How to get thereRoadmap / Next Steps

• Further extensions to adapters• Additional adapters • Tight integration with other services• Document Library - integral part of CM strategy for

Oracle WebCenter Suite

Activities - PORTAL

DEMO Grounds

10:30 AM – 2:00 PM 2:45 PM – 6:30 PMMonday

Open House: 5:30 – 6:30 PM

Wednesday 10:45 AM – 5:30 PM

Tuesday 10:15 AM – 3:15 PM 4:00 PM – 5:30 PM

Thursday 10:00 AM – 1:30 PM

Moscone SouthExhibition Hall

Sessions - PORTAL

Time RoomTitleDay

Wednesday

Enterprise Portal in 90 Days: Critical Success Factors

SOA: Compelling BPEL Human Workflow Interactions

Sneak Preview of WSRP 2.0 and JSR-286

11:00 AM MosconeSouth 102Thursday

12:30 PM MosconeSouth 308

8:00AM MosconeSouth 308

S283659

S281764

S281759

5:30 PM MosconeSouth 309 Process Portals: Using Portals To Work SmarterS283096

Summary

<Insert Picture Here>• Content is everywhere• Unify in phases• Standards-based development

Oracle - The following is intended to outline our …...The following is intended to outline our general product direction. It is intended for information purposes only, and may not

Documents