Skip Headers
Oracle® Enterprise Manager Cloud Administration Guide
12c Release 4 (12.1.0.4)

E28814-12
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 Setting Up an MWaaS Cloud

This chapter covers the initial configuration required to set up and enable a Middleware as a Service Cloud. It contains the following sections:

Note:

Click here to view a visual demonstration on how to use Middleware as a Service to rapidly deploy J2EE Applications.

18.1 Getting Started with MWaaS - Physical Flow

This section helps you get started by providing an overview of the steps involved in setting up the Middleware as a Service (MWaaS) to provision a service instance on one or more physical hosts. Before you set up MWaaS, you must download and deploy the required plug-ins. For more details, see Section 3.2, "Deploying the Required Plug-ins".

Table 18-1 Getting Started with MWaaS (Physical Flow)

Step Task Role

1

Define roles for administrators and self service users. See Section 3.3, "Defining Roles and Assigning Users".

Super Administrator

2

Install the Management Agent on unmanaged hosts so that they can be monitored by Enterprise Manager. Section 11.2, "Adding Hosts".

Super Administrator

3

Optionally, you may need to configure Privilege Delegation Settings on your managed hosts. Section 3.5, "Configuring Privilege Delegation Settings".

Super Administrator

4

Provision a Middleware Home. See Section 18.1.2, "Provisioning a Middleware Home".

Self Service Administrator

5

Load Middleware Provisioning Profiles into the Software Library. See Section 18.1.1, "Creating Provisioning Profiles".

Self Service Administrator

6

Create a WebLogic Domain Provisioning Profile (see Section 18.1.1.1, "Creating a WebLogic Domain Provisioning Profile") or optionally create a Configured Deployment Procedure (see Section 18.1.3, "Configuring and Saving the Deployment Procedure".)

Note: Oracle recommends that you use the WebLogic Domain Provisioning Profile to set up MWaaS.

Self Service Administrator


Figure 18-1 shows the sequence of steps required to enable MWaaS (physical hosts).

Figure 18-1 Getting Started with MWaaS (Physical Flow)

MwaaS Setup

18.1.1 Creating Provisioning Profiles

Provisioning profiles can be used to standardize deployments and help reduce errors when deployment procedures are configured. These provisioning profiles are used by operators for mass deployment. You can:

18.1.1.1 Creating a WebLogic Domain Provisioning Profile

A WebLogic Domain Provisioning Profile consists of the Middleware Home, binaries, and the domain configuration. You can create a profile, save it in the Software Library, and then use the saved profile as the source for creating new WebLogic domains. This will ensure that future WebLogic installations follow a standard, consistent configuration.

Before you create a WebLogic Domain Provisioning profile, ensure that the following prerequisites are met:

  • The Management Agent must be running on the Administration Server.

  • You must have the host credentials for the Administration Server running on the source machine.

  • The WebLogic Domain for which the profile is being created must be a monitored target in Enterprise Manager.

  • The disk space required to create a profile is calculated as follows:

    Disk Space = Middleware Home Size + WebLogic Domain Size + Space for Temporary Scripts

  • If Log Viewing support is required on the service instance, the JRF binaries must be installed in the Middleware Home and configured in the domain.

  • If Fusion Middleware console access support is required, you must configure the WebLogic domain through Fusion Middleware Control. This ensures that the Fusion Middleware Control link is displayed in the Service Instance Home page in the Middleware Self Service Portal. See Section 20.3, "Viewing the Middleware Service Home Page".

  • The WebLogic Domain that is used to create a profile must meet the following requirements:

    • The machine associated with the WebLogic Server must not be of Unix type.

    • The Administration Server must not be associated with a machine.

    • The Administration Server must be present on the same host as one of the Managed servers.

  • The maximum Java heap size of all the servers must have an appropriate -Xmx setting in multiples of 256. For example, Xms1024m -Xmx1536m -XX:PermSize=512m -XX:MaxPermSize=1536m and so on. You must define the -Xmx server setting to ensure that the MWaaS memory metric and quota checking feature works properly. The value of the memory metric for a MWaaS service is the sum of the maximum heap available for all servers in the service.

