Summary


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



Recommendations


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
  • Network printer drivers



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 Repository


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


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



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 performance 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



See Also


Application Server Management

Renaming an Application Server