Oracle Cloud Infrastructure Documentation

Configuring Patching and Server Control

Before you can patch a domain or managed instance, you must enable patching and set how servers stop, start and restart. You can also enable patch rollback and set server timeout limit.

Important

Pre-General Availability: 2024-10-11

The following legal notice applies to Oracle pre-GA releases. For copyright and other applicable notices, see Oracle Legal Notices.

Pre-General Availability Draft Documentation Notice

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

By default, patching is not configured for domains because the terms and conditions must be accepted (per domain) before you can apply or remove patches. When you enable patching, you must also decide whether to use Node Manager or scripts to start, stop and restart servers. You can optionally elect to rollback server patching if failures occur and set the timeout period before a server is forced to shutdown.

When WebLogic Management performs server lifecycle or patching operations, administrative credentials for the WebLogic domains are required. See Defining Admin Credentials.

To check whether servers can be patched and to see the available patches, see Patching Server Middleware.

Using the Console

  1. Open the navigation menu and click Observability & Management. Under WebLogic Management, click Domains.
  2. Under List scope, select the compartment that contains the domains.
  3. (Optional) Under Filters, select one or more of the following options to refine the list of domains:
    • State: Lists only the domains in the specified state.
    • Version: Lists only the domains with the specified middleware version.
    • Type: Lists only the domains with the specified middleware.
    • Patch readiness status: Lists only the domains with the specified readiness status.
  4. Under Name, click a domain to navigate to its details page.
  5. Click Edit domain settings.
  6. To configure patching, provide the following information:
    • Enable patching: Check to enable patching for the domain. You might be prompted to accept Terms and Conditions if you have not already done so.
    • Enable rollback when patching fails: (Optional) Check to rollback to previous patches when failures occur. Rollbacks are at the managed instance level, which means only the instances that fail are rolled back.
    • Server shutdown timeout (seconds): (Optional) Enter the number of seconds to wait before a server is forced to shutdown.
  7. Under Server control, select how servers are started, stopped and restarted:
    • Use Node Manager to start and stop servers
    • Use scripts to start and stop servers: Enter the path to the scripts that are to be used to start, stop, and restart the administration server and other servers in the domain. For detailed instructions on using scripts, see Using Scripts to Manage Server Lifecycle.
  8. Click Save changes.

Using the API

Run the UpdateWlsDomain operation to configure patching for a domain.