25 Provisioning the SOA Domain and Oracle Homes

This chapter describes how you can use the Middleware Provisioning solution offered in Enterprise Manager Cloud Control to provision a SOA Domain or/and an Oracle Home.

Note:

Before provisioning a SOA Domain/ Oracle Home, you must downloaded and apply the patches 20046866 and 20046898.

In particular, this chapter contains the following topics:

Note:

Enterprise Manager does not support creating domain profiles for SOA, OSB domain targets of version 12.2.1.3.0 and above only. If you attempt to create such a profile by clicking Create Button, you would run into errors.

25.1 Getting Started with Provisioning SOA Domain and Oracle Home

This section helps you get started by providing an overview of the steps involved in provisioning WebLogic Domain and Middleware Home using the Fusion Middleware Deployment procedure.

Table 25-1 Getting Started with SOA Provisioning

Step	Description	Reference Links
Step 1	Selecting the Use Case. This chapter covers the use cases for provisioning Oracle SOA Domain and Oracle SOA Home. Select the use case that best matches your requirements.	To learn about first time provisioning of a SOA Domain, see Use Case 1: First Time Provisioning of a SOA Domain. To learn about provisioning from an SOA home based provisioning profile, see Use Case 2: Provisioning from a SOA Oracle Home Based Provisioning Profile. To learn about cloning from an existing SOA domain, see Use Case 3: Cloning from a Provisioning Profile based on an Existing SOA Domain. To learn about provisioning from an existing SOA home, see Use Case 4: Provisioning from an Existing SOA Home. To learn about scaling out a SOA domain, see Use Case 5: Scaling Up an Existing SOA Domain. To learn about cloning a database in WebLogic domain, see Use Case 6 - Cloning a database in WebLogic Domain
Step 2	Meeting Prerequisites to Provision a Middleware Profile Before you run the Fusion Middleware Deployment Procedure, there are a few prerequisites that you must meet.	To learn about the prrequisites for provisioning a SOA domain or home, see Before you Begin Provisioning SOA Domain and Oracle Home.
Step 3	Running the Fusion Middleware Deployment Procedure Run this deployment procedure to successfully provision a Weblogic Domain and/or an Oracle Home.	To learn about provisioning from an Installation Media Profile or an Oracle Home Profile, see Provisioning of a new Fusion Middleware Domain from an Installation Media Based-Profile or an Oracle Home Based-Profile. To learn about provisioning from a WebLogic Domain Profile, see Provisioning a Fusion Middleware Domain from an Existing Oracle Home. To provision from an existing home, see Cloning from an Existing WebLogic Domain Based-Profile. To scale out from a SOA domain, see Scaling Up / Scaling Out Fusion Middleware Domains.

Step

Description

Reference Links

Step 1

Selecting the Use Case.

This chapter covers the use cases for provisioning Oracle SOA Domain and Oracle SOA Home. Select the use case that best matches your requirements.

To learn about first time provisioning of a SOA Domain, see Use Case 1: First Time Provisioning of a SOA Domain.
To learn about provisioning from an SOA home based provisioning profile, see Use Case 2: Provisioning from a SOA Oracle Home Based Provisioning Profile.
To learn about cloning from an existing SOA domain, see Use Case 3: Cloning from a Provisioning Profile based on an Existing SOA Domain.
To learn about provisioning from an existing SOA home, see Use Case 4: Provisioning from an Existing SOA Home.
To learn about scaling out a SOA domain, see Use Case 5: Scaling Up an Existing SOA Domain.
To learn about cloning a database in WebLogic domain, see Use Case 6 - Cloning a database in WebLogic Domain

Step 2

Meeting Prerequisites to Provision a Middleware Profile

Before you run the Fusion Middleware Deployment Procedure, there are a few prerequisites that you must meet.

To learn about the prrequisites for provisioning a SOA domain or home, see Before you Begin Provisioning SOA Domain and Oracle Home.

Step 3

Running the Fusion Middleware Deployment Procedure

Run this deployment procedure to successfully provision a Weblogic Domain and/or an Oracle Home.

To learn about provisioning from an Installation Media Profile or an Oracle Home Profile, see Provisioning of a new Fusion Middleware Domain from an Installation Media Based-Profile or an Oracle Home Based-Profile.

