Automation 360

Control Room log files

Download as PDF

Automation 360
Features, licenses, and deployment
- Platform licenses
  - Enterprise Platform
  - Automator AI Platform Base
- Deployment models
- Cloud licensing FAQ
Release Notes
- Automation 360 Release Notes
- Community Edition Release Notes
- Sandbox environment
- Package updates overview
- Previous Package SDK Release Notes
- Process Discovery Release Notes
- Browser extensions for Automation 360
- Automation 360 feature comparison matrix
- Automation 360 IQ Bot feature comparison matrix
- Automation 360 IQ Bot version compatibility
Automation 360 Cloud
- Automation 360 FAQ
- Automation 360 architecture and resiliency
- Automation 360 Cloud FAQ
- Automation 360 software lifecycle policy
- Automation resiliency
  - Managing unexpected pop-ups
    - Configure pop-up handling
  - Record automation execution
    - Configure automation recording
    - Manage automation recording
- Upcoming feature deprecations
- In-product user assistance
Automation and generative AI
- AI Agent Studio
- Automator AI
- Data security for generative AI - FAQ
Set up Automation 360
- Get started with Automation 360 Cloud
  - Automation 360 Cloud prerequisites
- Installing Control Room On-Premises
- Set up Community Edition
  - Community Edition capabilities
- Get started with Bot Agent
- Naming guidelines for Control Room URLs
- Post-installation user management
- Update Automation 360 to latest version
  - Update Automation 360 on Microsoft Windows Server using scripts
- Install and update Automation 360 IQ Bot
- Log in to Automation Anywhere Control Room
- Create your first bot
- Run your first bot
- Moving from Automation 360 On-Premises to Cloud
  - Moving data using Control Room operations
  - Migrate using Control Room APIs
- Migrate to Automation 360
Configure Automation 360
- Users
- Roles
- Manage licenses
  - View license details
  - Installing additional licenses
- Create your users and assign their licensed roles
- Configure Settings
- Edit My settings
  - Edit profile settings
- Set up your bot repository
- Working with repositories, credentials and roles
  - Manage user credentials
- Credentials and lockers in the Credential Vault
Manage Automation 360
- Devices
  - About multi-user devices
    - Configure RDP-based deployment for multi-user devices
    - Convert an existing device to a multi-user device
  - Edit multiple devices simultaneously
- About device pools
- Add queue, Bot Runner, and device pool
- Configure Active Directory in Control Room
- Configure OAuth connections in Control Room
- Packages
- External key vaults for Automation 360
- Workload management
- Bot Lifecycle Management
Monitor Automation 360
- Automation Command Center
- Automation program lifecycle with CoE Manager
- Activities
- Audit log
  - Audit events list
  - Export audit data to CSV
- Code analysis
- Notifications
- Control Room log files
Build automations
- Process Composer
- Interactive forms
  - Add a form to bot
- API Task
- Connector Builder
- Recorders
  - Universal Recorder for object-based automation
  - AISense for recording tasks from remote applications
- Task Bots
- Templates
- Bot Store
- Advanced bots and packages
- Troubleshooting and debugging
Automation Co-Pilot
Automation Co-Pilot for Business Users
- Embed automations in your application using Automation Co-Pilot
- Using Automation Co-Pilot for Business Users on desktop
- Automation Co-Pilot for Business Users on the web interface
- Approvals in Automation Co-Pilot
  - Using and sorting the Tasks view
- Automation Co-Pilot status and notifications
Users and roles for Automation Co-Pilot
- Create users for Automation Co-Pilot
- Create a team and assign roles to team members
- Manage roles and teams for Automation Co-Pilot
- Scheduler users and device pools in Automation Co-Pilot
- Configure deployment type for bots
Automation scenarios
- Scenario: Generating insurance quote with Automation Co-Pilot and Process Composer
- Scenario: Developing and using templates in an automation
Document Automation
- Document Automation processing workflow
- Document Automation FAQ
- Intelligent document processing solutions - feature comparison matrix
- Set up your Document Automation environment
- Create a learning instance in Document Automation
- Improve extraction accuracy through validation
  - Improve table data extraction
  - Lock the validation feedback
- Connect learning instance
  - Extracting data from check boxes
- Integrate third-party parser in learning instance
  - Create a parser and configure with learning instance
    - Sample codes for parser contracts
    - Sample SDK Project: AWS Textract
- Publish the learning instance to production
  - Build a bot to upload documents to Document Automation
  - Deploy the learning instance assets
- Validating documents through Automation Co-Pilot validator
  - Validate documents as Validator user
- Export or Import learning instances
  - Incorporating validation feedback in export/import of learning instances
- Create custom models in Document Automation using Standard Forms
- Document Automation support for Google Custom Document Extractor (CDE)
- Document Automation - Data extraction using generative AI
- Languages supported in Document Automation
  - Language support matrix and OCR engines
- Document Automation Community Edition
  - Create a learning instance in Community Edition
  - Process documents in Community Edition
Automation 360 IQ Bot
- IQ Bot architecture diagram
- Using Automation 360 IQ Bot On-Premises
- Using Automation 360 IQ Bot Cloud
- IQ Bot user personas and roles
  - Defining a custom role for IQ Bot
  - Creating a user with an IQ Bot specific role
- Languages supported in Automation 360 IQ Bot
- About the Classifier
  - Create a new document group
- Create a learning instance
- Train a learning instance
- Manage learning instances
- Rotate the external key
- Use the IQ Bot Validator
- Review the dashboard
  - Performance report page
  - Performance report details
- Custom domains in IQ Bot
- Using IQ Bot for standard forms
Process Discovery
- Overview of Process Discovery
  - Options to reduce exposure of sensitive data
