Thank you for your feedback!Categories
This appendix contains screenshots and descriptions for all of the Repository Creation Utility screens:
This is the first screen that appears when RCU is started.
Click Skip This Page Next Time if you do not want to see the Welcome screen the next time you start RCU.
Select Create to create component schemas in the database.
Select Drop to remove component schemas from the database.
Select Create to create component schemas in the database.
Select Drop to remove component schemas from the database.
Specific database requirements for the various schemas can be found in the Oracle Fusion Middleware System Requirements document, available on Oracle Technology Network:
http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm
For certified database versions, see the Oracle Fusion Middleware Certification Matrix, also available on Oracle Technology Network:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
For Oracle databases, specify the following connection credentials:
Host Name
Enter the name of the server where your database is running. Use the following format:
myhost.mydomain.com
For Oracle RAC databases, specify the VIP name or one of the node names in this field.
Port
Enter the port number for your database. The default port number for Oracle databases is 1521.
Database Name
Specify the service name for the database. Typically, the service name is the same as the global database name.
If you are unsure what the service name for your database is, you can obtain it from the SERVICE_NAMES parameter in the database's initialization parameter file. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.
For Oracle RAC databases, specify the service name of one of the nodes in this field. For example:
sales.mydomain.com
Username
Enter the user name for your database. The default user name is SYS.
Password
Enter the password for your database user.
Role
Select the database user's role from the drop-down list:
Normal
SYSDBA
The SYS user requires the SYSDBA role. All other users would use the Normal role.
For Microsoft SQL Server databases, specify the following connection credentials:
Unicode Support
Select Yes or No from the drop-down list.
Note:
Oracle SOA Infrastructure schemas are created with Unicode support (database tables created with NVARCHAR) only, regardless of the option selected in this field.Server Name
Enter the host name, IP address, or complete server name in host\server format of the server where your database is running.
Port
Enter the port number for your database.
Database Name
Specify the name of your database.
Username
Enter the user name for your database. The user must have SYSDBA or DBA privileges.
Password
Enter the password for your database user.
For IBM DB2 databases, specify the following connection credentials:
Server Name
Enter the host name, IP address, or complete server name in host\server format of the server where your database is running.
Port
Enter the port number for your database.
Database Name
Specify the name of your database.
Username
Specify the name of a user with DB Owner privileges.
Password
Enter the password for your database user.
Click Next when you are finished entering the connection credentials for your database.
The following screen appears, indicating the progress of the installer establishing the connection with the specified database.
If an error occurs while the connection is being established, the error message(s) appear in the Messages field on the Database Connection Details screen.
Click OK to dismiss this screen.
Below is the Select Components screen if you selected Create on the Create Repository Screen.
The following topics are covered in this section:
Note:
You must remember the prefix and schema names for the components you are installing; you will need this information during the configuration phase of Fusion Middleware product installation. Oracle recommends that you write these values down.IBM DB2 authenticates its database users using equivalent operating system users. Therefore, prior to running RCU, one operating system user must be created for each schema. The operating system user name must match the schema owner name and must contain only lowercase letters; no all-uppercase or mixed-case names are allowed. For example, if you create a schema named DEV_ODI using RCU, then the operating system user must be named dev_odi (all lowercase letters).
Prefixes are used to create logical groupings of schemas in a database. For example, if you want to create two versions of the MDS schema in the database, you can use different prefixes to uniquely identify each one (for example, TEST_MDS and PROD_MDS). Note that the prefix name and schema name are separated by an underscore (_) character.
Note:
The Oracle Internet Directory (
Sign In
ODS) component cannot be prepended with a custom prefix; there can only be one repository for this component per database.If you want to create a new prefix for your schemas, select Create a New Prefix and specify a new prefix name in the field. The prefix name must be a minimum of one character in length and cannot exceed 12 alphanumeric characters (0-9, a-z, or A-Z) in length (not including the underscore character). Prefixes should not start with a number. No whitespace or special characters are allowed.
Note:
For IBM DB2 databases, prefixes are limited to four characters in length (not including the underscore character).The default new prefix is DEV. If DEV already exists as a prefix, then DEV1 is used; if DEV1 exists, then DEV2 is the default, and so on.
Use existing prefixes to add additional components to an existing repository in the database. To use an existing prefix, select Select an Existing Prefix and choose a prefix from the drop-down list.
When you select a component, any other components that may be required by the component you select are also selected. For example, if you select SOA and BPM Infrastructure, then all schemas in this category are selected along with the Metadata Services schema. The Metadata Services schema is required by each component in SOA and BPM Infrastructure.
If a component has a plus sign (+) next to its name, then there are sub components available. Click on the plus sign (+) to expand the category to view all sub components. If you want to select a component with all its subcomponents, click on the top-most box with the plus sign (+).
Click on the name of any schema in the "Schema Owner" column to change the name of the schema. Schema names can only contain alphanumeric characters (0-9, a-z, or A-Z) and are case-sensitive.
Note:
The Oracle Internet Directory (ODS) component cannot be prepended with a custom prefix; there can only be one repository for this component per database.Click Next when you are finished specifying your prefix, schema names, and selecting components. The following screen appears, indicating the progress of component prerequisite checking before the schemas are created.
If an error occurs during the prerequisite checking, the error message(s) appear in the Messages field on the Select Components screen.
Click OK to dismiss this screen.
Below is the Select Components screen if you selected Drop on the Create Repository Screen.
First, select the prefix associated with the schema(s) you want to drop.
Then, select the component(s) whose schemas you want to drop.
Click Next when you are finished. The following screen appears:
Click OK to continue. The following screen appears:
If an error occurs during the prerequisite checking, the error message(s) appear in the Messages field on the Select Components screen.
Click OK to dismiss this screen.
Below is the Schema Passwords screen.
There are three ways to specify schema passwords on this screen:
Select Use same password for all schemas if you want to use a single password for all schemas and their auxiliary schemas. In the Password field, enter your password. Enter your password again in the Confirm Password field.
Select Use main schema passwords for auxiliary schemas if you want to specify different passwords for the main schemas, but still have the same password used for their respective auxiliary schemas. If you select this option, only the main schemas will be visible in the table. For each schema, you must enter each schema's password in the Password column in the table, and enter the same password in the Confirm Password column.
Select Specify different passwords for all schemas if you want to specify unique passwords for the main schemas and auxiliary schemas. If you select this option, all main schemas and auxiliary schemas will be visible in the table. For each schema and auxiliary schema, you must enter the password in the Password column in the table, and enter the same password in the Confirm Password column.
Note:
You must remember the passwords you enter on this screen; you will need this information during the configuration phase of Fusion Middleware product installation. Oracle recommends that you write these values down.
This page allows one or more components to specify additional configuration information required by the components during runtime.
This screen only appears if you selected a component on the Select Components Screen (for Create Operation) that supports custom variables.
This screen only appears if you selected the Create option on the Create Repository Screen. The following topics are covered:
Click Next when you are finished with your tablespace information. The following screen appears, asking you to confirm the creation of tablespaces for any new schemas.
Note:
RCU only creates tablespaces for those components associated with RCU.Click OK to continue. The following screen appears, indicating the progress of the tablespace creation.
Click Stop to cancel tablespace creation. When the tablespaces are created, click OK to dismiss this window.
The default tablespace mapping for each component are shown in Appendix B, "Repository Creation Utility Schemas, IDs, and Tablespaces".
In the Default Tablespace and Temp tablespace columns, you can click on the tablespace cell to select from a list of available additional tablespace names.
Note:
OID tablespace names cannot be user specified.To change the default tablespace for a component, select the tablespace name in the "Default Tablespace" column, then select the tablespace name you want to use from the drop-down list. You can have your components use as many or as few tablespaces as desired to suit your configuration.
To change the temporary tablespace for a component, select the tablespace name in the "Temp Tablespace" column, then select the tablespace name you want to use from the drop-down list.
Some components have additional tablespaces associated with their schemas. If this is the case, the Additional Tablespaces button will appear on this screen. If none of the selected components have additional tablespaces, then this button will not appear.
To view additional tablespaces associated with the selected components, click the Additional Tablespaces button. You will see a screen similar to the following:
Only those components with additional tablespaces as defined in the configuration files will appear on this screen.
To change the tablespace you want to use for a component, click in the "Tablespace Name" column and select the tablespace you want to use from the drop-down list.
Click OK when you are finished.
To manage your tablespaces and datafiles, click the Manage Tablespaces button. You will see a screen similar to the following:
The following topics are covered in this section:
Section A.9.4.1, "Adding, Modifying, and Removing Tablespaces"
Section A.9.4.2, "Adding, Modifying, and Removing Datafiles"
Only tablespaces that will be created by RCU can be modified or removed. Tablespaces that existed before RCU was launched are visible on this screen but are grayed out and cannot be modified or removed.
Only tablespaces that are used by a component are created. You can specify a new tablespace here, but unless it is actually used by a component it will not be created.
To modify a tablespace, select the tablespace name on the left-hand portion of the screen, and edit the following fields as necessary:
Name
Edit the tablespace name this field to change the name of your tablespace.
Type
Specify whether you want this tablespace to be a temporary tablespace or permanent tablespace.
Block Size (KB)
Specify the block size (in Kilobytes) to be used for data retrieval.
Storage Type
Select Use Bigfile Tablespace if you want to create a bigfile tablespace; this is typically used if you have single large files instead of multiple small files. Select Use Automatic Segment Space Management if you want to use bitmaps to manage the free space within segments.
To add a tablespace, click Add and specify the same details as above (for modifying a tablespace) for your new tablespace.
To remove a tablespace, select the tablespace name from the navigation tree, then click Remove. This tablespace will not get created.
In the Datafiles section, specify the datafiles that make up the selected tablespace. Select one of the following for more information:
To add a datafile, click the icon with the plus sign (+):
The Add Datafile screen appears:
Provide the following information:
File Name
Specify the name of the datafile.
File Directory
Specify the location where this datafile will reside.
Size
Specify the initial size of the datafile. Use the drop-down list to specify the size in kilobytes (KB), megabytes (MB), or gigabytes (GB).
Select Automatically extend datafile when full (AUTOEXTEND) if you want to automatically extend the size of your datafile when it becomes full. In the "Increment" field, specify the size by which your datafile should be increased each time it becomes full. Use the drop-down list to specify the size in kilobytes (KB), megabytes (MB), or gigabytes (GB).
If you want to limit maximum size of the datafile, specify this value in the "Maximum Size" field.
To modify or edit a datafile, select the icon next to the datafile name you want to edit, then click the icon with the pencil:
The Edit Datafile screen appears:
Provide the following information:
File Name
Specify the name of the datafile.
File Directory
Specify the location where this datafile will reside.
Size
Specify the initial size of the datafile. Use the drop-down list to specify the size in kilobytes (KB), megabytes (MB), or gigabytes (GB).
Select Automatically extend datafile when full (AUTOEXTEND) if you want to automatically extend the size of your datafile when it becomes full. In the "Increment" field, specify the size by which your datafile should be increased each time it becomes full. Use the drop-down list to specify the size in kilobytes (KB), megabytes (MB), or gigabytes (GB).
If you want to limit maximum size of the datafile, specify this value in the "Maximum Size" field.
To delete a datafile, select the icon next to the datafile name you want to delete, then click the icon with the "X":
Below is the Summary screen if you selected Create on the Create Repository Screen.
Review the information on this screen, and click Create to begin schema creation. The operations summarized on this page will be performed when you click Create.
While the schemas are being created, you will see the following progress screen:
Click Stop if you want to stop creating the schemas.
Below is the Summary screen if you selected Drop on the Create Repository Screen.
Review the information on this screen, and click Drop to begin the operations summarized on this page.
While the schema(s) are being dropped, you will see the following progress screen:
Click Stop if you want to cancel the operation.
Below is the Completion Summary screen if you selected Create on the Create Repository Screen.
Note the log file names for each component that are visible in the "Logfile" column.
The main RCU log and component log files are written to the following directory on UNIX operating systems:
RCU_HOME/rcu/log/logdir.date_timestamp
On Windows operating systems:
RCU_HOME\rcu\log\logdir.date_timestamp
If there were any problems encountered during schema creation, you can troubleshoot the issue using the log files. For more information, see Appendix C, "Troubleshooting Repository Creation Utility".
If errors are encountered during a Create operation, or if a Create operation fails for any component, the Cleanup for failed components checkbox appears on this page and is selected by default. If selected, RCU will perform cleanup operations for the component that failed during the Create operation. If you choose not to select this checkbox, you can cleanup the failed component at a later time by performing a Drop operation for the failed component(s).
Review the information on this screen, then click Close to dismiss this screen.
Below is the Completion Summary screen if you selected Drop on the Create Repository Screen.
Note the log file names for each component that are visible in the "Logfile" column.
The main RCU log and component log files are written to the following directory on UNIX operating systems:
RCU_HOME/rcu/log/logdir.date_timestamp
On Windows operating systems:
RCU_HOME\rcu\log\logdir.date_timestamp
If there were any problems encountered during schema creation, you can troubleshoot the issue using the log files. For more information, see Appendix C, "Troubleshooting Repository Creation Utility".
Review the information on this screen, then click Close to dismiss this screen.