To learn about provisioning from a WebLogic Domain Profile, see Provisioning a Fusion Middleware Domain from an Existing Oracle Home.

To provision from an existing home, see Cloning from an Existing WebLogic Domain Based-Profile.

To scale out from a SOA domain, see Scaling Up / Scaling Out Fusion Middleware Domains.

25.2 Source Environment and Destination Environment after SOA Provisioning

This section describes the middleware components the source environment contains before provisioning, and the components that get provisioned after you run the Provision Fusion Middleware Deployment Procedure. Primarily, two use cases are being described here using a typical SOA topology. First use case is of a fresh provisioning, where you start with an Installation Media based profile or an Oracle Home based profile, and provision the fresh domain and/or Oracle Home. The second use case describes how you can clone an existing SOA domain.

This section contains the following topics:

25.2.1 Source and Destination Environments for a Fresh SOA Provisioning Use Case

For a fresh SOA provisioning use case, before you begin, you must ensure that you have met the following topology requirements:

Oracle HTTP Server has been installed and discovered.
Virtual IP Address 1 and Virtual IP Address 2 have already been reserved.
APPHOST1 and APPHOST2 must be discovered in Cloud Control.
Database should have been discovered.

Note:

Ensure that Oracle HTTP Server, APPHOST1, APPHOST2, and the RAC database are being monitored as managed targets in Cloud Control.

After running the Fusion Middleware Deployment Procedure, all the products that are displayed inside the green box in the destination environment get provisioned.

25.2.2 Source and Destination Environments for SOA Cloning Use Case

For a SOA cloning use case, before you begin, ensure that you have met the following topology requirements:

Oracle HTTP Server has been installed and discovered.
Virtual IP Address 3 and Virtual IP Address 4 have already been reserved.
APPHOST3 and APPHOST4 must be discovered in Cloud Control.
Database must be cloned and discovered.
If source environment is configured with Oracle ID, then OID must be cloned and discovered.

Note:

Ensure that Oracle HTTP Server, APPHOST3, APPHOST4, and the RAC database are being monitored as managed targets in Cloud Control.

For the cloning case WLS_SOA1 and WLS_SOA2 are part of APPHOST1 and APPHOST2 respectively are cloned into APPHOST3 and APPHOST4. The RAC DB is cloned separately.

25.3 Supported Versions of SOA for Provisioning

The versions listed in the following table support SOA provisioning.

Product	Version
Oracle Repository Creation Utility (RCU)	11g
Oracle SOA	12c, 11g

25.4 Before you Begin Provisioning SOA Domain and Oracle Home

You must keep the things to keep in mind before you actually start creating middleware profiles and provisioning from these profiles.

In particular, this section contains the following topics:

25.4.1 Create Middleware Roles and Assign Privileges to them

In a typical data center, the main users of Deployment Procedures are Designers (Lead Administrators) and Operators. Deployment Procedure privileges enable users to perform some design-time activities such as, creating the profiles, granting accesses on the profile, creating profile lock-downs, and run-time activities like running the Deployment Procedure to provision software applications.

For Middleware Provisioning, you will need to create Administrators with the following roles:

Role: EM Super Administrator

Table 25-2 lists the roles based on which you can create administrators for Middleware Provisioning.

Table 25-2 Creating Administrators with the Required Roles

Enterprise Manager Role	Description
EM_PROVISIONING_DESIGNER	Role has privileges for provisioning designer
EM_PROVISIONING_OPERATOR	Role has privileges for provisioning operator

For instructions to create administrators with these roles, see Creating Enterprise Manager User Accounts.

25.4.2 Setting Named Credentials and Privileged Credentials for the Middleware Targets

Oracle recommends that you set the Named Credentials for normal operating system user account (Oracle) and Named Credentials for privileged user accounts (root) to perform any of the provisioning tasks in Enterprise Manager Cloud Control.

For instructions to set the Named Credentials, see Setting Up Credentials.

25.4.3 (Applicable only for a Cloning WebLogic Domain Use Case) Cloning a Database

You must have cloned a database from the source domain at the same time that the domain was being cloned. To clone a database, you must have discovered the source database as a managed target in Enterprise Manager, following which you can create a profile out of the source database, and then provision the profile to complete the cloning process.

