Your Aisera Tenant
Each Aisera customer has an instance of the Aisera Gen AI Platform, called a Tenant. Each tenant runs in the Aisera Cloud (computing space purchased by Aisera), and each tenant has a separate URL address, known as an endpoint.
The Aisera Gen AI Platform uses a multi-tenant architecture, which means that for each customer, there is a separate container with server software, a temporary data store (used only by the bot application(s) for that customer, and some shared processing modules (for CPU and GPU processing).
Your Aisera Team will assign you a Tenant ID that will define your tenant instance.
Use the Tenant ID when you log into your Aisera Gen AI Platform instance.
Multiple Bots Per Tenant Instance
Many companies create a single bot for a single purpose that uses the resources of their tenant. But you can create multiple bots for your company tenant instance. For instance, you may want an IT bot to help with IT requests, and an HR bot to help with HR requests.
The bots you create will share tenant parameters. But each bot has their own Bot ID and some unique parameters.
Universal Bot
If your company wants to use more than one bot, you can create separate bots or create a Universal Bot that connects them.
Connect a Data Source
To integrate a Data Source with your Aisera Tenant Instance, you need to perform two connector steps:
Add Integration
Add Data Source
Integrate a Data Source with Your Tenant
The Aisera term Integration means to create a way for either an Aisera user to log onto your data source and bring data to the temporary data store on your tenant, or for a user of your data source to log onto your Aisera tenant and transfer data to the temporary data store on your tenant.
Setting up the authentication credentials for this exchange is known as Creating the Integration. If your Aisera tenant user is logging on to your integrated data source, the login may include the authorization credentials, like this:
https://<tenantId>.login.aisera.cloud/?id=aisera.oauth.oauthCommandYou don't have to remember this, it will be explained again in future sessions.
When you add a tenant-level data source, navigate to Settings > Integrations in the Aisera Admin UI and you will see that we have many commercial sources that are pre-mapped to the Aisera GenAI Platform.
The steps to connect many of these sources is documented here. If the source you're connecting to is not documented yet, find out the authentication type you need to use, and follow these general instructions.
Map the Data from the Source to the Aisera Platform
The term Data Source for the Aisera Gen AI Platform is usually the tool that your company uses to create shared information, such as Tickets or Knowledge Base Articles that the platform will ingest and keep in temporary storage.
A few of the common software tools are Salesforce, ServiceNow, and Zendesk. For commonly used software tools, the Aisera Gen AI Platform has pre-mapped configurations that you can apply to your tenant using the Aisera Administration Application (also known as the Aisera Admin UI).
If the source you want to add is not in the Settings > Data Source> + New Data Source list, you can use a Generic Integration and then use Field Mapping.
Mapped Fields
The term Mapped Fields in the Aisera Gen AI Platform means that there is a software map where the Aisera Gen AI Platform, your Aisera Team, or you (with the Aisera Admin UI) have created a one-to-one correspondence between the fields in the Aisera Gen AI Platform's Data Model and the fields in your Ticket or Knowledge Tools.
For instance, if you plan to use Tickets from your Salesforce tool as a source of information for your bot responses, then you need to create an Integration for your Salesforce instance so you can ingest the data from the Tickets table and the other tables in Salesforce that are related to the Tickets table (to make a complete Ticket). Then you will Add a Salesforce Data Source to your tenant, and this will connect the pre-mapped Salesforce fields with the fields in the Aisera Gen AI Platform so that the data can be transferred to the temporary data store on your tenant instance. The example below displays the names of Aisera Knowledge Base Article fields on the left side and the corresponding Salesforce fields for Knowledge Base Articles on the right.
You can see the table above on the Data Source Details page of the Aisera Admin UI after you run a Data Ingestion Job, as described below.
Ingest the Data
After you have mapped your Data Source with the Aisera Gen AI Platform fields (either using the Aisera Admin UI or with a JSON file), you need to run a Data Ingestion Job to copy the data from your source to your tenant instance.
Associate the Tenant Data Source with a Bot
The last step in the data connection process is associating the Data Source with your Bot. You can do this any time AFTER you run a Data Ingestion Job, but BEFORE you complete your Bot configuration.
After you have performed the initial steps of bot creation, choose the
button to associated the tenant data source with your bot.
Choosing the tenant data source for your bot allows the bot to use the data from the connected source.
Tenant Configuration Options
There are many tenant configuration options in the Aisera Gen AI Platform. If you suspect that something in your tenant configuration is not set correctly, you can check the Tenant Configuration Options.
Last updated