|Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite
11g Release 1 (11.1.1)
Part Number E12036-08
|PDF · Mobi · ePub|
This chapter describes procedures for preparing your database for an Oracle SOA enterprise deployment. The procedures include initial setup of the database, loading the metadata repository, and backing up the database.
This chapter includes the following topics:
For the SOA enterprise topology, the database contains the Oracle Fusion Middleware Repository, which is a collection of schemas used by various Oracle Fusion Middleware components, such as the SOA components, BAM, and UMS. This database is separate from the Identity Management database, which is used in Identity Management Enterprise Deployment by components such as Oracle Internet Directory, DIP, and so on.
You must install the Oracle Fusion Middleware Repository before you can configure the Oracle Fusion Middleware components. You install the Oracle Fusion Middleware metadata repository into an existing database using the Repository Creation Utility (RCU), which is available from the RCU DVD or from the location listed in Table 2-2. For the enterprise topology, a Real Application Clusters (Oracle RAC) database is highly recommended.
When you configure the SOA components, the configuration wizard will prompt you to enter the information for connecting to the database that contains the metadata repository.
Before loading the metadata repository into your database, check that the database meets the requirements described in these subsections:
For 11g Release 1 (11.1) for Linux, refer to the Oracle Clusterware Installation Guide for Linux.
Oracle Real Application Clusters
For 11g Release 1 (11.1) for Linux, refer to the Oracle Real Application Clusters Installation Guide for Linux and UNIX. For 10g Release 2 (10.2) for Linux, refer to Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide.
ASM gets installed for the node as a whole. It is recommended that you install it in a separate Oracle Home from the Database Oracle Home. This option comes in at runInstaller. In the Select Configuration page, select the Configure Automatic Storage Management option to create a separate ASM home.
Oracle SOA Suite requires the presence of a supported database and schemas:
To check if your database is certified or to see all certified databases, refer to the "Oracle Fusion Middleware 11g Release 1 (11.1.1.x)" product area on the Oracle Fusion Middleware Supported System Configurations page:
To check the release of your database query the
SQL> SELECT VERSION FROM SYS.PRODUCT_COMPONENT_VERSION WHERE PRODUCT LIKE 'Oracle%';
Oracle SOA Suite requires the database be used to store its metadata (either 10g or 11g) supports the AL32UTF8 character set. Check the database documentation for information on choosing a character set for the database.
Ensure that the following initialization parameter is set to the required minimum value. It is checked by Repository Creation Assistant.
Table 5-1 Required Initialization Parameters
|Configuration||Parameter||Required Value||Parameter Class|
300 or greater
100 or greater
SOA and BAM
400 or greater
SOA and OSB
800 or greater
To check the value of the initialization parameter using SQL*Plus, you can use the SHOW PARAMETER command.
As the SYS user, issue the SHOW PARAMETER command as follows:
SQL> SHOW PARAMETER processes;
Set the initialization parameter using the following command:
SQL> ALTER SYSTEM SET processes=300 SCOPE=SPFILE;
Restart the database.
The method that you use to change a parameter's value depends on whether the parameter is static or dynamic, and on whether your database uses a parameter file or a server parameter file. See the Oracle Database Administrator's Guide for details on parameter files, server parameter files, and how to change parameter values.
Oracle recommends using the Oracle Enterprise Manager Cluster Managed Services Page to create database services that client applications will use to connect to the database. For complete instructions on creating database services, see the chapter on workload management in the Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide.
You can also use SQL*Plus to configure this using the following instructions:
SQL> EXECUTE DBMS_SERVICE.CREATE_SERVICE (SERVICE_NAME => 'soaedg.mycompany.com', NETWORK_NAME => 'soaedg.mycompany.com', );
Add the service to the database and assign it to the instances using
prompt> srvctl add service -d soadb -s soaedg.mycompany.com -r soadb1,soadb2
Start the service using
prompt> srvctl start service -d soadb -s soaedg.mycompany.com
For more information about the SRVCTL command, see the Oracle Real Application Clusters Administration and Deployment Guide.
Oracle recommends that a specific database service be used for a product suite, even when they share the same database. It is also recommended that the database service used is different than the default database service. In this case, the database is soadb.mycompany.com and the default service is one with the same name. The SOA install is configured to use the service soaedg.mycompany.com. It is recommended that a service named bamedg.mycompany.com is used for BAM.
The Repository Creation Utility (RCU) is available from the RCU DVD. The RCU used to seed the database must match the patch set level of the Oracle SOA Suite installation. This means that if you install Oracle SOA Suite 11gR1 PS5 (22.214.171.124) in this enterprise deployment, you must use RCU 11gR1 PS5 (126.96.36.199).
To load the Oracle Fusion Middleware Repository into a database:
Start RCU from the bin directory:
In the Welcome screen, click Next.
In the Create Repository screen, select Create to load component schemas into a database. Click Next.
In the Database Connection Details screen, enter the correct information for your database:
Database Type: select Oracle Database.
Host Name: Enter the name of the node that is running the database. For the Oracle RAC database, specify the VIP name or one of the node names as the host name:
Port: Enter the port number for the database: 1521.
Service Name: Enter the service name of the database: soaedg.mycompany.com
Password: Enter the password for the SYS user.
If you get this warning message: The database you are connecting is with non-UTF8 charset, if you are going to use this database for multilingual support, you may have data loss. If you are not using for multilingual support you can continue, otherwise we strongly recommend using UTF-8 database.
Click Ignore or Stop.
In the Select Components screen, do the following:
Select Create a New Prefix, and enter a prefix to use for the database schemas. Example:
PROD. Prefixes are used to create logical groupings of multiple repositories in a database. For more information, see Oracle Fusion Middleware Repository Creation Utility User's Guide.
Note the name of the schema because you will need to enter it during the procedure in Section 5.5.
Select the following:
AS Common Schemas:
- Metadata Services
- SOA and BPM Infrastructure
- User Messaging Service
- Business Activity Monitoring
Business Activity Monitoring (BAM) is only required for BAM installations.
Oracle Service Bus required objects are created as part of the SOA_INFRA schema.
In the Schema Passwords screen, select Use main schema passwords for auxiliary schemas, and click Next. In the subsequent screen refresh, enter the schema passwords for all components.
In the Map Tablespaces screen, choose the tablespaces for the selected components, and click Next.
A confirmation dialog is displayed stating that any tablespace that does not already exist in the selected schema will be created. Click OK to acknowledge this message.
In the Summary screen, click Create.
In the Completion Summary screen, click Close.
Verify that the required schemas are created by connecting to the database with the new user added:
Query the description of the CUBE_INSTANCE table for a simple verification. A table similar to the following should display:
SQL> desc CUBE_INSTANCE; Name Null? Type --------------------------------- ---- -------------------------- CIKEY NOT NULL NUMBER(38) CREATION_DATE NOT NULL TIMESTAMP(6) ...
About Oracle WSM policies and the OWSM MDS schemas
If Oracle WSM is part of your SOA enterprise deployment, Oracle recommends using the identity management database to store the Oracle WSM policies. Use the IM database connection information for the OWSM MDS schemas instead of the information used for the rest of SOA schemas. To create the required schemas in the database, repeat the steps above (run RCU again) using the IM database information, but select only AS Common Schemas: Metadata Services in the Select Components screen (step 7). See Chapter 15, "Integrating an Enterprise Deployment with Oracle Identity Management." for information on using the identity management database to store the Oracle WSM policies.
You need the appropriate database privileges to allow the Oracle WebLogic Server transaction manager to query for transaction state information and issue the appropriate commands, such as commit and rollback, during recovery of in-flight transactions after a WebLogic Server container crash.
These privileges should be granted to the owner of the soainfra schema, as determined by the RCU operations.
To configure the SOA schemas for transactional recovery privileges:
Log on to sqlplus as a user with sysdba privileges. For example:
sqlplus "/ as sysdba"
Enter the following commands:
SQL> Grant select on sys.dba_pending_transactions to soa_schema_prefix_soainfra; Grant succeeded. SQL> Grant force any transaction to soa_schema_prefix_soainfra; Grant succeeded. SQL>
After you have loaded the metadata repository into your database, make a backup before installing the software for your enterprise deployment.Backing up the database is for the explicit purpose of quick recovery from any issue that may occur in the further steps. You can choose to use your backup strategy for the database for this purpose or simply make a backup using operating system tools or RMAN for this purpose. Oracle recommends using Oracle Recovery Manager for the database, particularly if the database was created using Oracle ASM. If possible, you can also perform a cold backup using operating system tools such as tar.