Read and Review Automation Anywhere Documentation

Automation Anywhere Version 11.3

Close Contents

Contents

Open Contents

Postupgrade checklist

  • Updated: 5/12/2020
    • 11.3.x
    • Install
    • Enterprise

Postupgrade checklist

Version 11.3.1.1After upgrading the Control Room, verify that it installed as expected to ensure business continuity. Log in to the Enterprise Control Room and Enterprise Client. Compare the settings, audit logs, dashboards, users, and bots repository. Upload/download bots and Schedule/Run TaskBots from Enterprise Control Room or Enterprise client.

Verify Automation Anywhere Control Room scenarios

  1. Log in to the Control Room as an Admin user.
  2. Go to the Audit Log and verify an audit entry Credential Vault connected successfully exists.
  3. Verify that all postupgrade settings in Administration > Settings are identical to the preupgrade settings.
  4. Log in to all the required Automation Anywhere Enterprise Clients individually.
  5. Verify that the same Enterprise Clients are displayed online in the Users page of the Control Room Administration tab.
  6. Verify that the preupgrade Dashboards for bots and Devices are identical.

If the Control Room is installed in a Cluster mode, verify the Load Balancer URL:

  1. Since the Application Server is offline for the upgrade due to the recommended sticky session in Load Balancer (LB), close the browser in which the current Control Room session is running and relaunch it.
  2. Log in to the Control Room as an admin user to compare the Control Room Dashboard with the screenshot taken during the pre-upgrade, for example, Registered Clients, Active users, Number of folders, and files in the Control Room repository. All of these must be identical after the patch upgrade.
  3. Go to the Enterprise Clients tab and verify the Enterprise Clients that are currently online.

Verify Automation Anywhere Enterprise Client scenarios

  1. Upload a sample TaskBot and its dependency:
    1. Log in to the Automation Anywhere Enterprise Client using the Bot Creator (Development) license.
    2. Select a sample TaskBot with a dependency in a different folder.
    3. Upload the sample from the Enterprise Client to the Control Room.

      The upload successful message appears on the Enterprise Client.

    4. Log in to the Control Room and verify that the uploaded TaskBot and its dependencies are in the correct folders in the My Task Bots folder on the Bots page.
    5. Verify that the Audit Log message Task <taskname.atmx> uploaded successfully is returned.
  2. Download a sample TaskBot and its dependency:
    1. Log in to the Enterprise Client using the Bot Creator (Development) license.
    2. In the Enterprise Client, go to the Repository.
    3. Select a sample TaskBot with a dependency in a different folder from the Server.
    4. Download the sample from the Server to the Enterprise Client.

      The download successful message must appear in the Enterprise Client.

    5. Verify that the Enterprise Client Repository that downloaded the TaskBot and its dependencies are in the correct folders.
    6. Log in to the Control Room and verify the Audit Log message Task <taskname.atmx> downloaded successfully is returned.
  3. Verify a local schedule with auto login on theEnterprise Client in Lock mode:
    1. Log in to the Enterprise Client using a Bot Runner (Runtime) license.
    2. Set the auto login credentials in Tools/Options in theEnterprise Client and select the Autologin your computer check box.
    3. Create a local schedule in the Enterprise Client using a sample task.
    4. Lock the machine.
    5. Wait until the schedule runs.
      • The schedule must run on the local Enterprise Client.
      • Auto login must work successfully, and the bot Player must be invoked to run the task.
      Note: The audit log is not generated for this in the Control Room.
  4. Run (deploy) from the Control Room to the Enterprise Client:
    1. Log in to the Enterprise Client using a Bot Runner (Runtime) license.
    2. Set the autologin credentials in Tools > Options in theEnterprise Client and select the Autologin your computer check box.
    3. Lock the machine.
    4. Log in to the Control Room as an admin user.
    5. Select a sample task and choose the Run option.
    6. Select the Bot Runner to run the task and click Run.
      • The Task <taskname.atmx> deployed successfully on selected Clients message appears in the Control Room.
      • The same message must be logged and available in the Control Rooms Audit log.
      • TheBot Runner machine must be unlocked using the autologin credential, the bot Player must be invoked, and a task must run.
    7. Verify in the Control Room Activity/In progress page that the task is in progress.
      • The bot Player must close after the task completes successfully on the Enterprise Client machine and it must return to the locked mode.
      • The task in progress entry must not be shown in the Control Room Activity/In progress page.
    8. Verify in the Control Room Activity\Historical page that the history of available tasks exists.
    9. Verify that the task run completion entry exists in the Audit Log as Task <taskname.atmx> completed. Run duration xx:xx:xx.
  5. Schedule and run from the Control Room with autologin on the Enterprise Client as follows:
    1. Log in to the Enterprise Client using a Bot Runner (Runtime) license.
    2. Set the autologin credentials in Tools/Options in the Enterprise Client and select the Autologin your computer check box.
    3. Lock the machine.
    4. Log in to the Control Room as an Admin user.
    5. Select a sample task and choose the Schedule option.
    6. Select the required options for:
      • Schedule name: TestSchedule
      • Recurrence: None/Daily/Weekly/Monthly
      • Start date: Today's date
      • Schedule Time: 10 minutes from the current time.
    7. Select the Bot Runner to schedule the task and click Save.
    8. Wait for the schedule to run on the Bot Runner from the Control Room.
      • The Schedule <Schedule name> created successfully message appears in the Audit Log page.
      • The same schedule must be available in the Scheduled Activity page with the correct Start date/time and Next occurrence date/time.
      • The Task <taskname.atmx> of schedule <Schedule name> deployed successfully on: <Host name> message appears in the Audit Log when the schedule runs on the Bot Runner.
      • The Bot Runner machine must be unlocked using the auto login credential. The bot Player must be invoked, and a task must run.
      • The task in progress message must appear in the Control Room Activity/In progress page.
      • The bot Player must close on the Enterprise Client machine after the task completes successfully and the machine must return to the locked mode.
      • The task in progress entry must exist in the Control Room Activity/In progress page.
      • The history of tasks must be available in the Control Room Activity/Historical page.
      • The Task run completion entry must appear in the Audit Log as Task <taskname.atmx> completed. Run duration xx:xx:xx.
    9. Verify that the schedule next occurrence is available. If it is available, then it remains visible in the Control Room Scheduled activity page.
      Tip: Test the schedule and run from the Control Room with auto login on the Enterprise Client using different types of schedules from the Control Room.
Send Feedback