Skip Headers
Oracle® Enterprise Manager Lifecycle Management Administrator's Guide
12c Release 4 (12.1.0.4)

E27046-25
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

18 Overview of Middleware Provisioning

Provisioning involves repeatable, reliable, automated, unattended, and scheduled mass-deployment of software, applications, or servers across different platforms, environments, and locations.

Middleware Provisioning involves remotely installing a variety of middleware artifacts using automated deployment procedures. A deployment procedure is a pre-defined sequence of steps that is meant to perform a set of operations on one or most hosts monitored by Cloud Control.

In particular, this chapter covers the following:

18.1 Introduction to Middleware Provisioning

Provisioning is an important solution offered as a part of Lifecycle Management that enables you to provision middleware artifacts like WebLogic Server, Java EE Applications, Coherence Nodes and Clusters, SOA Artifacts and Composites, Oracle Service Bus Resources, Oracle BPEL Processes, and Oracle Application Server

The following figure shows the Middleware Provisioning solutions offered in Cloud Control:

Middleware Provisioning Solution

To manage these assets effectively in Cloud Control there a centralised middleware provisioning console with automated common provisioning operations. To access this page, from Enterprise menu, select Provisioning and Patching, then click Middleware Provisioning.

Middleware Home Page

The Middleware Provisioning page can broadly be categorized into the following sections:

Profiles

The profiles section lists all the provisioning profiles that you have created. You can:

  • Click the profile to view the profile details.

  • Filter the profile based on what you want to display in the Profiles table. To do so, from View menu, select Show Profiles, then click the option that you want to display. For example, if you click All, then all the profiles are displayed.

  • To clone a WebLogic Domain or an Oracle Home, select a profile and click Provision.

  • To create a new profile, select an option from the Create menu.

  • To delete an existing profile, select the profile name, and click Delete.

Deployment Procedures

The deployment procedures section lists all the Oracle-provided deployment procedures. Select a deployment procedure from the list, and perform any of the following action on them:

  • To configure and run a deployment procedure, select the procedure, and click Launch.

  • To create a copy of an Oracle-supplied deployment procedure, click Create Like.

  • To delete a User-owned deployment procedure, select the procedure, and click Delete.

  • To edit a deployment procedure, select the procedure and click Edit.

    Note: You can not edit Oracle-supplied procedures. If you want to edit a procedure, you must first clone an Oracle-supplied procedure using the Create Like option. You can now edit the newly cloned procedure that you own. To do so, click Edit.

  • To add new privileges for a procedure, click Edit Permissions.

18.2 Oracle Fusion Middleware Provisioning Terminology

