Ok, I try to debug with sql profiler.
Investigation shows that problem in Active/Passive cluster it gets port from ESS_FAILOVER_ACTIVE_NODE_VIEW.
For standalone servers EAS connects to the right port 6423
So the ESS_FAILOVER_LEASE_OWNER table is incorrectly populated, I thought this was driven by either the EPM registry or Essbase config, has the config been setup to only use SSL?
has the config been setup to only use SSL
Not, both ports availible, when I configured only ssl I faced problem with SharedServices application group EssbaseCluter-1 tries to connect to 1423 port, therefore I enabled both mode (secure and not secure)
I think problem not in ESS_FAILOVER_LEASE_OWNER it shows to port, secure and plain - problem in eas it takes only plain port
Hi rpc1 - your comment "when I configured only ssl I faced problem with SharedServices application group EssbaseCluter-1" - You might be able to fix that by adding those TLS statements to the FoundationServices0 (or whatever you WebLogic Managed Services name is for Shared Services). This should correct the Shared Services connection issues and you will be able to access EssbaseCluster-1:secure. You defiantly do not need to have both secure and non secure ports enabled. Sort of defeats the purpose of SSL enabling things.
The fix was to add the line:
To the Utility.bat JAVA_OPTIONS section if running LCM from a command line.
You should also modify the APS WebLogic Managed Server and FoundationServices Managed Server registry windows registry settings and add a new JVMOption and update the corresponding JVMOptionCount to increase the number to the new required value:
This allows FoundationServices (LCM) and Provider Services (APS)_ connections to downgrade their cipher level to support deprecated protocols.
iArchSolutions-Joe thanks for comment, but I make some tests, problem not in TLS,
When I have only ssl and click on the EssbaseCluster-1 application group in HSS, watch how FoundationService tried to connnect EssbaseServer:1423 instead of 6423.
I enabled SQL profiler and found that it takes port from [ESS_FAILOVER_ACTIVE_NODE_VIEW] column PORT_NUMBER. It didn't takes SECURE_PORT_NUMBER,
For the mentioned problem I changed view and set PORT_NUMBER = SECURE_PORT_NUMBER - it solved problem with EAS, but not in Shared Services.