15 Provisioning WebLogic Domains and Middleware Homes

Prerequisites

Before running the Deployment Procedure, meet the following prerequisites:

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

• The Operating System Host user must have Read permissions on:

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

  • Administration Server host domain directory.

  • Agent home directory.

• The user must have Write permissions on:

  • Working Directory on the source host machine which Administration Server is running.

  • Working Directory on all destination hosts.

  • Middleware Home directory on all destination hosts.

  • Domain location on all destination hosts

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

Deployment Procedure

The Clone WebLogic Domain option launches a wizard that enables you to clone a WebLogic Domain from an existing reference domain that is already discovered with Cloud Control. It allows you to clone the Middleware Home and its binaries, and the domain configuration.

To clone a WebLogic Domain from an existing installation, follow these steps:

1. From the Targets menu, select Middleware.

2. A list of Middleware targets is displayed. Find the WebLogic Domain that you want to use as the source for the cloning operation. Right click on that WebLogic Domain to access the context sensitive menu and select the Provisioning menu option. From the menu, select Provisioning and Clone WebLogic Domain.

3. You can select:

   • Clone Middleware Home: Select this option if you want to clone only the software in the Middleware Home.

   • Clone WebLogic Domain: Select this option to clone a WebLogic Domain from an existing reference domain that is already discovered with Cloud Control. It allows you to clone the Middleware Home and its binaries, and the domain configuration.

4. In the Select Source page, depending on your selection, the WebLogic Domain or the Middleware Home to be cloned is displayed.

   Figure 15-5 Middleware Provisioning: Source Page

   
   

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

6. In the Working Directory field, specify the directory on the destination Host on which the cloning related files are temporarily stored. The directory must have sufficient space to store the cloning related files. If this directory is not present, it will be created. When the cloning operation has been completed, 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.

7. In the Host Credentials section, enter the host credentials of the machine on which the Administration Server is running. Select one of the following options:

   • Preferred Credentials: The preferred credentials stored in the Management Repository are used. The Preferred Credentials option will be available only if it has already been defined in Cloud Control.

   • Named Credentials: The credentials of a named profile stored in the Management Repository is used. To use the Named Credentials stored in the Management Repository, you must have already registered each of the preferred credential types with a unique name. Select the desired Named credential from the list available in Credential Name. If you have created all necessary named credentials, you can use them now. If they have not been created, you can create them using this deployment procedure.

   • New Credentials: You can override the preferred credentials by specifying a new credential with a unique name and password.

8. Click Next. In the Middleware Provisioning: Destinations page, specify the destination hosts on which the Middleware Home or WebLogic Domain is to be cloned.

   Figure 15-6 Middleware Provisioning: Destinations Page

   
   

9. In the Select Destinations section, click Add Hosts. Select a host from the list and specify the operating system credentials for the owner of the Middleware Home on the destination host. The Host Credentials can be Preferred, Named, or New credentials.

10. 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. Specify an absolute path that is accessible by all targets here. If you select this option, the JDK Home Location associated with the Middleware Home and the Oracle Inventory location must also be shared.

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

12. 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 if a similar configuration is detected on the source machine.

13. In the Working Directory field, specify the directory on the destination Host on which the cloning related files are temporarily stored. This directory must have sufficient space to create the cloning related files. If this directory is not present, it will be created. When the cloning operation has been completed, 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.

14. Click Next. If you selected the Cloning a WebLogic Domain option, the Middleware Provisioning: Domain Configuration page appears. This page contains a set of links to several pages where you can enter the properties that are most likely to be reconfigured like domain name, listen addresses for the administration server and managed servers, Node Manager/Machine configuration, and JDBC data sources. By default, the source domain configuration settings are used as default values for the destination domain. For example, if the source domain has one cluster containing 4 managed servers, the destination domain will also have one cluster with 4 servers but these default values can be changed. For more information on configuring the domain, see Oracle® Fusion Middleware Creating Domains Using the Configuration Wizard guide.

    Figure 15-7 Domain Configuration: Domain Properties Page

    
    

15. In the Domain Properties page, enter or modify the following details:

    • Domain Name: The name of the domain is displayed but can be modified. 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. The domain name must not start with a number. The domain name is also listed on the Windows Start menu. For example, if your domain name is mydomain, and the Domain directory is user_projects, you can access commands for the domain by selecting Oracle WebLogic > user_projects > mydomain from the Windows Start menu.

    • 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:

      ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

    • Unique Domain Identifier: A farm is a collection of components managed by Cloud Control. It can contain an Oracle WebLogic Server domain, one Administration Server, one or more Managed Servers, and the Oracle 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.

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

    • 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 the destination host machine or network. On Windows, you must include the drive letter in this path.

