Perform the tasks in this workflow if you want to use both Automation 360
On-Premises and Enterprise 11 in parallel. You can continue
to use both environments till the time you are ready to start the migration from Enterprise 11 to Automation 360
On-Premises.
Prerequisites
- Ensure that you have completed the following tasks to check your readiness for migration
Check migration readiness.
- Ensure you have procured and activated your migration license.
Get migration license
- If you are installing Automation 360 on a machine on
which Enterprise 11 was previously installed, you must
delete the data from the Elasticsearch data folder located at
C:/ProgramData/elasticsearch/data.
If the location of the
Elasticsearch data folder was changed, you can find
the updated information in the
C:\Program Files\Automation
Anywhere\Enterprise\elasticsearch\config\elasticsearch.yml
file.
Important: If you delete the Elasticsearch data, you will lose the Enterprise 11 audit data.
Note: Install Automation 360 on a separate server
to ensure that your Enterprise 11 environment is not impacted by the
migration activities.
Procedure
-
We recommend that you create a backup of the Enterprise 11
database and restore it in the same or different SQL instance to avoid
failure of any automation task that is using the Enterprise 11 database.
Bot Insight migration: The
Bot Insight data and
dashboards are migrated as part of the overall migration process.
For the migration, clone your
Bot Insight database
(which is different from your
Enterprise 11
Control Room database) and extract and export your
dashboard metadata to
Automation 360 using the
Bot Insight pre-migration utility.
Export Enterprise 11 Bot Insight dashboards for migration
-
If you are migrating from Version 11.3.x or later versions, delete data from
the ES_SETTINGS table from the Enterprise 11
Control Room database.
-
Copy and paste the Enterprise 11
Control Room repository and update access URL and
repository path.
-
Ensure that all the credential variables used
in the Enterprise 11
bots are available in the
Enterprise 11
Control Room.
-
Install Automation 360
On-Premises:
-
Ensure you meet the system requirements.
-
Install Automation 360
On-Premises
Control Room in custom mode to a staging
environment.
-
Continue using both Enterprise 11 and Automation 360 environments in parallel.
Note: Create all new bots
and entities such as users, roles, and schedules in Automation 360.
-
If you create any new entity such as users, roles, or schedules (except bots) in Enterprise 11 after installing Automation 360, create the same entity in Automation 360.
-
When you are ready to use only Automation 360 as your production environment:
-
If you have created new bots in
Enterprise 11 after installing
Automation 360:
- Export all the bots and their dependencies that were
created after Automation 360 was installed using
Bot Lifecycle Management.
Export bots
- Import all the bots to Automation 360 using Bot Lifecycle Management.
Import bots
- Optional:
Migrate audit log data.