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 Apps Market service, the Recommender service, and, if you use them, the Mobile Gateway, Search and Video services. The following sections provide the ports and addresses you'll use when ensuring your firewall can access the correct ports and domains for these services. They also provide some pointers for successful setup.
General Best Practices
For all these components, you need to ensure that your proxy server is configured to access resources outside the firewall. See Connecting Through a Proxy Server for more information.
Recommender Service
Make sure your Activity Engine servers can connect through the firewall using the following settings.
Component | Jive CLI Name | Port(s) | Direction | Domain(s) or IPs |
|---|---|---|---|---|
Activity Engine | eae | TCP port: 7020JMX port: 7021,8026 RMI ports: 33030,56844 | Open |
After installation is complete, you can check the status each Activity Engine's connection to the Recommender service using the Activity Engine page in the Admin Console. Navigate 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 about the benefits of Jive Cloud Search, see About Cloud Search.
On-Premise Search uses the On-prem search service installed in your Jive environment.
The following table shows which ports and domains are required so the web application nodes can contact the Search service:
Component | Jive CLI Name | Port(s) | Direction | Domain(s) or IPs |
|---|---|---|---|---|
Cloud Search Service | 443 | Outbound | directory-service.phx1.jivehosted.com or directory-service.ams1.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. Navigate to System > Settings > Search 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.
Apps Market Service
Make sure the following ports and domains are enabled so the web application nodes can contact the Market.
| Component | Jive CLI Name | Port(s) | Direction | Domain(s) or IPs |
|---|---|---|---|---|
| Jive Apps Market | 80 or 443 | Outbound | market.apps.jivesoftware.com, gateway.jivesoftware.com, apphosting.jivesoftware.com, developers.jivesoftware.com |
After you complete your Jive installation, make sure you have enabled the legacy REST services under System > Settings > Web Services > Legacy Web Services and the Core API under System > Settings > Web Services > Core API. Complete instructions for setting up and troubleshooting your connection to the Apps Market service can be found under Setting Up Apps.
Note that if you relocate an instance by changing the jiveURL, and you then enable and disable the Apps Market on the instance, the Market restarts with a new ID for the instance. Installed Apps from before the jiveURL changed may be lost or work incorrectly. The correct path is to relocate the instance with the Market enabled, so that the ID remains the same.
Mobile Push Service (optional)
If you plan to have your community members receive Jive push notifications, you'll 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 | Port(s) | Direction | Domain(s) 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 |
| 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 |
Video Service
Setting up the firewall for video is complex. For complete information, see the Jive Video Help listed separately on our main documentation page.