|Oracle® Content Services Administrator's Guide
10g Release 1 (10.1.1)
Part Number B14493-01
This preface describes changes to administrative features in Oracle Content Services 10g Release 1 (10.1.1). If you are upgrading to Oracle Content Services 10g from a previous release, read the following information carefully, since there are significant differences in Oracle Content Services administration features, tools, and procedures.
New administrative features in Oracle Content Services include:
New Product Name
Oracle Content Services is the new name for the product formerly known as Oracle Files. For information about new product features, see Oracle Collaboration Suite Release Notes for your platform.
Many key terms from past releases have changed. Read the following list carefully to avoid confusion:
The role formerly known as Subscriber Administrator has been split into a variety of different administrative roles, such as User Administrator, Quota Administrator, and Content Administrator. Collectively, users who hold one or more of these roles are known as application administrators since they manage the Oracle Content Services application.
Tasks performed by the Site Administrator in previous releases (creating, modifying, and deleting Sites, as well as registering custom workflows) are now performed by the system administrator using the Oracle Collaboration Suite Control.
Workspaces are now known as Libraries.
Two new terms have been introduced to describe the Oracle Collaboration Suite architecture: Applications tier, which replaces the previously used term middle tier, and Infrastructure tier, which includes both the Oracle Collaboration Suite Database and Oracle Identity Management.
The administrative tool to manage each Applications tier is now called the Oracle Enterprise Manager 10g Application Server Control for Collaboration Suite (Oracle Collaboration Suite Control). This tool was formerly known as the Oracle Enterprise Manager 10g Application Server Control (Application Server Control).
The tools formerly known as the Bulk Administration Tools are now known as the Oracle Content Services command-line tools.
Integration with Oracle Records Management
Oracle Records Management is a records management application that ships with Oracle Content Services. When you install Oracle Content Services, Oracle Records Management is installed automatically, but the application is disabled by default.
You can now configure multiple Sites within one Oracle Content Services domain. In previous releases, this functionality was not supported by OracleAS Single Sign-On.
Site Management from the Oracle Collaboration Suite Control
In previous releases of Oracle Content Services, there was a separate administrative interface (and a separate administrative role) to manage Sites. Now, the system administrator can manage Sites from the Oracle Collaboration Suite Control.
BPEL Workflow Support
Oracle Content Services now supports integration with BPEL custom workflows. Because of this, custom workflows built using Oracle Workflow Builder are no longer supported.
In previous releases of Oracle Content Services, there was a separate administrative interface for registering custom workflows. Now, you can register custom workflows from the Oracle Collaboration Suite Control.
BFILE Archiving and Aging
As in previous releases of Oracle Content Services, an agent can move content in the Archive to BFILE storage. Rather than having two agents control BFILE archiving, however, a new agent called the Cleanup Agent performs this task, and this behavior is not activated by default.
In addition to BFILE archiving, you can now configure an agent called the Content Agent to periodically move content to BFILE after it has not been accessed for a specified period (BFILE aging). This agent is not activated by default.
Partner Integration for Retention Hardware Support
Oracle Content Services now integrates with EMC Centera and Network Appliance SnapLock in order to provide hardware storage for records retention and compliance. Use the Oracle Collaboration Suite Control to manage retention hardware integration.
The following list summarizes the changes to Oracle Content Services protocol support for this release:
Due to performance and security issues, the NFS protocol is no longer supported. UNIX users are encouraged to use FTP as an alternative.
Secure FTP (FTPS) is now supported, in addition to FTP.
The FTP and FTPS servers are not configured by default after you install and configure Oracle Content Services; you must enable these protocols using the Oracle Collaboration Suite Control.
Since the Oracle Content Services printing services relied on SMB, which is not supported in this release, you cannot add, modify, or delete printers from the Oracle Collaboration Suite Control. Instead, Oracle Content Services relies on partners for output management.
Oracle Content Services integrates with a partner solution, the Symantec AntiVirus Scan Engine (SAVSE), to provide options to verify that content is virus-free and to clean files that are found to be infected. Once antivirus integration has been enabled and configured, files are scanned for viruses whenever they are opened for read access, using the latest available virus definitions.
New Index to Speed Up Name Searches
Because Oracle Content Services is now fully integrated with OPMN, you can use
opmnctl to manage the Oracle Content Services domain and node. As a result, the
ifsctl tool is no longer available, and there is no longer an Oracle Content Services domain controller.
Changes to Administrative Accounts
Be aware of the following changes to administrative accounts used with Oracle Content Services:
There is no longer a
site_admin account. Administrative tasks formerly performed using the
site_admin account are now performed using the
ias_admin account in the Oracle Collaboration Suite Control.
There is no longer a Subscriber Administrator. Tasks performed by the Subscriber Administrator are now performed by a variety of administrators, such as the Content Administrator and the Quota Administrator, in Oracle Content Services Administration Mode.
orcladmin account for each realm has all of the Oracle Content Services access roles by default. Use the
orcladmin account to sign in to Oracle Content Services for the first time and delegate access roles to additional users.
Although the Oracle Content Services
system account is still used internally, it is no longer needed to perform any administrative tasks.
Using the Oracle Collaboration Suite Control, you can customize the level of information you would like logged by selecting and configuring loggers.
Multiple Applications Tiers on a Single Host
You can now have more than one Oracle Content Services Applications tier on a single host. Each Oracle Content Services Applications tier must be in its own Oracle home. The Applications tiers can be part of the same Oracle Content Services domain, or they can belong to different domains.
Easier Mechanism to Change the Oracle Content Services Schema Password
You can now change the Oracle Content Services schema password using the Oracle Collaboration Suite Control.
Metric Configuration Management
You can configure Oracle Content Services metrics, including SQL metrics, Java metrics, and URL Timing metrics, for particular Applications tiers using the Oracle Collaboration Suite Control.
Additional Default Formats
The number of default format shipped with Oracle Content Services has been greatly increased. Default support for common formats such as
.jar is now provided.
Simplified Installation and Configuration
The process of installing and configuring Oracle Content Services has been greatly simplified. The configuration process is now integrated with Oracle Universal Installer, and you no longer need to manually run the Oracle Content Services Configuration Assistant (formerly known as the Oracle Files Configuration Assistant, or
Option to Configure and Unconfigure Oracle Content Services from the Oracle Collaboration Suite Control
If you choose not to configure Oracle Content Services through Oracle Universal Installer during Oracle Collaboration Suite installation, you can configure Oracle Content Services at a later time using the Oracle Collaboration Suite Control. You can also use the Oracle Collaboration Suite Control to:
Unconfigure Oracle Content Services on a particular Applications tier
Reconfigure Oracle Content Services on a particular Applications tier, once it has been unconfigured
Simplified RAC Configuration
When you add or remove RAC nodes for Oracle Collaboration Suite, the RAC databases are automatically registered in Oracle Internet Directory. Oracle Content Services uses the information stored in Oracle Internet Directory in order to connect. You no longer need to specify database connect information on Applications tiers, although you do need to restart the Oracle Content Services domain after you add or remove a RAC node.
Changes to OC4J Instance Names for Oracle Content Services
The OC4J instance that supports the HTTP node for the Oracle Content Services application, called
OC4J_iFS_files in previous releases, is now called
OC4J_Content. This release also introduces a new OC4J instance to support the HTTP node for the Oracle Records Management application, called
OC4J_RM, but this OC4J instance is disable by default after Oracle Content Services is installed and configured.
Oracle Collaboration Suite Control Access to Oracle Content Services Ports and Logs
You can now view Oracle Content Services log files directly from the Oracle Collaboration Suite Control. You can also use the Oracle Collaboration Suite Control to view Oracle Content Services ports.