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

19 Provisioning SOA, Oracle Service Bus, and WebLogic Server Domains and Oracle Homes

Provisioning is a solution offered as a part of Lifecycle Management by Cloud Control. As a part of Middleware Provisioning solution, Cloud Control enables you to provision Service-Oriented Architecture (SOA), Oracle Service Bus (OSB), and WebLogic Server (WLS) Domains and Oracle Homes. In addition to provisioning a domain, you can extend an existing domain to include new Oracle Homes. For provisioning any of these entities, you can choose to create profiles. You can create a profile, save it, and then use the saved profile as the source for creating new artifacts. Doing this, ensures that the future installations follow a standard, consistent configuration.

Note:

The term Middleware Home is applicable only for WebLogic versions 10.3.x and 12.1.1.0. From 12.1.2.0.0 onward, it's known as Oracle Home.

This chapter explains how you can automate common provisioning operations for Middleware Homes and WebLogic Domains using Oracle Enterprise Manager Cloud Control. In particular, this chapter covers the following:

19.1 Getting Started

This chapter allows you to get started by providing an overview of all the steps involved in provisioning the various Middleware artifacts. The following figure illustrates the high level steps involved in Middleware Provisioning:

Surrounding text describes fmw_workflow.gif.

19.2 Prerequisites

This section describes how you can set up the infrastructure for provisioning. Meet these prerequisites before you start provisioning any of the Middleware profiles. This section is mainly for Administrators and designers who want to keep the infrastructure ready for provisioning Middleware entities.

This section covers the following:

19.2.1 Meeting Basic Infrastructure Requirements

Meet the basic infrastructure requirements as described in Chapter 2. The chapter describes both mandatory and optional requirements.

19.2.2 Creating Administrators with the Required Roles

Table 19-1 describes the roles and the minimum privileges required for creating profiles and running the deployment procedures. These roles are default roles available in Cloud Control. You need not create them, but you must explicitly create administrators based on these roles. For instructions, see Section 2.4.

Table 19-1 Roles and Privileges required for Middleware Provisioning

Roles Target Privileges Implementation Recommendation

EM_PROVISIONING_DESIGNER

Operator any Target

Role has privileges for provisioning designer. Administrators with this role can create profiles, custom procedures, and assign other users, privileges on the procedures.

EM_PROVISIONING_OPERATOR

Operator any Target

Role has privileges for provisioning operator. Administrator with this role can provision procedures on which access has been granted.


19.2.3 Prerequisites for Designers

Designers are lead administrators with increased privileges on Deployment Procedures and Software Library. Following are the prerequisites required for designers to create components in the library, customize the deployment procedure, and create and save deployment procedures for future usage by operators.

  • Ensure that you meet the mandatory infrastructure requirements described in the Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching.

  • Discover and monitor the destination hosts in Cloud Control. For this purpose, you need the latest version of Oracle Management Agent (Management Agent) on the destination hosts. For more information refer to the Oracle Enterprise Manager Cloud Control Basic Installation Guide. Ensure that the agents are installed in the same location on all hosts.

  • Set up the Oracle Software Library (Software Library). Create a folder to store the Software Library components and add components to the folder. Ensure that the WebLogic Domain Provisioning Profile and the Middleware Home Gold Image components have been added to the folder.

  • Store the operating system credentials of the destination hosts as preferred credentials in Oracle Management Repository (Management Repository) or use Named Credentials. If you are using SUDO, PowerBroker, see LCM Guide for information on setting up these authentication utilities.

  • You must have Operator any Target privilege.

19.2.4 Prerequisites for Operators

Operators are administrators who have restricted privileges on a Deployment Procedure and Software Library. Normally, operators can view and submit a deployment procedure. The Designer user may also grant the Operator the necessary privileges on any targets or entities. The following prerequisites are required:

  • You must have permissions to view credentials (set and locked by the designer), view targets, submit jobs, and launch deployment procedures.

  • You must have Operator any Target privilege.

  • If you are cloning a WebLogic domain using an existing installation, you must have Write permission on the source and the destination Middleware Homes.

  • If you are using an external JDK, ensure that the JDK software has been installed at the same location on all the destination hosts before you launch the deployment procedure.

  • Middleware Home Requirements:

    • Existing Middleware Home: The Middleware Home on the destination machine must be identical in content and product stack as the Middleware Home on the source machine.

    • Create New Middleware Home: Ensure that there is sufficient disk space on the destination machine. The space required is approximately 2 times the size of the source Middleware Home.

    • Shared Middleware Home: This option is applicable when you are provisioning on multiple hosts. You must specify a shared mount directory that is accessible by all destination hosts.

19.2.5 Additional Prerequisites for Windows

When you run the deployment procedures on Windows, ensure that the following prerequisites are met:

  • The Operating System user must be part of the Administrators Group.

  • If the source Middleware Home is being cloned, ensure that the Node Manager service has been stopped.

  • Ensure that directory paths and locations you specify are in the Windows standard format.

19.3 Identifying the SOA, OSB, and WebLogic Server Provisioning Profiles

Middleware Provisioning profiles include SOA Provisioning Profiles, OSB Provisioning Profiles, and WebLogic Server Provisioning Profiles. The procedure to create and provision each of these profiles are generic, and do not depend on the product type. For steps on how to create the profiles, and provision them, see Creating Middleware Provisioning Profiles and Applying the Provisioning Profiles respectively.

