By duplicating the environment of a JReport Server, you can migrate the server to anther JReport Server on other computers. The migration procedure is divided into two parts: migrating server system configurations and migrating server data. This document explains the migration based on Windows. It also applies to other systems.
When two JReport Servers have the same license, same JReport and JDK versions, and different system databases, you can migrate the system configurations of the original JReport Server on computer A to the target JReport Server on computer B. The server system configurations that can be migrated include JVM class path, JVM heap size, other JVM options, patch, JDBC driver, customized classes (UDS, UDF, UDO, etc.), customized JSP, white label, configurations stored in files like server.properties, and so on.
To synchronize the server system configurations:
<install_root>\bin
if they are changed. Data resources such as catalogs, reports, users, schedule tasks, security and so on can be migrated from the original JReport Server on computer A to the target JReport Server on computer B, provided that the two servers use different databases. For example, when JReport Server on computer A uses MySQL database f, JReport Server on computer B cannot use database f unless the database is on different DB servers.
Take the following steps to migrate the server data between two computers: