Oracle SOA Suite Domain Release Upgrade

This section describes how to upgrade Oracle SOA Suite domains from release 12.2.1.4 to 14.1.2.0.

Prerequisites

Before starting the automated domain upgrade, complete the following prerequisites:

  • Ensure that the servers in the domain can be stopped. Shut down the Administration Server and all co-located managed servers before the upgrade.
  • Back up all affected data.
  • Back up the domain home.
  • Ensure that the database version is certified by Oracle for the Fusion Middleware upgrade.
  • Ensure that the environment meets the required certifications and system requirements.
  • Review Secure Mode Disabled by Default in Upgraded Environment for scenarios affected by the upgrade.

Prepare to use the domain upgrade scripts

The sample scripts for automating Oracle SOA Suite schema and domain home upgrades are available at ${WORKDIR}/domain-upgrade.

Edit domain-upgrade-inputs.yaml (or a copy of it) to provide the domain upgrade details.

See the configuration parameters below for the information required in this file.

Configuration parameters

If SSL is disabled in the source environment, you cannot enable secure mode directly during the upgrade. Do not set secureEnabled to true, because this causes unexpected behavior. To enable a secure domain:

  1. Upgrade to a non-secure 14.1.2 domain using the domain upgrade scripts.
  2. After the upgrade, when the servers are up and running, follow the steps in Enable secure domain post upgrade.

If SSL is enabled in the source environment, you can set secureEnabled to true to enable a secure domain during the upgrade.

You can provide the following parameters in the inputs file:

Parameter Definition Default
domainHome Home directory of the Oracle SOA Suite domain. /u01/oracle/user_projects/domains/soainfra
domainPVMountPath Mount path of the domain persistent volume. /u01/oracle/user_projects
domainUID WebLogic Server domain name. soainfra
image Oracle SOA Suite 14.1.2 container image. soasuite:release-version
imagePullPolicy Oracle SOA Suite container image pull policy. Valid values are IfNotPresent, Always, and Never. IfNotPresent
imagePullSecretName Name of the Kubernetes secret used to access the container registry and pull the Oracle SOA Suite container image. The presence of the secret is validated when this parameter is specified.  
namespace Kubernetes namespace of the domain. soans
persistentVolumeClaimName Name of the persistent volume claim used for the domain home. soainfra-domain-pvc
rcuSchemaPrefix The schema prefix. SOA1
rcuDatabaseURL The database URL. "xxxxx.example.com:1521/xxxxx.example.com"
rcuCredentialsSecret The Kubernetes secret containing the database credentials. soainfra-rcu-credentials
secureEnabled Boolean indicating whether secure mode is enabled for the domain. false

Run the domain upgrade script

Run the domain upgrade script, specifying your inputs file and an output directory for the generated artifacts:

$ cd domain-upgrade
                $ ./domain-upgrade.sh \
                -i domain-upgrade-inputs.yaml \
                -o <path to output-directory>
            

The script performs the following steps:

  1. Stops the domain.
  2. Creates a pod using the 14.1.2 image and the domain home's persistent volume claim to perform the domain upgrade.
  3. Performs the UA schema upgrade.
  4. Performs the domain home upgrade.
  5. Sets the database values for the new WLS_RUNTIME schema.
  6. Enables a secure domain if secureEnabled is set to true.
  7. Updates the domain specification with the 14.1.2 image.
  8. Starts the domain and waits for it to be up and running with the 14.1.2 image.

All upgrade checkpoints and logs are captured in the upgrade_<domainUID> directory under the domain home root (the mount path of the domain persistent volume).

Upgrade ingress

This step is required if you set secureEnabled to true during the domain upgrade. For a secure domain, only sslType=E2ESSL is supported.

If the ingress controller is not configured to support E2ESSL (for example, an NGINX controller), recreate it with the required support. Then run helm upgrade to update the ingress-per-domain release with --set wlsDomain.secureEnabled=true. For example:

 $ cd $WORKDIR
                $ helm upgrade REPLACE-WITH-INGRESS-PER-DOMAIN-RELEASE-NAME charts/ingress-per-domain \
                --reuse-values --set wlsDomain.secureEnabled=true 
            

Enable secure domain post upgrade

Perform the following steps to enable a secure domain in a non-SSL Oracle SOA Suite 14.1.2 domain:

  1. Connect to an Administration Server using the WebLogic Remote Console.
  2. In the Edit Tree, navigate to Environment > Domain and enable the Secured Production Mode toggle on the Domain screen.
  3. Click Save.
  4. In the Edit Tree, navigate to Environment > Servers > AdminServer.
  5. Verify that SSL Listen Port Enabled is enabled. Set SSL Listen Port to 7002 and Local Administration Port Override to 9002.
  6. Click Save.
  7. In the Edit Tree, navigate to Environment > Servers > soa_server1.
  8. Set SSL Listen Port to 7004 and Local Administration Port Override to 9004.
  9. Click Save.
  10. Set SSL Listen Port to 7004 and Local Administration Port Override to 9004 for all SOA managed servers in the cluster (for example, soa_server2, soa_server3, soa_server4, and soa_server5).
  11. If your domain has an Oracle Service Bus cluster, navigate to Environment > Servers > osb_server1. Set SSL Listen Port to 8003 and Local Administration Port Override to 9007.
  12. Click Save.
  13. Similarly, set SSL Listen Port to 8003 and Local Administration Port Override to 9007 for all OSB servers in the cluster (for example, osb_server2, osb_server3, osb_server4, and osb_server5).
  14. After updating and saving, click Commit changes under Click to view shopping cart actions.
  15. Fully shut down and restart the domain. See Full Domain Restarts for more information.

Note:

After you enable Secured Production Mode, the existing ingress used to access the domain URLs no longer works. See Upgrade ingress for more information.