Note:

  • It is not mandatory to create profiles. If you have an existing Gold Image or a domain clone, you can directly provision them. However, using profiles ensures that the future installations follow a standard, consistent configuration.

  • To create a new schema for your WebLogic Domain, ensure that you create an Install Media Profile containing RCU before creating an Oracle Home profile. While provisioning the RCU profile, if you select Create New Schemas option, then you will need to provide the RCU Install Media location on the JDBC page. Note that, you do not need to create schema for a plain WebLogic Domain profile, technically, schema creation becomes relevant only for upper-stack products like SOA.

In general, any WebLogic Domain provisioning is a two-step process:

Step1: Create a WebLogic Domain profile using the profile creation wizard. This will store the profile in Enterprise Manager Software Library.

Step2: Provision a destination WebLogic Domain using the WebLogic Domain profile that you have created.

The following graphic explains that a single profile can be used to provision multiple WebLogic Domains and Oracle Homes at different points in time.

WebLogic Domains and Oracle Homes

This section describes the following provisioning flows:

19.3.1 SOA Provisioning Profiles

This table describes the different SOA provisioning flows:

Table 19-2 SOA Provisioning Profiles

Use case Description What gets Provisioned? Reference Links

SOA Installation Media

SOA + WLS + RCU

A new WebLogic Domain with SOA is set up.

If you do not upload RCU, you must choose a pre-created schema for your WebLogic Domain.

Creating an Installation Media Profile

Applying the Provisioning Profiles

SOA Gold Image

Gold image of an existing SOA home.

A new SOA Domain (WLS+SOA) is set up.

Creating a Middleware Home Profile

Applying the Provisioning Profiles

Existing SOA Middleware Home

A SOA home has already been installed.

You may provision the SOA home directly, or create a profile out of the image and then provision it.

A new SOA Domain (WLS+SOA) is set up.

Creating a Middleware Home Profile

Applying the Provisioning Profiles


Note:

SOA Domain Cloning is not supported in Enterprise Manager 12.1.0.4 release. When you clone an existing SOA Domain, only WebLogic Server specific cloning tasks are performed using the Pack/Unpack command. However, the SOA specific tasks are not performed on the domains. For more information about these limitations, see Limitations of Using Pack or UnPack Commands.

19.3.2 OSB Provisioning Profiles

This table describes the different OSB provisioning flows:

Table 19-3 OSB Provisioning Profiles

Use case Description What gets Provisioned Reference Links

OSB Installation Media

OSB + WLS +RCU

A new WebLogic Domain with OSB is set up.

If you do not upload RCU, you must choose a pre-created schema for your WebLogic Domain.

Creating an Installation Media Profile

Applying the Provisioning Profiles

OSB Gold Image

A Gold Image of an already patched OSB Home.

A new OSB Domain (WLS+OSB) is set up.

Creating a Middleware Home Profile

Applying the Provisioning Profiles

Existing OSB Middleware Home

An OSB home has already been installed.

You may provision the OSB home directly, or create a profile out of the image and then provision it.

A new OSB Domain (WLS+OSB) is set up.

Creating a Middleware Home Profile

Applying the Provisioning Profiles

OSB Domain Cloning

The following cases are possible:

Case 1: OSB Domain Profile

A profile containing the Gold Image of an already patched Oracle Home (MWH), and the configuration snapshot of the WebLogic domain that was configured out of that Oracle Home

Case 2: OSB Domain bitless Profile

A profile containing only the configuration snapshot of the WebLogic Domain without Oracle Home binaries.

OSB domain is cloned using the pack and unpack commands of Weblogic Server. In this case, the ldif files are copied. Additionally, support to customize the OSB projects is present. For more information on this, follow the steps outlined in Customizing Oracle Service Bus Profile section.

Creating a WebLogic Domain Profile


19.3.3 WebLogic Server Provisioning Profiles

This table describes the different WebLogic Server provisioning flows:

Table 19-4 WebLogic Server Provisioning Profiles

Use case Description What gets Provisioned Reference Links

WebLogic Server Installation Media

WLS only

A plain WebLogic Domain with a Middleware Home is setup

Creating an Installation Media Profile

Applying the Provisioning Profiles

WebLogic Server Gold Image Profile

A Gold Image of an already patched WebLogic Home.

A new WLS Domain is set up.

Creating a Middleware Home Profile

Applying the Provisioning Profiles

Existing WebLogic Server Middleware Home Profile

A WebLogic Server home has already been installed.

You may provision the WLS home directly, or create a profile out of the image and then provision it.

A new WLS Domain is set up.

Creating a Middleware Home Profile

Applying the Provisioning Profiles

WebLogic Server Domain Cloning

A profile containing only the configuration snapshot of the Web Logic Domain without Oracle Home binaries.

WebLogic Domain is cloned using the pack and unpack commands of Weblogic Server. For information on this, see Limitations of Using Pack or UnPack Commands.

Creating a WebLogic Domain Profile

Applying the Provisioning Profiles


19.4 Limitations of Using Pack or UnPack Commands

