Oracle by Example brandingApply Latest Patches to Oracle WebLogic Server for OCI Domain

section 0Before You Begin

This 15-minute tutorial shows you how to apply latest patches to the Oracle WebLogic Server for Oracle Cloud Infrastructure (Oracle WebLogic Server for OCI) domain using the Patching Utility Tool.

Background

Each Oracle WebLogic Server for OCI release includes patches from several products, namely, Oracle WebLogic Server, Oracle JDeveloper, Oracle Java Development Kit, Oracle Platform Security Services and Oracle Web Services Manager. These patches in the Oracle WebLogic Server for OCI release are not automatically applied to the Oracle WebLogic Server domain but you have to apply them manually so that your domain is updated  to match the latest release, or to match a specific supported release.

You can use the patching utility tool in Oracle WebLogic Server for OCI to apply the latest patches to the WebLogic Server instances.

This tutorial uses a stack provisioned with two 2 nodes that has an administration server and first managed server on first node, and second managed server on the second node. This tutorial shows how to apply the latest patches on these nodes for a specific Middleware Home using the patch-utils command.

When you run the patch-utils apply -L command on the first node, the latest patches are applied on the administration server and the first managed server, and when you run the patch-utils apply -L command on the second node, the latest patches are applied on the second managed server.

Note: You can use the patching tool utility only for Oracle WebLogic Server for OCI instances provisioned after December 2020.

What Do You Need?

  • An Oracle Cloud Infrastructure cloud tenant.
  • An Oracle Cloud Infrastructure user name and password.
  • A duly created stack in a compartment with 2 WebLogic Server nodes (1 administration server and 2 managed servers) that has access to NAT gateway or service gateway.

section 1Apply Latest Patches on the First Node

  1. Connect to the compute instance or the bastion instance.
    1. Identify the following IP address of the node in your domain.
    • The public IP address of the compute instance.
    • The public IP address of the bastion and the private IP address of the compute instance.
    1. Open an SSH connection to the node as the opc user.
    • If your domain is on a public subnet, then use the public IP address of the compute instance as follows:

      ssh -i path_to_private_key opc@node_public_ip

    • If your domain is on a private subnet, then use the public IP address of the bastion and the private IP address of the compute instance as follows:

      ssh -i path_to_private_key -o ProxyCommand="ssh -W %h:%p -i path_to_private_key opc@bastion_public_ip

  2. Set up the configuration to configure the region from where to download the patches.

    patch-utils setup

    To know the supported region and their object storage endpoints, see Configure Initial Setup.

  3. Upgrade the patching tool to the latest version.

    patch-utils upgrade

  4. List the latest patches.

    patch-utils list -L

  5. List the pending patches to be applied on your Middleware Home.

    patch-utils diff
  6. Stop the managed server and the administration server. See Start and Stop a Domain.
  7. To apply the patches, you can do one of the following:
    1. Apply all the latest patches.

      patch-utils apply -L

    2. Apply only the pending patches.

      patch-utils apply -l <patch_ID1>, <patch_ID2>

    The latest patches are applied on the administration server and the first managed server.

  8. Start the administration server and the managed server. See Start and Stop a Domain.

section 2Apply Latest Patches on the Second Node

  1. Connect to the compute instance or the bastion instance.
    1. Identify the following IP address of the node in your domain.
    • The public IP address of the compute instance.
    • The public IP address of the bastion and the private IP address of the compute instance.
    1. Open an SSH connection to the node as the opc user.
    • If your domain is on a public subnet, then use the public IP address of the compute instance as follows:

      ssh -i path_to_private_key opc@node_public_ip

    • If your domain is on a private subnet, then use the public IP address of the bastion and the private IP address of the compute instance as follows:

      ssh -i path_to_private_key -o ProxyCommand="ssh -W %h:%p -i path_to_private_key opc@bastion_public_ip

  2. Set up the configuration to configure the region from where to download the patches.

    patch-utils setup

    To know the supported region and their object storage endpoints, see Configure Initial Setup.

  3. Upgrade the patching tool to the latest version.

    patch-utils upgrade

  4. List the latest patches.

    patch-utils list -L

  5. List the pending patches to be applied on your Middleware Home.

    patch-utils diff
  6. Stop the managed server. See Start and Stop a Domain.
  7. To apply the patches, you can do one of the following:
    1. Apply all the latest patches.

      patch-utils apply -L

    2. Apply only the pending patches.

      patch-utils apply -l <patch_ID1>, <patch_ID2>

      3. The latest patches are applied on the second managed server.

    3. Start the managed server. See Start and Stop a Domain.

more informationWant to Learn More?