2 Running Repository Creation Utility (RCU)

2.3.1 Install Java Access Bridge

To install Java Access Bridge:

1. Download Java Access Bridge from the following URL:

   http://java.sun.com/javase/technologies/accessibility/accessbridge/
   

2. Install Java Access Bridge.

3. Copy the access-bridge.jar and jaccess-1_4.jar from your installation location to the jre\lib\ext directory.

4. Copy the WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll files from your installation location to the jre\bin directory.

5. Copy the accessibility.properties file to the jre\lib directory.

2.3.2 Configure RCU to Use Java Access Bridge

To configure RCU to use Java Access Bridge after you complete the installation, set the system variable ORACLE_OEM_CLASSPATH to point to the installed Java Access Bridge files:

1. Display System in the Control Panel.

2. Select the Advanced tab.

3. Click the New button under the System Variable list. The New System Variable dialog appears.

4. In the Variable Name field, enter ORACLE_OEM_CLASSPATH.

5. In the Variable Value field, enter the full path to access-bridge.jar and jaccess-1_4.jar.

   Use a semicolon to separate the two paths. Do not use quotes or character spaces.

6. Click OK.

2.4.1 Do all Schemas Have to Reside in the Same Database?

You can choose to create all the schemas in a single database or distribute them throughout multiple databases.

2.4.2 Are Multiple Schemas Supported?

You can use RCU to create multiple schemas of each component using custom prefixes (for example, you could use the prefix TEST to create a test version of the Metadata Services schema called TEST_MDS, then use the prefix PROD to create a production version of the same schema called PROD_MDS on the same database).

You are only allowed to use a prefix once per schema within a single database. For example, if you had a test version of the Metadata Services schema called DEV_MDS, then you can not use the DEV prefix again to create another version of the schema (for example, DEV_MDS2).

2.4.3 What Happens When a Schema is Created?

The following sequence takes place when a schema is created with RCU:

1. Prior to the schema being created, RCU performs global and component level prerequisite checks to ensure that certain minimum requirements are met.

2. The schemas are created; the required tablespaces and data files are created.

3. The schema_version_registry table is updated so that the schema type is mapped to the actual schema name (for example, TEST_MDS might be mapped to the MDS Schema type).

4. The scripts provided by the various component owners are invoked; these scripts perform the following:

   1. Create the user and grant the required roles.

   2. Run ALTER SESSION SET CURRENT SCHEMA to switch the schema to user context.

   3. Create the schema objects.

2.4.4 Creating Schemas

After successfully starting RCU (see Section 2.2, "Starting RCU"), follow the instructions in Table 2-1 to create schemas.

Click on the screen name to see more detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.

2.5.1 Dropping Shared Tablespaces

Tablespaces that are shared among multiple schemas will not be dropped. For example, if you created both the Audit Services (for example, DEV_IAU) and Metadata Services (for example, DEV_MDS) schemas, both schemas would use the temporary tablespace DEV_IAS_TEMP (see Section A.8.1, "Default Tablespace Mappings").

If you then drop the DEV_IAU schema, the DEV_IAS_TEMP tablespace would not be dropped since it is also being used by the DEV_MDS schema.

2.5.2 Dropping Schemas and Deleting Datafiles (Windows Only)

If your database is running on a Windows operating system, and you are using RCU to drop schemas from that database, some components datafiles are not dropped (for example, OID).

In the event you want to re-create the dropped schema, you must first manually delete the datafile before creating the schema.

2.7.1 CLI Syntax and Parameters

The syntax for the RCU command line interface is:

rcu [-silent | -interactive] [-createRepository | -dropRepository] {<options>}

Specify -silent if you want to run RCU with minimal interaction once you have entered the commend. You must specify all necessary command line parameters. If you use the -silent option, RCU will prompt you for the database and schema passwords.

Specify -interactive if you want to run RCU and be prompted for each parameter.

