Applying a Patch and Rolling Back a Patch for an Oracle Java Cloud Service Instance


Options



Before You Begin

Purpose

This tutorial explains how to apply a patch and roll back a patch for an Oracle Java Cloud Service instance.

Last Updates

May 2017, Release 17.2.3

Please note that Oracle develops its cloud services in an agile manner and makes rapid changes to meet our users' needs. Therefore this tutorial may not reflect all of the changes since the last update to this service. For the very latest information see:

Time to Complete

Approximately 30 minutes

Background

Patching and rollback are one-click processes that do not interrupt Oracle Java Cloud Service operation.

Scenario

To keep your service current, you can apply patches that Oracle makes available quarterly.

What Do You Need

A web browser is required for working with Oracle Cloud Services. These are the minimum requirements:

  • Microsoft Internet Explorer 9 or 10.
    • Set Browser Mode to IE9 or IE10
    • Set Document Mode to IE9 or IE10 standards
  • Google Chrome 29 and later
  • Mozilla Firefox 24 and later
  • Apple Safari 6 and later

Before starting this tutorial, you should have:

  1. Created an Oracle Java Cloud Service instance. See the tutorial Getting Started with Oracle Java Cloud Service.
  2. Deployed and started an application on that instance. See the Deploying an Application by Using the WebLogic Server Administration Console tutorial.

Verifying that Your Application is Running

Before you patch your instance, perform the following steps to verify that your application is running.

  1. Navigate to the Java Cloud Service Console.

    Java Cloud Service Console
    Description of this image
  2. Select the instance you have created.

    Oracle Java Cloud Service Instance
    Description of this image

    The Java Cloud Service Instance Overview page is displayed.

    Java Cloud Service Instance Overview page
    Description of this image
  3. Note the IP address of the load balancer. You will need this information later to run your application.

    Load Balancer section
    Description of this image
  4. Click the menu icon on the top right corner of the page, and select Open WebLogic Server Console.

    Select Open WebLogic Server Console
    Description of this image
  5. A message might appear, warning of an untrusted certificate. Allow the exception.

  6. Enter your log-in credentials to complete access. These are the credentials you specified when you created the instance.

    Welcome page
    Description of this image
  7. The WebLogic Server Administration Console home page is displayed.

    WebLogic Server Administration Console
    Description of this image
  8. On the Administration Console, click domain > Deployments, where domain is the domain where the application is deployed.

    Select Deployments
    Description of this image
  9. Find your application on the deployments table and verify that the status is Active.

    Active application
    Description of this image
  10. Leave the Administration Console open.

  11. Open a browser window and type the following information into the address bar:

    https://IP_addr_load_balancer/context_root_of_app

    In this example, the URL is:

    https://IP_addr_load_balancer/benefits

    The application is displayed.

    Benefits application
    Description of this image

Applying a Patch

To apply a patch, perform the following steps:

  1. Navigate to the Patching page.

  2. In the Available Patches section, click the Menu Icon menu to the right of the patch you want to apply and select Patch.

    Patching menu
    Description of this image

    Note: You can choose to run patching prechecks in order to identify and address any issues found before you attempt to patch the service instance. In this case, we choose to proceed directly to patching.

  3. In the Patch Service dialog:

    • Type a note for your reference, describing the purpose of the patch. Note: This note is required.

      Patch Service dialog
      Description of this image
    • If Oracle Coherence is enabled for your instance: Select the Confirm checkbox to override the default behavior, which is to verify the high availability status of the data stored in the Coherence data tier before shutting down a node to apply the patch.

      When Confirm is selected, know that this means there's a possibility of data loss by not requiring the services within the Coherence cluster to reach NODE-SAFE before stopping a server to apply the patch. If Confirm is not selected, understand that patching will fail if NODE-SAFE cannot be reached.

      If there's only one Managed Server on the Coherence data tier of your instance, the Confirm checkbox is selected and disabled by default.

      Note: If Coherence is not enabled, the Coherence information on this dialog does not appear.

  4. In the Patch Service dialog, click Patch.

    An hourglass is superimposed on the patch icon for the patch you are applying to show that patching is in progress.

    Patching button with hourglass icon
    Description of this image

    Note the status message shown on the Administration tile. The software will be updated to the version number shown.

    Version number on Admin Tile
    Description of this image

Verifying Your Application During Patching

  1. Return to the Deployments table on the Administration Console.

    Deployments table
    Description of this image
  2. On the Domains table, look for the status of your application.

    Active status for application
    Description of this image

    The application is still active while patching is in progress.

  3. Leave the Administration Console open.

  4. Open your browser and verify that your application is running.

    Benefits application
    Description of this image

Viewing the Backup

  1. Return to the Oracle Java Cloud Service Instance page.

  2. Click the Backup tab.The Backup page is displayed.

    Backup page
    Description of this image

    A message shows that the backup is for applying a patch.

    Backup message
    Description of this image

    If you need to restore the original state of the service instance, you can perform a restoration from the Backup page.

Verifying the Patch

  1. Click the Patching tab to return to the Patching page.

    When the patching operation completes, information about the patch is displayed in the Patch History section.

    Patch History section
    Description of this image

    A Roll Back button is displayed adjacent to the patch.

    Rollback button
    Description of this image

Verifying Your Application After Patching

After applying a patch, verify that the application you deployed is still running.

To verify that your application is running:

  1. Return to the Administration Console.

  2. Find your application on the deployments table and check that the status is Active.

    Active status for application
    Description of this image
  3. Leave the Administration Console open.

  4. Go back to your browser window and check that the application is still running.

    Application is still running
    Description of this image

Rolling Back a Patch

To roll back a patch, perform the following steps:

  1. Return to the Patching page.

    Patching page with Patch History section
    Description of this image
  2. In the Patch History section, click the Roll Back button adjacent the patch you want to roll back.

    Rollback button
    Description of this image
  3. The Roll Back Service dialog is displayed. Click Roll Back.

    Roll Back Service dialog
    Description of this image
  4. A Rolling Back... message appears on the Rollback button.

    Rolling Back... message
    Description of this image

    Note the status message on the Administration tile. The version number is shown.

    Rollback message on Admin tile
    Description of this image

    The service instance returns to the previous patch state.

    When the operation is complete, the Roll Back button in the Patch History section becomes inactive, preventing you from trying to rollback the patch again.

    Rollback button grayed out
    Description of this image

    The patch returns to the Available Patches section.

    Patch returns to Available Patches _
    Description of this image

    The Administration tile shows that the original patches are available. It also shows the last backup, which occurred during the patching operation.

    Original number of patches shown
    Description of this image

    Rolling back a patch has returned the service instance to its previous patch state.

Verifying Your Application After Rolling Back a Patch

Rollback does not undeploy your application, and in most cases the application remains running. If your application depends upon new features applied by the patch, the application remains deployed, but will not start.

To verify that your application is running:

  1. Return to the Administration Console.

  2. Find your application on the deployments table and check that the status is Active.

    Active status for application
    Description of this image
  3. Return to your browser window and check that the application is still running.

    Application is still running
    Description of this image

Want to Learn More?