For detailed instructions on how to create a WebLogic Domain Provisioning profile, see the Enterprise Manager Lifecycle Management Guide.

18.1.1.2 Using the Out-of-the-box Provisioning Profile

When you install Enterprise Manager, a self update archive with a sample out-of-the-box provisioning profile is available. You can download the profiles from the Self Update console.

To use the out-of-the-box provisioning profile, follow these steps:

  1. Log in to Enterprise Manager as a user with the EM_CLOUD_ADMINISTRATOR role.

  2. From the Setup menu, select Extensibility and then select Self Update. The Self Update Console with the list of entity types that can be downloaded appears.

    Figure 18-2 Self Update Console

    Self Update Console
  3. Select the Middleware Profiles and Gold Images folder and click Open. The Middleware Profiles and Gold Images Updates page appears. You will see "1" as an available update.

  4. Select the update and click Download. The Schedule Download dialog appears.

  5. Specify if the update is to be downloaded immediately or at a later date.

  6. Click Select. An Enterprise Manager job is created to download the update to the Software Library. Enterprise Manager starts downloading the archive from the Oracle Enterprise Manager store. Wait for the download to complete. (When in offline mode the system starts reading from the specified location.) When the download is complete, the status indicates that the update has been downloaded.

    Figure 18-3 Middleware Profiles and Gold Images Updates: Downloaded

    Middleware Profiles and Gold Images Updates: Downloaded
  7. Click Apply. A job is submitted to apply the update. The downloaded update is applied and appears on the Middleware Profiles and Gold Images Updates page.

    Figure 18-4 Middleware Profiles and Gold Images Updates: Applied

    Middleware Profiles and Gold Images Updates: Applied

When the updates have been applied, the profile is copied under the Oracle Supplied Fusion Middleware Provisioning Profiles/10.3.6.0/linux64 directory in the Software Library. These profiles can then be used to create services templates that can be used provision one or more service instances. See Section 19.1, "Setting Up the Middleware Cloud Self Service Portal" for details on creating service templates.

Note:

  • The out-of-the-box profile has been certified to work with WebLogic Server 10.3.6.0.

  • As the sample provisioning profile does not contain the Oracle Middleware Home Gold Image component, you must ensure that the Middleware Homes (WebLogic 10.3.6.0) and JRF binaries (if required) of the same version have been created on the selected destination host(s) when they are provisioned.

18.1.2 Provisioning a Middleware Home

A Middleware Home consists of the WebLogic Server Home and optionally, one or more Oracle Homes. The Middleware Home must be created on the hosts that are part of the PaaS Infrastructure Zone. See Section 11.3, "Creating a PaaS Infrastructure Zone" for details. If the Middleware Home has not been created on a host, that host cannot participate in the Middleware Pool.

If you provisioning the Middleware Home on multiple hosts, you must specify a shared mount directory that is accessible by all destination hosts.

Note:

You can also manually install the Middleware Home and use the Discover Promote Oracle Home Target job to discover it in Enterprise Manager.

To create a Middleware Home, you must run the Provision from Oracle Middleware Home Gold Image deployment procedure.

Prerequisites

Before running this deployment procedure, you must meet the following prerequisites:

  • The user must have Write permissions on:

    • The Working Directory on all destination hosts.

    • The Middleware Home on all destination hosts.

  • An Oracle Middleware Home Gold Image must be present in the Software Library. For details on creating this gold image. You can create an Oracle Middleware Home Gold Image and save it in the Software Library. You can then use this gold image as the source for future Middleware Home installations. For the detailed procedure on creating an Oracle Middleware Home Gold Image, see the Enterprise Manager Lifecycle Management Guide.

18.1.2.1 Provision from Oracle Middleware Home Gold Image Deployment Procedure

Note:

  • If you have manually created and discovered a Middleware Home, this step can be ignored.

  • You cannot have more than one Middleware Home of the same WebLogic Server version on a single host.

