Please enable JavaScript to view this site.

Altova FlowForce Server 2020 

Installation

Migrating Altova Servers

Scroll Home Prev Top Next More

This topic provides instructions for migrating Altova servers from one server machine to another (including across any of the various supported platforms). These instructions use the term "old server" or "old machine" to refer to the machine from which you are migrating data, and the term "new server" or "new machine" to refer to the machine to which you are migrating data.

 

Altova LicenseServer

To migrate Altova LicenseServer from one server machine to another with the least possible downtime, follow the steps below:

 

1.Install Altova LicenseServer on the new machine.

2.Stop the Altova LicenseServer service on the new machine and copy the licenseserver.db database file from the old machine to the new machine. Make sure to back up the licenseserver.db on the new server in case you want to revert to it for any reason. The licenseserver.db file can be found in the LicenseServer application directory and its path will vary depending on the operating system:

 

Windows

C:\ProgramData\Altova\LicenseServer

Linux

/var/opt/Altova/LicenseServer

macOS

/var/Altova/LicenseServer

 

3.Stop the Altova LicenseServer on the old machine and start the Altova LicenseServer service on the new machine. This ensures that the two instances of LicenseServer are not running simultaneously.

4.Register all Altova server products with the new Altova LicenseServer. If the number of licenses to be migrated is small, you can do this manually. If you have a large number of licenses to migrate, it is possible to automate registration with the help of custom scripts or code, as follows:

Write a command-line script which calls the "register" command for each server product that is under Altova LicenseServer control.

Write a program that can open the *.licsvr file of each Altova server product programmatically and modify the "host" attribute so that it points to the new Altova LicenseServer. You can find the .licsvr file in the application directory of the respective server product (the path varies by operating system, as shown in the table above).

 

Altova FlowForce Server

See Backup and Recovery.

 

Altova MobileTogether Server

Use the Backup and Restore functionality, as described in the MobileTogether Server documentation.

 

Altova MapForce Server

For MapForce Server, migration to a new machine consists of re-assigning the license from the old machine to the new machine, as follows:

 

1.Install MapForce Server on the new machine. If it has already been installed as part of FlowForce Server installation, ignore this step.

2.On the new machine, register MapForce Server with Altova LicenseServer.

3.On the old machine, make sure no clients are using the server (for example, no mappings are running).

4.Open the Altova LicenseServer administration page, and deactivate the license from the old MapForce Server machine and re-assign it to the new machine.

 

Altova RaptorXML(XBRL) Server

For RaptorXML(XBRL) Server, migration to a new machine consists of re-assigning the license from the old machine to the new machine, as follows:

 

1.Install RaptorXML(XBRL) Server on the new machine. If it has already been installed as part of FlowForce Server installation, ignore this step.

2.On the new machine, register RaptorXML(XBRL) Server with Altova LicenseServer.

3.On the old machine, make sure no clients are using the server (for example, no transformations are running).

4.Open the Altova LicenseServer administration page, and deactivate the license from the old RaptorXML(XBRL) Server machine and re-assign it to the new machine.

 

Altova StyleVision Server

For StyleVision Server, migration to a new machine consists of re-assigning the license from the old machine to the new machine, as follows:

 

1.Install StyleVision Server on the new machine. If it has already been installed as part of FlowForce Server installation, ignore this step.

2.On the new machine, register StyleVision Server with Altova LicenseServer.

3.On the old machine, make sure no clients are using the server (for example, no transformations are running).

4.Open the Altova LicenseServer administration page, and deactivate the license from the old StyleVision Server machine and re-assign it to the new machine.

© 2020 Altova GmbH