Weblogic Server Upgrade from 12.2.1.2 to 12.2.1.3

Oracle WebLogic Server Upgrade from 12.2.1.2 to 12.2.1.3

Applies To: Oracle Fusion Middleware - Version 12.2.1.2.0

Information in this document applies to any platform.

Goal: Goal of this document is to upgrade WebLogic Server from 12.2.1.2 to 12.2.1.3

What's New in Oracle WebLogic Server 12c (12.2.1.3.0):

Feature

Description

Service Restart In Place

Service Restart In Place adds support for the ability to use any custom store with any migration policy.

Message limit in a JMS message subscription

WebLogic JMS adds a message limit option to help prevent individual overloaded subscriptions from using up all available resources

Security

New features include:

The WebLogic Security Service adds the secured production mode feature, which helps ensure a highly secure environment for applications and resources. See Support for Secured Production Mode.

A new security provider, Oracle Identity Cloud Integrator, that is an authentication and identity assertion provider that can access users, groups, and Oracle Identity Cloud Service scopes and application roles stored in the Oracle Identity Cloud Service.

Use of the SHA2 signature algorithm as the default for signing requests and responses. For backward compatibility, set the com.bea.common.security.saml2.useSHA1SigAlgorithm to true. 

By default, certificates that are expired or not yet valid are no longer used in SAML signing. To allow use of these certificates, set the com.bea.common.security.saml2.allowExpiredCerts to true.

Zero Downtime Patching

ZDT Patching adds support for modifying workflows using custom hooks.

Applied Patches List

Oracle WebLogic Server adds the ability to obtain a list of patches that have been applied to a server instance.

JDBC data sources

New features include:

Shared pooling for WebLogic data sources. Shared pooling provides the ability for multiple data source definitions to share an underlying connection pool.

Additional integration support for several new Oracle Database 12.2 features.

Initial Capacity Enhancement in the Connection Pool. WebLogic Server 12.2.1.3 enhances creation of initial capacity connections in a data source by providing control over connection retry, early failure, and critical resources.

JTA

WebLogic JTA adds transaction guard, which provides at-most-once execution during planned and unplanned outages and prevents duplicate submissions. See Transaction Guard.

Temporary Configuration Overriding

Temporary configuration overriding lets administrators place configuration information, contained in an XML file, in a known location where running servers identify and load it, overriding aspects of the existing configuration.

Apache Ant

This patch set release of WebLogic Server now includes Apache Ant 1.9.8, which may have an impact on the use of the clientgen Ant task. See Upgraded Version of Apache Ant in Upgrading Oracle WebLogic Server.

JEP 290

WebLogic Server uses the JDK JEP 290 mechanism to filter incoming serialization data and prevent denial of service (DOS) attacks. See JEP 290 Utilization.

Deprecated components

The following components are deprecated in this patch set and will be removed in a future release of WebLogic Server:

The following WebLogic JMS features and components:

·         WebLogic Replicated Store, which is intended solely for use in Oracle Exalogic Elastic Cloud environments

·         JMS resource adapter

·         WebLogic JMS Automatic Reconnect

·         WebLogic JMS Application Modules for Deployment

WebLogic SAF Agent support for JAX-RPC Reliable Messaging

EJBGen utility

The AnonymousAdminLookupEnabled attribute on the SecurityConfigurationMBean

The RESTful management resources listed in Deprecated RESTful Management Features.

Solution: Upgrade can be performed by running the Reconfiguration Wizard only.   It is not necessary to run the Upgrade Assistant (UA) for schemas or configuration upgrades.

1.      Install WebLogic Server 12.2.1.3.0 in a new Oracle home.

2.      Run the Reconfiguration Wizard to upgrade your domain. Document below has detailed information about Reconfiguration Wizard:

Fusion Middleware Upgrading Oracle WebLogic Server

https://docs.oracle.com/middleware/12213/wls/WLUPG/upgrade_dom.htm#WLUPG384

Before that we have to upgrade java jdk version

[oraweb@orawlda1 ~]$ java -version

java version "1.8.0_112"

Java(TM) SE Runtime Environment (build 1.8.0_112-b15)

Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)

Take the Domain Backup

[oraweb@orawls u01]$ cp -r oraweb/ oraweb/oraweb_backup/

Reference Docs:

How to Install WebLogic 12.2.1.3 and Create the Domain (Doc ID 2329789.1)

How To Replicate WebLogic 12c (12.2.1.3.0) Standalone Installation onto Remote Linux Server Without XServer? (Doc ID 2535666.1)

How To Upgrade WebLogic Server From 12.2.1.1 To 12.2.1.3？ (Doc ID 2391980.1)

https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.3/wlsig/installing-oracle-weblogic-server-and-coherence-software.html#GUID-5C7D4437-46A2-45A2-85F3-738B0DFE9AE2

Existing System Properties:

/u01/oraweb/products/fmw_12.2.1

/u01/oraweb/config/domains

/u01/oraweb/config/applications

[oraweb@orawls applications]$ echo $ORACLE_HOME

/u01/oraweb/products/fmw_12.2.1

[oraweb@orawls applications]$ echo $DOMAIN_HOME

/u01/oraweb/config/domains/fra_domain

[oraweb@orawls applications]$ echo $JAVA_HOME

/u01/oraweb/jdk/current_ver

[oraweb@orawls jdk]$ ls

