Overview

When installing or upgrading Jive HOP 9.7.2 or HOP 9.8 on your on-premise environment, you notice that the setup doesn't complete successfully without access to an Internet connection.

The Admin Console webpage doesn't load after the setup ends and the sbs.log file records errors such as the following before invoking a connection to Apache httpd:

• Error creating bean with name 'resourceManager' - cannot resolve reference to Bean 'resourceManager' spring-setupWebContext.xml
• Error creating bean with name 'tagModels'

Solution

This is a known issue that was discovered in Jive HOP 9.7.2 when it is being installed in an air-gapped environment or an environment that prevents outbound connections from reaching the URL http://checkip.amazonaws.com. This URL call was used by the included loggers to get the public IP of the server as a part of Jive's legacy code and when the setup cannot resolve the IP address of this URL, it fails.

This issue was resolved in Jive HOP 9.9 with the issue key JVHOPST-55361 (release notes on Worx). Please get in touch with your Account Manager/Executive for planning and deploying a Jive upgrade.

Workarounds for Jive HOP 9.7.2 and Jive HOP 9.8

1. Whitelist the http://checkip.amazonaws.com in your environment. If you set firewall rules to allow outbound connection to the URL via a proxy server, you can run the following command on the Jive Webapp node as the Jive/new user (as you won't be able to access the admin console):
   

   jive set webapp.custom_jvm_args "-Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttp.proxyUser=jive -Dhttp.proxyPassword=1234 "

   Replace the values there for the corresponding ones in your instance; then you'll need to restart Jive by running the following command:jive restart to load the new settings. Note that even if there's no user and/or password set for the HTTP proxy, you'll still need to set these values with nothing besides it (-Dhttp.proxyUser= for example)
   
   

2. Set up Jive 9.5, then edit or add the following system properties to have a value of false and then upgrade to 9.7.2 or 9.8 as normal: ​

   jive.audit.authentication.logging.enabled
   jive.audit.email.logging.enabled
   jive.audit.email.body.logging.enabled
   jive.audit.logging.enabled

   You can verify their value of false by checking in the jiveproperty tab in the database.

3.  You can set up a simple NodeJS application (or a similar network spoofer) that runs in your infrastructure, that mimics the required URL with IP forwarding that makes Jive think it's actually talking to and getting a response from http://checkip.amazonaws.com. If you need further help with setting this up, you can contact your Account Manager/Executive to engage Professional Services. Please note that Professional Services engagements may incur additional costs.