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 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 |
|
Update ServerName |
|
Update UIURL |
|
SSL | If 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 |
|
Review Users
Perform the following steps after InfoBurst has been installed on the new application server and connected to existing InfoBurst repository.
_Review Folder |
|
Review DB Files |
|
XDC Users
- 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.