2 Running Repository Creation Utility (RCU)

2.2.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.2.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.3.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.3.2 Are Multiple Versions of the Same Schema Supported?

You can use RCU to create multiple versions of each schema using custom prefixes (for example, you could have a test version of the Metadata Services schema called TEST_MDS and also a production or live version of the same schema called PROD_MDS on the same database).

2.3.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.3.4 Creating Schemas

After successfully starting RCU (see Section 2.1, "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 CLI Syntax and Parameters

The syntax for the RCU command line interface is:

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

Table 2-3 describes the various command line options.

2.5.2 RCU and Password Handling

If you use the -silent flag, RCU will prompt you for the database and schema passwords. If you use the -randomizePasswords parameter and “false” is passed as the value, then RCU will prompt for the schema passwords. If they are not entered, RCU will generate random passwords and use those.

2.5.3 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]
   -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>]
   [-lockSchemas <true|false>]
   [-randomizePasswords <true|false>]
   [-schemaPrefix <schema prefix (optional for non-prefixable components)>]
   -component <component name>
]

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.

2.5.4 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]
   -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 name>

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.

2.5.5 RCU Environment Variables

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