Migration Overview

Migration Workbench is a tool that facilitates the process of migrating and mapping the data from the existing AssistEdge setup to the AssistEdge 19.0 setup. It provides you single interface to migrate existing process and transaction data to the new setup and upgrade running robots to be compatible with AssistEdge 19.0 setup. Created to solve the complexity of migrating data, Migration Workbench gets your migration completed faster with less effort and no errors.

 

This topic provides detailed information and steps for migration from AssistEdge version 17.2 onwards to AssistEdge version 19.0. The migration workbench can be used to migrate the server from Windows to Linux based machine by running the workbench from a Windows machine which is able to connect to the Linux machine and the server URLs. See the Supported Version for Migration section for more details

Migration Process

The migration process consists of migration of the following components from AssistEdge RPA 17.2 version onwards to 19.0 version.

 

Product Components:

• RPA Components
  • Database Migration (SQL, Oracle)
  • TxnStore Migration
  • RobotFarm Migration
  • Proctor Migration
  • Reporting Migration

 

For Customizations:

• Kibana Report Migration
• WebSite Map Migration
• Logstash Customization Migration
• Custom Code Migration
  • RPA
  • Microbots
• Custom Authentication
• EV Notification Customization Migration

 

Supported Versions

The migration workbench utility supports migration of the below specified versions of AssistEdge RPA to the latest 19.0 version.

 

 

 

 

 

NOTE:

These details are also applicable for users migrating from minor versions like 17.5.1 or 17.5.2.

 

High Level Migration Summary

Below is the summary of migration activities from AssistEdge RPA version 17.2 onwards to version 19.0 for all components.

 

			High Level Activities
Migration Sequence	From Version	To Version	Pre-Migration	Migration Activities	Post-Migration Verification
Database	17.2 onwards	19.0	Back-up and restore of DB copy as the admin needs to be running. Configuration changes (applies only to Oracle DB).	Migrate using utility	Check the migration status on the migration workbench utility
Installation				Copy and extract GA build provided by EdgeVerve Installation
TxnStore	17.2 onwards	19.0	Copy data folder from 17.x/18.x to 19.0 build TxnStore of previous version must be running and authentication is disabled.	Migrate using utility	Login to CT and verify that the number of Robots/Robot Agents are same as the previous version Verify that transactional data and reporting data of last configured number of days are available after migration
RobotFarm	17.2 onwards	19.0	After installation, copy the RobotAgent GA folder of 19.0 to 18.x RobotFarm machines.  Provide old RobotAgent path in 19.0 RoboAgent.exe.config	Migrate using utility	Login to CT and verify that Robot agent and Robots are available, also ensure that the controls are enabled for operation
Reporting	17.2 onwards	19.0	TxnStore of previous version should be running and authentication disabled	Migrate using utility.	Open reports from CT and verify that reporting data is available

 

Co-existence Possibility Summary

From version 17.6 onwards, there can be one or more versions of AE components (server side as well as client side) that can co-exist on the same machine.

 

The versions prior to 17.6 are not supported for coexistence and are not tested from product end.

 

NOTE:

If 18.x and 19.0 versions co-exist on the same server,  ensure that the Pre- Migration Steps of Kibana Report are completed before you begin with the migration process. Port numbers need to be changed if you want two versions of the same component to co-exist on the same server. The port numbers of all the components need to be changed before the installation starts. An error occurs if the numbers are not changed. The config files are located at: <<AssistEdge Build Folder>>\AssistEdgeAutomation\scripts\app\install\config.