25.5 Use Case 1: First Time Provisioning of a SOA Domain

This use case describes how you can perform a first time install of Oracle Fusion Middleware software, and first time provisioning of a WebLogic Domain. This is particularly useful when you do not have an existing domain in your data center, or if you do not wish to clone from a provisioning profile based upon an existing domain. To do so, follow these steps:

Note:

If you use a Windows machine to provision the SOA Domain, after you have discovered the source SOA domain, you must bring the Node Manager down, and only then proceed with the SOA Domain Profile creation.

Log in with Designer privileges (EM_PROVISIONING_DESIGNER role) to create a Installation Media Profile. To do so, follow the steps mentioned in Creating a Provisioning Profile Based on an Installation Media.
(optional) You may choose to create some lock-downs and save the profile as a template after it passes the prerequisite checks. Doing so can be useful when you have to run the same profile multiple times for provisioning middleware products. The added benefit of saving the profile as a template is that you can grant accesses to Operators so they can run the profiles and carry out the Middleware Provisioning.
Before you provision a middleware profile based on an Installation Media profile, meet the prerequisites mentioned in Prerequisites for Provisioning the Installation Media Profile or the Oracle Home Profile.
Log in with Operator Privileges (EM_PROVISIONING_OPERATOR). Select the template from the Deployment Procedure table, and click Launch.

If you have not created a template out of the profile, you can select your profile from the Profiles table on the Middleware Provisioning page, then click Provision.
For provisioning a SOA Domain and Oracle Home from an Installation Media, follow the steps mentioned in Provisioning of a new Fusion Middleware Domain from an Installation Media Based-Profile or an Oracle Home Based-Profile.
If you want to customize the settings in the destination environment, follow the steps mentioned in Customizing the Destination Environment from an Installation Media Based-Profile or an Oracle Home Based-Profile.

25.6 Use Case 2: Provisioning from a SOA Oracle Home Based Provisioning Profile

This use case describes how you can create a Gold Image from an existing Oracle Home (SOA) that has perhaps been patched, and provision this using the Oracle Home profile. This is particularly useful when you need to install Oracle Fusion Middleware software with or without a new WebLogic Domain.

Log in with EM_PROVISIONING_DESIGNER role to create an Oracle Home (SOA) Profile. To do so, follow the steps mentioned in Creating Middleware Provisioning Profiles.
Before you provision from a middleware profile based on an Oracle Home, meet the prerequisites mentioned in Prerequisites for Provisioning the Installation Media Profile or the Oracle Home Profile.
Select the profile from the Profiles table on the Middleware Provisioning page, then click Provision.
For creating a clone of an existing domain's Oracle Home (with binaries and patches) but no domain configuration, follow the steps mentioned in Provisioning of a new Fusion Middleware Domain from an Installation Media Based-Profile or an Oracle Home Based-Profile.
If you want to customize the settings in the destination environment, follow the steps mentioned in Customizing the Destination Environment from an Installation Media Based-Profile or an Oracle Home Based-Profile.

25.7 Use Case 3: Cloning from a Provisioning Profile based on an Existing SOA Domain

This use case describes how you can clone a WebLogic Domain from a provisioning profile based upon an existing WebLogic Domain. This is particularly useful when you need to install Oracle Fusion Middleware software and configure a new WebLogic Domain.

Log in with EM_PROVISIONING_DESIGNER role to create a WebLogic Domain Profile. To do so, follow the steps mentioned in Creating a Provisioning Profile Based on a WebLogic Domain.
Before you provision a middleware profile based on an WebLogic Domain profile, meet the prerequisites mentioned in Prerequisites for Provisioning the WebLogic Domain Profile.
Select the profile from the Profiles table on the Middleware Provisioning page, then click Provision.
For provisioning a SOA Domain and Oracle Home from a profile, follow the steps mentioned in Cloning from an Existing WebLogic Domain Based-Profile.
If you want to customize the settings in the destination environment, follow the steps mentioned in Customizing the Destination Environment from an Existing WeLogic Domain Based-Profile.

25.8 Use Case 4: Provisioning from an Existing SOA Home

If you have an Oracle Home that you want to provision as it is (without having to create a profile), then you can do so by selecting the Oracle Home source target in the Provision Fusion Middleware procedure. For more information, see Provisioning a Fusion Middleware Domain from an Existing Oracle Home.

