1 Installation Overview

Oracle Enterprise Content Management Suite, an Oracle Fusion Middleware component, is an integrated suite of products designed for managing content. This chapter provides an overview of the procedures for installing Oracle Enterprise Content Management Suite and configuring its products as applications deployed to Oracle WebLogic Server domains.

This chapter includes the following sections:

1.1 Oracle Enterprise Content Management Suite Applications

Oracle Enterprise Content Management Suite includes the following products:

  • Oracle Imaging and Process Management (Oracle I/PM)

    Oracle I/PM is an integrated framework of client software modules with a customizable user interface for managing documents from image capture to archiving. Client modules can be integrated within this framework to provide a single user interface, including third-party information systems, imaging, workflow process, and enterprise content management.

  • Oracle Information Rights Management (Oracle IRM)

    Oracle IRM secures and tracks sensitive digital information everywhere it is stored and used. The installation of Oracle IRM Desktop agent software is required on every end user device on which sealed information is created or used.

After you install these products on your system, you can configure one or more of them as applications deployed to a previously installed Oracle WebLogic Server.

1.2 Installation Roadmap

Table 1-1 describes the high-level tasks for installing and configuring Oracle Enterprise Content Management Suite. You need to perform the tasks in order except as noted. The table also provides information on where to get more details on each task.

Table 1-1 Oracle Enterprise Content Management Suite Installation Procedure

Task Description Mandatory/Optional? Documentation

Task 1 - Prepare your system environment for installation

Ensure that your system environment meets the general installation requirements for Oracle Fusion Middleware, for Oracle Enterprise Content Management Suite, and for Repository Creation Utility (RCU), which requires a supported database.

Mandatory

Section 3.1, "Preparing for Installation."

Task 2 - Create schemas for applications

Oracle Enterprise Content Management Suite applications require schemas that must be installed in a supported database, such as Oracle Database or Microsoft SQL Server. Prepare a database for Oracle Enterprise Content Management Suite schemas, then install RCU and use it to create schemas.

Note: You can perform this task before or after Task 3 - Install Oracle WebLogic Server in a Middleware home and Task 4 - Install Oracle Enterprise Content Management Suite.

Mandatory

Section 1.3.2, "Database"

Chapter 2, "Creating Schemas for Oracle Enterprise Content Management Suite"

Task 3 - Install Oracle WebLogic Server in a Middleware home

Oracle Enterprise Content Management Suite runs on Oracle WebLogic Server. You must install Oracle WebLogic Server before you install Oracle Enterprise Content Management Suite.

The installer creates the Oracle WebLogic Server home directory (WL_HOME) within the Middleware home directory (MW_HOME).

Note: You can perform this task before or after Task 2 - Create schemas for applications.

Mandatory

Section 3.1.2, "Installing Oracle WebLogic Server in a Middleware Home"

Task 4 - Install Oracle Enterprise Content Management Suite

Use the Oracle Fusion Middleware 11g Oracle Enterprise Content Management Suite Installer to install Oracle Enterprise Content Management Suite. Within the Middleware home, the installer creates an Oracle home directory named Oracle_ECM, where it installs the Oracle Enterprise Content Management Suite products.

The installer lays down the Oracle Enterprise Content Management Suite binaries for these products:

  • Oracle I/PM

  • Oracle IRM

Note: You can perform this task before or after Task 2 - Create schemas for applications, but you need to perform it after Task 3 - Install Oracle WebLogic Server in a Middleware home.

Mandatory

Chapter 3, "Installing Oracle Enterprise Content Management Suite"

Task 5 - Configure Oracle Enterprise Content Management Suite

Create or extend an Oracle WebLogic Server domain and choose the products that you want to deploy and configure as applications.

Fusion Middleware Configuration Wizard creates an Oracle WebLogic Server domain, which contains the Administration Server and one or more Managed Servers, such IRM_server1, depending on the products that you choose.

After you have created a domain, you can later extend that domain to deploy and configure additional Oracle Enterprise Content Management Suite products as applications.

Mandatory

Chapter 4, "Configuring Oracle Enterprise Content Management Suite"

Task 6 - Install and configure an external LDAP-based identity store

