1 Introduction

This section provides an introduction to the information in this guide. It covers the following topics:

1.1 About This Guide

This guide provides information about administration concepts and tasks for the following Content Server applications:

  • HTML Preview: provides content contributors with instant feedback on how their content will display on the published web site. This enables the contributors to modify the original content (if they do not like the published results) before the content is actually checked in.

  • Repository Manager: specifies how content is displayed or handled, such as creating customized content types, working with subscriptions, and managing revisions.

  • Metadata: specifies how metadata is used in working with schemas, rules, and content profiles.

  • Workflows: specifies how content is routed for review, approval, and release to the system.

  • PDF Watermark: enables watermarks to be applied to PDF files generated by the component PDFConverter (static) and returned to the content server.

  • Folders and WebDAV: provides a hierarchical folder interface to content in Content Server in the form of "virtual folders" (also called "hierarchical folders"). Virtual folders enable you to create a multi-level folder structure.

  • Content Folios: provides a quick and effective way to assemble, track, and access logical groupings of multiple content items from within the secure environment of Content Server.

1.2 What's New

This section provides a brief overview of changes to the functionality discussed in this book for this release of the Content Server.

  • This guide combines information that was previously contained in the following Content Server version 10g documents:

    • Managing Repository Content

    • Content Server Workflow Implementation Guide

    • Content Categorizer System Administration Guide

    • Content Tracker Administration Guide

    • PDF Watermark

    • Folders/WebDAV Administration Guide

    • Folios Administration Guide

  • Administration Applets: All Administration Applets in the user interface have been converted to Java Swing and are now accessible.

  • Content Tracker: New preferences have been set to provide maximum efficiency in high volume production environments. In addition, event log file locking within and between Java Virtual Machines is now managed using object synchronization and parallel log files.

  • Content Categorizer: Several enhancements have been made. Export conversion parameters are now available for user customization Dynamic metadata field length checks are now used so a server restart is not necessary. The Batch Categorizer executable is no longer on the Start menu but has been relocated to the contentcategorizer subdirectory in the Content Server instance.

  • PDF Watermark: The installation now includes five variants of the Albany font set. In addition the iText Common Library is now distributed with Content Server in the iText Component.

  • See the Oracle Fusion Middleware System Administrator's Guide for Content Server for a detailed description of changes to Content Server security for this release and for information about other changes to the product.

1.3 Understanding the Content Server System

This section covers these topics:

1.3.1 Purpose of Content Server

Use Content Server for sharing, managing, and distributing business information using a web site as a low-cost access point.

Designed for the web, this software is considered the unrivaled solution for medium to large companies for building secure business libraries with check in/check out, revision control, and automated publishing in web-ready formats. Current information is available to authorized users anytime, anywhere. You can link almost any type of file such as letters, reports, engineering drawings, spreadsheets, manuals, sales literature, and more under one powerful system of knowledge distribution.

1.3.2 Users Types

Content Server is designed for two types of users and two types of administrators:

  • Consumers: Users who just need to find, view, and print files.

  • Contributors: Users who need to create and revise files.

  • Administrators: Administrators who oversee an entire instance.

  • Subadministrators: Administrators who oversee a subset of an instance.

In a typical system, the majority of the users are consumers. These users do not need a user name and password to access the content server system unless security is placed on the files. To safeguard the integrity of the files, the contributors need a user name and password to check files in and out of the system.

Typically, the majority of administrators are subadministrators. They administer portions of the software that correspond to the rights that the system administrator assigns to them.

1.4 Administration Applications

The system provides administration applications to configure and maintain the Content Server user access.


Oracle recommends using Sun's JDK version 1.6 Java plug-in when opening any Java applets (such as a Content Server administration applet or the multiple-file upload applet) from a browser.

The Administration page provides access to administration applets and configuration tools page. To access this page, log in as an administrator or subadministrator, and click the Administration tray in the portal navigation bar. Then, click Admin Applets.

Figure 1-1 Admin Applets Menu

Surrounding text describes Figure 1-1 .

Many applications can be started as a stand-alone application at the server, as applets through a browser, or from the Apps menu in each of the tools.

1.4.1 Running Administration Applications as Applets

You can run several of the Content Server administration applications as applets from any browser with access to the content server. Applets are convenient for remote administration.

The Batch Loader, Component Wizard, System Properties, and Content Server Analyzer utilities cannot be run as applets; for security reasons, they must be run in stand-alone mode from the computer where the content server is installed. See "Running Administration Applications in Stand-alone Mode".

Some functions that are available in the stand-alone version of an application are not available from the applet version. See the documentation for each application for more information.

To run an administration application as a Java applet within a Java-enabled browser:

  1. Open a browser window.

  2. Log in to the content server as an administrator.

  3. Click the Administration tray link in the portal navigation bar.

  4. Click the Admin Applets link.

1.4.2 Running Administration Applications in Stand-alone Mode

You can run all Content Server administration applications in stand-alone mode from the computer where the content server is installed. The method required to start these programs differs slightly between Windows and UNIX installations.

Running the stand-alone version of an application offers greater security than browser applets, and enables you to send passwords without having them captured or copied from the web or a network. On Windows Systems

To run a stand-alone administration application on a Windows operating system:

  1. Select the application from the Windows Start menu:

    • To run one of the configuration applications, select Start, Programs, Content Server, instance, application.

    • To run one of the administration Utilities, select Start, Programs, Content Server, instance, Utilities, utility.

    For all applications except for Component Wizard and System Properties, a login screen is displayed. For Component Wizard and System Properties, the main screen of the application is displayed.


    It may take several seconds for the login screen or the application screen to appear, and the screen may be hidden by other windows.
  2. Enter the administrator login name and password.

  3. Click OK.

    The main screen of the application is displayed. On UNIX Systems

To run a stand-alone administration application on a UNIX operating system:

  1. Navigate to the DomainHome/ucm/cs/bin/ directory.

  2. Executable applications are listed. Enter ./application_name, where application_name is the name of one of the executable files. If an application is not listed, it can be entered as a parameter to the IntradocApp application, as in this example:

    % ./IntradocApp Workflow
  3. Press Enter.

    For all applications except for Component Wizard and System Properties, a login screen is displayed. For Component Wizard and System Properties, the main screen of the application is displayed.

  4. Enter the administrator login name and password.

  5. Click OK.

    The main screen of the application is displayed.