Use of Pack or Unpack command to create templates affects the following files and directories:

  • When you create a WebLogic Domain template, then all files and directories in the source domain are included except:

    • Temporary files that are created when you start a server.

    • The servers directory.

    • Files in the security directory that are created automatically when you create the domain, such as DefaultAuthenticatorInit.ldift and XACMLRoleMapperInit.ldift.

    Note:

    If you configure additional security data, for users, groups, or roles, using the WebLogic Server Administration Console or other online tools, then this data is stored in the LDAP server, and is not included in the template. To import the data into the target domain, you must first export the data, and then import it.
  • When you create a Managed Server (using the -managed=true option), then:

    The following files are included by default:

    • All files in the root directory with the following extensions: .cmd, .sh, .xml, .properties, and.ini.

    • Any files with .pem extension defined in the SSL configuration for your domain.

    • bin directory

    • lib directory

    • All files and subdirectories in the config directory

    The following files and directories are not included in a Managed Server template by default:

    • Applications and some application initialization files.

    • Temporary files that are created when you start a server.

    • The servers directory.

    • Files in the security directory that are created automatically when you create the domain, such as DefaultAuthenticatorInit.ldift and XACMLRoleMapperInit.ldift.

    Note:

    The config.xml file of the domain from where you create your template must contain Managed Server definitions that specify the IP address and port for the target remote machine. Only these Managed Server template can be used with the unpack command on the specified remote machines. This in turn helps create Managed Server domain directories for the Managed Servers defined in the config.xml file.

19.5 Launching and Submitting a Middleware Procedure

There are several entry points to launch and submit the Middleware Provisioning deployment procedure.

  • From Middleware Provisioning console: In Cloud control, from Enterprise menu, select Provisioning and Patching, then click Middleware Provisioning. On the Middleware Provisioning home page, from the Deployment Procedures table, select the middleware procedure, and click Launch.

    Surrounding text describes middleware_dp_page.gif.
  • From the Profiles section in the Middleware Provisioning console: In Cloud control, from Enterprise menu, select Provisioning and Patching, then click Middleware Provisioning. On the Middleware Provisioning home page, from the Profiles table, select the profile you want to run, and click Launch.

    Surrounding text describes middleware_profiles_pages.gif.
  • From the Procedure Library page: In Cloud control, from Enterprise menu, select Provisioning and Patching, then click Procedure Library. The Procedure Library page is displayed. From the Procedures table, select Provision Fusion Middleware.

    Surrounding text describes deployment_manager_page.gif.
  • From WebLogic Domain target menu: In Cloud Control, from Targets menu, select Middleware. On the Middleware targets page, select the WebLogic Domain that you want to provision. On the domain home page, from the WebLogic Domain menu, select provisioning, then click Clone Middleware Home or Clone WebLogic Domain to invoke the middleware provisioning deployment procedure.

    Surrounding text describes weblogic_target_menu.gif.
  • Using Enterprise Manager Command Line Interface: You can use the submit_procedure verb to submit the deployment procedure. Following which, run the EM CLI command get_instance_data to get a input properties file. This file can then be used as an input template for subsequent runs.

    emcli submit_procedure
    -name=FMWPROV_DP
    -input_file=data:input.properties
    -instance_name=TestDomainProvisioningRun
    

    Note:

    For more information about related EM CLI verbs, see Oracle Enterprise Manager Command Line Interface.

19.6 Creating Middleware Provisioning Profiles

Profiles are like templates that you can create and store in Software Library. Once a profile is created, it can be launched numerous times to provision WebLogic Domain and/or Oracle Home. The advantage of using a profile is that you can ensure that future WebLogic installations follow a standard, consistent configuration.

Profiles can be created from:

  • An Installation Media. For a detailed list of steps, see Section 19.6.3.

  • An Existing Middleware Home. For a detailed list of steps, see Section 19.6.2

  • An Existing WebLogic Domain. For a detailed list of steps, see Section 19.6.1.

19.6.1 Creating a WebLogic Domain Profile

Use this page to create a profile, save it in Software Library, and then use the saved profile as a source for creating new WebLogic domains. This way, you can ensure that future WebLogic installations follow a standard and consistent configuration.

Prerequisites:

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

  • Host credentials must be set for the source machine on which Administration Server is running.

  • The WebLogic domain for which the profile is being created must be a monitored target in Cloud Control.

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

    Disk Space = Middleware Home Size + WebLogic Domain Size + Space for Temporary Scripts (About one GB)

To create a WebLogic Domain profile, follow these steps:

  1. In Cloud Control, from the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning.

  2. On the Middleware Provisioning home page, in the Profiles section, from the Create menu, select From WebLogic Domain.

  3. On the Create Fusion Middleware Provisioning Profile page, in the Profile Details section, enter a unique name and description for your profile. By default, all the profiles are centrally located in Software Library under the Fusion Middleware Provisioning/Profiles directory.

  4. In the Reference Target section, click the search icon. In the Select Target dialog box, select a WebLogic Domain target from the table, and click Select.

    Once you select the domain, the corresponding host details like host name, and Oracle home, that are available within the host, get populated.

    You can also launch the WebLogic Domain Profile from the Middleware target page. For information on the navigation steps, see Section 19.5.If this is done, then the context of the target is maintained, and the fields like Type, Name, Host, and Oracle Home details appear pre-populated.

  5. Based on the target selection, you may create one of the following profiles:

    1. Bitless WebLogic Domain Profile: If you de-select the Include Oracle Home checkbox available in the Reference Target section, a plain Fusion Middleware domain without any binaries is created. This is particularly useful in servicing Cloud requests for which domains need to be created for existing middleware homes.

    2. WebLogic Domain Profile: If you retain the default selection of Include Middleware Home, then a WebLogic Domain with the domain configurations, Middleware Home, and binaries is created.

      Click the search icon to provide credentials. In the Select Credentials dialog box, select the credentials that you have already set, and click OK. Click Test to validate the credentials against the selected target.

  6. In the Storage section, select the Software Library storage details. Ensure that you provide a valid storage type, and upload location to update the profile.

  7. In the schedule section, you can retain the default option (Immediately), or schedule the job for a later time. If you select Later, ensure that you provide a valid date and time for running the job.

  8. Click Create Profile to submit the profile creation job.

  9. After the job has successfully run, a new entry is available in the Profiles table. You can click the profile name to view the details.

