While Oracle Universal Content Management (Oracle UCM) is highly functional "out of the box," there are many ways to tailor it to your site requirements. This guide provides the background information necessary to customize your Oracle UCM instance.
This guide is intended for developers and administrators who want to customize Oracle UCM software to suit content management needs that are specific to their business or organization.
This guide includes the following sections:
Chapter 1, "Introduction to Customizing Your Oracle UCM Instance," provides an introduction to the methods and tools you can use to customize Oracle UCM.
Chapter 2, "Oracle UCM Architecture," describes the architecture of Oracle UCM and how that affects the customization you can make.
Chapter 3, "Working with Standard, Server, and Custom Components," describes how to use components to modify or add functionality to Oracle Content Server.
Chapter 4, "Changing the Look and Navigation of the Oracle Content Server Interface," defines the items you can adjust to change the look and navigation of the Oracle Content Server interface.
Chapter 5, "Modifying System Functionality," describes how you can change the functionality of Oracle UCM settings, components, and configuration variables.
Chapter 6, "Integrating Oracle UCM with Enterprise Applications," provides information about integrating Oracle Content Server with enterprise applications such as application servers, catalog solutions, and enterprise portals.
Chapter 7, "Using the IdcCommand Utility to Access Services," provides information about using the IdcCommand utility to access Oracle Content Server services from other applications.
Chapter 8, "Using the COM API for Integration," provides information about how Oracle Content Server utilizes a Component Object Model-based API, which provides the capability to call functionality from within a Microsoft Component Object Model (COM) environment.
Chapter 9, "Using Remote Intradoc Client (RIDC)," describes Remote Intradoc Client (RIDC) and how you can use the RIDC API for communication with Oracle Content Server.
Chapter 10, "Using Content Integration Suite (CIS)," describes the Content Integration Suite (CIS) API, which you can use to access Oracle Content Server services and data from a unified object model.
Chapter 11, "Using the Java Content Repository Adapter," provides information about the Java Content Repository API, which was developed under the Java Community Process as JSR-170 and includes the Content Repository for Java API and the Java Content Repository (JCR).
Chapter 12, "Using Oracle UCM Web Services," discusses using web services and SOAP (Simple Object Access Protocol) to manage Oracle Content Server.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Oracle customers have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/support/contact.html or visit
http://www.oracle.com/accessibility/support.html if you are hearing impaired.
For more information, see the following documents in the Oracle Universal Content Management 11g Release 1 (11.1.1) documentation set:
The following text conventions are used in this document.
|boldface||Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.|
|italic||Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.|
||Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.|