16. In 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.

17. In the Machines page, enter the configuration information for the machines in the domain. A Machine is a logical representation of the system that hosts one or more WebLogic Server instances. The Administration Server and Node Manager use the Machine definition to start remote servers. 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.

      Note:

      If multiple machines are running on the same host, the Node Manager Home location must be different for each host.

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

18. In the Servers page, enter the configuration information for the Adminstration Server and one or Managed servers.

    Figure 15-8 Domain Configuration: Domain Properties: Servers Page

    
    

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

        Note:

        The host:port combination for the Administration Server must be unique among all the registered domains. For example, if an Administration Server running on myhost.example.com:7001 has been discovered in Cloud Control, this host name and port number combination cannot be used for a new Administration Server even if the status of the old Administration Server is Down or it has been removed.

      • Listen Address: Enter the listen address to be used to connect to the Aministration 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 65535. The port number you enter here must be available on the destination machine.

      • 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: 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 65535. 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 check box. Enter a valid value to be used for secure requests (through protocols such as HTTPS and T3S). The valid listen port range is from 1 to 65535. The port number you enter here must be available on the destination machine.

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

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

19. In the JDBC Data Sources page, enter the 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 in the data source.

    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.

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

21. In 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.

22. In the Security Store and Security Providers pages, you can configure an external database as a data store for various security providers.

23. In 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.

24. In the Schedule page, specify a Deployment Instance name. If you want to run the procedure immediately, then retain the default selection, that is, Immediately. If you want to run the procedure later, then select Later and provide time zone, start date, and start time details. You can set the notification preferences according to deployment procedure status. If you want to run only prerequisites, you can select Pause the procedure after the necessary prerequisite checks have been completed to pause the procedure execution after all prerequisite checks are performed. Click Next.

25. On the Review page, review the details you have provided for the Deployment Procedure. If you are satisfied with the details, then 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 where you want to make the changes.

26. In the Procedure Activity page, view the status of the execution of the job and steps in 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.

Prerequisites

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

• The hosts on which the Middleware domains are to be cloned must be discovered targets in Cloud Control.

• The user must have Read permissions on the Middleware Home directory on the host machine on which the Administration Server is running.

• The user must have Write permissions on:

  • Working Directory on the host machine which Administration Server is running.

  • Working Directory on all destination hosts.

  • Middleware directory on all destination hosts.

Deployment Procedure

This procedure launches a wizard that enables you to clone an Oracle Middleware Home that is already discovered or registered with Cloud Control. To clone an Oracle Middleware Home, follow these steps:

1. From the Targets menu, select Middleware.

2. A list of Middleware targets is displayed. Right click on WebLogic Domain target in the list and from the context sensitive menu, select Provisioning and then select Clone Middleware Home.

3. The Middleware Provisioning: Source page is displayed.

   Figure 15-9 Middleware Provisioning: Source Page

   
   

4. In the Source Information section, the Middleware Home to be cloned is displayed.

5. Follow Steps 6 to 9 as listed in Cloning a WebLogic Domain from an Existing Installation.

6. In the Schedule page, specify a Deployment Instance name. If you want to run the procedure immediately, then retain the default selection, that is, One Time (Immediately). If you want to run the procedure later, then select One Time (Later) and provide time zone, start date, and start time details. You can set the notification preferences according to deployment procedure status. If you want to run only prerequisites, you can select Pause the procedure to allow me to analyze results after performing prerequisite checks to pause the procedure execution after all prerequisite checks are performed. Click Next.

7. On the Review page, review the details you have provided for the Deployment Procedure. If you are satisfied with the details, then 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 where you want to make the changes.

8. In the Procedure Activity page, view the status of the execution of the job and steps in 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.

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.

  • Middleware Home on all destination hosts.

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

• A WebLogic Domain Provisioning Profile must be present in the Software Library. For details on creating this profile, see Creating a WebLogic Domain Provisioning Profile.

Deployment Procedure

You can clone a WebLogic Domain from a profile present in the Software Library. To clone a WebLogic Domain from a profile, follow these steps:

1. From the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning.

2. Select a profile from the Profiles section, and click Provision. You can also select the Middleware Provisioning deployment procedure and click Launch.

3. In the Source Information section, the selected component and its location is displayed. Click Next.

4. In the Middleware Provisioning: Destinations page, specify the destination hosts on which the WebLogic Domain is to be cloned.

   Figure 15-12 Middleware Provisioning: Destination

   
   