19.6.2 Creating a Middleware Home Profile

Use this page to create a Middleware Home (Oracle Home) Profile, save it in Software Library, and then use the saved profile as the source for creating new Oracle Home profiles.

Note: Starting with Cloud Control 12.1.0.6, you can create a new WebLogic Domain from an Oracle Home Profile.

Prerequisites

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

  • Host credentials must be set for the source machine on which Administration Server is running.

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

    Disk Space = Middleware Home Size + Space for Temporary Scripts

To create a Middleware Home profile, follow these steps:

  1. In Cloud Control, from the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning.

  2. On the Middleware Provisioning home page, in the Profiles section, from the Create menu, select From Oracle Home.

  3. On the Create Fusion Middleware Provisioning Profile page, enter a unique name and description for your profile.

    By default, all the profiles are centrally located in Software Library under Fusion Middleware Provisioning/Profiles directory.

  4. In the Reference Target section, click the search icon. In the Select Target dialog box, select an Oracle Home, and click Select. The corresponding host details are populated.

    You can also launch the Create Middleware Home Profile from the Middleware targets page. How? If you do so, the context of the target is maintained, and the fields like Type, Name, and Host appear pre-populated.

  5. Click the search icon to provide the credentials. In the Select Credentials dialog box, provide the necessary credentials for your target that is already set, and click OK. Click Test to validate the credentials against the selected target.

  6. In the Storage section, select the Software Library storage details. Ensure that you provide a valid storage type, and upload location details to update the Oracle Home profile.

  7. In the schedule section, you can retain the default Immediately option, or choose to schedule it for a later time. If you select Later, then ensure that you provide a valid date and time for running the job.

  8. Click Create Profile to submit the profile creation job.

  9. After the job has successfully run, a new entry is available in the Profiles table. You can click the profile name to view the details.

19.6.3 Creating an Installation Media Profile

Oracle now allows you the flexibility to upload Installation Media from a remote host, create a profile based on the Installation Media selected, and provision this profile from the Middleware Provisioning page. From this page, you can either create a WebLogic Server Profile or an Oracle SOA Suite Profile.

Note:

There are no validation checks to verify the compatibility of the Installation Media being uploaded. To avoid issues while provisioning, ensure that you upload the correct files while creating the Installation Media Profile.

Prerequisites

  • Set the host credentials for the source machine on which Administration Server is running.

  • Ensure that you have at-least 3 GB of disk space for a new SOA installation.

To create an Installation Media profile, follow these steps:

  1. In Cloud Control, from the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning.

  2. On the Middleware Provisioning home page, in the Profiles section, from the Create menu, select From Installation Media.

  3. On the Create Fusion Middleware Provisioning Profile page, enter a unique name and description for your profile.

    By default, all the profiles are centrally located in Software Library under Fusion Middleware Provisioning/Profiles directory.

  4. In the Product section, from the Product menu, select Oracle WebLogic Server, Oracle SOA Suite, Oracle Service Bus, or Oracle RCU. Depending on the option selected, the Platform and Version menus get updated. Select a suitable platform name and version from the list.

  5. In the Files section, do the following:

    1. Click the search icon to search for the host. In the Select Target dialog box, search and select the target where the Installation Media files reside, then click Select.

    2. To access the files on a remote host, you need to provide the host credentials. To do so, click search, and in the Select Credential dialog box, enter the necessary credentials, and click OK. Click Test to validate these credentials against the selected target.

    3. Based on the product selected, the Files table gets updated. One of the following options is possible:

      If you select Oracle SOA Suite from the Product menu, then you can upload Oracle WebLogic Server, Oracle SOA, Oracle Service Bus, and Oracle RCU files. Before actually uploading the files, as a prerequisite, you must create one directory for each product like SOA, OSB, RCU and WLS, and ensure that you add the necessary files under the respective directory.

      To add the files, select the product name from the files table, and click Select Folder. Navigate to the directory where the files are present, and click OK. To remove files, select the product type, and click Remove.

      If you select Oracle WebLogic Server from the product menu, then you will only need to upload Oracle WebLogic Server files. To do so, select the Oracle WebLogic Server from the files table, and click Select Folder. Navigate to the directory where the files are present, and click OK. To remove this file, select the product name, and click Remove.

      Note:

      There are some mandatory installation media files for each product that must be available in their respective folders, without which the Installation Media profile creation will fail.

      In the following example, Oracle WebLogic Server is the folder name, and wls1030_generic.jar is the installation media file. Similarly, basic installation media files required for Oracle SOA, Oracle Service Bus, and Oracle RCU are listed.

      • Oracle WebLogic Server: wls1036_generic.jar

      • Oracle SOA: soa1.zip, soa2.zip, soa3.zip, soa4.zip, soa5.zip, and soa6.zip

      • Oracle Service Bus: osb.zip

      • Oracle RCU: rcuHome.zip

      Note that this is just an example; the jar file names may change depending on the platform and version selected.

  6. In the Software Library Upload Location, select a valid storage type, and upload location to upload the Installation Media profile.

  7. Click Create to create a profile.

  8. After the job has successfully run, a new entry is available in the Profiles table. You can click the profile name to view the details.

19.7 Applying the Provisioning Profiles

The Provision Middleware Wizard offers GUI-rich interactive screens that allow you to clone and configure Oracle Middleware Homes and WebLogic Domains.

Note:

For understand the lock feature, see Oracle Enterprise Manager Lifecycle Management Administrator's Guide

