This preface introduces the new and changed features of Oracle Universal Content Management (Oracle UCM) Content Server system administration that are described in this guide.
11g Release 1 (11.1.1) includes the following new features in this guide:
This guide combines information that was previously contained in the following Content Server version 10g documents:
Managing Enterprise Search
Managing Security and User Access
Managing System Migration
Managing System Settings and Processes
System Overview
Working with Components
Need to Know Component Installation and Administration Guide
It includes a new chapter on using Oracle Enterprise Manager Fusion Middleware Control to manage Content Server configuration.
Content Server is deployed on an Oracle WebLogic Server, which causes several changes in Oracle Universal Content Management (Oracle UCM).
Using the Oracle Enterprise Manager Fusion Middleware Control: Some Oracle UCM Content Server functions can be managed with the Fusion Middleware Control user interface, including starting and stopping the server, modifying certain server and email configuration parameters, viewing log information, and viewing performance information.
Connecting to the System Database: Oracle UCM uses an Oracle WebLogic Server data source to communicate with the relational database where metadata and other information is stored. Database connection and communication information is managed with the Oracle WebLogic Server Administration Console, as opposed to Content Server's System Properties utility. As a result, JDBC username and password information are no longer stored in the Content Server's config.cfg file.
Running Administration Utilities as Standalone Applications: In order to run Content Server standalone applications or administration utilities in standalone mode (that is, from the command line or from the Windows Start menu), database connection information must be entered into the Content Server's config.cfg file. The administrator must run the System Properties utility to enter database connection information (database type, database user name, database user password, and so forth) in the config file. Unless this configuration is performed, the Content Server standalone applications and utilities cannot function in standalone mode because they cannot connect to the database. Only the administrator or an assigned local user (created on Content Server) can run Admin Applets in standalone mode
Database Connection Pooling and Management: Oracle UCM uses the Oracle WebLogic Server database connection pooling mechanism to handle database communication. The SystemDatabase Provider is still present and uses the Oracle WebLogic Server data source, which in turn handles the actual database authentication and communication.
Default User Provider: The JpsUserProvider is the default user provider for communication with Oracle WebLogic Server.
Database Providers: Oracle UCM administrators can still create database providers in the Content Server in one of two ways. Using one method, the administrator can create an Oracle WebLogic Server data source to the database, then configure a Content Server database provider to use that data source. The other method is for the administrator to create a Content Server database provider to connect directly to the database with JDBC without using the Oracle WebLogic Server data source. This second method is provided primarily for sites who may have such connections in Release 10gR3 deployments and are upgrading.
Admin Server: With Oracle UCM, each Content Server instance must have one Admin Server instance. An Admin Server can only manage the Content Server instance that is installed on the same Oracle WebLogic Server domain. The Admin Server no longer supports server starts, stops, or restarts, but it does continue to support configuration changes, status information, and logs. Stopping and starting Content Server must be managed with the Enterprise Manager Fusion Middleware Control Console, or the Oracle WebLogic Server Administration Console.
Proxy Servers and Master Servers: Oracle UCM does not support proxied Content Server instances. Only one Content Server can be deployed on each Oracle WebLogic Server domain. A single Oracle WebLogic Server domain can run one Content Server instance, one Inbound Refinery instance, and one Universal Records Management instance, and other Fusion Middleware applications. If you want to run more instances, a separate Oracle WebLogic Server domain is required for another Content Server instance, Inbound Refinery instance, or Universal Records Management instance.
Content Server Port: After initial installation of the Content Server, the Content Server does not listen on any port. After the IntradocServerPort parameter is set on the post-configuration page, Content Server starts listening on the specified port.
HTTP and HTTPS: By default, Oracle UCM is accessible with both HTTP and HTTPS. You can configure access methods with the Oracle WebLogic Server Administration Console.
User Administration: Oracle UCM uses Oracle WebLogic Server to manage users for Content Server, which involves several changes.
Oracle UCM uses the Oracle WebLogic Server user store to manage user names and passwords. User management tasks must be performed with Oracle WebLogic Server user management tools as opposed to the User Admin applet in Content Server. The JpsUserProvider is installed by default to communicate with the Oracle WebLogic Server user store for authentication and authorization purposes.
The Oracle WebLogic Server has limited capabilities to manage user metadata. User attribute values set in the Oracle WebLogic Server user store can be mapped to Content Server user metadata by editing the JpsUserProvider.
All user authentications are done against the Oracle WebLogic Server user store. Oracle WebLogic Server does not authenticate users against the Content Server user store. Although the Content Server User Admin applet allows you to create users and assign passwords, the users are not able to login to the Content Server unless the users have also been created and assigned passwords on Oracle WebLogic Server.
In the Oracle WebLogic Server user store, users can be assigned to groups. When a user logs in to Content Server, the user is authenticated against the Oracle WebLogic Server user store via the JPS provider and the user's groups are mapped to Content Server roles and accounts. All Oracle WebLogic Server groups assigned to the user are mapped over as roles in Content Server, except for groups that start with “@,” which are mapped to Content Server accounts.
Roles and security groups still must be created in the Content Server with the User Admin applet, but roles-to-security group assignments must be performed with Oracle WebLogic Server. For Oracle WebLogic Server groups to have meaning in Content Server, roles with the exact same names must be created in Content Server and assigned to security groups. If this is not done, the groups assigned to the user have no effect on user privileges in Content Server.
The following information is new for managing system settings and processes:
File Store System: A file store system for data management replaces the traditional file system for storing and organizing content. File Store Provider exposes the file store functionality in the Content Server interface, and allows additional configuration options. The File Store Provider component is installed and enabled by default with Content Server installation. See "Configuring a File Store System".
The following information is new for managing security and user access:
Extended User Attributes: The Extended User Attributes component enables administrators to add extended attributes to Content Server users. The extended attributes are merged into pre-existing user attributes and enable additional flexibility in managing users. The Extended User Attributes component is installed and enabled by default with Content Server. See "Extended User Attributes".
The following information is new for managing search tools:
Oracle SES Configuration: Oracle Universal Content Management can be configured to use Oracle Secure Enterprise Search (Oracle SES) as an external search engine for Content Server. For configuration information, see "Oracle Secure Enterprise Search".
11g Release 1 (11.1.1) includes the following changes:
Directory Structure: The directory structure of an installed Oracle UCM instance has changed. Unlike in Release 10gR3, runtime files, configuration files, and files that must be shared between clustered Content Server instances, server configuration files, and file store may be in various locations. The following locations and terms are important to understanding an Oracle UCM 11g Release 1 (11.1.1) installation:
IdcHomeDir: The variable used to refer to the directory in ECM_ORACLE_HOME where the Oracle UCM (ucm) server media is located. The server media can run Content Server, Inbound Refinery, or Universal Records Management.
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 application server. The DomainHome/ucm/short-product-id/bin directory contains the intradoc.cfg file and executables.
short-product-id: The variable used to refer to the type of Oracle UCM server deployed on an Oracle WebLogic Server. Possible values include:
cs (Content Server)
ibr (Inbound Refinery)
urm (Universal Records Management)
IntradocDir: The variable used to refer to the root directory for configuration and data files specific to a Content Server instance deployed on an Oracle UCM domain on an Oracle WebLogic Server. This Idoc Script variable is configured for one type of Content Server instance: Content Server, or Inbound Refinery, or Universal Records Management. This directory can be located elsewhere, but the default location is DomainHome/ucm/short-product-id/.
OracleTextSearch: The Oracle Text Search component has been incorporated into Content Server, so the OracleTextSearch engine is one of several search and indexing options. The OracleTextSearch interface has been integrated with the Repository Manager Indexer functions, so there is no separate Oracle Text Search page. See "OracleTextSearch".