Upgrade Per-Domain Node Manager To 12.1.3 On Windows Resulted in Loss Of Customized Properties In nodemanager.properties And Old Version Displayed In Console (Doc ID 2002510.1)

Last updated on APRIL 20, 2016

Applies to:

Oracle WebLogic Server - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

Node Manager was set up as per-domain on WLS 12.1.2 on Windows. Customer followed http://docs.oracle.com/middleware/1213/wls/WLUPG/toc.htm to upgrade to 12.1.3. After reconfig was completed, two issues were observed in Node Manager:

1. Reconfiguration Wizard changed nodemanager.properties file
       From:

...
CrashRecoveryEnabled=true
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityAlias=server_id
CustomIdentityKeyStoreFileName=...\\ProdIdentity.jks
CustomIdentityKeyStorePassPhrase=...
CustomIdentityKeyStoreType=JKS
CustomIdentityPrivateKeyPassPhrase=...
CustomTrustKeyStoreFileName=.\\ProdTrust.jks
CustomTrustKeyStoreType=JKS
CustomTrustKeyStorePassPhrase=...

       To:

...
CrashRecoveryEnabled=false
CustomIdentityKeyStorePassPhrase=...
CustomIdentityKeyStoreFileName=...\\ProdIdentity.jks

 

 

2. Console still shows Node Manager at version 12.1.2. The Environment -> Machines -> [Machine_Name] -> Monitoring tab showed that the node manager version was still 12.1.2.

Changes

The nodemanager.properties file for 12.1.2 was modified with CrashRecoveryEnabled=true and CustomIdentityAndCustomTrust properties.

The reconfig.cmd script in 12.1.3 was executed to reconfigure the domain to 12.1.3.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms