Migrating Sisense System Configurations

To migrate your Sisense Web Application configuration, you must copy several directories from the current environment and migrate them to the new environment.

In addition, your Sisense application database has an identifier associated with it when you install Sisense. This identifier must be deleted when migrating Sisense as each database should have its own unique identifier. A new identifier will be generated in the environment the next time Sisense is opened. You can access the database through RoboMongo and remove the identifier as described in the procedure below.

Notes:

  • The migration approach described here is for "Dev to Prod" or "Prod to Dev" migrations.
  • For this type of configuration settings migration, the target and source environments must have the same Sisense version.

To migrate the Sisense Web Application:

  1. Back up the old environment, open your machine’s Control Panel, and go to System and Security > Administrative Tools > Services, and stop the Sisense.Repository service (this will make the website inaccessible).
  2. Create a copy of the entire Repository directory located at:
    %ProgramData%\Sisense\PrismWeb\Repository
  3. Replace the existing Repository directory in the new environment with the one you backed up.
  4. Create a copy of the entire Discovery directory located at:
    %ProgramData%\Sisense\Infra

    Note:

    The Sisense.Discovery service should be stopped before copying the directory.

  5. Replace the existing Discovery directory in the new environment with the one you backed up.
  6. In Windows Services, start the Sisense.Repository service and Sisense.Discovery service.
  7. Open Robomongo and connect to your Sisense application database with a WriteUser.
  8. Under PrismWebDB , go to the servers collection and edit the file with address LocalHost.
  9. Verify that the value of "identity" is the same for each application database in your configuration. It should be the same as the value in %programdata%\Sisense\PrismServer\ServerIdentity.xml. If the values are different, update the value in the database to match the value in the ServerIdentity.xml file.
  10. Open Windows Services and restart the following services:
    • Sisense.Configuration
    • Sisense.Galaxy
    • Sisense.Gateway
    • Sisense.Identity
    • Sisense.Plugins
    • Sisense.ECMServer
    • Sisense.ECMLogs
    • Sisense.Jobs
    • Sisense.StorageManager
  11. Open the IIS Manager and restart the website SisenseWeb.
  12. On the target machine, back up the C:\ProgramData\Sisense\RabbitMQ\rmq.cred file.
  13. Copy the C:\ProgramData\Sisense\RabbitMQ\rmq.cred file from the source machine to the target machine.
    All of the following steps are performed on the target machine...
  14. Open http://localhost:3030 -> 5 clicks on the Sisense logo in the top-left corner -> 5 clicks on the "General" tab caption.
  15. Navigate to [File Explorer] -> [production] -> [configuration-service].
  16. Find the rabbitmq.connectionString parameter and copy the password, (found between the ":" and "@" symbols):
  17. Copy C:\Windows\system32\config\systemprofile\.erlang.cookie to C:\Users\\.erlang.cookie.
  18. Run the Command prompt as Administrator.
  19. Run the following commands:
    cd "C:\Program Files\Sisense\Infra\Rabbitmq\sbin"
    rabbitmqctl.bat change_password sisense [password_from_step_16]
    Example:
    rabbitmqctl.bat change_password sisense m3ZMg6c7KA
  20. Restart the Sisense.Broker service. Wait for 2 minutes until it starts.
  21. Restart the Sisense.Configuration service.
  22. Go to http://localhost:3030 and click [Restart Services].

.r.