| Installing Jive | |
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.
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.
| Component | Jive CLI Name | Port(s) | Direction | Domain(s) or IPs |
|---|---|---|---|---|
| Activity Engine | eae | TCP port: 7020 JMX port: 7021,8026 RMI ports: 33030,56844 |
Open |
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.
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 |
| 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 |
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.
| 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 | https://android.googleapis.com/gcm/send |
| Component | Port(s) | Direction | Domain(s) or IPs |
|---|---|---|---|
| Jive Present | 443 | Inbound to Jive instance | 188.93.102.111
188.93.102.112 188.93.102.115 188.93.103.35 188.93.103.36 188.93.103.37 |