We have created a WebLogic Cluster (Node 1 with AdminServer and ClusterServer_1, Node 2 with ClusterServer_2). Node 1 is the server with the local drive hosting the Oracle Untility (Work and Asset Management V126.96.36.199) and presenting the drive to Node 2. When node 1 is down, the application is still up, but when trying to login, it encountered an error saying it couldn't access the keystores file in the shared drive. We have another WebLogic Cluster for Oracle Utility (Customer To Meter V188.8.131.52.0), which has identical setup, and when Node 1 down, it run authentication without trying to access the keystore file in the missing drive.
Anyone know what setup in application remove the authentication dependency on the keystore file?
We are using WebLogic 184.108.40.206.0 with Oracle Utility Customer To Meter V220.127.116.11.0 which doesn't depending on the keystores file for authentication, also Work and Asset Management V18.104.22.168, which seemed to depend on keystore file for authentication.