There are two ways to back up data in FlowForce Server:
1.From the Web administration interface. This type of backup includes only configuration data: jobs, credentials, deployed MapForce mappings or StyleVision transformations, resources, AS2 certificates, AS2 partners. It does not include application settings or users. Any FlowForce Server user can perform import or export of configuration data, if their permissions on the respective object allow it.
2.Administrative backup of the application data directory. This approach requires access to the FlowForce Server application data directory on the machine where FlowForce Server is installed. The application data directory includes all the data from the previous bullet, and also users and roles (including users and roles imported from a Directory Service such as Active Directory) and application-level settings such as email or LDAP server settings, password policies, cluster settings.
|Note:||This topic does not cover backup and recovery of data external to FlowForce Server (such as files or directories that are input/output to jobs or to FlowForce resources, or local file-based databases). You will need to back up this data separately. As best practice, you might want to keep all such external data (if possible) in the same directory, for easier backup and maintenance.|
In the event that you will migrate data to a new machine in future, or restore it from a backup, you can ensure better portability of data by following the tips below:
•It is recommended to configure LicenseServer to have a fallback second server (the so-called "failover" server). For details, see the LicenseServer documentation (https://www.altova.com/documentation).
•It is recommended that all jobs should use standalone (not inline) credentials. If you are using local (inline) credentials in jobs, all such jobs will have to be edited on a new server machine, to match the user credentials linked to that operating system. By contrast, if you are using standalone credentials, you will only need to edit the standalone credentials on the new server machine.
•If you are running mapping functions deployed from MapForce, consider referring to file and folder paths and databases using resources, instead of absolute references.
•As an alternative to creating and maintaining users and roles directly in FlowForce Server, you might want to use Windows Active Directory or another LDAP Server with support for Directory Services. For details, see Changing the Directory Service Settings.
To perform a backup of selected objects, login to the FlowForce Web administration interface and use the Export functionality. To restore data, use the Import functionality. For details, see Importing and exporting configuration data.
|Note:||You can import configuration data into a FlowForce Server instance that is of the same or later version than the one from where data was exported. Importing configuration data into an earlier version of FlowForce Server may work but should be avoided.|
The backup of all application data essentially consists of creating a copy of the FlowForce Server database (DATADIR) in a safe location from where you can later restore it if necessary.
In the instructions below, DATADIR refers to the following directory:
To save time and disk space, you will want the DATADIR directory to be as compact as possible. You can achieve this by performing the following optional steps before the actual backup:
1. Archive the old log records, by creating a job that runs the built-in archive-log function
2. Delete old log records, by creating a job that runs the built-in truncate-log function
3. Delete unused files, by creating a job that runs the built-in cleanup-files function
4. Run the FlowForce Server executable with the compactdb.
You can now proceed to the actual back-up steps:
2. Create a copy of DATADIR to a safe directory (preferably on a different machine or disk). By convention, we will call this copy DATADIR_BACKUP in subsequent steps.
The private.db file inside DATADIR contains sensitive information, such as passwords and private keys. Ensure the backup is stored in a secure location.
If the DATADIR_BACKUP is of the same version and on the same machine as the currently running FlowForce Server, you can easily restore it as follows:
2. Rename DATADIR, for example, to temp_data.
3. Copy DATADIR_BACKUP to DATADIR.
4. Start both the FlowForce Web Server and FlowForce Server services.
You can also restore backups that originate from another machine and perhaps have an older database version. The steps below could be useful, for example, if you want to migrate FlowForce data to a new server, or in the event of a hardware failure.
•You can perform the restore on a machine that runs the same or a different operating system. In the latter case, note that all the paths used in jobs may not be valid on the new operating system, in which case they will need to be updated manually.
•Credentials that are tied to operating system user accounts (that is, credentials where the Allow usage for job execution option is enabled) may no longer be valid on a new machine, in which case they will need to be updated manually.
To restore data to a new FlowForce Server installation or version:
1.Install FlowForce Server and any of the following, as applicable: MapForce Server, StyleVision Server and RaptorXML Server. If you need to install LicenseServer as well, you can select it as part of FlowForce Server installation (Windows only). On other platforms, you will need to install LicenseServer separately.
2.Log on to the LicenseServer Web administration interface, and de-register all the products from the old machine. Next, register all the products from the new machine with LicenseServer. This step can also be performed after migration.
4.Rename DATADIR, for example, to temp_data.
5.Run the migratedb command, by supplying DATADIR as --datadir, and DATADIR_BACKUP as --olddatadir, for example:
sudo ./flowforceserver migratedb
6.Start (in this order) the FlowForce Server and FlowForce Web Server services.