3 Updating WebLogic Domains

The update process enables you to add a product component functionality or additional applications and services to an existing WebLogic domain. You can update a domain by using the Configuration Wizard.

Note:

To update a WebLogic domain that includes other Fusion Middleware products in addition to WebLogic Server, see Updating a WebLogic Domain That Includes Fusion Middleware Products.

For example, if you have created a base WebLogic domain and you want to add Advanced Web Services for JAX-WS, you can select the WebLogic Advanced Web Services for JAX-WS Extension template on the Templates screen. You can also use the Configuration Wizard to change your domain configuration without adding additional applications. For example, you may want to add additional Managed Servers and clusters, or you may want to change service targeting or the migratable target settings.

Note:

You can update only the domain that was created by the same WebLogic Server installation from which you run the Configuration Wizard. That is, the domain that you are updating must be registered in the domain-registry.xml file of your WebLogic Server installation. You cannot update a domain that is created by another WebLogic Server installation.

Before you update a domain that was created with an earlier release of WebLogic Server, you must use the Reconfiguration Wizard to reconfigure the domain. Doing so updates the domain to be compatible with the current WebLogic Server release, and registers the domain in your current WebLogic Server installation. See Reconfiguring WebLogic Domains in Upgrading Oracle WebLogic Server.

The Configuration Wizard simplifies the task of updating an existing WebLogic domain by using extension templates. Oracle provides various sample extension templates, as well as extension templates for various Fusion Middleware products. You can also create your own extension templates by using WLST or the unpack command.

For information about extension templates provided by Oracle, see Types of Templates in Domain Template Reference.

This chapter includes the following sections:

• Before You Begin
  Set the value of the CONFIG_JVM_ARGS environment variable to reduce the time it takes for the Configuration Wizard to create or update a domain.
• Domain Update Process
  You can update a domain by adding additional product components to the domain or by specifying an extension template JAR file.
• Updating a WebLogic Domain in Graphical Mode
  The Configuration Wizard takes you through a series of screens that help you update a WebLogic Server domain.
• Updating Startup Scripts on Remote Servers
  When you update a WebLogic domain in which the Managed Servers are distributed (by using the pack and unpack commands) to remote machines, the startup scripts on the remote machines are not updated automatically. You must update them manually.

Before You Begin

Set the value of the CONFIG_JVM_ARGS environment variable to reduce the time it takes for the Configuration Wizard to create or update a domain.

Before you update a domain on a UNIX or Linux operating system, if you have not already done so, set the CONFIG_JVM_ARGS environment variable to the following value:

-Djava.security.egd=file:/dev/./urandom

Domain Update Process

You can update a domain by adding additional product components to the domain or by specifying an extension template JAR file.

To update a WebLogic domain, select the domain to update and, if you want to add additional products to the domain, select one or more additional product components on the Templates screen. Alternatively, you can update an existing domain by specifying an extension template JAR file that includes additional applications and services, or defines additional components (such as Managed Servers and clusters). You can also customize the JDBC connections and change the JMS file store. The Configuration Wizard uses your input to update the configuration files, such as config.xml, and all other generated components in the domain directory, as required.

Updating a WebLogic Domain in Graphical Mode

The Configuration Wizard takes you through a series of screens that help you update a WebLogic Server domain.

To begin the update process, start the Configuration Wizard as described in Starting the Configuration Wizard.

Note:

In situations where you cannot run the Configuration Wizard in the GUI mode, Oracle recommends that you use a WLST script to create or update a domain. See Creating and Using a Domain Template (Offline) in Understanding the WebLogic Scripting Tool.

If your installation includes Fusion Middleware products, see Configuring Fusion Middleware Domains, for instructions. Fusion Middleware product configuration includes additional Configuration Wizard screens that are not included in the workflow in this chapter.

The Configuration Wizard displays a sequence of screens, in the order listed in Table 3-1. For more information on each screen, refer to the related section in Configuration Wizard Screens, or click the link in the Screen column.

Table 3-1 Configuration Screens for Extending an Existing WebLogic Domain

