|
1 | 1 | +++ |
2 | 2 | title = "Upgrade managed domains" |
3 | | -date = 2023-10-05T16:43:45-05:00 |
| 3 | +date = 2019-02-23T17:39:00-05:00 |
4 | 4 | weight = 6 |
5 | 5 | pre = "<b> </b>" |
6 | | -description = "Upgrade managed domains to a higher, major version." |
| 6 | +description = "Upgrade managed domains, general and specific guidelines." |
7 | 7 | +++ |
8 | 8 |
|
9 | | - |
10 | | -This document provides guidelines for upgrading WLS and FMW/JRF infrastructure domains to a higher, major version. |
11 | | - |
12 | | -In general, the process for upgrading WLS and FMW/JRF infrastructure domains in Kubernetes is similar to upgrading domains on premises. For a thorough understanding, we suggest that you read the [Fusion Middleware Upgrade Guide](https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/asmas/planning-upgrade-oracle-fusion-middleware-12c.html#GUID-D9CEE7E2-5062-4086-81C7-79A33A200080). |
13 | | - |
14 | | -**Before the upgrade**, you must do the following: |
15 | | - |
16 | | -- If your [domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}) is Domain on Persistent Volume (DoPV), then back up the domain home. |
17 | | -- If your domain type is `JRF`: |
18 | | - - Back up the JRF database. |
19 | | - - Back up the OPSS wallet file, this allows you to reuse the same JRF database schemas if you need to recreate the domain. |
20 | | - |
21 | | - The operator provides a helper script, the [OPSS wallet utility](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/scripts/domain-lifecycle/opss-wallet.sh), for extracting the wallet file and storing it in a Kubernetes `walletFileSecret`. In addition, you should save the wallet file in a safely backed-up location, outside of Kubernetes. For example, the following command saves the OPSS wallet for the `sample-domain1` domain in the `sample-ns` namespace to a file named `ewallet.p12` in the `/tmp` directory and also stores it in the wallet secret named `sample-domain1-opss-walletfile-secret`. |
22 | | - |
23 | | - ``` |
24 | | - $ opss-wallet.sh -n sample-ns -d sample-domain1 -s -r -wf /tmp/ewallet.p12 -ws sample-domain1-opss-walletfile-secret |
25 | | - ``` |
26 | | -
|
27 | | -- Make sure nothing else is accessing the database. |
28 | | -- **Do not delete** the domain resource. |
29 | | -
|
30 | | -{{% notice note %}} According to My Oracle Support [Doc ID 2752458.1](https://support.oracle.com/epmos/faces/DocumentDisplay?id=2752458.1), if you are using an FMW/JRF domain and upgrading from 12.2.1.3 to 12.2.1.4, then before upgrading, you do _not_ need to run the Upgrade Assistant or Reconfiguration Wizard, but we recommend moving the domain to a persistent volume. See [Move MII/JRF domains to PV]({{< relref "/managing-domains/model-in-image/move-to-pv.md" >}}). |
31 | | -{{% /notice %}} |
32 | | -
|
33 | | -To upgrade WLS and FMW/JRF infrastructure domains, use the following procedure. |
34 | | -
|
35 | | -1. Shut down the domain by patching the domain and/or cluster spec `serverStartPolicy` to `Never`. For example: |
36 | | - ``` |
37 | | - $ kubectl -n sample-domain1-ns patch domain sample-domain1 --type=json -p='[ {"op": "replace", "path": "/spec/serverStartPolicy", "value": "Never"}]' |
38 | | - ``` |
39 | | -
|
40 | | -2. After the shutdown completes, upgrade the base image in the domain resource YAML file and redeploy the domain. |
41 | | -
|
42 | | - You can patch the domain resource YAML file, update the base image and change `serverStartPolicy` to `IfNeeded` again, as follows: |
43 | | -
|
44 | | - ``` |
45 | | - $ kubectl -n sample-domain1-ns patch domain sample-domain1 --type=json -p='[ {"op": "replace", "path": "/spec/serverStartPolicy", "value": "IfNeeded"}, {"op": "replace", "path":"/spec/image", "value":"<New WebLogic or Fusion Middleware base image>"]' |
46 | | - ``` |
| 9 | +{{% children style="h4" description="true" %}} |
0 commit comments