Verify if IQ Bot is installed, and ensure the IQ Bot services are running using the healthcheck APIs.
Automation Anywhere IQ Bot
Ensure that the Automation Anywhere IQ Bot item exists in of the machine where IQ Bot is installed.
Confirming Automation Anywhere cognitive services are running
Ensure that the following services are installed on the machine where IQ Bot is installed and the status of the services is set to Running on the Microsoft Windows services window.
To see the list of services that are currently running, open services.msc using.
- Automation Anywhere Cognitive Alias
- Automation Anywhere Cognitive Application
- Automation Anywhere Cognitive Classifier Service
- Automation Anywhere Cognitive File Manager
- Automation Anywhere Cognitive Console
- Automation Anywhere Cognitive Gateway
- Automation Anywhere Cognitive MLScheduler Service
- Automation Anywhere Cognitive MLWeb Service
- Automation Anywhere Cognitive Projects
- Automation Anywhere Cognitive Report
- Automation Anywhere Cognitive Validator
- Automation Anywhere Cognitive Visionbot Manager
- Automation Anywhere Cognitive VisionbotEngine Service
Doing a healthcheck
If needed, use the Healthcheck API to verify about the required service. The request/response details of the Healthcheck API are described in the following table.
The following table lists the API requests sent for doing a healthcheck of different IQ Botservices:
In the table listing, replace
the host name/IP address of IQ Bot to create the Healthcheck API
request using a web browser on the machine on which IQ Bot is
For example, if your IQ Bot is accessible at http://localhost:3000, the FileManager Healthcheck can be accessed using this URL: http://localhost:9996/healthcheck.
A typical successful response is in the following code example:
Application uptime: 0d 3h 45m 6s
MessageQueue Connectivity: OK
**<Service Name> could be alias, application,
filemanager, project, reports, gateway, validator, or
Dependencies: lists the status of all the
dependent services, for example, database and message queue of probed
Checking created databases and tablesLearn which databases and tables are created after installation of IQ Bot.
Log in to the database using the <dbusername> and <dbpasswd> to verify the names of the databases and tables using <hostname>, <dbusername>, and <dbpasswd>.
The system creates the following databases:
- AliasData: This is the master database that stores data about different aliases related to a field in the system for different document types. This database also has the information about the languages and different document types supported by the IQ Bot system.
- ClassifierData: This database has the data related to classification output for both layout and content classification.
- Configurations: This database stores data about the configurations used when installing IQ Bot, for example, Control Room URL, output path, and so on.
- FileManager: This database stores data related to learning instances, files uploaded related to learning instances, and vision bots.
MLData: This database stores the training data used by a Machine Learning (ML) system in IQ Bot.