Installing Oracle SOA suite 11g. Updated and more accurate SOA installation steps here. Repository creation utility (ofm_rcu_win_11.1.1.7.0_32_disk1. The RCU creates all the needed schemas required by the SOA Suite. You can find RCU 11.1.1.6.0 installation here: http://download.oracle.com/otn/nt/middleware/11g.
Oracle Fusion Middleware 11g (ofm11g) on. BAM by using Repository Creation Utility (RCU) Install Oracle. Fusion Middleware 11g (ofm11g) on Centos 5.
- 2 Running Repository Creation Utility (RCU) This chapter describes how to use RCU to create and drop schemas using both the graphical interface and command line.
- 3.2 Installing and Configuring Oracle Fusion Middleware. The following are the general steps you need to take to install and configure Oracle Fusion Middleware.
- Cookbook: Installing and Configuring Oracle BI Applications 11.1.1.7.1. By Mark Rittman and Kevin McGinley. A step-by-step guide to installing, configuring, and.
- Installing Oracle SOA Suite. The name of the package is ofm_rcu_win32_11.1. If you have picked the default prefix of “DEV_” during the RCU install then.
- My environment for ODI installation is a Intel Core i5 machine with 8 GB memory. To start with the repository creation, ofm_rcu_win_11.1.1.6.0_disk1_1of1.zip is.
- What to install. ofm_rcu_win_11.1.1.5.0_disk1_1of1.zip. The Repository Creation Utility opens. On the welcome screen, click. Next. Select.
Running Repository Creation Utility (RCU)5/9. This chapter describes how to use RCU to create and drop schemas using both the graphical interface and command line interface. The following topics are covered: 2. Starting RCUTo start RCU, insert the RCU CD- ROM and start RCU from the rcu. Home/bin (on UNIX) or rcu.
Home\bin (on Windows) directory: On UNIX. You can also download a .
RCU from Oracle Technology Network (OTN): http: //www. After downloading the . RCU from the RCU_HOME/bin (on UNIX) or RCU_HOME\bin (on Windows) directory with the commands shown above, where RCU_HOME is the folder where RCU was unzipped, or the drive or mount point of the CD- ROM.
Note. On Windows systems, make sure that you do not extract the RCU . Note. RCU is available only on Linux and Windows platforms. Either the Linux RCU or Windows RCU may be used to create schemas on any supported database platform.
Using RCU with Java Access Bridge (Windows Only)Java Access Bridge enables assistive technologies, such as JAWS screen reader, to read Java applications running on the Windows platform. Assistive technologies can read Java- based interfaces, such as Oracle Universal Installer and Oracle Enterprise Manager. Install Java Access Bridge. To install Java Access Bridge: Download Java Access Bridge from the following URL: http: //java. Install Java Access Bridge. Copy the access- bridge.
Copy the Windows. Access. Bridge. dll, Java. Access. Bridge. dll, and JAWTAccess. Bridge. dll files from your installation location to the jre\bin directory. Copy the accessibility.
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: Display System in the Control Panel. Select the Advanced tab. Click the New button under the System Variable list. The New System Variable dialog appears. In the Variable Name field, enter ORACLE_OEM_CLASSPATH. In the Variable Value field, enter the full path to access- bridge.
Use a semicolon to separate the two paths. Do not use quotes or character spaces.
Click OK. 2. 3 Creating Schemas. RCU is used to create the various component schemas in an existing database. 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.
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). What Happens When a Schema is Created? The following sequence takes place when a schema is created with RCU: Prior to the schema being created, RCU performs global and component level prerequisite checks to ensure that certain minimum requirements are met. The schemas are created; the required tablespaces and data files are created. 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).
The scripts provided by the various component owners are invoked; these scripts perform the following: Create the user and grant the required roles. Run ALTER SESSION SET CURRENT SCHEMA to switch the schema to user context. Create the schema objects. Creating Schemas. After successfully starting RCU (see Section 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. Table 2- 1 How to Create Schemas. Dropping Schemas. To drop schemas from the database, start RCU (see Section 2. Starting RCU"), then follow the instructions in Table 2- 2. Click on the screen name to see more detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.
Table 2- 2 How to Drop Schemas. Using the Repository Creation Utility CLIThis section describes how to use the Repository Creation Utility's (RCU) command line interface (CLI). The CLI is necessary for integration with both the Oracle Fusion Middleware installer and Enterprise Manager during application deployment. Additionally, you can use the CLI in cases where Xserver is not configured or if you are using a telnet terminal that does not have proper display capabilities.
This section contains the following topics: 2. CLI Syntax and Parameters. The syntax for the RCU command line interface is. Table 2- 3 describes the various command line options. Table 2- 3 RCU Command Line Interface Options and Descriptions.
Option. Description- silent or - interactive. 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. Specify - interactive if you want to run RCU and be prompted for each parameter. One of the following: 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 - randomize.
Passwords 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. Creating a Repository. The full syntax for the RCU command line interface to create a repository is shown below. Repository. [- comp.
Info. XMLLocation < location of Component. Info. xml file> ]. XMLLocation < location of Storage. Type ORACLE]. - connect. String < database connect string (for example: host: port: service_id)>. User < database username>. Role < database role> ].
Schemas < true|false> ]. Passwords < true|false> ].
Prefix < schema prefix (optional for non- prefixable components)> ]. When loading 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, RCU will stop before any loading takes place. 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 - comp. Info. XMLLocation parameter before the - component parameter. Dropping a Repository. The full syntax for the RCU command line interface to drop a repository is shown below.
Repository. [- comp. Info. XMLLocation < location of Component. Info. xml file> ]. XMLLocation < location of Storage.
Type ORACLE]. - connect. String < database connect string (for example: host: port: service_id)>. User < database username>. Role < database role> ].
Prefix < schema prefix (optional for non- prefixable components)> ]. 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 - comp. Info. XMLLocation parameter before the - component parameter. 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. Table 2- 4 RCU Environment Variables. Variable. Default. Description. RCU_LOG_LOCATIONORACLE_HOME/rcu/log (UNIX)ORACLE_HOME\rcu\log (Windows)Location of the RCU log file. RCU_TIMESTAMP_LOG_DIRtrue.
Determines whether or not a directory with the format logdir. RCU log file. Set this variable to true or false. RCU_LOG_NAMErcu. log. Name of the RCU log file.
RCU_LOG_LEVELERRORDetermines the RCU log level. Set this variable to one of SEVERE, ERROR, NOTIFICATION, or TRACE.