Prerequisites

  • The destination host machines on which the WebLogic domains or the Middleware homes are to be cloned must be discovered targets in Cloud Control.

  • The operating system host user must have read permissions on the Administration Server domain directory.

  • Ensure that you have Write permissions on:

    • Host machine on which Administration Server is running.

    • Working Directory on all destination hosts.

    • Middleware Home directory on all destination hosts.

    • Domain location on all destination hosts

    • Middleware Home directory on the host machine on which the Administration Server is running

  • The ports for the Administration Server, Managed Server, and Node Manager on the destination host must be free.

To provision the middleware profile, follow these steps:

  1. Launch the Middleware Provisioning Deployment wizard. You can do so from:

    • Middleware Provisioning Page: From the Enterprise menu, select Provisioning and Patching, then click Middleware Provisioning. On the Middleware Provisioning page, you can launch a provisioning procedure in any of the following ways:

      • From the Profiles table select a profile, and click Provision.

      • From the Deployment Procedures table, select Provision Middleware, then click Launch.

    • Middleware Target Home Page: From the Targets menu, select Middleware. On the Middleware page, select a WebLogic Domain target from the table, right click and select Provisioning, then select one of the following options from the context menu:

      • Clone WebLogic Domain

      • Clone Middleware Home

      Note:

      If you are launching the Middleware Provisioning procedure from the targets page, then the context of the target is maintained.
  2. Specify the source environment details. For more information, see Section 19.7.1.

  3. Specify the destination environment details. For more information, see Section 19.7.2.

  4. Specify the domain configuration details. For more information, see Section 19.7.3.

  5. Specify the credentials. For more information, see Section 19.7.4.

  6. Specify the schedule for the provisioning operation. You can choose to provision the Middleware Home or WebLogic Domain immediately or at a later date. For more information, see Section 19.7.5.

  7. Review the inputs and submit the deployment procedure. For more information, see, Section 19.7.6.

19.7.1 Middleware Provisioning: Source Page

Depending on the context you opened the provisioning wizard from, the values may appear pre-populated on the Source page.

The following cases are possible:

  • Provisioning an Installation Media Profile:

    In this case, depending upon the type of Installation Media files uploaded to Software Library, the values get populated. For example, if you have uploaded Oracle SOA Suite, then intelligence is built into the system to pre-select values like Oracle SOA Suite, and Middleware Home. However, you can choose to create a new WebLogic Domain or extend an existing domain. If you choose to extend an existing domain, ensure that you search and select the target domain before moving to the next step.

    Click Next.

  • Provisioning a Middleware Home Profile:

    In this case, the Provision Middleware Home option appears pre-selected. Additionally, you can choose to configure a new WebLogic Domian.

    Click Next.

  • Provisioning a WebLogic Domain Profile:

    In this case, you can choose to provision just the Oracle Weblogic Domain or/and Middleware Home. If you created a bitless profile, (which means that you deselected Middleware Home option at the time of profile creation) then you can provision the WebLogic Domain. However, if you selected an Oracle Home at the time of WebLogic Domain profile creation, then you can now decide whether or not to provision the Oracle Home.

    Provide the relevant details, and click Next.

  • Cloning a WebLogic Domain or a Middleware Home Gold Image from Middleware Target Page:

    In this case, depending on your selection, the WebLogic Domain or the Oracle Home to be cloned is displayed.

    In the Source Information section, the location of the WebLogic Domain, Middleware Home, WebLogic Server, or the location of the Oracle Homes is displayed.

    In the Host Credentials section, enter the host credentials of the machine on which the Administration Server is running. You can choose to provide Preferred Credentials, or Named Credentials.

    In the Working Directory field, specify the directory on the destination host, where the cloning-related files are temporarily stored. Ensure that the directory has at least one GB of space to store these files. If this directory is not present, it will be created. Once the cloning operation completes, the contents of this directory will be deleted.

    Note:

    The Working Directory must not be created under the Middleware Home or the WebLogic Domain Home directory.

    Click Next.

19.7.2 Middleware Provisioning: Destinations Page

Specify the destination hosts on which the Middleware Home or WebLogic Domain is to be cloned. To do so, follow these steps:

  1. In the Select Destination Hosts section, click Add Hosts to add one or more hosts.

  2. In the Destinations dialog box, you can perform a search to select the desired target host machine, and click Select.

  3. In the Select Destination Locations section, specify the location of the Middleware Home on the Host machine. You can select one of the following:

    • Create a New Middleware Home: Select this option to create a new Middleware Home on the destination host.

    • Use an Existing Middleware Home: Select this option to use the existing Middleware Home present on the destination host.

    • Use a Shared Location: If you have added more than one host, select this option to use a shared location for all the destination hosts.

  4. In the Middleware Home Directory field, enter the full path to the directory in which the Middleware Home is to be created.

  5. In the Working Directory field, specify the directory on the destination host where the cloning-related files are temporarily stored. Ensure that the directory has at least one GB of space to store the cloning-related files. If this directory is not present, it will be created. When the cloning operation completes, the directory and its contents will be deleted.

    Note:

    • The Working Directory must not be created under the Middleware Home or the WebLogic Domain Home directory.

    • If the source and destination machines are the same, the Working Directory for the source and destination must be different.

  6. In the JDK Home Location field, enter the absolute path to the JDK directory to be used on the destination host. You need to specify this path even if a similar configuration is detected on the source machine.

  7. Click Next.

19.7.3 Middleware Provisioning: Domain Configurations Page

