<Insert Picture Here>

Oracle Universal Content Management

Sreekanth Chintala (hacked by Dan!)
 Oracle Enterprise Content Management

• Universal Content Management

• Universal Records Management
• Imaging and Process Management
• Content Conversion Server
• Information Rights Management
UCM : Core Content Server Architecture
 Architecture Details
Relational Database

• Manages
• Metadata & Revision Information
• User & Security Information
• Configuration information

• Oracle Specifics
• Supports 11g, 10g
• Application queries optimized for Oracle DB

• Other Databases
• MS SQL Server
• DB2
 Architecture Details
Search Index

• General Architecture
• Pluggable search engine architecture
• Engine-agnostic “Universal Query Syntax”
• No search down time during re-indexing

• Supported engines
• Database (Oracle, SQL Server)
• Oracle Secure Enterprise Search 11g

• Metadata search can be executed against database even when

other full-text search engine is present
Architecture Details
File Store

File Store

Weblayou
Vault t
 Architecture Details
File Store (File System or Database)

Content Web Server

Server
Publish

Weblayou
Vault t

• Native Files • Renditions and thumbnails of content

• Any number of renditions
• Access via service calls only • Mapped to web server for optimized content
delivery
• Images, CSS & JS files needed to render UI
Vault files are well • Published data for optimized performance
• Content Server: Metadata Schema
Relational suited to be stored
• WCM: Site Structure, Fragments, etc.
Database in a relational • Allows assets to be cached by web server and
database browser
 Architecture Details
Metadata

Metadata Pool Rules Engine Profile HR Policy for

HR Employee in USA
Standard Metadata Present the right metadata • Title
Content ID for the right user • Type
Title at the right time
Content Type
• Comments
. Control fields and
• Department
. values with rules based on
• Other metadata
• User attributes Profile HR Policy for
Custom Metadata • Content state
• Any other criteria
Director of HR
Comments
Department
• Title
Retention Policy Use rules to determine • Type
• Default values
Image Rendition Set • Comments
• Derived values
Contract Due Date • Field Captions • Department
Country • Metadata Groups • Sub Department
State • and more…
City
• Region
.
.
 Architecture Details
Security

• Security Models
• Multiple models available
Roles and Groups • Multiple models can be used at the same time

• Popularity
Accounts • Most customers use Roles and Groups
• Growing use of Accounts in recent years
# Customers
• ACLs used by very few customers (mainly for
Collaboration and RM)
• Need To Know is used only by a couple of
ACL government agencies

NTK
• LDAP and Single Sign-On Support
• OID, Oracle Access Manager
 Architecture Details
Security: Roles and Groups

R,W,D,A
Roles and Groups Users Roles Groups Documents
R, W
Joe HR HR Vacation
Contributor Policy Schedule
Accounts R
Finance Finance Expense
User Policy Report
# Customers

ACL

NTK
 Architecture Details
Security: Accounts

Hierarchal Model
Roles and Groups
Users Accounts Documents

Accounts

# Customers Acme/HR/EMEA EMEA Vacation Schedule