current_ver  jdk1.8.0_112  jdk-8u112-linux-x64.tar.gz

[oraweb@orawls jdk]$ pwd

/u01/oraweb/jdk

[oraweb@orawls ~]$ vi .bash_profile

export JAVA_OPTIONS="-Djava.security.egd=file:/dev/./urandom ${JAVA_OPTIONS}"

# Oracle sourcing for Forms / Reports Install

export TNS_ADMIN=/u01/$USER/config/domains/fra_domain/config/fmwconfig

export ORACLE_HOME=/u01/$USER/products/fmw_12.2.1

export FORMS_PATH=/u01/$USER/products/fmw_12.2.1/forms

export PATH=$ORACLE_HOME/OPatch:$PATH

export PATH=$JAVA_HOME/bin:$ORACLE_HOME/bin:$FORMS_PATH/bin:$PATH

export PATH=$ORACLE_HOME/oracle_common/common/bin/:$PATH

# end of Oracle sourcing for Forms / Reports Install.

# Set $ORACLE_SID for custom written scripts.

export ORACLE_SID=WEB

# Oracle sourcing for Weblogic rda tool.

export DOMAIN_HOME=/u01/$USER/config/domains/fra_domain

# End of Oracle sourcing for Weblogic rda tool.

PATH=$PATH:$HOME/bin

export PATH

[oraweb@orawls applications]$ echo $PATH

/u01/oraweb/products/fmw_12.2.1/oracle_common/common/bin/:/u01/oraweb/jdk/current_ver/bin:/u01/oraweb/products/fmw_12.2.1/bin:/u01/oraweb/products/fmw_12.2.1/forms/bin:/u01/oraweb/products/fmw_12.2.1/OPatch:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/oraweb/bin

Create a complete backup copy of your existing deployment.

Complete all of the required pre-upgrade tasks for your environment.

Pre-Upgrade Checklist in component upgrade guides

Install the product distributions in a new Oracle home.

Oracle Universal Installer (OUI)

Run a pre-upgrade readiness check to determine if your deployment is ready to be upgraded.

Upgrade Assistant (UA)

Create new schemas for your Fusion Middleware components.

Use the Repository Creation Utility (RCU) for schemas that require custom settings such as additional tablespace size, for example.

Or:

Use the Upgrade Assistant to create missing or required schemas using the default schema settings. Schemas are created during the upgrade process.

Upgrade the 11g or previous 12c database schemas for the components you will be upgrading.

Upgrade Assistant (UA)

Reconfigure the domain.

Reconfiguration Wizard

Upgrade component configurations.

Upgrade Assistant (UA)

Perform all required post-upgrade tasks.

Verify that the upgrade is successful. At a minimum, verify that the servers and node manager start and your applications functions as expected.

Moved the files fmw_12.2.1.3.0_infrastructure_Disk1_1of1 and jdk-8u131-linux-x64.tar to the server and unzip at the desired location.

Before you upgrade, you must backup your domain folders and shut down all servers in the application environment.

(Reference: https://docs.oracle.com/cd/E23943_01/web.1111/e13754/roadmap.htm#WLUPG123)

Jdk Upgrade:

we will upgrade from JDK version 1.8.0_112 to 1.8.0_131 and we have a Linux 64 bit environment.

Make sure weblogic server and admin server are all stopped before following the below steps (nohup $DOMAIN_HOME/bin/stopWebLogic.sh &)

·         Download JDK, copy it to the server and unzip it.

[oraweb@orawls jdk]$ ls -ltrh

total 352M

-rwxr--r-- 1 oraweb oinstall 175M Apr 17  2017 jdk-8u112-linux-x64.tar.gz

lrwxrwxrwx 1 oraweb oinstall   30 Apr 17  2017 current_ver -> /u01/oraweb/jdk/jdk1.8.0_112

drwxr-xr-x 8 oraweb oinstall 4.0K Sep  7  2018 jdk1.8.0_112

-rwxr--r-- 1 oraweb oinstall 177M Oct 31 14:02 jdk-8u131-linux-x64.tar.gz

[oraweb@orawls jdk]$ tar -xvnzf jdk-8u131-linux-x64.tar.gz

Symbolic link changed to point to new version

ln -nfs jdk1.8.0_131/ current_ver

Update the Java Home path in following files

ORACLE_HOME/oui/.globalEnv.properties

DOMAIN_HOME/bin/setNMJavaHome.sh  

DOMAIN_HOME/nodemanager/nodemanager.properties

DOMAIN_HOME/bin/setDomainEnv.sh 

Now start the admin server

[oraweb@orawls products]$ export DISPLAY=”172.22.23.27:10.0”

Ran the below command through VNC server to launch GUI

$ $JAVA_HOME/bin/java -jar fmw_12.2.1.2.0_infrastructure.jar

ADF managed server details

Installing and Configuring Oracle Forms and Reports

Download the software

unzip fmw_12.2.1.3.0_fr_linux64_Disk1_1of2.zip

./fmw_12.2.1.3.0_fr_linux64.bin

Give the JAVA_HOME as jdk_home

Now run the upgrade assistant ua from the new home

Password: adminpw

Start NodeManager from backend. Got error as it is already running. Shutdown the weblogic server admin. Kill all the processes running on the node. Start weblogic admin.

Check NodeManager Properties file. Commented SecureListener parameter or make it false and start the NodeManager now. Go to the weblogic console and start the managed servers one by one.