The definitions of terms listed in this section are useful in helping to understand the Middleware concepts presented in this part:

  • WebLogic Server Domain: A WebLogic Server domain is a logically related group of Java components. A domain includes a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional WebLogic Server instances called managed servers.

  • Administration Server: The Administration Server operates as the central control entity for the configuration of the entire domain. It maintains the domain's configuration documents and distributes changes in the configuration documents to managed servers. The Administration Server is the central location from where you can monitor all the resources in a domain. Each WebLogic Server domain must have one server instance that acts as the Administration Server.

  • Managed Server: Managed servers host business applications, application components, Web services, and their associated resources. To optimize performance, managed servers maintain a read-only copy of the domain's configuration and security document. When a managed server starts up, it connects to the domain's Administration Server to download the configuration and security data. If the Administration Server is unavailable, the managed server fails to start unless Managed Server Independence (MSI) mode is enabled, and configuration from the last boot is available.

  • Node Manager: Node Manager is a Java utility that runs as separate process from Oracle WebLogic Server and enables you to perform common operations for a Managed Server, regardless of its location with respect to its Administration Server. While use of Node Manager is optional, it provides valuable benefits if your WebLogic Server environment hosts applications with high-availability requirements.

    In addition to this, if you run Node Manager on a machine that hosts Managed Servers, you can start and stop the Managed Servers remotely using the Administration Console or from the command line. Node Manager enables you to restart the managed servers without having to physically log into to the host, and facilitates automatic restart of the managed servers after an unexpected failure.

  • WebLogic Server Home: A WebLogic Server home contains installed files necessary to host a WebLogic Server. The WebLogic Server home directory is a peer of Oracle home directories and resides within the directory structure of the Middleware home.

  • Middleware Home: A Middleware home consists of the Oracle WebLogic Server home, and, optionally, one or more Oracle homes. A Middleware home can reside on a local file system or on a remote shared disk that is accessible through NFS.

  • Oracle Home: An Oracle home contains installed files necessary to host a specific product. For example, the SOA Oracle home contains a directory that contains binary and library files for Oracle SOA Suite. An Oracle home resides within the directory structure of the Middleware home.

  • Cloning: The process of creating a copy of the WebLogic Domain and the Oracle home binaries present within the domain is referred to as cloning. Typically, cloning is performed at the WebLogic Domain-level. Fusion Middleware Domain cloning can be performed from an existing target or using provisioning profiles.

  • Provisioning Profiles: A profile is a snapshot of a live WebLogic Domain or Oracle Home, or it can simply contain a set of installation media archives pertaining to the product suite. A profile can be created from the UI or using Enterprise Manager Command Line Interface.

  • Gold Image: The gold image is a single image that includes the binaries for an Oracle home.

  • Scaling Out: To address growing business demands, modern data centers must augment and relocate resources quickly. Using Oracle Enterprise Manager, administrators can rapidly scale out an Oracle WebLogic Domain or Cluster by adding new managed servers and installing the binaries on new hosts. This in turn accommodates an increase in application load.

  • Scale Up:

18.3 Supported Use Cases and Targets Provisioned Using Middleware Provisioning Procedures

This section lists all the supported use cases in the middleware space and the corresponding targets that get provisioned.

In particular, this section covers the following:

18.3.1 Provisioning Middleware Domains and Oracle Homes

This table covers the use cases for deploying SOA Domain, Oracle Service Bus (OSB) Domain, and WebLogic Domain and Oracle homes.

Table 18-1 Provisioning Middleware Domains and Oracle Homes

Deployment Procedure Use Case Targets Provisioned Link

Provision Middleware

  • SOA Installation Media

  • SOA Gold Image

  • Existing SOA Middleware Home

SOA Domain 11.1.1.6.0 or 11.1.1.7.0

Section 19.3.1

 
  • OSB Installation Media

  • OSB Gold Image

  • Existing OSB Middleware Home

  • OSB Domain Cloning

OSB Domain 11.1.1.6.0 or 11.1.1.7.0

Section 19.3.2

 
  • WebLogic Server Installation Media

  • WebLogic Server Gold Image Profile

  • Existing WebLogic Server Middleware Home Profile

  • WebLogic Server Domain Cloning

WLS 10.3.4.0, 10.3.5.0, 10.3.6.0,12.1.1.0, and 12.1.2.0 .0.

Section 19.3.3


18.3.2 Scaling SOA, Oracle Service Bus, and WebLogic Server Domains

This table covers the use cases for scaling an existing SOA Domain, Oracle Service Bus (OSB) Domain, and WebLogic Domain:

Table 18-2 Scaling SOA, OSB, WLS Domains

Deployment Procedure Use Case Targets Provisioned Link

Scaling up/Scale out Middleware

Scaling SOA Domain

SOA Domain 11.1.1.6.0 or 11.1.1.7.0

Section 20.4

 

Scaling OSB Domain

OSB Domain 11.1.1.6.0 or 11.1.1.7.0

Section 20.4

 

Scaling WLS Domain

WLS domain 10.3.4.0, 10.3.5.0, 10.3.6.0,12.1.1.0, and 12.1.2.0 .0.

Section 20.4


18.3.3 Deploying / Redeploying / Undeploying Java EE Applications

This table covers the use cases for deploying, undeploying, and redeploying Java EE Application.

Table 18-3 Deploying, Undeploying, or Redeploying Java EE Applications

Deployment Procedure Use Case Targets Provisioned Link

Deploy/Undeploy Java EE Applications

Deploying a Java EE Application

Deploy Java EE Applications to and from WebLogic versions 10.3.1 and later, including 12.1.1, and 12.1.2.

