How to Overcome Self-signed Certificate trust issue during Application Server Upgrade (Doc ID 1011566.1)

Last updated on APRIL 28, 2023

Applies to:

Symptoms

The following are the two scenarios in which an upgrade is performed:

Side-by-side Upgrade : The source server and the target server are
installed on the same machine , but under different install locations.
You can choose to perform this type of upgrade if you wish to have the
configuration corresponding to these installations on the same machine
in different locations.

In-place Upgrade: The target server is installed in the same installation
location as the source server. You can choose to perform this type of upgrade
if you wish to install the configuration (that is, the domains ) in the same
location as before. In this scenario, you install the binaries in the same
location as the existing binaries using the installer. After installation,
if you select the Upgrade checkbox during installation, the installer invokes
the upgrade tool , pre-populating it with the source domains directory and
target server directory. In this type of upgrade, you provide the source
domains root and all the domains under this domains root are upgraded.
If you have created multiple domains roots that are customized, you need
to specify each of these domains root for upgrading the domains under them.

Before Upgrade one should be aware that Enterprise Edition (EE) Class
Application Server (E.g 8.2 EE) uses Network Security Services (NSS) to
manage security database that stores the keys and certificates, where as
Platform Edition (PE) class Application Server (E.g 8.2 PE) on the server
side, uses Java Keystore (JKS) to manage it's security database.

After Upgrade from PE to EE edition and then starting the Domain, one may
encounter the following below strange message requesting to trust the
self-signed certificate in server.log and eventually this could fail the
domain and it's services to start-up successfully

Message Trace:

Changes

Cause