This preface describes new and changed features in Oracle WebCenter Content Server (Content Server) system administration which are described in this guide.
This release includes the following new features:
The Folders Migration utility migrates folder content and structure from Contribution Folders (supported by the Folders_g component) to Folders (supported by the FrameworkFolders component). For details, see Section 8.12.
Support for Sun Storage Archive Manager (SAM-QFS), a hierarchical file storage system that runs on the Sun Solaris operating system. For details, see Section 4.3.6.
Oracle Fusion Middleware supports IBM WebSphere as an application server, which will affect using Oracle Enterprise Manager Fusion Middleware Control to manage Content Server. For more information, see Oracle Fusion Middleware Third-Party Application Server Guide.
Support for GridLink data sources. See Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.
Additional material in this guide includes:
Support for the Oracle Fusion Middleware BPEL component for Content Server. See Appendix C.
Support for the Kofax Capture Export Connector to Oracle WebCenter Content. See Appendix D.
11g Release 1 (11.1.1) includes the following new features:
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
Working with Components
Need to Know Component Installation and Administration Guide
It includes a chapter on using Oracle Enterprise Manager Fusion Middleware Control to manage Content Server configuration.
The Content Server instance is deployed as part of the Oracle WebCenter Content (WebCenter Content) domain on an Oracle WebLogic Server system, which causes several changes in Content Server configuration.
Using Oracle Enterprise Manager Fusion Middleware Control: Some 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 Content Server 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 Content Server's System Properties utility. As a result, JDBC user name and password information is no longer stored in the Content Server config.cfg file. (If you do set database connection information (for example, JdbcUserName) using the System Properties 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 Content Server applications or administration utilities in standalone mode (that is, from the command line or from the Windows Start menu), 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 Content Server config.cfg file. Unless this configuration is performed, 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 Content Server instance) can run Admin Applets in standalone mode
Database Connection Pooling and Management: The Content Server uses the Oracle WebLogic Server database connection pooling mechanism to handle database communication. The SystemDatabaseProvider 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 the Content Server instance and an Oracle WebLogic Server domain.
Database Providers: Content Server administrators can still create database providers in the Content Server instance 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 an Oracle WebCenter 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 Content Server instance must have one Content Server Admin Server instance. The 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 support configuration changes, status information, and logs. Stopping and starting the 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 WebCenter Content does not support proxy 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 Oracle WebCenter Content Server instance, one Oracle WebCenter Content: Inbound Refinery instance, and one Oracle WebCenter Content: Records instance, plus other Oracle WebCenter Content applications. If you want to run more Content Server instances, a separate Oracle WebLogic Server domain is required for each Content Server instance (plus an Oracle WebCenter Content: Inbound Refinery instance and Oracle WebCenter Content: Records instance).
Content Server Port: After initial installation of Oracle WebCenter Content Server software, the Content Server instance does not listen on any port. After the
IntradocServerPort parameter is set on the post-configuration page, the Content Server instance starts listening on the specified port. If necessary, the port number can be reconfigured using Fusion Middleware Control.
HTTP and HTTPS: By default, the 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 Oracle WebCenter Content Server 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: By default, WebCenter Content uses the Oracle WebLogic Server user store to manage user names and passwords for Oracle WebCenter Content Server. Therefore user management must be performed using the Oracle WebLogic Server user management tools rather than the User Admin applet in the Content Server instance. All user authentications are done against the Oracle WebLogic Server user store. You can use the Admin applet to create local users and assign passwords, but the users must also be created and assigned passwords in the Oracle WebLogic Server user store.
For enterprise-level systems, Oracle Platform Security Services (OPSS) can be used instead of the Oracle WebLogic Server user store to authenticate and authorize users.
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. The File Store Provider component exposes the file store functionality in the Content Server interface and allows additional configuration options. The File Store Provider component is installed, enabled, and upgraded by default with Content Server installation. For details, see Section 4.3.
The following information is new for managing security and user access:
Access Control Lists: The 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.
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 installation. For details, see Section 5.9.3.
The following information is new for managing search tools:
Oracle SES Configuration: WebCenter Content can be configured to use Oracle Secure Enterprise Search (Oracle SES) as an external search engine for the Content Server instance. For details, see Section 7.2.
SESCrawlerExport: The SES Crawler Export component adds functionality as an RSS feed generator to the 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 Content Server instance and provides it to the Oracle SES Crawler. For details, see Section 7.2.2.
11g Release 1 (11.1.1) includes the following changes:
Sysadmin user: The sysadmin user, which previously functioned as the system administrator for the Content Server instance, is no longer created by default. You can explicitly create a user with administration privileges for your Content Server instance.
Directory Structure: The directory structure of an installed Oracle WebCenter Content system has changed. Unlike in Release 10gR3, runtime files, configuration files, server configuration files, file store, and files that must be shared between Oracle WebCenter Content Server, Oracle WebCenter Content: Inbound Refinery, and Oracle WebCenter Content: Records instances can be in various locations.
WebCenter Content documentation uses the following terms when referring to variables in the directories associated with the WebCenter Content installation, configuration, and deployment:
IdcHomeDir: This variable refers to the
ucm/idc directory in the Oracle WebCenter Content home where the WebCenter Content server media is located. The server media can run Oracle WebCenter Content Server, Oracle WebCenter Content: Inbound Refinery, or Oracle WebCenter Content: Records software. This is essentially a read-only directory. The default location is
/ucm/idc. The variable portion of the default location can be changed, but the path cannot be changed from
DomainHome: This variable refers to the user-specified directory where a WebCenter Content application is deployed to run on an Oracle WebLogic Server application server. The
/bin directory contains the intradoc.cfg file and executables. The default location for
base_domain, but you can change the path and domain name (
base_domain) during the deployment of a WebCenter Content application to an application server.
short-product-id: This variable refers to the type of WebCenter Content server deployed to an application server. This name is used as the context root (default
HttpRelativeWebRoot configuration value). Possible values include:
cs (Oracle WebCenter Content Server)
ibr (Oracle WebCenter Content: Inbound Refinery)
urm (Oracle WebCenter Content: Records)
IntradocDir: This variable refers to the root directory for configuration and data files specific to a Content Server instance that is part of a WebCenter Content application deployed to an application server. This Idoc Script variable is configured for one type of Content Server instance: Content Server (
cs), Inbound Refinery (
ibr), or Records (
urm). This directory can be located elsewhere, but the default location is
short-product-id. The specified directory must be an absolute path to the instance directory and must be unique to a particular server or node. The directory files include startup files (intradoc.cfg and executables).
OracleTextSearch: The OracleTextSearch component has been incorporated into the WebCenter Content 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. For details, see Section 7.1.