Use the -createRepository command to create a repository. For more information, see Section 2.7.4, "Creating a Repository".

Use the -dropRepository command to drop a repository. For more information, see Section 2.7.5, "Dropping a Repository"

Table 2-3 describes the various options and their descriptions.

-component component_ID

-component component_ID -component component_ID

-component PORTAL -component PORTLET

2.7.2 RCU and Password Handling

If you use the -silent flag, RCU will prompt you for the database and schema passwords.

2.7.3 RCU Component IDs and Schema Dependencies

Before you create any schemas, you must be aware of and specify all dependencies for the component you are loading. For example, the SOAINFRA schema depends on the MDS and ORASDPM schemas; if you try to load the SOAINFRA schema without specifying both the MDS and ORASDPM schemas, or if the MDS and ORASDPM schemas do not already exist in the database, RCU will stop before any loading takes place.

Table 2-4 lists the schemas along with their component IDs and dependencies:

In addition to the component IDs listed in the table, there is also a SAMPLE schema that can be used for testing purposes.

You must also be aware of these dependencies when dropping schemas. For example, if you can see from Table 2-4 that several schemas require the MDS schema to be present; if you choose to drop the MDS schema, then all the schemas that require the MDS schema will stop working.

2.7.4 Creating a Repository

The full syntax for the RCU command line interface to create a repository is shown below:

rcu [-silent | -interactive] -createRepository
   [-compInfoXMLLocation <location of ComponentInfo.xml file>]
   [-storageXMLLocation <location of Storage.xml file>]
   [-databaseType [ORACLE|SQLSERVER]]
   -connectString <database connect string (for example: host:port:service_id)>
   -dbUser <database username>
   [-dbRole <database role>]
   [-unicodeSupport Yes|No (default is Yes. Applicable for SQLSERVER databases only.)]
   [-variables <comma separated variables in the format: variablename=value>]
   [-schemaPrefix <schema prefix (optional for non-prefixable components)>]
   -component <component ID>
]

In order to work properly, make sure that the parameters are specified in the same order that they are listed. For example, do not specify the -compInfoXMLLocation parameter before the -component parameter.

When specifying the -component, you must use the correct component IDs, which are listed in Table A-1 in Section A.8.1, "Default Tablespace Mappings".

Below is a sample command to create the SOA Infrastructure schemas on a UNIX system:

./rcu -silent -createRepository -databaseType ORACLE -connectString host1.oracle.com:1521:orcl -dbUser sys -dbRole sysdba -schemaPrefix TEST -component SOAINFRA -component MDS -component ORASDPM

Notice that this command takes into account the correct component IDs and dependencies for the SOA Infrastructure schemas, as listed in Table 2-4.

2.7.5 Dropping a Repository

The full syntax for the RCU command line interface to drop a repository is shown below:

rcu [-silent | -interactive] -dropRepository
   [-compInfoXMLLocation <location of ComponentInfo.xml file>]
   [-storageXMLLocation <location of Storage.xml file>]
   [-databaseType [ORACLE|SQLSERVER]]
   -connectString <database connect string (for example: host:port:service_id)>
   -dbUser <database username>
   [-dbRole <database role>]
   [-variables <comma separated variables in the format: variablename=value>]
   [-schemaPrefix <schema prefix (optional for non-prefixable components)>]
   -component <component ID>

In order to work properly, make sure that the parameters are specified in the same order that they are listed. For example, do not specify the -compInfoXMLLocation parameter before the -component parameter.

Below is a sample command to drop the WebCenter Spaces schemas on a UNIX system:

./rcu -silent -dropRepository -databaseType ORACLE -connectString host1.oracle.com:1521:orcl -dbUser sys -dbRole sysdba -schemaPrefix TEST -component WEBCENTER

2.7.6 RCU Environment Variables

Table 2-5 shows the variables picked up by RCU from the environment. If the environment variable is not set, then RCU uses the default value.