Postinstallation checklist

Verify that IQ Bot is installed, ensure that the IQ Bot services are running using the healthcheck APIs, and register IQ Bot with the Control Room.

Step 1: Verify IQ Bot in the Control Panel

Ensure that the Automation Anywhere IQ Bot item exists in Control Panel > Programs > Programs and Features of the machine where IQ Bot is installed.

Step 2: Confirm that 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 Start > Run.

Automation Anywhere Cognitive Alias
Automation Anywhere Cognitive Application
Automation Anywhere Cognitive Classifier Service
Automation Anywhere Cognitive Console
Automation Anywhere Cognitive File Manager
Automation Anywhere Cognitive Gateway-2
Automation Anywhere Cognitive MLScheduler Service
Note: As of Build 12350, this service is disabled, by default.
Automation Anywhere Cognitive MLWeb Service
Note: As of Build 12350, this service uses a new model to better detect check boxes and tables. To revert to the previous model, open the CognitiveServiceConfiguration.json file, locate the following code snippet, and update the version value to v1:
```
"MLWebService": {
"port": "9991",
"version": "v2"
}
```
Automation Anywhere Cognitive Projects
Automation Anywhere Cognitive Report
Automation Anywhere Cognitive Validator
Automation Anywhere Cognitive Visionbot Manager
Automation Anywhere Cognitive VisionbotEngine Service

To reinstall the IQ Bot services, Run reinstall-allservices.bat as an administrator from IQ Bot Installation Directory > Configuration Folder. You will see a list of services with serial numbers. Perform either of the following steps to reinstall the services:

Enter the serial number of the service that you want to reinstall.
Enter the serial number of the service followed by the domain username and password.

Step 3: Perform a healthcheck

Use the Healthcheck API to verify about the required service. The request/response details of the Healthcheck API are described in the following table.

Requests

The following table lists the API requests sent for doing a healthcheck of different IQ Bot services:


Service name	URL
`Alias`	`http://<hostname/IP>:9997/healthcheck`
`Application Service`	`http://<hostname/IP>:9002/healthcheck`
`Project Service`	`http://<hostname/IP>:9999/healthcheck`
`FileManager Service`	`http://<hostname/IP>:9996/healthcheck`
`Visionbot`	`http://<hostname/IP>:9998/healthcheck`
`Validator Service`	`http://<hostname/IP>:9995/healthcheck`
`Report Service`	`http://<hostname/IP>:9992/healthcheck`
`Gateway Service`	`http://<hostname/IP>:8100/healthcheck`
`Frontend or Console Service`	`http://<hostname/IP>:3000/healthcheck`
`MLWeb Service`	`http://<hostname/IP>:9991/healthcheck`

In the table listing, replace <hostname/IP> with 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 installed.

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.

Responses

A typical successful response is in the following code example:

Subsystem

Application: <Service Name>

Status: OK

Application uptime: 0d 3h 45m 6s

Version: 1.2.0-RELEASE

Branch: RC-5.2-1

GIT #: d88e59c0435c3a836bb47cd586081205564904c5

Build Time: 2018-02-17T09:26:52.523Z

Dependencies:

Database Connectivity: OK

MessageQueue Connectivity: OK

Project: OK

VisionBot: OK

**<Service Name> could be alias, application, filemanager, project, reports, gateway, validator, or visionbot.

Dependencies: lists the status of all the dependent services, for example, database and message queue of probed service.

If the API responds with Status: Not_OK, see Healthcheck status Not_Ok (A-People login required).

Step 4: Verify the database

The system creates the IQBot database.

Log in to the database using the <dbusername> and <dbpasswd> to verify the names of the databases and tables using <hostname>, <dbusername>, and <dbpasswd>.

Step 5 (optional): Create the appropriate certificates and configure the HTTP and HTTPS settings

Creating a self-signed certificate with Subject Alternative Name

Configuring IQ Bot with HTTP and HTTPS

Step 6: Register

You must register IQ Bot with Control Room before you can start using IQ Bot.

Registering IQ Bot with the Control Room

If registration fails:

Do the steps in the following pages to resolve the issue:

Next:

Install an OCR engine (optional): During IQ Bot installation, the system sets the latest version of Tesseract Optical Character Reader as the default OCR engine. To use a different engine, follow the steps in the respective link:

Use Microsoft Azure Computer Vision OCR engine

Use ABBYY FineReader Engine OCR engine in IQ Bot

Use Google Vision API OCR engine

Use Tegaki API OCR engine

Login and set up the Control Room:Create and register IQ Bot specific users in the Control Room. Learn more about IQ Bot roles and access permissions: IQ Bot user personas and roles

Automation 360