6 Preparing the Database for an Enterprise Deployment

This chapter describes procedures for preparing your database for an Oracle WebCenter Content enterprise deployment. The procedures include initial setup of the database, loading the metadata repository, and backing up the database.

This chapter includes the following topics:

• Section 6.1, "Overview of Preparing the Database for an Enterprise Deployment"

• Section 6.2, "Database Requirements"

• Section 6.3, "Creating Database Services"

• Section 6.4, "Loading the Oracle Fusion Middleware Metadata Repository in the Oracle RAC Database"

• Section 6.5, "Backing Up the Database"

6.1 Overview of Preparing the Database for an Enterprise Deployment

For the Oracle WebCenter Content enterprise topology, the database contains the Oracle Fusion Middleware repository, which is a collection of schemas used by various Oracle Fusion Middleware components, such as the Oracle SOA and WebCenter Content components. This database is separate from the Identity Management database, which is used in the identity management enterprise deployment by components such as Oracle Internet Directory, DIP, and so on.

You must install the Oracle Fusion Middleware repository before you can configure the Oracle Fusion Middleware components. You install the Oracle Fusion Middleware metadata repository into an existing database using the Repository Creation Utility (RCU), which is available from the RCU distribution or from the location listed in Table 2-2. For the enterprise topology, a Real Application Clusters (Oracle RAC) database is highly recommended.

When you configure the SOA components, the configuration wizard will prompt you to enter the information for connecting to the database that contains the metadata repository.

6.2 Database Requirements

Before loading the metadata repository into your database, check that the database meets the requirements described in these sections:

• Section 6.2.1, "Database Host Requirements"

• Section 6.2.2, "Supported Database Versions"

• Section 6.2.3, "Initialization Parameters"

6.2.1 Database Host Requirements

On the hosts CUSTDBHOST1 and CUSTDBHOST2 in the data tier, note the following requirements:

• Oracle Clusterware

  For 11g Release 1 (11.1) for Linux, refer to the Oracle Clusterware Installation Guide for Linux.

• Oracle Real Application Clusters

  For 11g Release 1 (11.1) for Linux, refer to the Oracle Real Application Clusters Installation Guide for Linux and UNIX. For 10g Release 2 (10.2) for Linux, refer to the Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Linux.

• Automatic Storage Management (optional)

  ASM gets installed for the node as a whole. It is recommended that you install it in a separate Oracle Home from the Database Oracle Home. This option comes in at runInstaller. In the Select Configuration page, select the Configure Automatic Storage Management option to create a separate ASM home.

6.2.2 Supported Database Versions

Oracle WebCenter Content requires the presence of a supported database and schemas. To check if your database is certified or to see all certified databases, refer to the "Oracle Fusion Middleware 11g Release 1 (11.1.1.x)" product area on the Oracle Fusion Middleware Supported System Configurations page:

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

To check the release of your database, you can query the PRODUCT_COMPONENT_VERSION view as follows:

SELECT VERSION FROM SYS.PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE "Oracle%";

Note:

Oracle WebCenter Content requires that the database used to store its metadata (either 10g or 11g) supports the AL32UTF8 character set. Check the database documentation for information on choosing a character set for the database.

6.2.3 Initialization Parameters

Ensure that the following initialization parameter is set to the required minimum value. It is checked by Repository Creation Utility.

Table 6-1 Required Initialization Parameters

Configuration	Parameter	Required Value	Parameter Class
SOA	PROCESSES	400 or greater	Static
Oracle WebCenter Content	PROCESSES	100 or greater	Static
SOA and Oracle WebCenter Content	PROCESSES	500 or greater	Static

To check the value of the initialization parameter using SQL*Plus, you can use the SHOW PARAMETER command.

As the SYS user, issue the SHOW PARAMETER command as follows:

SHOW PARAMETER processes

Set the initialization parameter using the following command:

ALTER SYSTEM SET processes=500 open_cursors=500 SCOPE=SPFILE;

Restart the database.

Note:

The method that you use to change a parameter's value depends on whether the parameter is static or dynamic, and on whether your database uses a parameter file or a server parameter file. See the Oracle Database Administrator's Guide for details on parameter files, server parameter files, and how to change parameter values.

6.3 Creating Database Services

Oracle recommends using the Oracle Enterprise Manager Cluster Managed Services page to create database services that client applications will use to connect to the database. For complete instructions on creating database services, see the chapter on workload management in the Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide.

You can also use SQL*Plus to configure this using the following instructions:

1. Use the CREATE_SERVICE subprogram to create the wccedg.mycompany.com database service. Log in to SQL*Plus as the sysdba user and run the following command:

   EXECUTE DBMS_SERVICE.CREATE_SERVICE
   (SERVICE_NAME => "wccedg.mycompany.com",
   NETWORK_NAME => "wccedg.mycompany.com"
   );
   

2. Add the service to the database and assign it to the instances using srvctl:

   srvctl add service -d ecmdb -s wccedg.mycompany.com -r ecmdb1,ecmdb2
   

3. Start the service using srvctl:

   srvctl start service -d ecmdb -s wccedg.mycompany.com
   

Note:

For more information about the SRVCTL command, see the Oracle Real Application Clusters Administration and Deployment Guide.

