This guide describes concepts and tasks for configuring and managing the Oracle Content Server system.
This guide is intended for people who are responsible for configuring and administering Content Server.
This guide includes the following sections:
Chapter 1, "Introduction to Oracle Content Server Administration," provides an overview of Content Server administration tasks, Oracle Enterprise Manager Fusion Middleware Control, Oracle WebLogic Server Administration Console, Oracle WebLogic Scripting Tool, the Content Server Administration page and utilities, and how to run Content Server administration applications.
Chapter 2, "Using Oracle Fusion Middleware Control to Manage Oracle UCM Content Server", provides information on using Fusion Middleware Control to access UCM Content Server and manage certain Content Server tasks and configuration.
Chapter 3, "Managing System Settings and Processes," provides information on configuring and managing Content Server using system settings and processes.
Chapter 4, "Managing Security and User Access," provides information on managing content security, user access, and network security for Content Server.
Chapter 5, "Working With Components," provides information on adding, removing, and managing components, which provide additional specialized functionality.
Chapter 6, " Managing Search Tools," provides information on using Oracle Text Search to search content.
Chapter 7, "Managing System Migration and Archiving," provides instructions for the tasks needed to migrate both the content and structure of one Content Server to another.
Appendix A, "User Interface," contains reference information on the graphical user interface screens used for administration functions and tasks.
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 Fusion Middleware Content Server 11g Release 1 (11.1.1) documentation set:
Oracle Fusion Middleware Content Server Release Notes
Oracle Fusion Middleware Developer's Guide for Content Server
Oracle Fusion Middleware Application Administrator's Guide for Content Server
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.|
|Slash (/)||A slash is used to separate the directory levels in a path to a UNIX server, directory, or file. Slashes are also used to separate parts of an Internet address. A slash will always be included at the end of a UNIX directory name and might or might not be included at the end of an Internet address.|
|Backward slash (\)||A backward slash is used to separate the levels in a path to a Windows server, directory, or file. A backward slash will always be included at the end of a Windows server, directory, or file path.|