By default, the configuration for the source domain is displayed. You can customize the configuration for the destination domain by selecting a series of pages from the left panel. You can proceed to the next step in the wizard only after you have completed all the required pages. On the Configure Domain page, you can enter the basic properties that are most likely to be reconfigured like domain name, administration server, clusters, machines, server, and JDBC Data Sources.

  • On the Domain Properties page, enter the following details:

    Domain Name: The name of the domain. The generated components for the domain are stored under the specified Domain directory. For example, if you enter mydomain, your domain files are stored (by default) in MW_HOME\user_projects\domains\mydomain.

    Domain Administrator Username: The default Administrator account for the domain. This account is used to boot and connect to the domain's Administration Server. The username must not contain commas, tabs, or any of these characters: < > # | & ? ( ) { }.

    Password—The password for the Administrator account. The password must be at least eight characters, and must contain at least one numeric character or at least one of the following characters:! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

    Enable Administration Port: When enabled, this port allows the managed servers to communicate with administration server.

    Unique Domain Identifier: A farm is a collection of components managed by Enterprise Manager Cloud Control. It can contain Oracle WebLogic Server domain, one Administration Server, one or more Managed Servers, and the Oracle Fusion Middleware components that are installed, configured, and running in the domain. The Unique Domain Identifier is used as a prefix to ensure that the farm names are unique in environments with the same domain name. It is used to name the farm target as a prefix in conjunction with the WebLogic domain name. For example, if the Unique Domain Identifier is farm and the domain name is base_domain then the farm name would be farm_base_domain.

    Domain Location: The location in which your domain directory will be stored. By default, this directory is created under the parent directory of the Middleware Home, but can be changed. For example: If the Middleware Home is located at /user/mwh, the application directory is created as /user/domains. The domain location can be anywhere on your local drive or network. On Windows, you must include the drive letter in this path.

    Applications Location: The directory in which the applications will be deployed on the destination host. By default, this directory is created under the parent directory of the Middleware Home. For example: If the Middleware Home is located at /user/mwh, the application directory is created as /user/applications.

  • On the Clusters page, you can modify the name of the cluster, enter the cluster address that identifies the Managed Servers in the cluster, and the messaging mode (multicast or unicast). If you selected Multicast as the Messaging Mode, enter the address and port number that will be dedicated for multicast communications on the cluster.

    Note:

    The destination domain can have the same number of clusters as the source domain. If the source domain has no clusters, you cannot add a cluster in the destination domain.
  • On the Machines page, enter configuration information for machines in the domain. A Machine is a logical representation of the hosts.

    A Node Manager process is not associated with a specific WebLogic domain, but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process. Node Manager must run on each computer that hosts WebLogic Server instances, whether Administration Server or Managed Server, that you want to control with Node Manager. The machine configurations present in the source domain are listed here. You can modify the configuration details defined for each machine or click Add Rows to add one or more machine configurations. Enter the following details:

    Machine Name: Enter a valid machine name or modify an existing name. The machine name is used to identify the machine within the WebLogic domain; it does not have to match the network name for the machine. The name must be unique among all component names within the domain.

    Node Manager Listen Address: Enter the listen address used by Node Manager to listen for connection requests. By default, the IP addresses defined for the local system and localhost are shown in the drop-down list. The default value is the same as specified in the source domain.

    Node Manager Listen Port: Enter a valid value for the listen port used by Node Manager to listen for connection requests. The valid Node Manager listen port range is 1024 to 65535. The default value is 5556. The port number must be available on the destination machine.

    Node Manager Home: Enter the directory in which the Node Manager is to be installed. For existing machine configurations, the Node Manager is installed under the parent directory of the Middleware Home directory by default, but this can be modified.

  • On the Servers page, enter the configuration information for the Administration Server and one or more managed servers.

    Administration Server: Enter the following details for the Administration Server:

    Name: Valid names are a string of characters (alphabetic and numeric).

    Host: Select the host on which the Administration Server is to be installed.

    Listen Address: Enter the listen address to be used to connect to the Administration Server.

    Listen Port: Enter a valid value for the listen port to be used for regular, nonsecure requests (through protocols such as HTTP and T3). The valid listen port range is from 1 to 1024. The port number you enter here must be available on the destination machine.

    Local Administration Port Override: If you select Enable Administration Port on the Domain Properties page, then you can use this option to override the existing administration ports for the Managed Server.

    SSL Listen Port: If you check the Enable SSL checkbox, enter the number of the SSL Listen Port for secure requests. You must ensure that the port numbers you specify for the Listen Port and SSL Listen Port are available. If you are using the SSL configuration, you must ensure that the security/identity stores are present in the file system under the same path as on the source and are configured with certificates generated for the destination hosts

    Machine (optional): Select the machine configuration that is to be associated with the Administration Server.

    Managed Servers: You can add or delete the configuration for the Managed Servers. A Managed Server is a WebLogic Server instance to which you deploy Web applications, EJBs, and other resources. Enter the following details:

    Name: Valid server names are a string of characters (alphabetic and numeric). The name must be unique in the domain.

    Host: The host on which the managed server is running.

    Listen Address: Enter the listen address to be used to connect to the Managed Server instance.

    Listen Port: Enter a valid value for the listen port to be used for regular, nonsecure requests (through protocols such as HTTP and T3). The valid listen port range is from 1 to 1024. The port number you enter here must be available on the destination machine.

    Note:

    If a domain was registered on the host with a port number whose status is down, you need to select a different port or manually deregister the domain before launching the deployment procedure.

    Enable SSL: Select this check box to enable the SSL listen port. By default, SSL is disabled for all new servers.

    SSL Listen Port: This field is enabled only if you selected the SSL enabled checkbox. Enter a valid value to be used for secure requests (through protocols such as HTTPS and T3S). The valid listen port range is 1024 to 65535. The port number you enter here must be available on the destination machine.

    Machine: Select the machine configuration to be associated with the Managed Server.

    Cluster: Select the cluster to be associated with the Managed Server.

    Note:

    To configure custom SSL Certificates, select Use Custom Certificate option available in the Configure Keystore for Managed Server section.
  • On the JDBC Data Sources page, enter configuration information for the data source. A JDBC data source contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a data source on the JNDI tree, and then request a connection. When the applications no longer need the connections, they return the connections to the connection pool.

    By default, the cloned domain is configured with the same JDBC data sources as the source domain but it can be changed here. In the Driver field, select the correct driver from the drop down list. Based on the driver you have selected, enter the URL in the correct format. Select the target from the drop down list, and specify the database user name and password.

    Note:

    Oracle provides you the flexibility of creating schemas dynamically while provisioning. To do so, click Create Schemas, and select the database target.

    Starting with 12.1.0.6, RAC databases are also supported.

  • On the Server Startup Mode page, you can optionally start up the Managed Servers and / or the Administration Server.

  • On the JMS page, you can add new JMS persistent stores and JMS servers. A JMS file store is a disk-based file in which persistent messages can be saved. You can modify the JMS file stores configured in your domain. If these are not configured in the source domain, they cannot be configured in the destination domain. On the Security Store and Security Providers page, you can configure an external database as a data store for various security providers.

  • On the Security Store and the Security Providers page, you can configure an external database as a data store for various security providers or use an LDAP store.

  • On the Files page, specify any external files that need to be cloned from the source domain. All the external files must reside in the same directory on the Administration Server host and will be cloned to the same directory on the destination host.

  • The WebTier feature is available in all flows where a new WebLogic Domain will be created (as opposed to a WebLogic Domain being cloned). This is achievable from the following sources: Installation Media Profile or Oracle Home Profile or Existing Middleware Home profile. To allow the application to be front ended with the selected Oracle HTTP Server, on the Web Tier page, click Add. From the Target Selected dialog box, select Web Tier targets, then click Select.

