閱讀及檢閱 Automation Anywhere 文件

Automation 360

關閉內容

內容

開啟內容

Automation 360 Cloud Updates

  • 已更新:2022/01/03
    • Automation 360 v.x
    • RPA 工作區
    • Learn

Automation 360 Cloud Updates

Automation 360 Cloud is a multi-tenant cloud service that leverages the latest best practices in delivering web scale SaaS to rolling out incremental updates globally using a continuous deployment pipeline.

Automation 360 Cloud provides updates to the Bot agents running on your infrastructure. The Bot agent is a lightweight Java based modular application to handle the particular bots and their packages when they are scheduled to run. Bot agent updates are transparent to active bot creation users. For operations, the Bot agent updates are carried out automatically by default without requiring administrative privileges (much like a browser update).
註: This is irrespective of whether the Bot agent was installed as a system user or local user.
Each update, products such as RPA Workspace, Control Room, IQ Bot, Bot Insight, Discovery Bot and AARI have incremental security and features enhanced and bug fixes applied. Application command packages can also be enhanced and made available for inclusion into bots on your release cycle.
註: Notifications of maintenance windows for updates are posted here: Maintenance Window
There is a target 4-hour maintenance window per GEO region when updates will roll out. These are posted on the status page. While the actual downtime during the update varies, completion is typically within 10-15 minutes. If IQ Bot is in use, completion time is typically 20-30 minutes. In general, bots run to completion during the update; exceptions are:
  • If the bot tags data for Bot Insight.
  • Parent / Child bots will run to completion as the child bots are downloaded at the start of running the parent bot. Unless the child bots are referenced using a variable parameter -calling those child bots need the Control Room to be available during parent bot runs.
  • Bots using WLM.

Once the Bot agent has reconnected to the control room the bot status is updated in the Bot run activity logs.

Automated Bot agent takes place once an agent finishes any current bot run. Once update the agent reconnects to the Control Room.

During this short downtime, any bots scheduled to run will not be scheduled. It is therefore recommended that bots are not scheduled to start to run during the planned maintenance window.

表 1. Targeted Maintenance Windows by Region
Region Day Time in UTC
AP-AUS Wednesday 12:00 to 16:00
AP-Sing Wednesday 16:00 to 20:00
EU-West1 Tuesday 20:00 to Wednesday 02:00
EU-West4 Tuesday 20:00 to Wednesday 00:00
LATAM Thursday 02:00 to 07:00
ME Thursday 20:00 to Friday 00:00
S. Africa Thursday 20:00 to Friday 00:00
US-East Friday 02:00 to 07:00
US-Central Friday 02:00 to 06:00
India Friday 02:00 to Saturday 00:00
US-West Monday 02:00 to 08:00
Canada Monday 02:00 to 06:00
Japan Monday 16:00 to 20:00
註: A small interim update maybe be planned to address urgent priority updates mid cycle between the primary quarterly updates. These will occur on the same day of the week and time as the schedule above.

Regular Updates

Regular updates are planned approximately every 3 months and scheduled to occur during non-business hours and not close to the month end or beginning. Notifications are posted to the cloud status site 2 weeks in advance of the update. A notification message is also pushed to administrators in the Control Room in advance.

You can review changes in the release notes that are made available 3 weeks before each update.

註: A Sandbox Control Room environment can be used by customers to try out the next update typically 3-4 weeks before the main Dev/UAT/Prod environments are updated.
Command packages may be updated and made the default for creating new bots. Existing bots running or being edited remain using their existing package versions. New bots created, will use the new default package version however users have the control to revert to previous versions.

Cloud Infrastructure Updates

Cloud infrastructure updates are carried out typically once per three month period. If these infrastructure updates involve planned downtime for Automation 360 Cloud, notifications are posted on the status site at least one week in advance.

Critical Patch Updates

Patch updates may be required for either critical security updates or where serious issues with an update impact the majority of cloud customers.

Any patches will require a maintenance window as described above. Typically, these would not require an agent update. As much notice as possible would be provided on the cloud status page.

Planned Maintenance Windows

Automation Anywhere offers planned update maintenance windows to enable customer operations to any support bot life cycle change management. Outside of planned maintenance windows for the updates above, the Automation 360 Cloud availability SLA is 99.9% per month.
註: Details are linked under the Cloud Automation Agreement.
Type of updates Frequency Time expectation Client action
Regular Automation 360 Control Room & Bot Agent 3-4 months

4 hour window

~10 min downtime

Bots can run to completion. Do not schedule bots to start during this 4 hour window.
Sandbox 4 weeks prior to regular cloud updates Try new features out after the window. Sanity test production bots.
Cloud infrastructure Once per 3 month period Varies. Scheduled on weekends. Bots can run to completion. Do not schedule bots to start during window
Critical Patch As needed Critical notice given ASAP
傳送意見反饋