Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

Prerequisites for manual migration

  • Updated: 10/06/2021
    • Automation 360 v.x
    • Explore
    • RPA Workspace

Prerequisites for manual migration

When you migrate from Enterprise 11 or Enterprise 10, if you have not used the Enterprise 11 database or copied Enterprise 10 data, you must manually create all the entities of Enterprise 11 or Enterprise 10 in Automation 360.

Create the following Enterprise 11 or Enterprise 10 entities except bots in Automation 360:
  • Create a user
  • Create a role
  • Credentials and lockers used in bots

    Credentials and lockers in the Credential Vault

  • AAApplicationPath global value and set its value the same as Enterprise 11 or Enterprise 10 for the required users
  • AADefaultDateFormat global value and set its value as MM/DD/YYYY HH:MM:SS.
  • The following global values that will be used by the Send email action:
    • AAE_EmailSettings_auth
    • AAE_EmailSettings_host
    • AAE_EmailSettings_port
    • AAE_EmailSettings_ssl

    The values for the preceding global values must be the same as those specified in Enterprise 11 in Tools > Options > Email Settings.

    You must create the AAE_EmailSettings_auth and AAE_EmailSettings_ssl global values of type boolean. The value for these must be assigned based on the Enterprise 11 configuration. For example, if the My server requires authentication option is selected in Enterprise 11, you must set the AAE_EmailSettings_auth value as true. Similarly, if the My server uses a secure connection option is selected in Enterprise 11, you must set the AAE_EmailSettings_ssl value as true.

  • The following global values if you have used Exchange Web Services (EWS) in Enterprise 11:
    • AAE_EmailSettings_tenantId
    • AAE_EmailSettings_clientId
    • AAE_EmailSettings_domainName
  • Create the same folder structure as Enterprise 11 or Enterprise 10 in Automation 360.
    Important: You must create the MetaBots folder in the Bots folder in Automation 360 even if you do not have any MetaBots in Enterprise 11 or Enterprise 10.
  • Upload all Enterprise 11 or Enterprise 10 bots and their dependencies to the Automation 360 Control Room.

    You must upload the bots and their dependencies at the same location as in Enterprise 11 or Enterprise 10.

  • Migrate the bots in the following sequence:
    1. MetaBots
    2. Child bots
    3. Parent or main bots
Important: You must create all of the preceding entities in Automation 360 the same as how they are available in Enterprise 11 or Enterprise 10.
Send Feedback