Moving and copying instances

Jive's security and licensing service keeps track of your production and development environments and the licenses required for production environments.

CAUTION:
Several features of the application rely on the jiveURL. For information about changing the jiveURL, see Changing community URL.

For more information about how automatic and manual license reporting works, see Managing deployment license.

If you change the URL of your instance by copying your instance (changing the jdbcURL system property) or moving your instance (changing the jiveURL system property), the fingerprint sent to Jive's security and licensing service differs from the one already recorded. In clustered environments, the master node communicates with Jive's security and licensing service.

Your system need to try to communicate with the security service, either automatically or manually (if automatic is not available), on system startup after you've completed the move or copy wizard (which is what pops up when the system figures out you've tried to either move or copy an instance due to URL changes). If your system is unable to successfully communicate within five days, it will stop working except for the Admin Console. Note that you will be warned if automatic license verification with the security service is not an option.

Using the same license, you can:
  • Move a production instance to a different server (by using a different URL)
  • Copy and move a test or development environment
Note: You cannot copy a production instance and declare the new instance as a production instance with the same license!