This guide provides concept and task information for administering applications for Content Server.


This guide is intended for people who are responsible for administering applications for Content Server. Administrators set up, maintain, and manage the content server users, content, and system configurations. Common tasks for an administrator include configuring the system to manage and index files, archiving and replicating information, working with content server security, adjusting system properties, reviewing log files, etc.

Documentation Accessibility

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

Accessibility of Code Examples in Documentation

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.

Accessibility of Links to External Web Sites in Documentation

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.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired.

Related Documents

Documentation for administrators and sub-administrators of the Content Server software includes the following:


The optional add-ons to Content Server generally have their own administration documentation, which is included as PDF files on the add-on distribution media, typically in a /documentation directory.


The following text conventions are used in this document:

Convention Meaning
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 Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.
Forward slashes (/) Forward slashes are used to separate the directory levels in a path to a UNIX server, directory, or file. Forward slashes are also used to separate parts of an Internet address. A forward 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 slashes (\) Backward slashes are 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.
DomainHome The variable used to refer to the user-specified directory where an Oracle UCM server is deployed to run on an Oracle WebLogic Server. DomainHome is a term used in Oracle WebLogic Server deployment, and it is provided here only because IntradocDir refers to it.
IntradocDir The variable used to refer to the root directory for actual configuration and data files specific to a Content Server instance deployed on the Oracle UCM domain on Oracle WebLogic Server. The files include startup files (intradoc.cfg and executables). This variable is configured for one type of instance: Content Server, Inbound Refinery or Universal Records Management.

The specified directory must be an absolute path to the instance directory, and it must be unique to a specific server or node. For install that will be in a cluster, the instance directory must be in a network share accessible to all nodes in the cluster.

The default location for the instance directory is specified as DomainHome/ucm/short-product-id where short-product-id can be:

  • cs (Content Server)

  • ibr (Inbound Refinery)

  • urm (Universal Records management)