| Oracle® Content Services Administrator's Guide 10g Release 1 (10.1.2) Part Number B25275-04 |
|
|
View PDF |
| Oracle® Content Services Administrator's Guide 10g Release 1 (10.1.2) Part Number B25275-04 |
|
|
View PDF |
This section describes changes to administrative features in Oracle Content Services 10g Release 1 (10.1.2). If you are upgrading to Oracle Content Services 10g from a previous release of Oracle Files, read the following information carefully, because there are significant differences in administration features, tools, and procedures.
New administrative features in Oracle Content Services include:
New Method to Change the Oracle Content Services Schema Password
Oracle Collaboration Suite Control Provides Access to Oracle Content Services Logs and Ports
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 have changed. Read the following list carefully to avoid confusion:
The organizational entity formerly known as a Subscriber is now called a Site. Sites are based on identity management realms.
The role formerly known as Subscriber Administrator was 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.
Tasks performed by the Site Administrator in Oracle Files (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.
There are two new terms 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 Oracle Enterprise Manager 10g Application Server Control for Collaboration Suite (Oracle Collaboration Suite Control). This tool was formerly known as Oracle Enterprise Manager 10g Application Server Control (Application Server Control).
The tools formerly known as Bulk Administration Tools are now called Oracle Content Services command-line tools. See "Oracle Content Services Command-line Tools" in Chapter 9 of Oracle Collaboration Suite Migration and Coexistence Guide for information about how to use these tools.
Integration with Oracle Records Management
Oracle Collaboration Suite 10g 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 use the Oracle Collaboration Suite Control to enable Oracle Records Management.
For information about how to use Oracle Records Management, see Oracle Records Management Administrator's Guide.
Multiple Site Support
You can now configure multiple Sites within one Oracle Content Services domain. In previous releases of Oracle Collaboration Suite, this functionality was not supported by OracleAS Single Sign-On.
Site Management from the Oracle Collaboration Suite Control
In Oracle Files, there was a separate administrative interface (and a separate administrative role) to manage Sites. In Oracle Content Services, 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 Oracle Files, there was a separate administrative interface for registering custom workflows. In Oracle Content Services, you can register custom workflows from the Oracle Collaboration Suite Control.
BFILE Archiving and Aging
In Oracle Files, two agents moved content from the Archive to BFILE storage. This feature was enabled by default. In Oracle Content Services, a new agent called the Cleanup Agent performs this task. This feature 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 storage if it was not accessed for a specified period (BFILE aging). The Content Agent is not activated by default.
Partner Integration for Retention Hardware Support
Oracle Content Services integrates with Network Appliance SnapLock and EMC Centera to provide hardware storage for records retention and compliance. Use the Oracle Collaboration Suite Control to manage retention hardware integration.
|
Note: The features described in this section were added to Oracle Collaboration Suite in the Oracle Collaboration Suite Cumulative Patchsets 10.1.2.1 and 10.1.2.2. Support for Network Appliance SnapLock was added in the Oracle Collaboration Suite Cumulative Patchset 10.1.2.1, and support for EMC Centera was added in the Oracle Collaboration Suite Cumulative Patchset 10.1.2.2.If you are using a previous version or patchset of Oracle Collaboration Suite, the features described are not available. |
The following is a summary of the changes to Oracle Content Services protocol support for this release:
The NTFS and SMB protocol servers are no longer included as native Oracle Content Services protocol servers. Instead, the Oracle Drive client provides support similar to Server Message Block (SMB) for users, while using WebDAV as the actual file protocol.
The NFS protocol is no longer supported. UNIX users are encouraged to use FTP as an alternative.
The AFP protocol is no longer supported, but WebDAV is now supported for the Macintosh. Macintosh users are encouraged to use WebDAV 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.
Changes to File Synchronization Support
The Oracle FileSync client was replaced by the Oracle Drive client. Oracle Drive provides file synchronization features similar to what was provided in Oracle FileSync.
Changes to Print Services Support
Because the Oracle Files 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.
Antivirus Integration
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. After the antivirus software is 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
Oracle Content Services ships with a new index, called IFS_LYKE, that makes item name searches faster.
OPMN Integration and Elimination of Domain Controller
Because Oracle Content Services is now fully integrated with OPMN, you can use the opmnctl utility 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
The following are 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.
The 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 administrative tasks.
Enhanced Logging
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.
New Method 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 was increased. Support for common formats, such as .jar, is now provided.
Simplified Installation and Configuration
The process of installing and configuring Oracle Content Services was 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 ifsca).
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, after Oracle Content Services was unconfigured
Simplified Oracle RAC Configuration
When you add or remove Oracle RAC nodes for Oracle Collaboration Suite, the Oracle RAC databases are automatically registered in Oracle Internet Directory. Oracle Content Services uses the information stored in Oracle Internet Directory to connect. Because of this, you no longer need to specify database connection information on Applications tiers. You do need to restart the Oracle Content Services domain, however, after you add or remove an Oracle 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. This OC4J instance is, by default, not enabled after Oracle Content Services is installed and configured.
Oracle Collaboration Suite Control Provides Access to Oracle Content Services Logs and Ports
You can now view Oracle Content Services logs directly from the Oracle Collaboration Suite Control. You can also use the Oracle Collaboration Suite Control to view Oracle Content Services ports.
