Important Considerations:

• Any custom system properties that should not be altered need to be communicated in the refresh case.
• Email addresses in the jiveUser table are scrubbed. The outbound email settings are also cleared. The customer needs to ask explicitly if they want their email settings to be retained (most likely, this will generate emails to be sent from the UAT instance, that is something that most customers do not want).
• With the exception of the properties below all other application database content is carried forward into the UAT instance. Selective data replication is not supported.

The following system properties are not affected during the refresh and will not be altered based on their counterparts in Production. If you need any clarifications on any of them, ask Support:

• jiveInstanceId
• jiveReportingInstanceId
• jiveURL
• jive.cluster.jgroup.servers.address%
• jive.cache.voldemort.servers.address%
• __jive.analytics.%
• jive.storageprovider.FileStorageProvider.rootDirectory
• jive.storageprovider.classname
• jive.storageprovider.cache.enabled
• jive.dv.%
• %smtp%
• %sso%
• %ldap%
• %video%
• %mands%
• %checkmail%
• %eae%
• %activity%
• %appsmarket%
• %master%
• %saml%
• %bobj%
• %sharepoint%
• botcache.externalURL
• botcache.externalMessageURI
• botcache.coreMessageURI
• %jms%
• %twitter%
• outlook.mail.alias
• jive.sbs.instance.type
• jive.oauth.consumer_secret
• jive.oauth.consumer_key
• jive.auth.forceSecure
• jive.usernames.case.insensitive
• jive.profiler.widget.add-markup
• globalRenderManager.EmoticonFilter.imageURL
• %services.skyhook%
• services.secret.rebuildSearchIndex.epoch
• services.secret.rebuildSearchIndex.secret
• services.secret.search.epoch
• services.secret.search.secret
• services.secret.searchIndexManage.epoch
• services.secret.searchIndexManage.secret
• services.secret.directory.secret
• services.secret.directory.epoch
• services.secret.activityIngress.secret
• services.secret.activityIngress.epoch
• saml.keystore.password
• virusscan.virusScannerUrl

• At the time of the UAT refresh case, there are two options - you need to choose the one you prefer:
  1. Plugins from Prod should replace the existing ones on UAT (default choice)
  2. Keep the plugins currently installed on UAT intact
• Refreshing between different SBS versions may cause some plugins to malfunction until the plugin is updated to the necessary version.
• Some plugins may require additional configuration after the refresh is complete. Some examples are the Mobile and Video plugins that require specific actions to be taken after the refresh is complete.
• Custom plugins are not carried over by default. If instead, you want them to be copied, please let the Agent know.

All analytics data is copied over.

All EAE data is copied over.

All binary storage data is copied over. Please include whether the site uses SSO so we are aware of existing SAML metadata.

Note: Jive customers are responsible for ensuring SSO is set up properly after the refresh is complete.