Objective:

In the previous article Oracle Fusion Middleware products, Tools and Metadata Repository we have learned about the products and the tools used in Fusion Middleware.

In this article we will learn about the Schemas used in Fusion Middleware.

SOA Suite Schemas:

The above components actually get loaded in database when we actually run RCU in SOA suite. we can give any prefix name but the owner name will remain the same.

For e.g. In SOA Infrastructure component, the Schema owner is SOAINFRA but the prefix can be changed in it. In Dependencies, the MDS is Metadata services. SOAINFRA schema is dependent on MDS and

ORASPDM.

Oracle Webcentre Portal Schemas:

If you are an application developer and want to build WebCenter Portal applications, you must run RCU a

second time to create a second version of the Spaces and Services (prefix_WEBCENTRE)on Oracle and

Microsoft SQL Server databases or prefix_WC on IBM DB2 databases) schema. Note that this schema is

separate from the Spaces and Services schema used by Oracle WebCenter Portal: Spaces, so you should

make sure you use a different schema prefix. For information about the WebCenter services that require

the WebCenter schema.

Oracle Webcentre Content Schema:

Oracle WebCenter Content requires that an application schema exists in the database before configuration

of the application. You must run the Repository Creation Utility (RCU) to create application schemas in the

database, which must be up and running before you start RCU. You can create application schemas before

or after you install Oracle WebLogic Server or Oracle WebCenter Content.

Oracle Identity Management Schemas:

Oracle Identity Management schemas are not supported on Microsoft SQL Server or IBM DB2 databases. Table shows the required schemas and dependencies for Oracle Identity Management products on Oracle databases.

Understanding Creation screen:

”Create Repository” create and load component Schemas into a database.

“Drop Repository” removes the component Schemas from a database.

You can see three options under Create Repository i.e

• System Load and product load

• Prepare Scripts for system load

• Perform product load.

Any one of the above three options can be selected depending on the requirement of the User.

we can create new prefix or use the existing prefix for all schemas. for e.g. we have taken “DEV1212” as new Prefix.

Now once the “Oracle AS Repository component” is selected, all the sub components will be automatically selected and the prefix name can be seen along with the Schema Owner.

Once all the sub components are selected click on “Next”.

In the next screen, you can keep the same password or different passwords for all the schemas.

Once the password is set, click on Next.

Master and work repository gives you the flexibility to customize things in the database according to your requirement.

There will be a supervisor who will try to play with the data in the different inbuilt schemas. So work repository will have a different password.

Depending on the work there are two types of work repository i.e. Development and production.

The next screen will show Tablespace.

Each owner will have separate tablespace created.

It will check if the table already exists or not. If the table does not exist then click on OK to create table.

we can store the files and can see all the files stored

It will then start creating the schema.

Log file is made for particular component.

for e.g. msd.log, lau.log etc.

Varun Kapila