2 What's New

2.1 Changes to Services

Updates have been made to the following services:

• The CHECKIN_NEW service has been revised to include information about the DirectReleaseNewCheckinDoc variable, which directs content items being checked in to bypass Inbound Refinery, workflow, and indexing.

• The CollaborationManager component and its services have been removed because the product is not supported in 11g Release 1 (11.1.1). Core collaboration services have been moved to the Core Services chapter.

• Extended User Attributes component services have been added.

• Folios component services have been added.

• VirtualContentRepository component services have been added.

• The GET_ENVIRONMENT service has been revised to include information about the StartTime variable.

• Pathnames have been revised to reflect the new file structure for a Oracle Content Server instance deployed on an Oracle WebLogic Server.

• The DELETE_DOC service has been revised to show that it removes all revisions of a content item, not just a single revision.

• The CHECKIN_SEL service has been revised to remove inaccurate information about metadata values not specified in the service call being inherited from the previous revision. Metadata values are not inherited from the previous revision. CHECKIN_UNIVERSAL and UPDATE_DOCINFO are the two services that inherit unspecified metadata values.

2.2 New Services Interface

When adding a service through the Component Wizard, you can now preview details about services. Information for a service can be viewed by selecting the new Preview button in the upper right corner of the Resource Selection Dialog. When the Preview Information for 'SERVICE_NAME' dialog is displayed, the online help for that service is available by clicking the Help button.

See Section 4.3.3, "Creating a Custom Service using Component Wizard", step 1, for information about accessing this new functionality.

2.3 Additional Changes

Additional changes include the following:

• The directory structure of an installed Oracle Universal Content Management (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. References to install_dir have been changed to one of the following:

  • IdcHomeDir: Refers 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: Refers 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: An abbreviated name for 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: Refers to the root directory for configuration and data files for a Oracle Content Server instance deployed in 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/.