1. Middleware Lifecycle Management Administrator's Guide
  2. Provisioning Fusion Middleware Domain and Oracle Homes
  3. Prerequisites for Provisioning from the Middleware Provisioning Profiles

Prerequisites for Provisioning from the Middleware Provisioning Profiles

This section describes all the prerequisites to be met before actually launching the Provision Fusion Middleware deployment procedure. In particular, it covers the following:

Note:

Before provisioning using a domain profile or an Oracle Home profile, you must download the following patches by signing in to My Oracle Support Web site at https://support.oracle.com.:

  • For SOA: 22912570
  • For Service Bus: 23003815

If you are provisioning from a domain profile using an existing Middleware Home, then ensure that the Middleware Home is patched appropriately.

Note:

In Enterprise Manager Cloud Control 13.4, there is no way to Create a Provisioning Profile for OBIEE 12.2.1.x

Note:

If you are performing a provisioning operation on a domain that was created in Development Mode, ensure that you disable the active configuration locks. To do so, perform the following steps:

  • Log in to the Middleware Administrator Console.

  • Click Preferences.

  • Deselect Automatically Acquire Lock and Activate Changes option.

  • Click Save.

  • Ensure that the Lock and Edit button is enabled in the Change Center.

Prerequisites for Provisioning the Installation Media Profile or the Oracle Home Profile

Meet the following prerequisites:

  • Write permission on the Working Directory, which is a temporary directory used for staging and provisioning entities across Cloud Control.

    If the working directory is not specified, then the Management Agent's working directory is used, and write permission on that is required.

  • Following permissions on the Oracle Home directory:

    1. Write, if a new Oracle Home has to be created. For an Installation Media profile, creating a new Oracle Home is mandatory.

    2. Read, if you are using an existing Oracle Home. Note that this is applicable only for an Oracle Home profile, and not for an Installation Media profile.

  • If you are using a shared storage, then mount the domain home and inventory directories on all the hosts beforehand. Typically, for a two-node setup, with two SOA Managed Servers running on two different hosts, for example host 1 and host 2; you can choose to create the shared storage on host 1. Effectively, this means that the Middleware Home location, the domain details, Inventory details, and all other information are mounted on host 1 for easy access from host 2.

    Note:

    Support for provisioning using a Shared Storage is not available on a Window machine.

  • All the hosts involved in the provisioning operation should be monitored as targets in Enterprise Manager.

  • Server and Node Manager Ports should be free.

  • If the domain uses a database or LDAP or Oracle HTTP Server, then ensure that the respective servers are monitored as targets in Enterprise Manager.

  • Write permission on Domain /Application/Node Manager Directories.

Prerequisites for Provisioning the WebLogic Domain Profile

In addition to the requirements mentioned in Prerequisites for Provisioning the Installation Media Profile or the Oracle Home Profile, you need to meet the following for cloning using a WebLogic Domain profile:

  • Before cloning an existing Fusion Middleware domain, you must have cloned the source database, so that the data in the schema is in sync with the source database. If you haven't already cloned your source database, you can do so using the Cloning Database feature available in Enterprise Manager Cloud Control, see Cloning Oracle Databases and Pluggable Databases.

    Note:

    Before cloning the domain, run the following data scrubbing SQL scripts on the database.

    For SOA

    Create a Generic Component and upload truncate_soa_oracle.sql script to Software Library. For more information on creating generic components, see Oracle Enterprise Manager Cloud Control Administrator's Guide. Note that the truncate script (truncate_soa_oracle.sql) is located in the following directory under SOA Installation: /MW_HOME/SOA_ORACLE_HOME/rcu/integration/soainfra/sql/truncate

    For Service Bus

    Create a Generic Component and upload llr_table.sql script to Software Library. To create this script, for each server present in the Service Bus domain, you need to add the following statement in the SQL script:

    TRUNCATE table WL_LLR_<SERVER_NAME>

    For example, if the Service Bus domain has administrator server and two managed servers with name OSB_SERVER1 and OSB_SERVER2, then the content of the sql script would look like:

    TRUNCAETE table WL_LLR_ADMINSERVER

    TRUNCATE table WL_LLR_OSB_SERVER1

    TRUNCATE table WL_LLR_OSB_SERVER2

  • If the source domain was wired with LDAP, then before cloning an existing Fusion Middleware domain, ensure that the data (users, roles and policies) has been migrated from the source LDAP to a new LDAP and the new LDAP has been discovered in Enterprise Manager as a target.

Note:

Middleware provisioning fails for JRF 12.1.2.0.0 enabled WebLogic domain, in case the source database is either down or not reachable. While unpacking the installable file, an attempt is made for connecting to the source database. In case the source database is down or unresponsive the provisioning task fails. The database must be up and running. This is not applicable for WebLogic 12.1.3.0.0 and onwards.