Section 21.6.1

 

Undeploying a Java EE Application

Undeploy Java EE Applications to and from WebLogic versions 10.3.1 and later, including 12.1.1, and 12.1.2.

Section 21.6.3

 

Redeploying a Java EE Application

Redeploy Java EE Applications to and from WebLogic versions 10.3.1 and later, including 12.1.1, and 12.1.2.

Section 21.6.2


18.3.4 Provisioning Coherence Nodes and Clusters

This table covers the use case to successfully deploy a Coherence node.

Table 18-4 Provisioning Coherence Nodes and Clusters

Deployment Procedure Use Case Targets Provisioned Link

Coherence Node Provisioning

Deploying Coherence Nodes and Clusters

Oracle Coherence 3.5, 3.6, and 3.7.

Oracle Coherence 12.1.2 Standalone Version.

Section 22.3.3


18.3.5 Provisioning SOA Artifacts

This table covers the use case to successfully deploy the various SOA artifacts:

Table 18-5 Provisioning SOA Artifacts

Deployment Procedure Use Case Targets Provisioned Link

SOA Artifacts Provisioning

Provisioning SOA Artifacts from a Reference Installation

Oracle SOA Suite 11gR1 (11.1.1.2.0 to 11.1.1.7.0):

  • SOA Composites

  • Oracle WebLogic Server Policies

  • Assertion Templates

  • JPS Policy and Credential Stores

  • Human Workflow

  • Oracle B2B

Section 23.4.1

 

Provisioning SOA Artifacts from a Gold Image

Oracle SOA Suite 11gR1 (11.1.1.2.0 to 11.1.1.7.0):

  • SOA Composites

  • Oracle WebLogic Server Policies

  • Assertion Templates

  • JPS Policy and Credential Stores

  • Human Workflow

  • Oracle B2B

Section 23.4.2

Deploy SOA Composites

Provisioning SOA Composites

Oracle SOA Suite 11gR1 (11.1.1.2.0 to 11.1.1.7.0)

SOA Composites

Section 23.5


18.3.6 Provisioning Oracle Service Bus Resources

This table covers the use case to successfully deploy OSB resources:

Table 18-6 Provisioning Oracle Service Bus Resources

Deployment Procedure Use Case Targets Provisioned Link

Oracle Service Bus Resource Provisioning

Provision OSB resources from OSB Domain

Oracle Service Bus 2.6.0 - 2.6.1, 3.0.0, 10.3.0.0 - 10.3.1.0, 11.1.1.3.0 - 11.1.1.7.0, 12.1.3.0.0

Section 24.4

 

Provision OSB resources from Software Library

Oracle Service Bus 2.6.0 - 2.6.1, 3.0.0, 10.3.0.0 - 10.3.1.0, 11.1.1.3.0 - 11.1.1.7.0, 12.1.3.0.0

Section 24.5


18.3.7 Provisioning Oracle BPEL Processes

This table covers the use case to successfully deploy BPEL resources:

Table 18-7 Provisioning Oracle BPEL Processes

Deployment Procedure Use Case Targets Provisioned Link

BPEL Process Provisioning

Provision BPEL Processes

BPEL processes for Oracle BPEL Process Manager 10.1.3.1, 10.1.3.3, and 10.1.3.4.

Section 25.4


18.3.8 Provisioning Oracle Application Server

This table covers the use case to successfully deploy Oracle Application Server and and the various targets that can be provisioned.

Table 18-8 Provisioning Oracle Application Server

Deployment Procedure Use Case Targets Provisioned Link

Application Server Deployment 10.1.3.

Provision Application Server 10.1.3.x

Oracle Application Server 10g Release 3 (10.1.3.4 and 10.1.3.5)

Core components deployed:

  • Application tier

  • Web tier

Section 26.3

Application Server Deployment 10.1.3.xSOA3

Provision Application Server 10.1.3.x with SOA Suite 10.1.3.x

Deploys Oracle SOA Suite 10g (10.1.3.x) with the application tier and Web tier of Oracle Application Server 10g Release 3 (10.1.3.4 and 10.1.3.5)

Section 26.4