Migrating Altova Servers

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  Installation >

Migrating Altova Servers

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 (for step-by-step instructions, see Start LicenseServer ). 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 in the standard way, as described in Register Products. If you have a large number of licenses to migrate, it is possible to automate registration only by 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

Preparing for migration:

 

1.Ensure you have administrative privileges both on the old and the new server machine.
2.It is recommended that all jobs should use globally (not locally) stored credentials. If you are using locally stored (inline) credentials in jobs, all such jobs will have to be edited on the new server machine to match the user credentials linked to that operating system. By contrast, if you are using globally stored (standalone) credentials, you will only need to edit the standalone credentials on the new server machine. For more information, see How Credentials Work.
3.If your FlowForce Server uses Windows Active Directory integration, then, for a smooth migration, ensure that the new server machine has the same operating system users and configuration as the old machine.
4.Delete any FlowForce files (jobs, MapForce mappings, StyleVision transformations) that are not in use. In addition to this, perform a general FlowForce Server cleanup and maintenance by running the built-in functions "archive-log", "cleanup-files", and "truncate-log". The size of the internal FlowForce database can be reduced by running the compactdb command. This will help you significantly reduce the time required to copy the configuration data from the old server to the new server (as described in the steps below).

 

Performing the migration:

 

1.On the new server machine, install FlowForce Server. To minimize server downtime during migration, at this time you may also want to register FlowForce Server with Altova LicenseServer, without transferring yet the license to the new server machine; this will be done in a subsequent step. For step-by-step instructions on how to install FlowForce Server, see Installation on Linux, macOS, and Windows.

If you are migrating MapForce Server, StyleVision Server, and RaptorXML(XBRL) Server as well, it is recommended to install these products as part of the FlowForce Server installation.

2.On the old server machine, ensure that there are no running jobs, and stop both the FlowForce Server and the FlowForce Web Server services. For instructions on how to start/stop services on each operating system, see:

 

Linux: Starting and Stopping Services (Linux)

macOS: Starting and Stopping Services (macOS)

Windows: Starting and Stopping Services (Windows)

 

3.On the old server, locate the data directory of FlowForce Server (see FlowForce Server Application Data ), and then copy it to the new server machine, with a temporary name, for example "C:\transfer\migrated_data". The data directory includes any deployed jobs, MapForce mappings and StyleVision transformations, as well as FlowForce users, system functions, settings, and logs (for a complete list, see FlowForce Server Application Data ). The duration of this operation will depend on the amount of you FlowForce configuration data.

The copying time will be greatly reduced provided that you cleaned up the FlowForce Server logs in advance (as explained above, see "Preparing for migration").

4.On the new server machine, stop both the FlowForce Server and FlowForce Web Server services, and then rename the data directory to data_backup or a similar name. This will serve as a backup of the initial FlowForce Server configuration on the new server, in case you will want to revert to it for any reason.
5.From the command-line interface, change the current directory to the FlowForce program directory, and then run the "migratedb" command, for example:

 

FlowForceServer migratedb --datadir=C:\ProgramData\Altova\FlowForceServer2019\data --olddatadir=C:\transfer\migrated_data

 

On UNIX systems, use lowercase flowforceserver to call the executable, and adjust the paths accordingly (see FlowForce Server Application Data ). You may also need to prepend the "./" characters to flowforceserver, to indicate the current directory.
If the source data directory is of a major version of FlowForce Server that is older than the FlowForce Server version to which you are migrating, the configuration data will be upgraded automatically to the new FlowForce Server version. The same result can be achieved by running manually the "upgradedb" command from the command-line interface.
6.On the new server machine, start (in this order) the FlowForce Server and the FlowForce Web Server services.
7.If you haven't done that already, register FlowForce Server with Altova LicenseServer. For step-by-step instructions, see Register FlowForce Server.
8.From the Altova LicenseServer web interface, deactivate your FlowForce Server license from the old server and re-assign it to the new server machine (see Assign Licenses to Registered Products ).

 

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 (see Assign Licenses to Registered Products ).

 

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 (see Assign Licenses to Registered Products ).

 

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 (see Assign Licenses to Registered Products ).

© 2019 Altova GmbH