Screen	When Does This Screen Appear?	Perform the Following Action
Configuration Type	Always	Select Update an Existing Domain. Select the domain directory from the Existing Domain Directory drop-down list, or click Browse to navigate to and select the domain directory. Click Next.
Templates	Always	Do one of the following: Select Update Domain Using Product Templates, and then select the check box for each product to add to the domain. Select Update Domain Using Custom Template, and then click Browse to locate the template on your local drive or network. Click Next. Note: When you update a domain by using a custom template, you must comply with the domain version restrictions as described in Domain Version Restrictions.
High Availability Options	Only if the templates that you have selected in the Templates screen are configured for high availability.	At the time of updating a domain, this screen appears only if new templates are introduced and you have not configured the HA options for those templates. For example, if the new templates that you use to update the domain contain the “Automatic Service Migration (ASM)” parameter, and you have not defined the ASM parameter in the existing, the screen appears. Select the applicable HA options for the domain you are updating. Click Next.
Application Location	Only if one or more of the selected templates define an application	Specify the directory in which the domain applications have to be stored. Click Next.
Data Source Configuration	Only if the selected products or template includes components that require JDBC data sources or Oracle RAC multi-data sources	See Configuring Data Sources for information about these screens.
Advanced Configuration	Always	Select the check box for each category (if any) for which you want to perform advanced configuration tasks. The available check boxes depend on the resources that are configured in the selected products or template. Note: When extending a domain, you cannot change the Administration Server and Node Manager configurations. Therefore, these options are not available. Click Next.
Managed Servers	Only if you have selected Managed Servers, Clusters, and Coherence on the Select Advanced Configuration screen	Add, delete, or reconfigure Managed Servers as needed. Click Next.
Clusters	Only if you have selected Managed Servers, Clusters, and Coherence on the Select Advanced Configuration screen	Add, delete, or reconfigure clusters as needed. Click Next.
Assign Servers to Clusters	Only if you have selected Managed Servers, Clusters, and Coherence on the Select Advanced Configuration screen, and your domain includes at least one cluster	Add servers to or remove servers from the clusters in your domain. Click Next.
HTTP Proxy Applications	Only if you have selected Managed Servers, Clusters, and Coherence on the Select Advanced Configuration screen, and your domain includes at least one cluster, and at least one Managed Server that is not assigned to a cluster	For each cluster, specify whether or not you want to create an HTTP proxy application for the cluster. If you select the Create HTTP Proxy check box for a cluster, select the proxy server to use for that cluster. Click Next.
Coherence Clusters	Only if you have selected Managed Servers, Clusters, and Coherence on the Advanced Configuration screen, and Coherence is installed with WebLogic Server	Accept the default cluster name or type a new name for the Coherence cluster. Enter the port number to use as the Coherence cluster listen port. Click Next.
Machines	Only if you have selected Managed Servers, Clusters, and Coherence on the Select Advanced Configuration screen	Add, delete, or reconfigure machines as needed. Click Next.
Assign Servers to Machines	Only if you have selected Managed Servers, Clusters, and Coherence on the Select Advanced Configuration screen, and there is at least on machine configured in the domain	Assign the Administration Server and Managed Servers to the appropriate machines. Click Next.
Virtual Targets	Only if you have selected Topology on the Advanced Configuration screen	Add, configure, and delete virtual targets that you want to use to run WebLogic Server in a multitenant mode. For an overview of multitenancy in Oracle WebLogic Server, see Oracle WebLogic Server Multitenant in Using Oracle WebLogic Server Multitenant. For a definition of virtual targets, see Virtual Targets in Using Oracle WebLogic Server Multitenant. Click Next.
Partitions	Only if you have selected Topology on the Advanced Configuration screen	Add the required number of partitions. Later, you assign virtual targets to each partition that you define. For more information about virtual targets and partitions, see Configuring Virtual Targets: Overview and Configuring Domain Partitions: Overview in Using Oracle WebLogic Server Multitenant. Click Next.
Assign Virtual Targets to Partitions	Only if you have defined virtual targets and partitions for the domain being configured	Associate a virtual target to a partition. A partition can have zero or more virtual targets. Click Next.
Deployments Targeting	Only if you have selected Deployments and Services on the Select Advanced Configuration screen, and a selected product or template contains J2EE applications or libraries	Select the target server or cluster on which you want to deploy applications or libraries. Select the check box for each application or library you want to deploy on the selected target. Note: While creating a Restricted JRF domain by using the config.cmd or config.sh command, you must target the Enterprise Manager (EM) related libraries to the cluster to access the Enterprise Manager Console. Click Next.
Services Targeting	Only if you have selected Deployments and Services on the Select Advanced Configuration screen	Select the target server or cluster. Select the check box for each service you want to target to it. Click Next.
File Store	Only if you have selected File Store on the Select Advanced Configuration screen	Change the settings for each JMS file store as needed, and select the synchronous write policy for each file store. Click Next.
Configuration Summary	Always	Review the configuration for your domain by selecting a Summary View, and then selecting individual items in the list for that view. If the domain is configured as you want it, click Update to extend the domain. To modify the configurations, click Previous to return to the appropriate screen for the settings you want to change.
Configuration Progress	Always	Shows the progress of the domain creation. When the process completes, click Next.
Configuration Success	Always	Click Finish to exit the Configuration Wizard.

Note:

WebLogic Server Multitenant domain partitions and virtual targets are deprecated in WebLogic Server 12.2.1.4 and will be removed in the next release.

Updating Startup Scripts on Remote Servers

When you update a WebLogic domain in which the Managed Servers are distributed (by using the pack and unpack commands) to remote machines, the startup scripts on the remote machines are not updated automatically. You must update them manually.

To ensure that startup scripts on the remote machines are updated:

1. Delete the Managed Server directories on the remote machines.
2. Create a Managed Server template from the updated domain by using the pack command with the -managed=true option.
3. Create Managed Servers on the remote machines by using the unpack command to unpack the Managed Server template.

For more information about the pack and unpack commands, see Overview of the Pack and Unpack Commands in Creating Templates and Domains Using the Pack and Unpack Commands.