This chapter describes how you can use the Middleware Provisioning solution offered in Enterprise Manager Cloud Control to provision an OSB Domain or/and an Oracle Home.
Important:
Before provisioning an OSB Domain/Oracle Home, you must downloaded and apply the patch 20046866.In particular, this chapter contains the following topics:
Getting Started with Provisioning OSB Domain and Oracle Home
Use Case 2: Provisioning from a OSB Home Based Provisioning Profile
Use Case 3: Cloning from a Provisioning Profile based on an Existing OSB Domain
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 OSB Provisioning
| Step | Description | Reference Links |
|---|---|---|
|
Step 1 |
Selecting the Use Case. This chapter covers the use cases for provisioning an OSB Domain and OSB Home. Select the use case that best matches your requirements. |
|
|
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 an OSB domain or home, see Section 25.3. |
|
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 Section 23.6. To learn about provisioning from a WebLogic Domain Profile, see Section 23.7. To provision from an existing home, see Section 23.8. To scale out from an OSB domain, see Section 29. |
The versions listed in the following table support OSB provisioning.
| Product | Version |
|---|---|
| Oracle Repository Creation Utility (RCU) | 11g |
| Oracle OSB | 11g |
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:
Setting Named Credentials and Privileged Credentials for the Middleware Targets
(Applicable only for a Cloning WebLogic Domain Use Case) Cloning a Database
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 like 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 Section 2.4.
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 Section 2.3.
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.
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:
Log in with Designer privileges (EM_PROVISIONING_DESIGNER role) to create a Installation Media Profile. To do so, follow the steps mentioned in Section 23.5.1.
(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 Section 23.4.1.
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 OSB Domain and Oracle Home from an Installation Media, follow the steps mentioned in Section 23.6.
If you want to customize the settings in the destination environment, follow the steps mentioned in Section 23.6.1.
This use case describes how you can create a Gold Image from an existing Oracle Home (OSB) 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 Designer privileges (EM_PROVISIONING_DESIGNER role) to create an Oracle Home (OSB) Profile. To do so, follow the steps mentioned in Section 23.5.2.
Before you provision a middleware profile based on an Oracle Home, meet the prerequisites mentioned in Section 23.4.1.
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 Section 23.6.
If you want to customize the settings in the destination environment, follow the steps mentioned in Section 23.6.1.
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 Designer privileges (EM_PROVISIONING_DESIGNER role) to create a WebLogic Domain Profile. To do so, follow the steps mentioned in Section 23.5.3.
Before you provision a middleware profile based on an WebLogic Domain profile, meet the prerequisites mentioned in Section 23.4.2.
Select the profile from the Profiles table on the Middleware Provisioning page, then click Provision.
For provisioning a OSB Domain and Oracle Home from a profile, follow the steps mentioned in Section 23.8.
If you want to customize the settings in the destination environment, follow the steps mentioned in Section 23.8.1.
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 select the Oracle Home source target in the Provision Fusion Middleware procedure. For more information, see Section 23.7.
To scale up a OSB 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 Section 29.