If your Jive community is
deployed on-premise (and not hosted by Jive Software), you can change the jiveURL, which
is the Web address of your community. To change the jiveURL, go to and edit the property jiveURL. (If you want to know how
to change the root context of your community, be sure to read Changing the Root Context (optional).
Next, be sure to update the following components with the new URL.
CAUTION:
If you change the jiveURL system property from https to http
temporarily for the purpose of doing an upgrade, you will need to also
change the value of the system property jive.auth.forceSecure to false.
This system property causes a redirect of all incoming requests to https.
Note: This list may not include all relevant
considerations for your specific deployment configuration.
Component: |
How to update with the new jiveURL: |
Web Application Nodes |
Change the jiveURL system property (). Then, as the jive user, set the following:
- jive set webapp.http_proxy_name <newdomainname>
- jive set webapp.http_proxy_port 443
- jive set webapp.http_proxy_scheme https
|
SSO |
Update the base metadata URL by going to , or by editing the system property saml.baseURL
().
In addition, update the Location attribute in the metadata itself. After you have made these changes, you'll need
to restart the server. |
Mobile |
We strongly recommend that your Mobile Gateway Access URL matches the jiveURL (this is not required,
however). If you change the jiveURL, update the Gateway Access URL to reflect the change
(). |
SSL/Tomcat |
Update the new URL in the server.xml file for the Tomcat connector. |
Apache |
Ensure that any redirects you have configured previously are reconfigured to point to the new URL. |
Jive for Office and Outlook plugins |
Ensure that the account configured in the Jive for Office/Outlook plugin contains
the new URL (even if the change was due to adding SSL support). |
Emoticons |
Update the URL setting for the emoticon post-processing filter (). |