Monday, December 8, 2014

Managed Servers don't talk to Admin Server

I have a network deployment for Hyperion BI+,Calc Man, Planning and EAS where all these components are load balanced with the exception of Essbase and it is a distributed server install, 

I ran into an issue with Weblogic where it displayed the below symptoms:

1. Hyperion Planning, EAS, CalcMan, and other things not running on the Admin Server Machine take FOREVER to startup.
2. Once started, AdminServer still shows all the remote nodes as DOWN
3. Errors in the managed server sysout files show managed servers were trying to talk to the wrong IP address to get to the Admin Server
(it was trying to use the VIP address, and not the address associated with the FQDN for the server.









On digging further, I found that the servers are multihomed, mainly due to an odd load balancer setup where there are local loopback addresses on the
admin server that are really hosted by the VIP on the LB. The managed servers were able to make an initial connection to the
admin server, and the admin server responded back with the WRONG IP (the loopback, not the public IP).

The resolution is to set the LISTEN address on the WL AdminServer "Server" to the public DNS name. example.host.domain.com
For this, Login to the WL Console and click Lock & Edit (see Use the Change Center).


On the Servers page, click the name of the server , Select Configuration > General.On the Severs: Configuration: General page, enter a value in Listen Address.



Restart AdminServer,wait for it to be fully running, Restart all the other services. 


No comments:

Post a Comment