Summary

This article describes how to move the InfoBurst application from one server to another.


Recommendations

Dependencies

Any server dependencies used by InfoBurst must be replicated on the new server prior to installation. Dependencies can include:

  • Windows account assigned to the InfoBurst service
  • Local network shares or source files
  • ODBC connections
  • Mail server whitelisting
  • Printer drivers


Schedule and Event Processing

As part of a production application server move, you may consider disabling Schedule and Event processing prior to the move. This would prevent all production schedules from running after the move and allow for testing of select jobs. Schedule and Event processing can then be enabled upon completion of testing.


Application Server Move

This process pertains only to the relocation of the InfoBurst application server. See Moving a Repository for details on relocating a repository.


Original Application Server (Server #1)

Stop and disable the InfoBurst service.


New Application Server (Server #2)

Installation
Connect RepositorySee the Connect to an Existing Repository section of Repositories for instructions to connect Server #2 to the database repository previously used by Server #1.

SQLite repository users: The process to move a server that uses a SQLite repository may vary. Please open an InfoSol Help Desk ticket to discuss this requirement with support.
Update License
  • Open a Remote Desktop session to Server #2
  • Open the application root folder (default = C:\Program Files\InfoSol\InfoBurstPlatform)
  • Double-click license.exe to launch the license manager
  • Select and delete the license from Server #1 
  • Install the license key for Server #2
  • Restart the InfoBurst service

Update ServerName
  • Select System > Configuration
  • Category: Select General
  • Select ServerName
  • Value: Enter server name of Server #2
  • Select the Save button

Update UIURL
  • Select System > Configuration
  • Category: Select General
  • Select UIURL
  • Enter InfoBurst server URL (e.g. http://<SERVER>:8554)
  • Select the Save button

SSLIf SSL was enabled for Server #1, then follow the Change SSL Certificate process to enable SSL on Server #2.


InfoBurst Portal Users

Perform the following steps after InfoBurst has been installed on the new application server and connected to existing InfoBurst repository.


Portal Storage

Copy the contents of the Portal Storage folder from the original application server to the same folder on the new application server. See System > Configuration > Category:Portal > PortalStorage for portal storage location.


Portal DB Files
  • Open the _SysDb folder located in the InfoBurst application root folder (default = C:\Program Files\InfoSol\InfoBurst) of the original server, then open the folder that corresponds to the name of the current repository connection
  • Copy any/all files with prefix Portal (example: Portal_1.db) and paste them into the same _SysDb folder on the new application server


Review Users

Perform the following steps after InfoBurst has been installed on the new application server and connected to existing InfoBurst repository.


_Review Folder
  • Open the _Portal folder located in the InfoBurst application root folder (default = C:\Program Files\InfoSol\InfoBurst) of the original application server, then copy the _Review folder
  • Paste the _Review folder from the original server to the \_Portal folder on the new application server

Review DB Files
  • Open the _SysDb folder located in the InfoBurst application root folder (default = C:\Program Files\InfoSol\InfoBurst) of the original application server, then open the folder that corresponds to the name of the current repository connection
  • Copy any/all files with prefix Defer (example: Defer_1.db) and paste them into the same _SysDb\<REPOSITORY> folder on the new application server


XDC Users

The following are general recommendations to consider when moving an application server. XDC usage can vary in complexity of implementation. Please consider all aspects of your XDC usage prior to a server move to ensure dashboard availability will not be affected. Contact your InfoSol account manager for consultation, regarding a server move and InfoBurst-connected dashboards and web applications.
  • Update dashboard connections to reflect new application server name
  • Refresh all XDCs to recreate caches


InfoBurst Apps Users

Users who host web applications or dashboards in the InfoBurst application root directory Apps folder must relocate any folders/files to the new application server and update references to these assets accordingly.


See Also

Application Server Management

Renaming an Application Server