Preparing to connect to Jive Hosted services

To ensure a successful installation, you need to make sure you can connect successfully to several component services that are hosted by Jive.

In addition to the Core components of Jive that you install on your own servers, running Jive requires connections through your firewall to the Recommender service, and, if you use them, the Mobile Gateway, Search and Video services. The following sections provide the ports and addresses you use when ensuring your firewall can access the correct ports and domains for these services.

General best practices

For all these components, you need to ensure that your proxy server is configured to access resources outside the firewall. For more information, see Connecting through proxy server.

Jive Core components

Component Jive CLI name Ports Direction Domains or IPs
Jive Core (Hosted only) when connecting to custom services behind a firewall1      

AWS US-East-1 Region: 34.192.45.122, 34.198.91.162, 34.231.78.214, 34.225.172.123, 34.193.143.104, 52.55.123.87, 52.20.222.9, 34.230.231.2, 34.197.60.63, 52.207.30.159, 3.213.1.211

AWS EU-West Region: 54.154.171.198, 108.129.50.14, 52.31.199.172, 34.247.7.187, 34.252.244.183, 52.211.222.108, 63.33.30.202

Recommender service

Make sure your Activity Engine servers can connect through the firewall using the following settings.

Component Jive CLI name Ports Direction Domains or IPs
Activity Engine eae TCP port: 7020

JMX port: 7021,8026

RMI ports: 33030,56844

 Open  

After installation is complete, you can check the status of each Activity Engine's connection to the Recommender service by using the Activity Engine page in the Admin Console.

  • Go to System > Settings > Activity Engine and check the Recommender column of the Activity Engine Overview table.

Note that if you relocate an instance by changing the jiveURL, and you then enable and disable the Recommender on that instance, the Recommender restarts with a new ID for the instance. Recommendations from before the jiveURL changed will be lost.

Search service

With an on-premise installation, you can choose from either Jive Cloud Search or On-Premise Search.

The Jive Cloud Search offers socially contextual search and requires a simple support case to whitelist your IP Addresses. Jive Cloud and Hosted both use Cloud Search. For more information, see Cloud Search service.

On-Premise Search uses the On-Premise search service installed in your Jive environment. For more information, see On-Premise Search service.

The following table shows which ports and domains are required so the web application nodes can contact the Search service.

Component Jive CLI name Ports Direction Domains or IPs
Cloud Search service   443 Outbound

US customers only:
search-ingress-adapter.aws-us-east-1-prod.svc.jivehosted.com
search-query.aws-us-east-1-prod.svc.jivehosted.com

EU customers only:
search-ingress-adapter.aws-eu-west-1-prod.svc.jivehosted.com
search-query.aws-eu-west-1-prod.svc.jivehosted.com
On-Premise Search service search-service

Service port: 30000

Debug port: 27001

JMX port: 27002

 Open localhost

You can check the status and connection to the Search service using the Search page in the Admin Console.

  • Go to System > Settings > Search and check the Search service settings.

You can also use the Admin Console's Search page to make changes to the location or type of Search service. If you change the type of search service (Cloud Search or On-Premise Search), you need to perform a full index rebuild. For more information, see Selecting Search service.

Mobile Push service (optional)

If you plan to have your community members receive Jive push notifications, you need access to the Jive Mobile Push service. Make sure the following ports and IPs are enabled so the web application nodes can contact it.

Component Ports Direction Domains or IPs
Mobile (all locations, including EMEA) when you are sending push notifications to the publicly available apps 443 Outbound from Jive instance mobilepush.prod.jiveon.com (204.93.64.255 and 204.93.64.252)
Mobile (all locations, including EMEA) when you are using your custom branded iOS app with your own push notification certificate

TCP port 5223 (used by devices to communicate to the APNs servers)

TCP port 2195 (used to send notifications to the APNs)

TCP port 2196 (used by the APNs feedback service)

TCP Port 443 (used as a fallback on Wi-Fi only, when devices are unable to communicate to APNs on port 5223)

 Outbound from Jive instance  
Mobile (all locations, including EMEA) when you are using your custom branded Android app with your own Google Cloud Messaging key 443 Outbound from Jive instance https://android.googleapis.com/gcm/send

Video service

Setting up the firewall for video is complex. For more information, see Configuring video.

1 This applies to Hosted communities only. If your organization utilizes whitelisting to connect your Jive instance to your organization's services behind a firewall, you need to whitelist the IPs as specified. This may be required, for example, if your Jive community is configured for LDAP directory syncing, and you utilize a whitelist on your firewall to allow your Jive community to connect to it.