This preface introduces the new and changed features of Oracle Universal Content Management (Oracle UCM) Oracle 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 Oracle Content Server version 10g documents:
Managing Enterprise Search
Managing Security and User Access
Managing System Migration
Managing System Settings and Processes
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 Oracle Content Server configuration.
An Oracle Content Server instance is deployed as part of the Oracle Universal Content Management (Oracle UCM) system on an Oracle WebLogic Server instance, which causes several changes in Oracle Content Server configuration.
Using Oracle Enterprise Manager Fusion Middleware Control: Some Oracle Content Server functions can be managed with the Fusion Middleware Control user interface, including starting and stopping the server, modifying certain server and e-mail configuration parameters, viewing log information, and viewing performance information.
Connecting to the System Database: The Oracle Content Server system 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 through the JpsUserProvider, as opposed to Oracle Content Server's SystemProperties utility. As a result, JDBC user name and password information is no longer stored in the Oracle Content Server config.cfg file. (If you do set database connection information (for example, JdbcUserName) using the SystemProperties utility, the information is encrypted and stored in a secret location to prevent malicious attacks.)
Running Administration Utilities as Standalone Applications: In order to run certain Oracle Content Server 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 Oracle Content Server config.cfg file. The administrator must run the SystemProperties utility to enter database connection information (database type, database user name, database user password, and so forth) in the config.cfg file. Unless this configuration is performed, the Oracle 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 the Oracle Content Server instance) can run Admin Applets in standalone mode
Database Connection Pooling and Management: The Oracle Content Server system 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 between an Oracle Content Server instance and an Oracle WebLogic Server instance.
Database Providers: Oracle Content Server administrators can still create database providers in the Oracle Content Server system in one of two ways. Using one method, the administrator can create an Oracle WebLogic Server data source to the database, then configure an Oracle Content Server database provider to use that data source. The other method is for the administrator to create an Oracle 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: Each Oracle Content Server instance must have one Oracle Content Server Admin Server instance. The Admin Server can only manage the Oracle 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 support configuration changes, status information, and logs. Stopping and starting an Oracle Content Server instance 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 proxy Oracle Content Server instances. Only one Oracle Content Server can be deployed on each Oracle WebLogic Server domain. A single Oracle WebLogic Server domain can run one Oracle Content Server instance, one Inbound Refinery instance, and one Universal Records Management instance, and other Fusion Middleware applications. If you want to run more Oracle Content Server instances, a separate Oracle WebLogic Server domain is required for each Content Server instance (plus an Inbound Refinery instance and Universal Records Management instance).
Content Server Port: After initial installation of Oracle Content Server software, the Oracle Content Server instance does not listen on any port. After the
IntradocServerPort parameter is set on the post-configuration page, the Oracle Content Server instance starts listening on the specified port. If necessary, the port number can be reconfigured using the Fusion Middleware Control.
HTTP and HTTPS: By default, an Oracle Content Server instance is accessible with both HTTP and HTTPS. You can configure access methods with the Oracle WebLogic Server Administration Console.
Security Configuration: Security configuration for the Oracle Content Server system is managed differently. User creation and authentication are managed with the Oracle WebLogic Server Administration Console using Oracle Platform Services Security (OPSS) and Oracle Access Manager (OAM). Single Sign-On (SSO) is supported.
User Administration: The Oracle Content Server system uses the Oracle WebLogic Server Administration Console to manage users for an Oracle Content Server instance, which involves several changes.
An Oracle Content Server instance 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 the Oracle Content Server instance. The JpsUserProvider is installed by default to communicate with the Oracle WebLogic Server user store for authentication and authorization purposes.
The Oracle WebLogic Server Administration Console has limited capabilities to manage user metadata. User attribute values set in the Oracle WebLogic Server user store can be mapped to Oracle Content Server user metadata by editing the JpsUserProvider.
All user authentications are done by default against the Oracle WebLogic Server user store, not against the Oracle Content Server user store. Although the Oracle Content Server User Admin applet allows you to create users and assign passwords, the users are not able to login to the Oracle Content Server instance unless the users have also been created and assigned passwords with the Oracle WebLogic Server Administration Console.
Roles and security groups still must be created in the Oracle Content Server instance with the User Admin applet, but roles-to-security group assignments must be performed with the Oracle WebLogic Server Administration Console. For Oracle WebLogic Server groups to have meaning in an Oracle Content Server system, roles with the exact same names must be created in the Oracle Content Server instance and assigned to security groups. If this is not done, the groups assigned to the user have no effect on user privileges in the Oracle Content Server instance.
In the Oracle WebLogic Server user store, users can be assigned to groups. When a user logs in to the Oracle Content Server instance, the user is authenticated against the Oracle WebLogic Server user store using the JpsUserProvider, and the user's groups are mapped to Oracle Content Server roles and accounts. All Oracle WebLogic Server groups assigned to the user are mapped as roles in the Oracle Content Server instance, except for groups that start with "@," which are mapped to Oracle Content Server accounts.
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. FileStoreProvider exposes the file store functionality in the Oracle Content Server interface, and allows additional configuration options. The FileStoreProvider component is installed and enabled by default with Oracle Content Server installation. For details, see Section 4.3, "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 Oracle 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 Oracle Content Server installation. For details, see Section 5.9.3, "ExtendedUserAttributes."
The following information is new for managing search tools:
Oracle SES Configuration: Oracle UCM can be configured to use Oracle Secure Enterprise Search (Oracle SES) as an external search engine for an Oracle Content Server instance. For details, see Section 7.2, "Oracle Secure Enterprise Search."
SESCrawlerExport: The SESCrawlerExport component adds functionality as an RSS feed generator to the Oracle Content Server instance and allows it to be searched by Oracle Secure Enterprise Search (Oracle SES). The component generates a snapshot of content currently on the Oracle Content Server instance and provides it to the Oracle SES Crawler.
The following is new for managing access control lists:
Access Control Lists: The Oracle Content Server instance can be configured to support access control lists (ACLs). An access control list is a list of users, groups, or enterprise roles with permission to access or interact with a content item. For details, see Section 5.6, "Access Control List Security."
11g Release 1 (11.1.1) includes the following changes:
Sysadmin user: The sysadmin user, which has functioned as the system administrator for the Oracle Content Server instance, is no longer created by default. You can explicitly create this user for your Oracle Content Server instance.
Directory Structure: The directory structure of an installed Oracle UCM server has changed. Unlike in Release 10gR3, runtime files, configuration files, server configuration files, file store, and files that must be shared between Oracle Content Server, Oracle Inbound Refinery, and Oracle Universal Records Management instances 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 Oracle Content Server, Oracle Inbound Refinery, and Oracle Universal Records Management software.
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 an Oracle Content Server instance deployed on an Oracle UCM domain on an Oracle WebLogic Server instance. This Idoc Script variable is configured for one type of Oracle Content Server instance: Content Server (
cs), or Inbound Refinery (
ibr), or Universal Records Management (
urm). This directory can be located elsewhere, but the default location is DomainHome/ucm/short-product-id/.
OracleTextSearch: The OracleTextSearch component has been incorporated into the Oracle Content Server media, 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 OracleTextSearch page. See "OracleTextSearch".