My Oracle Support Banner

Changes to $NMS_CONFIG/jconfig/build.properties Are Not Reflected in the NMS Client (Doc ID 2748833.1)

Last updated on FEBRUARY 26, 2021

Applies to:

Oracle Utilities Network Management System - Version 2.4.0.1.0 and later
Oracle Network Management for Utilities - DMS - Version 2.4.0.1.0 and later
Information in this document applies to any platform.

Symptoms

On : 2.4.0.1.0 version, Web Workspace

After commenting out the "option.no_force_https" option in $NMS_CONFIG/jconfig/build.properties, the NMS web workspace client is still connecting via "t3" instead of "t3s".

The client java log has two "t3" entries:

[C:\Program Files (x86)\Java\jre1.8.0_271\bin\java, -classpath, ..., -Djava.naming.provider.url=t3://<HOSTNAME>:<PORT>,...]
...
JNDI_URL = "t3://<HOSTNAME>:<PORT>"




The client should be connecting using "t3s"


Changes

 The "option.no_force_https" line in $NMS_CONFIG/jconfig/build.properties was commented out, the ear file was rebuilt (nms-install-config --java), the cesejb.ear was redeployed and the NMS managed server was restarted.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.