26 Provisioning the Oracle WebCenter Domain and Oracle Homes

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

In particular, this chapter contains the following topics:

26.1 Getting Started with Provisioning WebCenter 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 26-1 Getting Started with WebCenter Provisioning

Step Description Reference Links

Step 1

Selecting the Use Case.

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

  • To learn about first time provisioning of a WebCenter Domain, see Section 26.6.

  • To learn about provisioning from a WebCenter home based provisioning profile, see Section 26.7.

  • To learn about cloning from an existing WebCenter domain, see Section 26.8.

  • To learn about provisioning from an existing WebCenter home, see Section 26.9.

  • To learn about scaling out a WebCenter domain, see Section 26.10.

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 WebCenter domain or home, see Section 26.5.

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 a WebCenter domain, see Section 29.

26.2 About WebCenter Topologies Supported in Enterprise Manager

Oracle WebCenter Portal provisioning is now supported from Enterprise Manager Cloud Control.

Primarily, the following use cases are supported:

Table 26-2 WebCenter Provisioning Use cases

Task Description

1. WebCenter Provisioning - Fresh Install

This use case is useful if you want to provision a fresh vanilla WebCenter (Oracle WebCenter Portal + Oracle WebCenter Content) environment.

2. WebCenter Provisioning - Cloning (like-to-like)

This use case is useful if you already have installed WebCenter environment (Oracle WebCenter Portal + Oracle WebCenter Content), and a later point want to copy/clone from that environment.

The following topologies are supported for provisioning WebCenter:

Table 26-3 Supported Topologies for WebCenter


 Topologies Components External Components

1

Development Topology

WCP, WCC, OHS, DB, embedded LDAP, SAML/SSO

DB, OHS

2

Production Topology (HA)

WCP, WCC, DB, OHS, LBR, SES, LDAP w/SSO

DB, OHS, OTD, SES, LDAP

Development Topology Details

Development topology supports only a single node environment which is consistent with the following topology definition.

Surrounding text describes dev_wc_topology.gif.

Production Topology Details

Production topology supports multi-node cluster environment, which means that you can select however many nodes per cluster. After provisioning, you can even reconfigure the node count for clusters.

Surrounding text describes prod_wc_topology.gif.

26.3 Source Environment and Destination Environment after WebCenter Provisioning

This section describes what the source environment might contains, and what gets provisioned after you run the Fusion Middleware Deployment Procedure. You can see two topologies being displayed. First topology is a fresh provisioning use case where you start with an Installation Media based profile or an Oracle Home based profile, and provision that. Second is a cloning topology, where you are creating a copy of an existing domain.

This section contains the following topics:

26.3.1 Source and Destination Environments for a Fresh WebCenter Provisioning Use Case

Before you begin, ensure that you have met the following topology requirements:

  • Oracle HTTP Servers must have been installed and discovered.

  • 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.
Surrounding text describes webcenter_freshinstall.gif.

26.3.2 Source and Destination Environments for WebCenter Cloning Use Case

Before you begin, ensure that you have met the following topology requirements:

  • Oracle HTTP Servers have been installed and discovered.

  • 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.
Surrounding text describes webcenter_clone.gif.

26.4 Supported Versions of WebCenter for Provisioning

The versions listed in the following table support WebCenter provisioning.

Product Version
Oracle Repository Creation Utility (RCU) 11g
Oracle WebCenter Portal 11g
Oracle WebCenter Content 11g

26.5 Before you Begin Provisioning WebCenter 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.

Note:

To provision a WebCenter Domain using LDAP in the Production mode, ensure that a Weblogic user is present with Administrator group privileges in the LDAP.

Ensure that you have identical topology of servers on all nodes in a single cluster. For example, in case of a two node cluster, the same set of servers must be available on node 1 and node 2 of the cluster.

In particular, this section contains the following topics:

26.5.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 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 26-4 lists the roles based on which you can create administrators for Middleware Provisioning.

Table 26-4 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.

26.5.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 Section 2.3.

26.5.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.

26.6 Use Case 1: First Time Provisioning of a WebCenter Portal with Lock-downs

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:

  1. 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.

  2. Before you provision a middleware profile based on an Installation Media profile, meet the prerequisites mentioned in Section 23.4.1.

  3. (optional) While provisioning the profile, you can create a template from the inputs that has already been entered in this deployment procedure. For this, you need to use the lockdown feature offered in Enterprise Manager, which enables you to lock select inputs thereby restricting other users to the change these values in future. For example, you can lock the values entered in the Middleware, Database, Identity and Security, and WebTier sections. By saving the Deployment Procedure with these lockdowns, other administrators can leverage the defaulted inputted values and submit the procedure with very few inputs required from them.

  4. 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.

  5. For provisioning a WebCenter Domain and Oracle Home from an Installation Media, follow the steps mentioned in Section 23.6.

  6. If you want to customize the settings in the destination environment, follow the steps mentioned in Section 23.6.1.

26.7 Use Case 2: Provisioning a WebCenter Home

This use case describes how you can create a Gold Image from an existing Oracle Home (WebCenter) 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.

  1. Log in with Designer privileges (EM_PROVISIONING_DESIGNER role) to create an Oracle Home (WebCenter) Profile. To do so, follow the steps mentioned in Section 23.5.2.

  2. Before you provision a middleware profile based on an Oracle Home, meet the prerequisites mentioned in Section 23.4.1.

  3. Log in with Designer/Operator privileges, select your profile from the Profiles table on the Middleware Provisioning page, then click Provision.

  4. 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.

  5. If you want to customize the settings in the destination environment, follow the steps mentioned in Section 23.6.1.

26.8 Use Case 3: Cloning an Existing WebCenter Portal Environment

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.

  1. 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.

  2. Before you provision a middleware profile based on an WebLogic Domain profile, meet the prerequisites mentioned in Section 23.4.2.

  3. Log in with Designer/Operator Privileges, select your profile from the Profiles table on the Middleware Provisioning page, then click Provision.

  4. For provisioning a WebCenter Domain and Oracle Home from a profile, follow the steps mentioned in Section 23.8.

  5. If you want to customize the settings in the destination environment, follow the steps mentioned in Section 23.8.1.

26.9 Use Case 4: Provisioning from an Existing WebCenter 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 select the Oracle Home source target in the Provision Fusion Middleware procedure. For more information, see Section 23.7.

26.10 Use Case 5: Scaling Up an Existing WebCenter Domain

To scale up a WebCenter 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.