Version 9



    This document outlines the process for performing an assessment of your On-Premise environment in preparation for migrating to a Jive Hosted or Jive Cloud instance. This assessment will help you gather important details about your environment that need to be noted in the Migration Project document that Jive creates in your support group on the Jive Community after you request a migration. Jive Hosting and Environment Management will use the details you provide to help coordinate a migration plan that helps minimize the risk of unforeseen issues.



    The table below includes a section for each item which is impacted during a migration and correlates to a field on the Migration Project document. Please follow the list of Assessment Checks to gather details about the environment and update the Migration Project document in your group with your findings, according to the Document Entry column on the right. Some items will also have a Developer field in the Migration Project document; these items are customizations which we need to know the developer for, such as Jive Professional Services, a third party, or your organization.



    Assessment Checks

    Document Entry
    Site URLThis is the URL used to navigate to your community.Supply exact URL.
    Current WAR/RPM Version

    You can confirm your version by logging in to the Admin Console and looking in the upper right corner for a small version notation.

    Exact version


    This is assumed knowledge, but if you are unsure if you have a custom WAR, it is defined as a deployed package that replaces core files which are not part of a plugin or theme. Please note that custom WARs are not supported in Jive Cloud.

    Standard or Custom


    Note: Themes built with the Jive Theme Builder are not considered custom and should migrate seamlessly into your new environment.

    1. Log in to your Admin Console and navigate to System > Settings > Theme.
    2. If you do not see a specifically labeled theme, or only see a "Global Theme Map" there are no customizations.
    None or Custom


    Checking for SSO varies based on the Jive version you are running:

    • Pre 5.0 Sites: Check for an installed plugin with 'SSO' in the name.
    • 5.0+ Sites:
      • Check for an installed plugin with 'Ratpack' or 'SSO' in the name.
      • Log in to the Admin Console and navigate to People > Settings > Single Sign On
        • Check the SAML and Kerberos tabs for the Enabled option to be marked.
    Yes or No


    Log in to the Admin Console and navigate to System > Management > System Properties: Look for the ldap.searchFilter property to be present.

    Yes or No


    We don't expect On-Premise customers to have a VPN, but you may consider purchasing one with Jive for your new Hosted environment (VPNs are not supported in Jive Cloud) if you plan to use the Sharepoint Connector or AD/LDAP integration (Jive for SharePoint does not require a VPN). Please note on the Migration Project document whether you will want to set up a VPN.

    Yes or No


    There are two types of SSL that need to be checked for: Forced SSL (most common), and SSL for Logins & Registrations Only. Here are the methods to check for each:

    • Forced
      1. Log into a single web app node and navigate to /jiveHome/conf/server.xml.
      2. Look for the snip scheme="https" under the Service Name > Connector segment. Example:
        • Cloud Admin   View Log   jiveHome conf server.xml  on  telvent utilities group .png
      3. If this is present, the environment has this type of SSL.
    • Logins & Registrations:
      • Log in to the Admin Console and navigate to System > Management > System Properties and look for the property 'jive.auth.forceSecure':
        • True: Environment has this type of SSL.
        • False, or no property: Environment doesn't have this type of SSL.

    Please Note: As of Jive 7, Forced SSL is required on our Hosted and Cloud environments. If you do not currently have Forced SSL, our Hosting team will work to help you get it set up on your new environment. For more information please see The specified item was not found..

    Yes or No

    Vanity URL

    Your Jive Hosted environments will be given a standard URL with the or domain (E.g. We assume On-Premise customers will have their own URL they wish to continue using, which will require an update to your DNS to point to the Jive Hosted URL. It's important to note that root domains ( are not supported; Vanity URLs pointing to Jive require a subdomain ( For more information on setting a Vanity URL to point to Jive please see this document: SSL, Vanity URLs, and Akamai Information Sheet .

    Update the Migration Project document based on whether you will want to use a Vanity URL, and include the desired URL if so.

    Yes w/URL or No

    Akamai or other Content Delivery Network (CDN)

    • Akamai and other CDN's require a Vanity URL, so if your environment does not have one, it is not using a CDN.
    • If there is a Vanity URL, you can confirm if a CDN is actually being used with an nslookup of that URL:
      • No CDN will return your site URL as the Name.
      • With a CDN will return an address from the CDN as the Name, such as
        • Example NS Lookup Output:
          • Non-authoritative answer:Name:  Address:
    Yes or No

    Session Timeout

    Check under /usr/local/jive/applications/customer_name/application/WEB-INF/web.xml to find the session timeout setting (Ex: 60).

    Enter the actual timeout setting


    • Look for any customizations to ~jive/var/www/robots.txt.
    • By default the file will look like this:

    User-agent: *

    Crawl-Delay: 30

    Disallow: /servlet/JiveServlet/download/

    Yes or No

    Look for the presence of any files under /usr/local/jive/applications/[instance name]/home/etc.

    Yes or No
    Apache RewritesThis is assumed knowledge, as Apache Rewrites can reside anywhere in the Apache configuration on your webapps, so there is no guaranteed formula we can provide to check if they exist.None, or list all

    Analytics Database Size

    You can run the following query against your Analytics Database to get the size of all tables, and the sum of those tables will give you the database size:

        pg_size_pretty(table_size) AS table_size,
        pg_size_pretty(indexes_size) AS indexes_size,
        pg_size_pretty(total_size) AS total_size
    FROM (
            pg_table_size(table_name) AS table_size,
            pg_indexes_size(table_name) AS indexes_size,
            pg_total_relation_size(table_name) AS total_size
        FROM (
            SELECT ('"' || table_schema || '"."' || table_name || '"') AS table_name
            FROM information_schema.tables
        ) AS all_tables
        ORDER BY total_size DESC
    ) AS pretty_sizes
    The size of your DB in Gigabytes.

    Instance Sizing

    Please provide the following information to allow us to properly size your Hosted instance:

    • Current number of active users.
    • Average monthly page views for the past 3 months.
    See left.


    Investigate /usr/local/jive/applications/customer_name/application/WEB-INF/lib for a list of any installed fixpacks.

    List the JAR file name(s) for any found, or enter None.


    The Migration Project document includes a list of all Jive-Supported and Community plugins. Please follow these instructions to update the document to reflect your environment.

    1. Review the list in comparison to your environment and delete the table row for any Jive plugins you do not have installed so all that remains is what you wish to have included on your Jive Hosted environment.
    2. Add rows under the Custom Plugins section to include any that you may have installed.
    3. Use the Notes field to let us know if you do not plan to continue using a plugin, or wish to start using one you do not have installed yet.



    • The links on each plugin name in the document are intended for Jive use; you will not be able to access some of them.
    • Jive will install the latest version of all Jive and Community plugins to your Hosted environment during the setup process.
    See left.