iAutomate Components
iAutomate follows a multi-tier architecture and includes the following components:
- Web Components- This includes the user interface that enables the configuration, management, and quick resolution of tickets.
- Service Components - It is divided into two categories:
- Application Components- This includes essential services that work together to achieve the core functionality of iAutomate.
- Advanced AI Components- This includes features like Solution Creation; Natural Language Processing (NLP) based assisted services, and so on.
The following table lists the components available on different servers.
| Server Type | Components | Description |
|---|---|---|
| Web Component | Web UI | Web User Interface for Admin, Configuration, Operations Console, Dashboards and Knowledge Analysis and Search functionalities |
| Web API | It is an API in the iAutomate web module that can be accessed using the HTTP protocol. | |
| KRS | The Key Rotation Service component serves the purpose of providing additional security through rotation of keys on a periodic basis. | |
| Application Component | iRecommend | It leverages Natural Language Processing and is responsible for recommending the best-suited runbook for resolving the issue based on the ticket description |
| iParse | It serves the purpose of analyzing the ticket description and summary for extracting relevant parameters to be passed to configurable runbooks | |
| iUnique | It helps in clustering the ticket data (incident, service requests, change requests) into different categories for identification of automation opportunities | |
| Data Collector | It is responsible for collecting ticket information from the ITSM tool | |
| Generic Executor | It is used for data processing at the DB layer for enabling backend processes. | |
| RBA Executor | It helps in triggering the identified runbook for automatic resolution using an underlying RBA tool | |
| Release | It is used to release the ticket in case an appropriate runbook is not recommended OR runbook execution for a ticket fails. In the latter case, the ticket is released and assigned to a human agent to investigate it. | |
| Generic Listener | Ticket passes through multiple stages during the resolution lifecycle using iAutomate. Generic Listener module is responsible for ensuring the ticket is moved to the next stage based on the outcome. Its job is to identify the status of the present stage and based on success / failure, move the ticket to the consequent stage in the lifecycle | |
| AD Sync | It is responsible for fetching LDAP user from LDAP Server. | |
| Email Service | It is responsible for sending mail-based notifications to user. | |
| DAG Service | It is responsible for triggering network related use cases. | |
| Assignation Service | It is used to assign tickets to the group fetched from Gen AI Studio. | |
| Ansible CLI Wrapper Component | Ansible CLI Wrapper | It is responsible for triggering Ansible Inside Tool |
| Advanced AI Component | Advanced Knowledge | It returns a list of relevant documents for a query that have been crawled from different repositories like SNOW KB, Web URL, Satori repository, and internal files and folders. |
| iKnowledge | It returns a list of relevant results from Google for a query, if no relevant document exists in the organization’s repository. | |
| Knowledge rating | It enables users to provide feedback as a rating for the document search corresponding to the ticket summary. | |
| iScrape | It helps in automated runbook creation for ticket categories for which runbooks don’t exist by exploring various internal and external data sources for relevant executable code snippets and scripts. |
Before starting the installation, identify the components that user needs to install based on the requirement. Also, the user needs to identify the deployment mode from the below list based on the Environment categorization identified earlier.