- Process Discovery user roles
- Create Process Discovery users and assign roles
- Integrate SAML with SSO for Process Discovery
- Create your event reporting password
- Create a URL and application list
- Configure Observer activity
- Use Process Discovery with Kibana dashboard
  - Access the Kibana dashboard
- Create a cycle
- Classify application screens and create web applications
  - Applications with auto-assigned screen signatures
- Review Events and filter data
- Mining for processes
- Analyze and prioritize processes
- Creating groups for the process and generate a PDD
- Process Discovery - CoE Manager integration
- Getting started with Privacy Enhanced Gateway
- Process Discovery Sensor application
- Process Discovery FAQ
- Process discovery by using Discovery Bot
Bot Insight
- Business analytics through Bot Insight
- Accessing Bot Insight
- Using Bot Insight
  - Business analytics
    - Configuring a task for business analytics
- Using widgets
- Data connector for Power BI
- Configure Tableau web data connector in Bot Insight
API References
- Control Room APIs
- Filtering, pagination, and sorting
- API response codes
- Comparing Automation 360 and Enterprise 11 APIs
- Configure the Control Room
- Roles and permissions
- How to find a migration journalid
- Using Auto registration API
Glossary

Control Room log files

Download as PDF

Updated: 2024/06/25

Control Room log files

Various types of information about the Control Room are captured in different log files. You can analyze these log files when the Control Room or a bot encounters an error and identify the root cause for that error.

Overview

The log files capture information about the errors encountered by various components of the Control Room such as the Bot Store, devices, and license. You can use the information in the log files to identify the root cause of an error and resolve that error.

Log file locations

The Control Room log files are available at C:\ProgramData\AutomationAnywhere\Logs on the machine on which you have installed the Control Room. This location also contains the log files from other applications, such as Automation Co-Pilot. The log files are named WebCR_<COMPONENT-NAME>, for example, WebCR_BotStore, WebCR_Devices, and WebCR_License.

You can refer the following log files for the Control Room.

WebCR.log: Contains log entries related to the initialization of the Control Room and messages, if any.
WebCR_UserManagement.log: Contains log entries related to the user management module.
WebCR_Ignite.log: Contains log entries related to the Apache Ignite or caching system.
WebCR_ServerRepository.log: Contains log entries of the server repository related functions.
WebCR_CredentialVault.log: Contains log entries of Credential Vault related function calls.
WebCR_Hibernate.log: Contains log entries related to the Hibernate system, ORM mapping and Query system, ActiveMQ messaging subsystem.
WebCR_Atmosphere.log: Contains log entries related to Atmosphere framework, a popular open-source library used to build asynchronous web applications.
WebCR_Audit.log: Contains log entries related to Elasticsearch audit log that can help you track access, changes, and other significant events within your cluster.
WebCR_Authentication.log: Contains log entries related to Authentication logs. In the context of web applications, authentication ensures that only authorized users can access certain resources or perform specific actions.
WebCR_BI.log: Contains log entries related to Bot Insight that provides valuable insights into the performance and impact of bots, helping businesses optimize their processes, improve efficiency, and achieve better ROI.
WebCR_Configuration.log: Contains log entries related to configuring Automation Anywhere involves setting up the Control Room, managing users and roles, configuring security settings, setting up Bot Creator and Bot Runner tools, enabling and configuring Bot Insight, and setting up email notifications.
WebCR_Deploy.log: Contains log entries related to deploying bots in Automation Anywhere involves several steps, from creating and testing bots in the Bot Creator to deploying them to the Control Room and configuring them for execution.
WebCR_Devices.log: Contains log entries related to devices that are the machines or environments where bots are executed that allows the user to distribute bot execution across multiple devices for efficient automation.
WebCR_Jetty.log: Contains log entries related to Jetty server logs that provide valuable information about the server's behavior, request processing, and errors encountered during runtime.
WebCR_License.log: Contains log entries related to license related operations as Licensing is essential for accessing the platform's features and capabilities and managing bot executions.
WebCR_MFA.log: Contains log entries related to Multi-factor authentication that enhances security by requiring users to provide additional authentication factors beyond just a username and password.
WebCR_Migration.log: Contains log entries related to Migration related activities that involve moving Bots, workflows, schedules, credentials, and other resources between development, testing, and production environments, or migrating from an older version of AA to a newer one.
WebCR_OperationsRoom.log: Contains log entries related to operations room that serves as a central hub for monitoring, managing, and optimizing automation operations across the organization.
WebCR_Packages.log: Contains log entries related to bot packaging that involves the process of bundling automation assets, such as bots, workflows, dependencies, and configurations, into a deployable package for distribution, sharing, or deployment across different environments.
WebCR_Quartz.log: Contains log entries related to log messages generated by the Quartz Scheduler, an open-source job scheduling library for Java applications. Quartz Scheduler allows developers to schedule and execute tasks (jobs) at specific times or intervals.
WebCR_Scheduler.log: Contains log entries related to automation schedules that is responsible for managing the execution of tasks or bots according to predefined schedules, intervals, or conditions.
WebCR_Settings.log: Contains log entries related to Settings that refer to configurable options, parameters, and preferences that control the behavior, functionality, and appearance of the Automation Anywhere platform, including the Control Room and Bot Creator. Settings allow administrators and users to customize their AA environment to meet specific requirements, preferences, and organizational policies.
WebCR_Springframework.log: Contains log entries related to the Spring framework that is related to the initialization and shutdown phases of the Spring application context and also contains information about the dependency injection process, such as auto wiring, bean wiring, and resolution of bean dependencies.
WebCR_WLM.log: Contains log entries related to Workload Management (WLM) that enable organizations to optimize resource utilization, improve performance, and ensure the scalability and reliability of automation processes.

Note: For information on the Linux OS directory structure, see Installed Control Room directories and files.