Summary
This article describes how to move the InfoBurst Platform 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 InfoBurstPlatform service
- Local network shares or source files
- ODBC connections
- Mail server whitelisting
- Network printer software/drivers
Application Server Move
This process pertains only to the relocation of the InfoBurst Platform application server. See Moving a Repository for details on relocating a repository.
Original Application Server (Server #1)
- Stop and disable the InfoBurstPlatform service
- Back up the InfoBurst database repository
New Application Server (Server #2)
Installation
- Install the InfoBurst Platform
- Assign a Service Account
- Obtain a license key
SwitchRepo
Use SwitchRepo to connect Server #2 to the repository formerly used by Server #1:
- Open a command prompt (Run as administrator)
- Change directory to the application root folder (default = C:\Program Files (x86)\InfoSol\InfoBurstPlatform)
- Enter SwitchRepo
- Enter 2 (Connect to another repo)
- Enter number corresponding database type used by Server #1
- Follow prompts to connect to repository used by Server #1
- See Platform Preparation & Installation > Post-Installation > Repository Setup for database-specific connection strings.
- Restart the InfoBurstPlatform service
Update License
- Open the application root folder (default = C:\Program Files (x86)\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 InfoBurstPlatform 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
- Update dashboard connectors to reflect new application server name
- Refresh all XDCs to recreate caches
See Also