By default, Oracle Enterprise Content Management Suite uses the Oracle WebLogic Server embedded LDAP server. Although secure, the out-of-the-box embedded LDAP may not scale appropriately for enterprise production environments.

To manage the identities of users across diverse servers and enable single sign-on across applications, you can install and configure an external LDAP-based identity store.

Note: If you perform this task before Task 7 - Perform Postinstallation Configuration and Task 8 - Verify the installation, the postinstallation configuration is easier.

Optional

Section 4.4, "Reassociating the Identity Store with an External LDAP Authentication Provider."

Task 7 - Perform Postinstallation Configuration

For each Oracle Enterprise Content Management Suite application, you need to perform some initial configuration to get the application up and running in the Managed Server. Some of this initial configuration needs to be done before you start the Managed Server for the first time.

Mandatory

Chapter 5, "Configuring Oracle Imaging and Process Management"

Chapter 6, "Configuring Oracle Information Rights Management"

Task 8 - Verify the installation

To verify the installation, you can start the Administration Server and Managed Servers.

Before you can start a Managed Server the first time, you must start the Administration Server.

To start working with an Oracle Enterprise Content Management Suite application, you must start the Managed Server to which that application is deployed. You can then access the application's URL and complete the configuration according to your requirements.

Mandatory

Chapter 7, "Verifying the Installation and Configuration"


1.3 Installation Modules

The following installation modules are required for installing the products in Oracle Enterprise Content Management Suite:

1.3.1 Oracle Fusion Middleware and Oracle WebLogic Server Homes

Oracle Enterprise Content Management Suite requires a Middleware home with Oracle WebLogic Server on your system. If your system does not already have Oracle WebLogic Server, you can install it in a new Middleware home directory, as described in Section 3.1.2, "Installing Oracle WebLogic Server in a Middleware Home."

A Middleware home is a container for the Oracle WebLogic Server home, and, optionally, one Oracle Common home and one or more Oracle homes, with a directory structure like this:

/middleware_home
     wlserver_10.3
     jdk160
     oracle_common
     ECM_ORACLE_HOME
     user_projects

The ECM Oracle home contains the binary and library files necessary for Oracle Enterprise Content Management Suite. ECM_ORACLE_HOME represents the ECM Oracle home in path names.

The ECM Oracle home can be associated with multiple Oracle WebLogicServer domains. The Oracle Common home contains the binary and library files required for Oracle Enterprise Manager 11g Fusion Middleware Control and Java Required Files (JRF).

A Middleware home can reside on a local file system or on a remote shared disk that is accessible through a network file system (NFS).

For more information about the structure and contents of a Middleware home, see "Understanding Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide.

1.3.2 Database

The configuration of Oracle Enterprise Content Management Suite requires the availability of a supported database. The database must be up, and a database instance must be running. It does not have to be on the same machine where you are installing the suite.

The database must also be compatible with Repository Creation Utility (RCU), which creates the schemas for the suite's applications. For more information, see Chapter 2, "Creating Schemas for Oracle Enterprise Content Management Suite."

Note:

RCU is available only on a Linux or Windows operating system. You can use either the Linux-based RCU or Windows-based RCU to create schemas in any supported database.

For the latest information about supported databases, see the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network at

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

For more information about Oracle Database, see the Oracle Database Documentation page on Oracle Technology Network at

http://www.oracle.com/technology/documentation/database.html

1.3.3 Repository Creation Utility

You need to install and run Repository Creation Utility (RCU) to create a database schema for each Oracle Enterprise Content Management Suite application that you plan to configure.

RCU is available only on a Linux or Windows operating system. You can use RCU from a Linux or Windows system to create schemas in a supported database installed on any operating system.

For information about installing and running RCU, see Chapter 2, "Creating Schemas for Oracle Enterprise Content Management Suite."

1.3.4 Oracle Enterprise Content Management Suite

Installation of Oracle Enterprise Content Management Suite copies the files for all of the products in the suite to your system. To use one or more these products, you need to configure each one to run in a Managed Server, as an application deployed to Oracle WebLogic Server.

