This article will cover how to migrate a server installation to a new server. A migration will maintain all control definitions, historical data and output reports.
As part of the migration, you can optionally perform a product upgrade. This is known as a parallel upgrade, as the new installation will be fully isolated from the old installation.
If performing an upgrade as part of the migration, please ensure your new server and existing database are in-line with the latest version's system requirements.
Preparing for the migration
Overview of migration instructions
- Unpack the new product binaries on the new server
- Migrate key elements from the old server to new server
- Migrate config files
- Migrate disk-based reports and outputs
- Migrate custom scripts and config override files
- Migrate custom components
- Update configuration files and scripts
- Recreate product JVMs
- Run database upgrade scripts (product upgrades only)
- Validate, start JVMs and deploy
- Remove old server name references from within product
Familiarization with standard install or upgrade steps
It is recommended to familiarize yourself with, or have a copy of, the standard install or upgrade instructions. These documents are available within the product documentation page under the All Installation Documentation bundle.
This article will provide an outline of steps specific to performing a migration. The details on how to perform certain core installation steps, as in, installation steps that are not unique to a migration, such as extracting the install files or running a deploy, will be referenced in this article. The specific steps or considerations of core installation steps will be documented within the installation and upgrade documents instead.
1 ) Unpack the new product binaries on the new server
Migrating an installation of Infogix is a prime opportunity to ensure the team is on the latest version of the software. If a more up-to-date version of Infogix is available, utilize the latest binaries found on our support site at the following location :
Download product installation files
The installation files are available within the Knowledge base section linked below. Please note, to view the hosted files on our support site, you will be required to log in:
Infogix Assure, Insight, Perceive and ER Installation Files
Extract product installation files
Run the infogixextract script per the standard installation and upgrade instructions.
2 ) Migrate key elements from the old server to new server
Recreating or moving core config files
Migrations without a product upgrade
If you are performing a migration without an upgrade, copy your entire configuration folder from your old to new server. Your config file location is specified by the CONFIG_HOME property within appserver.properties. By default, this is hosted within your config directory.
Updates to these files will be required and handled in the subsequent steps.
Migrations with a product upgrade
If you are performing an upgrade alongside your server migration, run init-config to recreate the base configuration files with the new version's settings. Note that you cannot directly copy your old configuration files, as there will be new settings that are added with each new release.
Updates to these files will be required and handled in the subsequent steps. Keep a copy of your old configuration files for future reference.
Migrate disk-based reports and outputs
Migrate Assure reports
Within your prior install's appserver.properties configuration file, check the following locations specified and migrate the contents, including the directory themselves, to your new server :
<install_home>/igx-data/<config>/IA/data
Within your prior install's IA.properties configuration file, check the following locations specified and migrate the contents, including the directory themselves, to your new server. Actual locations may differ, if changed from defaults:
DX_EXPORT_DATA_DIR=<install_home>/igx-data/<config>/IA/exports
EXECUTE_SCRIPTS_HOME=<install_home>/igx-data/<config>/scripts
TEST_DATA_REPOSITORY_HOME=<install_home>/igx-data/<config>/testdata
Migrate Insight reports
When utilizing Insight and ACR, migrating reports will be necessary if the team would like to still access old control, user and freeform reports. The following folder's will need to be copied from the "old" server to the "new"
REPORTS_FOLDER=<install_home>/igx-data/<config>/II/insightreports
SECONDARY_REPORTS_FOLDER=<install_home>/igx-data/<config>/II/insightreports2
Please note, the insightreports directory hosts all ACR reports. This location ( and name ) of this folder may differ based on how your II.properties is defined. Once migrated, the reload-base-data script will need to be executed. Instructions on this are defined within the product version's installation / upgrade guides hosted on our support site.
Migrate Perceive reports
Within your prior installation's IV.properties configuration file, check the following locations specified and migrate the contents, including the directory themselves, to your new server. The locations may differ based on how your IA.properties is defined, the defaults are displayed below:
ASSURE_EXPORT_DIR=<install_home>/igx-data/<config>/IA/exports
IVP_IMPORT_DIR=<install_home>/igx-data/<config>/scripts
Migrate custom components
JNDI connections
When utilizing Wildfly, your JNDI connections will be recreated based upon your datasources.properties within the Assure's configuration directory.
When utilizing WebSphere, JNDI connections will only need to be recreated if you also migrated WebSphere instances. This is completed through the WebSphere Console by your WebSphere administrator.
Custom message queues
When utilizing Wildfly, custom message queues will need to be recreated after a migration.
When utilizing WebSphere, custom message queues will only need to be recreated if you also migrated WebSphere instances. This is completed through the WebSphere Console by your WebSphere administrator.
3 ) Update configuration files and custom scripts
Update standard product properties
If you are performing a migration, with or without an upgrade, the property files will need updates to server names. Update the following property files with the new server names:
appserver.properties - hostname of the application server(s) and/or load balancer
IA.properties - hostname of the Insight and ER server(s) and/or load balancer
If your server path references differ between your old and new installations, then review the same two property files above to ensure file paths are still accurate.
If you are performing a migration without an upgrade, then your standard property file migration is complete.
If you are performing a migration with an upgrade, you will need to review the content of all configuration files and reapply any configuration changes. Note that you cannot directly copy your old config file contents into your new config files, as there will be new settings that are added with each new release - the updates will need to be on a property-by-property basis.
Update custom scripts and properties
In an advanced configuration, you may be leveraging custom scripts or custom property files. These custom files will exist in external directories that were not yet migrated to the new server.
If you uncertain if you are leveraging these features, review the properties in the section below.
Custom properties
Custom properties exist in two locations. One location is your config folder, which would have been copied over already. The other location is within a config override directory. To determine if you are using config override, check if a directory is defined as the CONFIG_OVERRIDE property within appserver.properties.
If this location is defined, copy the entire content, including the directory itself, from your old server to your new server.
Custom scripts
Infogix Assure has the ability to add custom scripts for execution within the product. These scripts would exist within the directory defined as your EXECUTE_SCRIPTS_HOME property within IA.properties.
If this location is defined, copy the entire content, including the directory itself, from your old server to your new server. In addition, please review the content of these scripts to ensure they contain the correct server name and paths.
Database connection details
If you are performing a migration without an upgrade, your database connection details will remain the same.
If you are performing a migration with an upgrade, it is recommended to copy your database into a new instance prior to the upgrade. The benefit of this is that it leaves the old product server and old database servers fully intact and isolated from the new upgraded version. If you choose to copy your database, then update your database.properties with the new connection information.
4 ) Recreate the product JVMs
If you are performing a migration without an upgrade, then you may copy and paste the <install_home>/config folder to the new <install_home>/config location. Please review to ensure server names and file paths still hold true within the property files.
If an upgrade is taking place, fresh JVM's will be required by executing the "init-config" scripts, editing the property files, and achieving a successful validation. Please note, these steps are located within both the Server Upgrade and Server Installation PDF's :
Ensure a successful validation of the application is achieved prior to moving on to the next step.
5) Run database upgrade scripts (product upgrades only)
If you are performing a migration without an upgrade, then no database changes are needed.
If you are performing a migration with an upgrade, then the product upgrade scripts will need to be executing against your database. It is recommended to copy your database to a new instance prior to running the upgrade scripts. This allows the original server to connect with your original database instance, and the new server to connect with your new database instance. This fully isolates the two environments from each other, allowing them to be online simultaneously.
The full details of the database upgrade scripts can be found within the Database Upgrade section of the product upgrade guide.
6 ) Validate, start product JVMs, and deploy
Run a validate, then deploy and then start the product JVMs. Please review the following articles on the specifics on running a validate, deploy and starting the JVMs:
How to use the validate-config-values script
How to start and stop the Assure, Insight, Perceive and ER JVM
How To Redeploy Assure/ER/Insight/Perceive
7 ) Remove old server name references from within product UI
Please note, this should only be performed once the migration has completed, and the new server's application install is online.
Updating Assure-Insight and/or Assure-Perceive connections
The product UI contains additional configuration for Assure-Insight and Assure-Perceive communication. Please review our Updating Information Source, Source System article to update these connections with your new server names.
Remote Event Subscriptions
If the hostname / URL was updated in point 3 above, it will be recommended to review your out-of-date event subscriptions. This will be old connections from Assure to your old Insight and/or Perceive servers. Note that after you update Assure to point to a new Insight or Perceive instance, the old connections remain active, as this appends to Assure's list of known Insight/Perceive instances. This is a quick process, and is explained in the following article :
Comments
0 comments
Please sign in to leave a comment.