Version 8


    Overview

    This document will go over the process for migrating from an On-Premise to Hosted or Jive-n/Jive-x instance, and provide you with all the general details you need to know before beginning. Please read through this document carefully and in its entirety; it outlines in detail what the process is, what you can expect, when you can expect it, and what we expect from you.


    Getting Started

    The first step is to understand the critical pieces of information that are required by Jive to begin the process. Once a migration case is created we will ask you for the following information:

    • Cutover Date
      • If you have a specific constraint regarding the cutover date, it is critical to communicate this at the start of the process so we can make sure our expectations are aligned with yours.
    • Data Transfer Method
      • You will need to determine the method of transfer for your data. Our preference is for you to provide an SFTP location for us to download your data from.


    Process

    The On-Premise to Hosted or Jive-n/x migration process is fairly straight forward:

    1. Jive Hosting will request a transfer of your Postgres database.
    2. We will then schedule and perform a Test-Run of the migration process on your new hosted instance.
    3. Once the Test-Run has been completed we will schedule a final Go-Live of your Hosted site.

     

     

    Scheduling

    • Migrations are performed by Jive Hosting during the following hours: Monday thru Friday from 1am to 6pm PT. Some flexibility may be available based on the Hosting team's discretion.
    • The entire process can take anywhere from 90 minutes to several hours or more, depending on the database size. Most communities are within a 2-6 hour range.
    • Once a Test-Run of your migration is completed, we will coordinate the timing of the Go-Live with you. We typically require 2-4 weeks notice to secure a preferred time slot for the Go-Live.

     

    Requirements and Considerations

    Below are the requirements and considerations to take into account when planning an On-Premise to Hosted migration.  Please review and address any applicable items.

     

    ItemDetail
    Required Assets
    Database
    • Required Databases:
      • Application Database
      • Analytics Database
      • EAE
        • Only needed for versions 5.x+
    • Supported Database Format:
      • Only Postgres databases are supported.
      • Other database formats need to be converted into Postgres
        • Jive Hosting is not responsible for this conversion. Typically this is handled by Jive Professional Services which can be negotiated through your Jive Account Representative.
    Binary ContentThis needs to be included in the database or split into binstore files.
    Static ResourcesAny administrator-modified files in the application directory structure.
    Encryption Keys or SAML DataThis is kept in the binstore, so it should be included in either your database dump or the split binstore files (if applicable).
    Quickly Transferring Data to Jive
    Supported Transfer Methods
    • Encrypted transfer methods, such as SFTP.
    • Usually the best option is to provide Jive with a server to access and download the files as we do not have file size restrictions.
    Expected Transfer SpeedsTransfer speeds are dependent upon client's upload speed. Rates are determined during the initial Test Run process of the migration.
    Configuration Items or Specific Functionality That Can Cause Issues
    SSO
    • Please specify the type of SSO being used, if applicable.
      • (Ex. SAML, kerberos, Custom SSO).
    • SSO will need to be disabled until the database is updated to the new schema version. You may need to download new metadata to import into your IDP for all of the server changes.
    • Jive-n and Jive-x sites require a PS engagement to enable SSO.
    SSL
    • Forced SSL is required on Hosted and Jive-n/Jive-x sites as of version 7.0.
    • If you are not using SSL and you are migrating to:
      • Hosted: Hosting will apply a wildcard certificate to your instance and assist you with purchasing your own cert which must be applied before the Go-Live.
      • Jive-n/Jive-x: SSL is included with the jiveon.com URL; if you plan to use a Vanity URL you must have your own SSL cert for it.
    • If you currently use SSL, we will need the key and the cert you are using. These files should be password protected and sent to the hosting engineer assisting with your SSL case.
    VPN
    • If LDAP is currently being used for authentication purposes and this needs to be in place once your site is hosted, a VPN will need to be setup between your corporate network and Jive to allow for this.
    • Another option is to utilize LDAPS over the internet.  This option wouldn't require a VPN, but would require the customer to open access through their firewall to their LDAP host for Jive IP addresses.
    • Please note that a VPN connection is a purchased module.
    LDAP
    • LDAP will need to be re-configured on the hosted/Jive-n/Jive-x instance.
    DNS
    • The vanity URL should be setup with a CNAME, not an A record, when pointing to the new site.
    • Vanity URL is included for Jive-x, or as an additional purchase for Jive-n.
    Redirects
    • Hosted: Any custom Apache redirects will need to be communicated to Jive.
    • Jive-n/Jive-x: Entries are only supported via the Admin Console.
    Access Restrictions

    Any type of access restrictions such as Basic Auth, or IP restrictions (Unsupported in Jive-n and Jive-x).

    Bot Access
    • Hosted: Please provide us with the desired contents of the robots.txt file.
    • Jive-n/Jive-x: Custom entries are unsupported.