Oracle bundles an installer for WebLogic with their Oracle EPM suite of products, that ‘phones home’ to Oracle for more information. Many of us deal with clients who have firewalls that may block all attempts to communicate from the installation server to Oracle.com or other outside Internet addresses. In these cases, the installer for Oracle EPM informs us of the communication error and asks us to provide proxy information for the installer to communicate with Oracle.com. Refusal to grant the proxy information results in another nag screen after which we can move on with our installation.
In some cases, the client firewall may allow communication but blocks content from lb-ccr.oracle.com to the installer. The installer appears to ‘hang’ during the WebLogic installation portion of the Foundation common install, and won’t allow you to continue. Unfortunately, there is nothing in the log files to indicate what content is being blocked, and Oracle does not willingly admit this call-back occurs. The client was unable or unwilling to share what specific content was being blocked by their firewall rules.
Steps we took to attempt to resolve the issue from the server were unsuccessful. The Windows server ‘HOSTS’ file modification to re-point lb-ccr.oracle.com to another address only resulted in the installer attempting to connect using the IP address for the actual lb-ccr.oracle.com server, and another hung state. Attempts to install a stand-alone WebLogic instance to the server failed for similar reasons.
The short-term solution was to request the client create a rule to block access to lb-ccr.oracle.com via Doman Name Resolution and via direct IP addressing. As this would have caused the client issues with other Oracle product activities, we limited the rule to only apply to our specific Oracle EPM servers.The longer-term solution will be for a packet-sniffing software client to be installed on an Oracle EPM server to determine the content of the response from lb-ccr.oracle.com after the initial confirmation of connection by that host. That information will be shared with the client to assist them in determining which of their firewall rules is interfering with the pre-packaged WebLogic installer.