How to Replicate a TIBCO Spotfire Environment

How to Replicate a TIBCO Spotfire Environment

book

Article ID: KB0073334

calendar_today

Updated On:

Products Versions
Spotfire Server All

Description

If the goal is to create a separate copy of a Spotfire environment, for example a copy of a Production environment to have as UAT, this can be done by replicating the database. But it is not that straight-forward since the database contains a number of references to the servers and nodes used (hostnames, etc) which will result in cross-communication between the environments and which need to be corrected. This article provides the steps to replicate a TIBCO Spotfire environment with the full library. 

Issue/Introduction

This article provides the steps to replicate a TIBCO Spotfire environment with the full library.

Environment

All

Resolution

The most straightforward way to "replicate" a Spotfire Environment is to:
  1. Make a backup of the Spotfire database schema and to restore this in another location
  2. Install Spotfire Server of the same release and service pack as was used on the originating Spotfire environment on a suitable machine
  3. Create a new bootstrap to the restored database schema (remember to use the same encryption password if used)
  4. Use the config commands list-nodes and delete-node to remove all previous nodes (just leave the server node registered by the bootstrap creation)
  5. Do all the other post-installation tasks needed (database drivers, extensions, kerberos, certificates, customizations to the server.xml, etc)
  6. Start the Spotfire Server service and monitor the catalina.log and the server.log at startup (setting server log config to debug helps)
  7. If things looks ok, try to login using the Admin Web UI
  8. Start to build up the rest of the environment as desired with other servers, nodes, etc.
The next time you would want to take a snapshot of the environment and bring it over (and the version/service pack have not changed) you can skip step 2 and 5.

If you do not want to bring over the whole environment (e.g. large library) there is no other supported path than to use the library export/import commands that are available. If that is used it is important to start with the users and groups and remember to include-guids so later imports will get mapped correctly (regarding rights and ownership, etc).

Additional Information

Doc: Installation and configuration
Powered by Wolken Software