This article deals with the following topics:
...
- Click Create Tenant on the Tenant Management page.
- On the Tenant details section, specify the following information:
- Tenant name.
- The tenant which is used when logging into the Bot Builder.
- The tenant ID which must fall in the range from 1000 to 999999999. If you do not specify the tenant id, a unique id is auto-generated after the tenant is created.
- Specify the symbol. This symbol is used internally to identify the tenant in the database. The maximum number of characters is limited to 6. The allowed characters are A-Z, a-z, 0-9,_. Values must start with a letter and must not end with _(underscore).
- Click on Next to add Default Bot & Domain Details. By default, the data is automatically populated based on the Tenant Details section. However, you can configure the bot and domain details, if required.
- The bot name. This is used to identify the bot easily in the Bot Builder.
- Select the language that the bot can communicate with the user. Currently, the bot supports the following languages:
- English
- Chinese
- Japanese
- Spanish
- Portuguese
- Build and Publish Service: The Service assigned to the Tenant, required to build and publish the training data to the bot. It could be AWS Sagemaker or RASA Adapter.
- The bot symbol. This symbol is used internally to identify the bot in the database. The maximum number of characters is limited to 6. The allowed characters are A-Z, a-z, 0-9,_. Values must start with a letter and must not end with _(underscore).
- The domain name. The skills and attributes are associated with a domain.
The unique identifier for the domain.
Info title AWS Sagemaker - RASA adapter runs the Build and Publish process on the Local infrastructure.
- Run time performance is better on AWS SageMaker.
- Customers must subscribe to AWS services and configure AWS SageMaker for On-Premise implementations.
- Click Next to navigate to Tenant Administrator Details to define the tenant administrator information:
- The username of the tenant administrator.
- The email id of the tenant administrator.
- The password using which the tenant administrator can log in to the Bot Builder.
- Select the language from English or Chinese. This is the language to be used across the Bot Builder UI.
- The first name of the tenant administrator.
- The last name of the tenant administrator.
- Click Next to navigate to Automation Integration, to enable automation for the tenant. Luma supports Flint automation.
To configure automation with Flint, follow the below steps:- Select Enable Provision AutomationAdd the required details to connect to the Flint
- Domain: Represents your tenant, as in Flint tenant
- Organization: Represents your organization, as in Flint tenant
- Email Address: Email address, as in Flint tenant
- User Name: Username, as in Flint tenant
- Password: Username, as in Flint tenant
- Token: This is the secret key generated for your Flint tenant
Flint UserID: This is the flintUserUuid generated for your Flint tenant
The above information is added or generated in Flint while creating tenant for your organization.Info - Select ‘Automation Version’ as V2
- Add Automation Tenant Identifier and Access Token in retrieved from ITAS Tenant Provisioning API in ‘Tenant Secret Key’ fields in VSA.
Click Save.
FlintInfo The above information is generated through ITAS Tenant Provisioning API. Contact the Serviceaide support team to create your tenant in
ITAS and obtain the details required to enable automation for your tenant in Luma VA.
...
Info |
---|
Please ensure that the correct Subscription type is selected while Tenant creation. Once Tenant is created License Type and Contract duration cannot be updated |
.
View Tenant Details
To view the tenant details, select one of the tenants from the Tenant Management list.
...