1.3.5 Oracle Universal Content Management 10g for Oracle I/PM Repository

Oracle I/PM uses Oracle Universal Content Management (Oracle UCM) for its repository. Therefore, your system needs to have Oracle UCM configured before the configuration of Oracle I/PM.

The Oracle Fusion Middleware 11g media packs include the Oracle UCM 10g media parts listed in Table 1-2.

Table 1-2 Oracle UCM 10g Media Parts in Oracle Fusion Middleware 11g

Part number Media Part

V13682-01

Oracle Content Server 10gR3 (10.1.3.3.3) for Microsoft Windows (32-bit)

V13684-01

Oracle Content Server 10gR3 (10.1.3.3.3) for Linux x86 (32-bit) and Linux x86-64

V13687-01

Oracle Content Server 10gR3 (10.1.3.3.3) for IBM zSeries Based Linux

V13683-01

Oracle Content Server 10gR3 (10.1.3.3.3) for Solaris Operating Environment (SPARC 64-bit)

V13688-01

Oracle Content Server 10gR3 (10.1.3.3.3) for Solaris Operating Environment (x86)

V13685-01

Oracle Content Server 10gR3 (10.1.3.3.3) for AIX5L Based Systems (64-bit)

V13686-01

Oracle Content Server 10gR3 (10.1.3.3.3) for HP-UX PA-RISC (64-bit)

V13689-01

Oracle Content Server 10gR3 (10.1.3.3.3) for HP-UX Itanium (64-bit)


All other Oracle UCM 10g components that Oracle I/PM 11g requires are on separate media parts. The ContentServerUpdateBundle component includes Content Tracker and all Oracle Content Server fixes since Release 10.1.3.5.0.

For information about installing Oracle UCM 10g, see the Oracle Universal Content Management page on Oracle Technology Network at

http://www.oracle.com/technology/products/content-management/ucm/index.html

1.4 Oracle WebLogic Server Domain

Each Oracle WebLogic Server domain includes an Administration Server and one or more Managed Servers. You can configure each Oracle Enterprise Content Management Suite application on a Managed Server by creating or extending a domain.

After you create a domain, you can use the Oracle WebLogic Server Administration Console and Oracle Fusion Middleware 11g Fusion Middleware control to perform postinstallation tasks on the domain. You can also use WebLogic Scripting Tool commands to perform some of the postinstallation tasks.

1.5 Directory Structure for Oracle Enterprise Content Management Suite

Figure 1-1 shows the directory structure of an Oracle Enterprise Content Management Suite installation.

When you install Oracle WebLogic Server, the installer creates a Middleware home directory (MW_HOME) that contains the Oracle WebLogic Server home directory (WL_HOME) and an Oracle Common home directory (ORACLE_COMMON_HOME), which contains the binary and library files required for the Oracle Enterprise Manager Fusion Middleware Control and Java Required Files (JRF).

When you install Oracle Enterprise Content Management Suite, an ECM Oracle home directory for the suite (ECM_ORACLE HOME) is created under the Middleware home directory. The ECM Oracle home directory contains the binary and library files for Oracle Enterprise Content Management Suite.

When you configure Oracle Enterprise Content Management Suite to create an Oracle WebLogic Server domain, a domain directory is created under the MW_HOME/user_projects/domain directory. The directory for the domain where you configure Oracle Enterprise Content Management Suite contains the Administration Server and one or more Managed Servers, each hosting an Oracle Enterprise Content Management Suite application. Based on the application or applications that you install, the following Managed Servers are created:

  • Oracle I/PM Managed Server

  • Oracle IRM Managed Server

Figure 1-1 illustrates the directory structure that installation and configuration of these products will create on your system. Numbers in the figure show the order in which to perform certain tasks.

Figure 1-1 Directory Structure of an Oracle Enterprise Content Management Suite Installation

Description of Figure 1-1 follows
Description of "Figure 1-1 Directory Structure of an Oracle Enterprise Content Management Suite Installation"

The topology in Figure 1-1 includes multiple applications configured on the same host in one Oracle WebLogic Server domain that includes only Oracle Enterprise Content Management Suite applications. The schemas for the applications are in the same database.