25.9 Use Case 5: Scaling Up an Existing SOA Domain

To scale up a SOA Domain to include one or more managed servers, run the Scaleup/Scale Out Middleware procedure from the Deployment Procedures table on the Middleware Provisioning page. For more information, see Scaling Up / Scaling Out Fusion Middleware Domains.

25.10 Use Case 6 - Cloning a database in WebLogic Domain

A database can be cloned from the source domain at the same time the domain is being cloned. To clone a database, the source database must be discovered as a managed target in Enterprise Manager. This constitutes of creating a profile of the source database and provisioning the profile.

For an overview of database cloning methods, see Overview of Classic Cloning Methods.

The database cloning for WebLogic Server domain, SOA, Oracle Service Bus, WebCenter can be accomplished in the following ways:

The user can manually clone the database from the source domain to the destination domain before provisioning. The destination database inherits the schema from the original database.
The user can choose to export the database metadata as part of provisioning. This exports the product metadata necessary to clone the domain. The user can clone the application related schema later. Exporting the metadata is supported from SOA release 11g onwards and the schema creation is supported from SOA release 12c onwards.

Note:

While cloning the WebLogic domain, the entire database along with schema must be cloned in the destination domain before provisioning. Else, the cloning fails.

The following tables list the mapping of database cloning process supported with schema for the respective domains and releases.

Table 25-3 Database cloning process with schema supported for SOA domain

Case	SOA 12c	SOA 11g
User exports metadata during profile creation and provides a blank database with no schema during provisioning. The schema is created through Provisioning user interface in release 12c onwards.	Yes	No
User exports metadata during profile creation and provides a blank database with empty schema pre-created during provisioning.	Yes	Yes
User exports metadata during profile creation and provides a cloned database during provisioning.	No	No
Metadata not exported during profile creation, blank database with no schema provided during provisioning.	No	No
Metadata not exported during profile creation, blank database with schema provided during provisioning.	No	No
Metadata not exported during profile creation, cloned database provided during provisioning.	Yes	Yes

Table 25-4 Database cloning process with schema supported for Service Bus domain

Case	Service Bus 12c	Service Bus 11g
User exports metadata during profile creation and provides a blank database with no schema during provisioning. The schema is created through Provisioning user interface in release 12c onwards.	Yes	No
User exports metadata during profile creation and provides a blank database with empty schema pre-created during provisioning.	Yes	Yes
User exports metadata during profile creation and provides a cloned database during provisioning.	No	No
Metadata not exported during profile creation, blank database with no schema provided during provisioning.	No	No
Metadata not exported during profile creation, blank database with schema provided during provisioning.	No	No
Metadata not exported during profile creation, cloned database provided during provisioning.	Yes	Yes

Table 25-5 Database cloning process with schema supported for WebCenter domain

Case	WebCenter 12c	WebCenter 11g
User exports metadata during profile creation and provides a blank database with no schema during provisioning. The schema is created through Provisioning user interface in release 12c onwards.	Yes	No
User exports metadata during profile creation and provides a blank database with empty schema pre-created during provisioning.	Yes	Yes
User exports metadata during profile creation and provides a cloned database during provisioning.	No	No
Metadata not exported during profile creation, blank database with no schema provided during provisioning.	No	No
Metadata not exported during profile creation, blank database with schema provided during provisioning.	No	No
Metadata not exported during profile creation, cloned database provided during provisioning.	Yes	Yes

Note:

In case of WebCenter, it is recommended to clone the database instead of exporting the metadata.

Table 25-6 Database cloning process with schema supported for JRF domain

Case	JRF
User exports metadata during profile creation and provides a blank database with no schema during provisioning. The schema is created through Provisioning user interface in release 12c onwards.	No
User exports metadata during profile creation and provides a blank database with empty schema pre-created during provisioning.	No
User exports metadata during profile creation and provides a cloned database during provisioning.	No
Metadata not exported during profile creation, blank database with no schema provided during provisioning.	No
Metadata not exported during profile creation, blank database with schema provided during provisioning.	No
Metadata not exported during profile creation, cloned database provided during provisioning.	Yes

Note:

Metadata includes MDS (Metadata Services) and OPSS (Oracle Platform Security Services) data.