Oracle recommends that a specific database service be used for a product suite, even when they share the same database. It is also recommended that the database service used is different than the default database service. In this case, the database is ecmdb.mycompany.com and the default service is one with the same name. The Oracle WebCenter Content install is configured to use the service wccedg.mycompany.com. It is recommended that a service named soaedg.mycompany.com is used for SOA.

Note:

For simplicity, the data source configuration screens in this guide use the same service name (wccedg.mycompany.com)

6.4 Loading the Oracle Fusion Middleware Metadata Repository in the Oracle RAC Database

The Repository Creation Utility (RCU) is available from the RCU distribution. The RCU used to seed the database must match the patch set level of the Oracle WebCenter Content installation. This means that if you install Oracle WebCenter Content 11gR1 (11.1.1.6) in this enterprise deployment, you must use RCU 11gR1 (11.1.1.6).

To load the Oracle Fusion Middleware Repository into a database, complete these steps:

1. Open the Repository Creation Utility (RCU) distribution, and then start RCU from the bin directory in the RCU home directory:

   cd RCU_HOME/bin
   ./rcu
   

2. In the Welcome screen (if displayed), click Next.

3. In the Create Repository screen, select Create to load component schemas into a database. Click Next.

4. In the Database Connection Details screen, enter the connect information for your database:

   • Database Type: Select Oracle Database.

   • Host Name: Specify the name of the node on which the database resides. For the Oracle RAC database, specify the VIP name or one of the node names as the host name: CUSTDBHOST1-VIP.

   • Port: Specify the listen port number for the database: 1521.

   • Service Name: Specify the service name of the database (wccedg.mycompany.com).

   • Username: Specify the name of the user with DBA or SYSDBA privileges: SYS.

   • Password: Enter the password for the SYS user.

   • Role: Select the database user's role from the list: SYSDBA (required by the SYS user).

   Click Next.

   Figure 6-1 Database Connection Details Screen

   
   Description of "Figure 6-1 Database Connection Details Screen"
   
   

5. If your database is not using the UTF-8 character set, you will see a warning message indicating that there may be data loss if you are going to use the database for multilingual support. If you are not planning to use multilingual support, then you can click Ignore. Otherwise, click Stop.

6. In the Select Components screen, do the following:

   • Select Create a new Prefix, and enter a prefix to use for the database schemas, for example DEV or PROD. You can specify up to six characters as a prefix. Prefixes are used to create logical groupings of multiple repositories in a database. For more information, see the Oracle Fusion Middleware Repository Creation Utility User's Guide.

     Tip:

     Note the name of the schema because the upcoming steps require this information.

   • Select the following components:

     • AS Common Schemas:

       - Metadata Services

     • WebCenter Content:

       - Oracle WebCenter Content Server - Complete

       - Oracle WebCenter Content: Imaging

     • SOA and BPM Infrastructure:

       - SOA Infrastructure

       - User Messaging (automatically selected with SOA Infrastructure)

   Click Next.

   Figure 6-2 Select Components Screen

   
   Description of "Figure 6-2 Select Components Screen"
   
   

7. In the Schema Passwords screen, select Use main schema passwords for auxiliary schemas and click Next. In the subsequent screen refresh, enter the schema passwords for all components.

   Tip:

   Note the name of the schema because the upcoming steps require this information.

   Figure 6-3 Schema Passwords Screen

   
   Description of "Figure 6-3 Schema Passwords Screen"
   
   

8. In the Map Tablespaces screen, choose the tablespaces for the selected components, and click Next.

   A confirmation dialog opens stating that any tablespace that does not already exist in the selected schema will be created. Click OK to acknowledge this message.

9. In the Summary screen, click Create.

10. In the Completion Summary screen, click Close.

11. Verify that the required schemas were created successfully by connecting to the database with the new user added:

    ORACLE_HOME/bin/sqlplus
    

    Log in as the DEV_OCS user and enter the password. A simple verification can be performed by querying the schema version registry:

    -bash-3.00$ $ORACLE_HOME/bin/sqlplus DEV_OCS/password as SYSDBA
    SQL> SELECT version, status FROM schema_version_registry where owner = "DEV_OCS";
    
    VERSION STATUS-----------------------------------------11.1.1.6.0 VALID
    

Note:

Oracle recommends using the database used for identity management (see Chapter 15, "Integration with Oracle Identity Management") to store the Oracle WSM policies. It is therefore expected to use the IM database information for the OWSM MDS schemas, which will be different from the one used for the rest of SOA schemas. To create the required schemas in the database, repeat the steps above using the IM database information, but select only AS Common Schemas: Metadata Services in the Select Components screen (step 6).

6.5 Backing Up the Database

After you have loaded the metadata repository into your database, you should make a backup before installing the software for your enterprise deployment.

Backing up the database is for the explicit purpose of quick recovery from any issue that may occur in the further steps. You can choose to use your backup strategy for the database for this purpose or simply make a backup using operating system tools or RMAN for this purpose. It is recommended that you use Oracle Recovery Manager for the database, particularly if the database was created using Oracle ASM. If possible, a cold backup using operating system tools such as tar can also be performed.