19.7.4 Middleware Provisioning: Credentials Page

On the Credentials page, you can assign or create Named Credentials for all your hosts.

Note:

To create a new schema, you will need to additionally provide the database credentials.

To extend an existing WebLogic Domain, you will need to additionally provide the WebLogic Administrator credentials.

To do so, follow these steps:

  1. From the Credential menu, select either Same for all Hosts or Different for each host option. If you have more than one host, you may select Same for all Hosts to maintain a single credential set for all your hosts. However, if you select Different for each host, then you need to provide the credentials of each host. If you have already created Named Credentials for a particular host, then they will be displayed in the menu. Select one, and click Next.

  2. To add Named Credentials, click the add icon for a host. In the Add New Credentials dialog box, enter the login details such as username and password for the selected host, and click OK. If the newly added credential set is valid, it will appear in the menu for the selected host.

19.7.5 Middleware Provisioning: Schedule Deployment Page

On the Schedule page, specify a Deployment Instance name.

If you want to run the procedure immediately, retain the default selection, which is Immediately.

To run the procedure later, select Later and provide time zone, start date, and start time details.

You can set the notification preferences for a deployment procedure. For example, if you select Suspended, then a notification will be sent to you if any of the steps in this procedure go into suspended state.

To run only prerequisites checks, select Pause the procedure after the necessary prerequisite checks have been completed. Click Next.

19.7.6 Middleware Provisioning: Review Page

On the Review page, review the details you provided for the Deployment Procedure. Once you confirm the details, click Submit to run the Deployment Procedure according to the schedule set. If you want to modify the details, click the Edit link in the section to be modified or click Back repeatedly to reach the page you want to make the changes.

After you submit the deployment procedure, you will return to the Procedure Activity page where you can view the status of the Deployment Procedure. Click the Status link for each step to view the details of the execution of each step. You can click Debug to set the logging level to Debug and click Stop to stop the procedure execution. When the Deployment Procedure has successfully completed, the newly cloned environment will be added as a new target in Enterprise Manager Cloud Control and can be monitored along with the other Fusion Middleware targets.

19.8 Provisioning a Shared Middleware Home

It is possible to provision an Oracle Home on one or more hosts using the middleware provisioning profiles. You can use an existing Middleware Home Gold Image or provision it from an existing Middleware Home itself. Alternatively, you can create a Install Media profile, and provision this profile.

The Use a Shared Location option is enabled when the following conditions are met:

  1. The profile being provisioned contains a middleware home.

  2. The profile is provisioned on one or more destination hosts.

If the share option is enabled, provide a mounted location for the middleware home. The middleware home will be created only on one host, and because the location is shared, the home will be accessible by all hosts. When the Provision Middleware deployment procedure is run, it will trigger the Oracle home target discovery job on all the hosts so that an Oracle home target is discovered for all hosts.

If you have a shared middleware home mounted on multiple hosts, then the Fusion Middleware procedure can configure a new domain or extend an existing domain on all these hosts. The procedure will ensure that it selects the right hosts.

Note:

Although the shared middleware home concept does not apply to provisioning a plain WebLogic Domain, it is always important to ensure that the central inventory is available in a shared location, so that if any Fusion Middleware product is installed, its info is always available on all hosts through the central inventory.

End state of a shared Middleware Home provisioning flow:

Surrounding text describes shared_mwh_prov_flow_1.gif.

End state of a domain provisioning using an existing shared Middleware Home:

Surrounding text describes shared_mwh_prov_flow_2.gif.

19.9 Customizing Oracle Service Bus Profile

You can provide a custom file to customize the OSB profile while provisioning. To do so, follow these steps:

  1. Create a Generic Component. For a detailed list of steps, see Creating Generic Components.

    Note:

    In the Generic Component wizard, in the Select files page, ensure that you select the text file that contains the OSB customization details.
  2. Create an OSB Domain Profile. For a detailed list of steps, see Section 19.6.1.

    Note:

    Ensure that you select an existing WebLogic Domain that contains Oracle Service Bus projects.
  3. Provision the OSB Domain profile. For a detailed list of steps, see Section 19.7.

    Note:

    In the Provisioning wizard, on the Domain Configuration page, an additional section called Customization is displayed. In this section, click Select Customization File. In the Search and Select Entities dialog box, select the OSB customization file that you uploaded as a part of step 1 in this procedure, and click Select.

19.10 Creating Middleware Profiles Using Enterprise Manager Command Line Utility

This section lists all the EM CLI verbs used for accomplishing the various Middleware provisioning tasks.

Table 19-5 Creating Middleware Profiles using EMCLI

Verb and its usage Description Example

emcli create_fmw_domain_profile

Usage:

emcli create_fmw_domain_profile
-name="Profile Name" 
-ref_target="Reference Target Name"
[-description="Profile Description"]
[-oh_cred="Oracle Home Owner
Credentials"] 
[-includeOh]
[-schedule= start_time:yyyy/MM/dd HH:mm; 
[tz:{java timezone ID}]; 
[grace_period:xxx];

Creates a Fusion Middleware Provisioning Profile from a WebLogic Domain.

For a detailed explanation about the options, you can run the following command:

emcli help create_fmw_domain_profile

Example 1

To schedule a WebLogic Domain profile creation from an existing WebLogic Domain target using Preferred Credentials, run the following command:

emcli create_fmw_domain_profile 
-name="BitlessDomainProfile" 
-ref_target="/Farm01_base_domain/base_domain" 
-description="A domain profile without software bits" 
-schedule="start_time:2014/6/21 21:23;tz:America/New_York;grace_period:60" 

Example 2:

To create a WebLogic Domain plus an Oracle Home profile from an existing WebLogic Domain target using the Named Credentials, run the following command:

emcli create_fmw_domain_profile 
-name="DomainProfileWithBits" 
-ref_target="/Farm01_base_domain/base_domain" 
-oh_cred="MY_HOST_CRED:SYSMAN" 
-includeOh

emcli create_fmw_home_profile

Usage:

emcli create_fmw_home_profile 
-name="Profile Name" 
-ref_target="Reference Target Name" 
        [-description="Profile Description"] 
[-oh_cred="Oracle Home Owner Credentials"] 
[-schedule= 
start_time:yyyy/MM/dd HH:mm; 
[tz:{java timezone ID}]; 
[grace_period:xxx]; 
        ] 

Creates a Fusion Middleware Provisioning Profile from an Oracle Home.

For a detailed explanation about the options, you can run the following command:

emcli help create_fmw_home_profile

Example 1:

To create a profile at a specified schedule from a existing Oracle home target using Preferred Credentials, run the following command:

emcli create_fmw_home_profile 
-name="OhProfile1" 
-ref_target="/Farm01_base_domain/base_domain" 
-description="An Oracle Home profile" 
-schedule="start_time:2014/6/21 21:23;tz:America/New_York;grace_period:60" 

Example 2:

To create a profile from an existing Oracle home target using Named Credentials, run the following command:

emcli create_fmw_home_profile 
-name="OhProfile2" 
-ref_target="WebLogicServer_10.3.6.0_myhost.mycompany.com_5033" 
-oh_cred="MY_HOST_CRED:SYSMAN" 

emcli create_inst_media_profile

Usage:

emcli create_inst_media_profile 
        -name="Profile Name" 
        -host="Reference Target Name" 
        -version="Reference Target Name" 
        -platform="Reference Target Name" 
        [-description="Profile Description"] 
[-host_cred="Oracle Home Owner Credentials"] 
-files= 
WebLogic:WLSFile1; 
SOA:SOAFile1,SOAFile2; 
OSB:OSBFile; 
RCU:RCUFile; 

Creates a Fusion Middleware Provisioning Profile from an Installation Media profile.

For a detailed explanation about the options, you can run the following command:

emcli help create_inst_media_profile

Example 1:

To upload an Installation Media file for a WebLogic Server to the Software Library from a specified location on an existing host using Preferred Credentials, run the following command:

emcli create_inst_media_profile 
-name="WebLogic1036Installer" 
-host="myhost.mycompany.com" 
-description="WebLogic Server 10.3.6.0 installer" 
-version="10.3.6.0" 
-platform="Generic" 
-files="WebLogic:/u01/media/weblogic/wls1036_generic.jar" 

Example 2:

To upload the Installation Media files for SOA and WebLogic Server to the Software Library from a specified location on an existing host using Named Credentials, run the following command:

emcli create_inst_media_profile 
-name="SOA+WLSInstaller" 
-host="myhost.mycompany.com" 
-description="SOA 11.1.1.7.0 and WebLogic Server 10.3.6.0 installer" 
-version="11.1.1.7.0" 
-platform="Generic" 
-host_cred="MY_HOST_CRED:SYSMAN" 
-files="WebLogic:/u01/media/weblogic/wls1036_generic.jar;SOA:/u01/media/soa/soa1.zip,/u01/media/soa/soa2.zip"