5. Click Add Hosts and select a host from the list. Specify the credentials for the destination host. The credentials can be:

   • Preferred Credentials: The preferred credentials stored in the Management Repository are used. The Preferred Credentials option will be available only if it has already been defined in Cloud Control.

   • Named Credentials: The credentials stored in the Management Repository is used. To use the Named Credentials stored in the Management Repository, you must have already registered each of the preferred credential types with a unique name. Select the desired Named credential from the list available in Credential Name. If you have created all necessary named credentials, you can use them now. If they have not been created, you can create them using this deployment procedure.

   • New Credentials: You can override the preferred credentials by specifying a new credential with a unique name and password. These credentials can be different for each host or the same for all the hosts.

6. In the Select Destination Locations section, specify the location of the Middleware Home on the Host machine. The Create a New Middleware Home option is selected by default.

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

8. In the JDK Home Location field, enter the absolute path to the JDK directory to be used on the destination Host. This field can be edited only if the JDK Home in the source domain is in an external location. If the JDK Home in the source domain is internal and installed in the Middleware Home, this field cannot be edited.

   Note:

   If there are several destination hosts, the location of the Middleware Home, Working Directory, and JDK Home Location is the same across all the hosts.

9. In the Working Directory field, specify the directory on the destination Host on which the cloning related files are temporarily stored. This directory must have sufficient space to store the files. If this directory is not present, it will be created. When the cloning operation has been completed, the directory and its contents will be deleted.

10. Click Next. Follow Steps 13 to 26 as listed in the Cloning a WebLogic Domain from an Existing Installation section.

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.

  • 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, see Creating an Oracle Middleware Home Gold Image.

Deployment Procedure

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. To clone a Middleware Home from a gold image, follow these steps:

1. From the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning.

2. From the Middleware Provisioning Deployment Procedures section, select the Provision Middleware procedure from the list and click Launch.

3. In the Middleware Provisioning: Source page, select the Provision from Oracle Middleware Home Gold Image option. Click the Search icon next to the Home Gold Image from Software Library field and select a gold image from the list.

   Figure 15-13 Middleware Provisioning (Gold Image): Source

   
   

4. In the Source Information section, the selected component and its location is displayed. Click Next.

5. In the Middleware Provisioning: Destinations page, specify the destination hosts on which the Middleware Home is to be cloned.

   Figure 15-14 Middleware Provisioning (Gold Image): Destination

   
   

6. Click Add Hosts and select a host from the list. Specify the credentials for the destination host. The credentials can be:

   • Preferred Credentials: The preferred credentials stored in the Management Repository are used. The Preferred Credentials option will be available only if it has already been defined in Cloud Control.

   • Named Credentials: The credentials of a named profile stored in the Management Repository is used. To use the Named Credentials stored in the Management Repository, you must have already registered each of the preferred credential types with a unique name. Select the desired Named credential from the list available in Credential Name. If you have created all necessary named credentials, you can use them now. If they have not been created, you can create them using this deployment procedure.

   • New Credentials: You can override the preferred credentials by specifying a new credential with a unique name and password. These credentials can be different for each host or the same for all the hosts.

7. In the Select Destination Locations section, specify the location of the Middleware Home on the Host machine. The Create a New Middleware Home option is selected by default.

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

9. In the JDK Home Location field, enter the absolute path to the JDK directory to be used on the destination Host. This field can be edited only if the JDK Home in the source domain is in an external location. If the JDK Home in the source domain is internal and installed in the Middleware Home, this field cannot be edited.

   Note:

   If there are several destination hosts, the location of the Middleware Home, Working Directory, and JDK Home Location is the same across all the hosts.

10. In the Working Directory field, specify the directory on the destination Host on which the cloning related files are temporarily stored. This directory must have sufficient space to store the files. If this directory is not present, it will be created. When the cloning operation has been completed, the directory and its contents will be deleted. Click Next.

11. In the Schedule page, specify a Deployment Instance name. If you want to run the procedure immediately, then retain the default selection, that is, One Time (Immediately). If you want to run the procedure later, then select One Time (Later) and provide time zone, start date, and start time details. You can set the notification preferences according to deployment procedure status. If you want to run only prerequisites, you can select Pause the procedure after the necessary prerequisite checks have been completed to pause the procedure execution after all prerequisite checks are performed. Click Next.

12. On the Review page, review the details you have provided for the Deployment Procedure. If you are satisfied with the details, then 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 where you want to make the changes.

13. In the Procedure Activity page, view the status of the execution of the job and steps in 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.