Joe Acme/HR/*
Acme/HR/General/Policies Benefits Overview
ACL

Dave Acme/HR/US/* Acme/HR/US/Policies US Vacation Schedule

NTK
 Architecture Details
Security: ACL

User Access Lists, Group Access List

Roles and Groups
Users Documents

Joe, Dave, Ann Benefits Overview

Accounts Joe, Dave US Vacation Schedule
Joe, Ann EMEA Vacation Schedule
# Customers

ACL

NTK
 Architecture Details
Security: Need To Know

Rule-based access to content

Roles and Groups

If User = ‘Joe’ AND

Accounts Type LIKE ‘Document’ AND
CurrentTime > 9 AM AND
# Customers CurrentTime < 5 PM
Then
ACL Allow access to HR Documents

NTK
Integrating with UCM Services

Course-grained actions and functions

Focused on content management

 UCM Services

Check-in Search Info Add user Remove user

UCM Services

My fancy custom My totally cool “print

check-in service from server” service
DocCompliance / WCC Feature Map
The Integration vs Customization question...

DocCompliance Webcenter Content

Electronic Signature
FDA 21 CFR Part 11
Role-based ES
Audit Trail
Hardcopy Management
Automated Version Control
Read & Understood
Electronic Signature Component
FDA 21 CFR Part 11 (USDM cert)
unknown
Need to identify the 270 events.
PDF Watermarking
Core feature
none
 Integration Techniques
SOAP – Standardized XML-based Messaging Protocol

Advantages:
• Well-known standard protocol
• Available for any language that supports SOAP (C#, VB.NET, ASP, Java, PHP, Javascript,
Python, many more)

Disadvantages:
• No configurable caching; all caching must be coded into application
• No built-in application logging; all logging must be coded into application
• Requires extensive Content Server architecture knowledge
• Requires more overhead than other integration methods (i.e. possible performance issues
without caching)
• Must be familiar with building the SOAP requests and parsing the SOAP responses
• Only supports connecting via the web server (authentication required for every request)
 UCM Services

Service Name: GET_SEARCH_RESULTS

Request Parameters: QueryText, ResultCount, SortField, SortOrder, …
UCM Services
UCM Services

IsSoap=1 for SOAP response

UCM Services

IsSoap=1 for SOAP response

UCM Services

IsSoap=1 for SOAP response

 Integration Techniques
WSDL – Content Server Implementation of Standardized WDSL

Advantages:
• Well-known protocol (SOAP-based)
• SOAP tool kits available available for many languages (automatically generate the source
code necessary for integration)
• Not necessary to extensively learn the Content Server architecture
• Not necessary to be familiar with building SOAP requests or parsing the responses

Disadvantages:
• No configurable caching; all caching must be coded into application
• No built-in application logging; all logging must be coded into application
• Requires more overhead than other integration methods (i.e. possible performance issues
without caching)
• Only supports connecting via the web server (authentication required for every request)
UCM Services as Web Services

• Execute services with

IsSoap=1 over HTTP

• Use WSDLs
– Pre-defined WSDLs for
common services
– WSDLGenerator to create
WSDLs for any service

• Technology Agnostic
– .Net, PHP, Python, etc.
JavaScript Object Notation
(JSON)
Simple way to integrate with UCM via AJAX
• Integrate from JavaScript
Web Page
• Ideal for web integrations
– Intranet Portals
HTTP – Web Sites
JSON

• Native support for JSON in

UCM
UCM

• Perfect for accessing Site

Studio services
UCM Services

IsJson=1 for JSON response

IsJava=1 for serialized
data response
 JSON

Connect & Execute Service Request

Parse Response

Extract Data from Response

 Integration Techniques
Content Server Integration Suite – CIS – Proprietary Java API for
Communicating with Content Server (not recommended)

Advantages:
• Abstracted from Content Server (faster to use for experienced Java Developers who have
less Content Server experience)
• Built-in Configurable Caching
• Highly scalable
• Provides easy method for federating requests to multiple Content Servers at once (single
request is built and sent to multiple content servers)
• Very verbose configurable logging at the application level, and communication with Content
Server
• Supports connecting via web server (authentication required for every request) or directly to
Content Server socket (trusted connection)

Disadvantages:
• Large and highly abstracted; can be difficult for beginners to learn
• Not lightweight; uses more system resources for enterprise applications
• Only available for Java applications
 Integration Techniques
RIDC – Proprietary Thin-Client API for Communicating with Content Server

Advantages:
• Easy to learn for those with extensive Content Server experience (very little abstraction from
Content Server)
• With proper development, can be highly scalable, but requires more attention to detail
• Very lighweight; uses less system resources than CIS for enterprise applications
• Supports connecting via web server (authentication required for every request) or directly to
Content Server socket (trusted connection)

Disadvantages:
• No configurable caching; all caching must be coded into application
• No built-in application logging; all logging must be coded into application
• Requires extensive Content Server architecture knowledge
• Only available for Java applications
Remote Intra-Doc Client (RIDC)
Simple yet Powerful

• “Plain Old Java Object”-

based API to execute any
RIDC
SOAP Trusted service

HTTP • Multiple Communication

Modes
Socket – Trusted (provide username
UCM only)
– SOAP over HTTP (requires
username and password)

• Part of Content Integration

Suite (CIS)
 RIDC

Connect to Server

Add info about service to execute

Execute Service and Extract Response Data

 Useful Links

Oracle Fusion Middleware books:

http://docs.oracle.com/cd/E23943_01/nav/portal_booklist.htm

RIDC Java API Reference:

http://docs.oracle.com/cd/E23943_01/apirefs.1111/e17274/toc.htm

The Definitive Guide to Stellent Content Server Development:

http://www.apress.com/9781590596845

USDM Part 11 Certification for Oracle Webcenter Content

http://usdatamanagement.com/enterprise-content-management-/274.html
 Useful Links

Oracle Fusion Middleware books:

http://docs.oracle.com/cd/E23943_01/nav/portal_booklist.htm

RIDC Java API Reference:

http://docs.oracle.com/cd/E23943_01/apirefs.1111/e17274/toc.htm

The Definitive Guide to Stellent Content Server Development:

http://www.apress.com/9781590596845

USDM Part 11 Certification for Oracle Webcenter Content

http://usdatamanagement.com/enterprise-content-management-/274.html

Web User Interface Developer's Guide for Oracle Application Development

Framework
http://docs.oracle.com/cd/E23943_01/web.1111/b31973.pdf