You can clone a Middleware Home from a gold image present in the Software Library. This gold image must have been created earlier by pointing to an existing Middleware Home. For a detailed description on cloning a Middleware Home from a gold image, refer to the Enterprise Manager Lifecycle Management Guide.

18.1.3 Configuring and Saving the Deployment Procedure

Note:

Oracle recommends that the WebLogic Domain Provisioning Profile is used instead of the Configured Deployment Procedure described in this section.

You can configure and save a Middleware Provisioning deployment procedure. This Configured Deployment Procedure can then be used by the EM_SSA_ADMINISTRATOR while creating a Middleware Service Template. To customize the deployment procedure, follow these steps:

  1. Log into Enterprise Manager as a user with EM_SSA_ADMINISTRATOR role.

  2. From the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning. The Middleware Provisioning page appears.

  3. The profiles that have been uploaded are listed in the Profile section. The profile you select must contain only one cluster with one WebLogic Server.

  4. Select the Provision Middleware Deployment Procedure from the Deployment Procedures region and click Launch.

  5. Select Provision from WebLogic Domain Provisioning Profile option. Click the Search icon and select one of the profiles as the image to use for the oracle home.

  6. Enter a name for the customized deployment procedure and click Save.

    The MWaaS feature will not work if any variables in the deployment procedure are locked.

  7. After the deployment procedure has been saved, click Cancel to exit the current deployment procedure. You will see the new customized deployment procedure listed in the Deployment Procedures table in the Middleware Provisioning page. The saved deployment procedure can now be used while creating a service template.

    Note:

    The Configured Deployment Procedure you have created must contain only one cluster with one or more WebLogic Servers.

18.2 Getting Started with MWaaS - Virtual Flow

This section helps you get started by providing an overview of the steps involved in setting up the Middleware as a Service (MWaaS) and provision a service instance on one or more Oracle VM Zones. Before you set up MWaaS, you must download and deploy the required plug-ins. For more details, see Section 3.2, "Deploying the Required Plug-ins".

Note:

MWaaS (Virtual Flow) can be used only with Oracle VM Servers. Third party virtualization technology is not supported.

Table 18-2 Getting Started with MWaaS (Virtual Flow)

Step Task Role

1

Define roles for administrators and self service users. See Section 3.3, "Defining Roles and Assigning Users".

Super Administrator

2

Optionally, you may need to configure Privilege Delegation Settings on your managed hosts. Section 3.5, "Configuring Privilege Delegation Settings".

Super Administrator

3

Register Oracle VM Manager. See Section 5.3, "Registering the Oracle VM Manager".

Cloud Administrator

4

Discover Virtual Servers. See Section 5.5, "Discovering a Virtual Server".

Cloud Administrator

5

Register Storage Servers. See Section 5.9, "Registering Storage Servers".

Cloud Administrator

6

Configure Networks. See Section 5.7, "Setting Up Networks".

Cloud Administrator

7

Create Virtual Server Pool. See Section 5.14, "Creating a Virtual Server Pool".

Cloud Administrator

8

Create Oracle VM Zone. See Section 5.15, "Creating a Zone"

Cloud Administrator

9

Create a PaaS Infrastructure Zone. See Section 11.3, "Creating a PaaS Infrastructure Zone".

Cloud Administrator

10

Deploy an Oracle Virtual Assembly (ova) and create a Deployment Plan. See Section 9.8.4, "Provisioning Guest Virtual Machines Using Oracle Virtual Assemblies (OVA)".

For more information on assemblies, see the Oracle Virtual Assembly Builder page http://www.oracle.com/technetwork/middleware/ovab/overview/index.html on the Oracle Technology Network.

For instructions on building assemblies, see the Oracle Virtual Assembly Builder Installation Guide.

Self Service Administrator


Figure 18-5 shows the sequence of steps required to enable middleware as a service (virtual hosts).

Figure 18-5 Getting Started with MWaaS (Virtual Flow)

Getting Started with MWaaS (Virtual Hosts)

After you followed the steps listed in Figure 18-5, do the following: