This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 115
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Samples] Add 13-core.bot sample (#1034)
* Add main pom for core-bot sample * Add deploymentTemplates folder * Add cognitiveModels folder * Add main documentation of the sample * Add dialogs classes * Add resources folder * Add webapp folder * Add bot for sample * Add BookingDetails model * Add recognizer for LUIS model * Add Startup file * Add package-info * Add empty test for sample
- Loading branch information
Showing
24 changed files
with
3,003 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
MIT License | ||
|
||
Copyright (c) Microsoft Corporation. All rights reserved. | ||
|
||
Permission is hereby granted, free of charge, to any person obtaining a copy | ||
of this software and associated documentation files (the "Software"), to deal | ||
in the Software without restriction, including without limitation the rights | ||
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
copies of the Software, and to permit persons to whom the Software is | ||
furnished to do so, subject to the following conditions: | ||
|
||
The above copyright notice and this permission notice shall be included in all | ||
copies or substantial portions of the Software. | ||
|
||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE | ||
SOFTWARE |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,216 @@ | ||
# Setting up LUIS via CLI: | ||
|
||
This README contains information on how to create and deploy a LUIS application. When the bot is ready to be deployed to production, we recommend creating a LUIS Endpoint Resource for usage with your LUIS App. | ||
|
||
> _For instructions on how to create a LUIS Application via the LUIS portal, see these Quickstart steps:_ | ||
> 1. _[Quickstart: Create a new app in the LUIS portal][Quickstart-create]_ | ||
> 2. _[Quickstart: Deploy an app in the LUIS portal][Quickstart-deploy]_ | ||
[Quickstart-create]: https://docs.microsoft.com/azure/cognitive-services/luis/get-started-portal-build-app | ||
[Quickstart-deploy]:https://docs.microsoft.com/azure/cognitive-services/luis/get-started-portal-deploy-app | ||
|
||
## Table of Contents: | ||
|
||
- [Prerequisites](#Prerequisites) | ||
- [Import a new LUIS Application using a local LUIS application](#Import-a-new-LUIS-Application-using-a-local-LUIS-application) | ||
- [How to create a LUIS Endpoint resource in Azure and pair it with a LUIS Application](#How-to-create-a-LUIS-Endpoint-resource-in-Azure-and-pair-it-with-a-LUIS-Application) | ||
|
||
___ | ||
|
||
## [Prerequisites](#Table-of-Contents): | ||
|
||
#### Install Azure CLI >=2.0.61: | ||
|
||
Visit the following page to find the correct installer for your OS: | ||
- https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest | ||
|
||
#### Install LUIS CLI >=2.4.0: | ||
|
||
Open a CLI of your choice and type the following: | ||
|
||
```bash | ||
npm i -g luis-apis@^2.4.0 | ||
``` | ||
|
||
#### LUIS portal account: | ||
|
||
You should already have a LUIS account with either https://luis.ai, https://eu.luis.ai, or https://au.luis.ai. To determine where to create a LUIS account, consider where you will deploy your LUIS applications, and then place them in [the corresponding region][LUIS-Authoring-Regions]. | ||
|
||
After you've created your account, you need your [Authoring Key][LUIS-AKey] and a LUIS application ID. | ||
|
||
[LUIS-Authoring-Regions]: https://docs.microsoft.com/azure/cognitive-services/luis/luis-reference-regions#luis-authoring-regions] | ||
[LUIS-AKey]: https://docs.microsoft.com/azure/cognitive-services/luis/luis-concept-keys#authoring-key | ||
|
||
___ | ||
|
||
## [Import a new LUIS Application using a local LUIS application](#Table-of-Contents) | ||
|
||
### 1. Import the local LUIS application to luis.ai | ||
|
||
```bash | ||
luis import application --region "LuisAppAuthoringRegion" --authoringKey "LuisAuthoringKey" --appName "FlightBooking" --in "./cognitiveModels/FlightBooking.json" | ||
``` | ||
|
||
Outputs the following JSON: | ||
|
||
```json | ||
{ | ||
"id": "########-####-####-####-############", | ||
"name": "FlightBooking", | ||
"description": "A LUIS model that uses intent and entities.", | ||
"culture": "en-us", | ||
"usageScenario": "", | ||
"domain": "", | ||
"versionsCount": 1, | ||
"createdDateTime": "2019-03-29T18:32:02Z", | ||
"endpoints": {}, | ||
"endpointHitsCount": 0, | ||
"activeVersion": "0.1", | ||
"ownerEmail": "[email protected]", | ||
"tokenizerVersion": "1.0.0" | ||
} | ||
``` | ||
|
||
For the next step, you'll need the `"id"` value for `--appId` and the `"activeVersion"` value for `--versionId`. | ||
|
||
### 2. Train the LUIS Application | ||
|
||
```bash | ||
luis train version --region "LuisAppAuthoringRegion" --authoringKey "LuisAuthoringKey" --appId "LuisAppId" --versionId "LuisAppversion" --wait | ||
``` | ||
|
||
### 3. Publish the LUIS Application | ||
|
||
```bash | ||
luis publish version --region "LuisAppAuthoringRegion" --authoringKey "LuisAuthoringKey" --appId "LuisAppId" --versionId "LuisAppversion" --publishRegion "LuisAppPublishRegion" | ||
``` | ||
|
||
> `--region` corresponds to the region you _author_ your application in. The regions available for this are "westus", "westeurope" and "australiaeast". <br/> | ||
> These regions correspond to the three available portals, https://luis.ai, https://eu.luis.ai, or https://au.luis.ai. <br/> | ||
> `--publishRegion` corresponds to the region of the endpoint you're publishing to, (e.g. "westus", "southeastasia", "westeurope", "brazilsouth"). <br/> | ||
> See the [reference docs][Endpoint-API] for a list of available publish/endpoint regions. | ||
[Endpoint-API]: https://westus.dev.cognitive.microsoft.com/docs/services/5819c76f40a6350ce09de1ac/operations/5819c77140a63516d81aee78 | ||
|
||
Outputs the following: | ||
|
||
```json | ||
{ | ||
"versionId": "0.1", | ||
"isStaging": false, | ||
"endpointUrl": "https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/########-####-####-####-############", | ||
"region": "westus", | ||
"assignedEndpointKey": null, | ||
"endpointRegion": "westus", | ||
"failedRegions": "", | ||
"publishedDateTime": "2019-03-29T18:40:32Z", | ||
"directVersionPublish": false | ||
} | ||
``` | ||
|
||
To see how to create an LUIS Cognitive Service Resource in Azure, please see [the next README][README-LUIS]. This Resource should be used when you want to move your bot to production. The instructions will show you how to create and pair the resource with a LUIS Application. | ||
|
||
[README-LUIS]: ./README-LUIS.md | ||
|
||
___ | ||
|
||
## [How to create a LUIS Endpoint resource in Azure and pair it with a LUIS Application](#Table-of-Contents) | ||
|
||
### 1. Create a new LUIS Cognitive Services resource on Azure via Azure CLI | ||
|
||
> _Note:_ <br/> | ||
> _If you don't have a Resource Group in your Azure subscription, you can create one through the Azure portal or through using:_ | ||
> ```bash | ||
> az group create --subscription "AzureSubscriptionGuid" --location "westus" --name "ResourceGroupName" | ||
> ``` | ||
> _To see a list of valid locations, use `az account list-locations`_ | ||
```bash | ||
# Use Azure CLI to create the LUIS Key resource on Azure | ||
az cognitiveservices account create --kind "luis" --name "NewLuisResourceName" --sku "S0" --location "westus" --subscription "AzureSubscriptionGuid" -g "ResourceGroupName" | ||
``` | ||
The command will output a response similar to the JSON below: | ||
|
||
```json | ||
{ | ||
"endpoint": "https://westus.api.cognitive.microsoft.com/luis/v2.0", | ||
"etag": "\"########-####-####-####-############\"", | ||
"id": "/subscriptions/########-####-####-####-############/resourceGroups/ResourceGroupName/providers/Microsoft.CognitiveServices/accounts/NewLuisResourceName", | ||
"internalId": "################################", | ||
"kind": "luis", | ||
"location": "westus", | ||
"name": "NewLuisResourceName", | ||
"provisioningState": "Succeeded", | ||
"resourceGroup": "ResourceGroupName", | ||
"sku": { | ||
"name": "S0", | ||
"tier": null | ||
}, | ||
"tags": null, | ||
"type": "Microsoft.CognitiveServices/accounts" | ||
} | ||
``` | ||
|
||
|
||
|
||
Take the output from the previous command and create a JSON file in the following format: | ||
|
||
```json | ||
{ | ||
"azureSubscriptionId": "00000000-0000-0000-0000-000000000000", | ||
"resourceGroup": "ResourceGroupName", | ||
"accountName": "NewLuisResourceName" | ||
} | ||
``` | ||
|
||
### 2. Retrieve ARM access token via Azure CLI | ||
|
||
```bash | ||
az account get-access-token --subscription "AzureSubscriptionGuid" | ||
``` | ||
|
||
This will return an object that looks like this: | ||
|
||
```json | ||
{ | ||
"accessToken": "eyJ0eXAiOiJKVtokentokentokentokentokeng1dCI6Ik4tbEMwbi05REFMcXdodUhZbkhRNjNHZUNYYyIsItokenI6Ik4tbEMwbi05REFMcXdodUhZbkhRNjNHZUNYYyJ9.eyJhdWQiOiJodHRwczovL21hbmFnZW1lbnQuY29yZS53aW5kb3dzLm5ldC8iLCJpc3MiOiJodHRwczovL3N0cy53aW5kb3dzLm5ldC83MmY5ODhiZi04NmYxLTQxYWYtOTFhYi0yZDdjZDAxMWRiNDcvIiwiaWF0IjoxNTUzODc3MTUwLCJuYmYiOjE1NTM4NzcxNTAsImV4cCI6MTU1Mzg4MTA1MCwiX2NsYWltX25hbWVzIjp7Imdyb3VwcyI6InNyYzEifSwiX2NsYWltX3NvdXJjZXMiOnsic3JjMSI6eyJlbmRwb2ludCI6Imh0dHBzOi8vZ3JhcGgud2luZG93cy5uZXQvNzJmOTg4YmYtODZmMS00MWFmLTkxYWItMmQ3Y2QwMTFkYjQ3L3VzZXJzL2ZmZTQyM2RkLWJhM2YtNDg0Ny04NjgyLWExNTI5MDA4MjM4Ny9nZXRNZW1iZXJPYmplY3RzIn19LCJhY3IiOiIxIiwiYWlvIjoiQVZRQXEvOEtBQUFBeGVUc201NDlhVHg4RE1mMFlRVnhGZmxxOE9RSC9PODR3QktuSmRqV1FqTkkwbmxLYzB0bHJEZzMyMFZ5bWZGaVVBSFBvNUFFUTNHL0FZNDRjdk01T3M0SEt0OVJkcE5JZW9WU0dzd0kvSkk9IiwiYW1yIjpbIndpYSIsIm1mYSJdLCJhcHBpZCI6IjA0YjA3Nzk1LThkZGItNDYxYS1iYmVlLTAyZjllMWJmN2I0NiIsImFwcGlkYWNyIjoiMCIsImRldmljZWlkIjoiNDhmNDVjNjEtMTg3Zi00MjUxLTlmZWItMTllZGFkZmMwMmE3IiwiZmFtaWx5X25hbWUiOiJHdW0iLCJnaXZlbl9uYW1lIjoiU3RldmVuIiwiaXBhZGRyIjoiMTY3LjIyMC4yLjU1IiwibmFtZSI6IlN0ZXZlbiBHdW0iLCJvaWQiOiJmZmU0MjNkZC1iYTNmLTQ4NDctODY4Mi1hMTUyOTAwODIzODciLCJvbnByZW1fc2lkIjoiUy0xLTUtMjEtMjEyNzUyMTE4NC0xNjA0MDEyOTIwLTE4ODc5Mjc1MjctMjYwOTgyODUiLCJwdWlkIjoiMTAwMzdGRkVBMDQ4NjlBNyIsInJoIjoiSSIsInNjcCI6InVzZXJfaW1wZXJzb25hdGlvbiIsInN1YiI6Ik1rMGRNMWszN0U5ckJyMjhieUhZYjZLSU85LXVFQVVkZFVhNWpkSUd1Nk0iLCJ0aWQiOiI3MmY5ODhiZi04NmYxLTQxYWYtOTFhYi0yZDdjZDAxMWRiNDciLCJ1bmlxdWVfbmFtZSI6InN0Z3VtQG1pY3Jvc29mdC5jb20iLCJ1cG4iOiJzdGd1bUBtaWNyb3NvZnQuY29tIiwidXRpIjoiT2w2NGN0TXY4RVNEQzZZQWRqRUFtokenInZlciI6IjEuMCJ9.kFAsEilE0mlS1pcpqxf4rEnRKeYsehyk-gz-zJHUrE__oad3QjgDSBDPrR_ikLdweynxbj86pgG4QFaHURNCeE6SzrbaIrNKw-n9jrEtokenlosOxg_0l2g1LeEUOi5Q4gQREAU_zvSbl-RY6sAadpOgNHtGvz3Rc6FZRITfkckSLmsKAOFoh-aWC6tFKG8P52rtB0qVVRz9tovBeNqkMYL49s9ypduygbXNVwSQhm5JszeWDgrFuVFHBUP_iENCQYGQpEZf_KvjmX1Ur1F9Eh9nb4yI2gFlKncKNsQl-tokenK7-tokentokentokentokentokentokenatoken", | ||
"expiresOn": "2200-12-31 23:59:59.999999", | ||
"subscription": "AzureSubscriptionGuid", | ||
"tenant": "tenant-guid", | ||
"tokenType": "Bearer" | ||
} | ||
``` | ||
|
||
The value needed for the next step is the `"accessToken"`. | ||
|
||
### 3. Use `luis add appazureaccount` to pair your LUIS resource with a LUIS Application | ||
|
||
```bash | ||
luis add appazureaccount --in "path/to/created/requestBody.json" --appId "LuisAppId" --authoringKey "LuisAuthoringKey" --armToken "accessToken" | ||
``` | ||
|
||
If successful, it should yield a response like this: | ||
|
||
```json | ||
{ | ||
"code": "Success", | ||
"message": "Operation Successful" | ||
} | ||
``` | ||
|
||
### 4. See the LUIS Cognitive Services' keys | ||
|
||
```bash | ||
az cognitiveservices account keys list --name "NewLuisResourceName" --subscription "AzureSubscriptionGuid" -g "ResourceGroupName" | ||
``` | ||
|
||
This will return an object that looks like this: | ||
|
||
```json | ||
{ | ||
"key1": "9a69####dc8f####8eb4####399f####", | ||
"key2": "####f99e####4b1a####fb3b####6b9f" | ||
} | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
# CoreBot | ||
|
||
Bot Framework v4 core bot sample. | ||
|
||
This bot has been created using [Bot Framework](https://dev.botframework.com), it shows how to: | ||
|
||
- Use [LUIS](https://www.luis.ai) to implement core AI capabilities | ||
- Implement a multi-turn conversation using Dialogs | ||
- Handle user interruptions for such things as `Help` or `Cancel` | ||
- Prompt for and validate requests for information from the user | ||
|
||
## Prerequisites | ||
|
||
This sample **requires** prerequisites in order to run. | ||
|
||
### Overview | ||
|
||
This bot uses [LUIS](https://www.luis.ai), an AI based cognitive service, to implement language understanding. | ||
|
||
### Create a LUIS Application to enable language understanding | ||
|
||
The LUIS model for this example can be found under `cognitiveModels/FlightBooking.json` and the LUIS language model setup, training, and application configuration steps can be found [here](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-howto-v4-luis?view=azure-bot-service-4.0&tabs=cs). | ||
|
||
Once you created the LUIS model, update `application.properties` with your `LuisAppId`, `LuisAPIKey` and `LuisAPIHostName`. | ||
|
||
``` | ||
LuisAppId="Your LUIS App Id" | ||
LuisAPIKey="Your LUIS Subscription key here" | ||
LuisAPIHostName="Your LUIS App region here (i.e: westus.api.cognitive.microsoft.com)" | ||
``` | ||
|
||
## To try this sample | ||
|
||
- From the root of this project folder: | ||
- Build the sample using `mvn package` | ||
- Run it by using `java -jar .\target\bot-core-sample.jar` | ||
|
||
## Testing the bot using Bot Framework Emulator | ||
|
||
[Bot Framework Emulator](https://github.com/microsoft/botframework-emulator) is a desktop application that allows bot developers to test and debug their bots on localhost or running remotely through a tunnel. | ||
|
||
- Install the latest Bot Framework Emulator from [here](https://github.com/Microsoft/BotFramework-Emulator/releases) | ||
|
||
### Connect to the bot using Bot Framework Emulator | ||
|
||
- Launch Bot Framework Emulator | ||
- File -> Open Bot | ||
- Enter a Bot URL of `http://localhost:3978/api/messages` | ||
|
||
## Deploy the bot to Azure | ||
|
||
To learn more about deploying a bot to Azure, see [Deploy your bot to Azure](https://aka.ms/azuredeployment) for a complete list of deployment instructions. | ||
|
||
## Further reading | ||
|
||
- [Bot Framework Documentation](https://docs.botframework.com) | ||
- [Bot Basics](https://docs.microsoft.com/azure/bot-service/bot-builder-basics?view=azure-bot-service-4.0) | ||
- [Dialogs](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-concept-dialog?view=azure-bot-service-4.0) | ||
- [Gathering Input Using Prompts](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-prompts?view=azure-bot-service-4.0&tabs=csharp) | ||
- [Activity processing](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-concept-activity-processing?view=azure-bot-service-4.0) | ||
- [Azure Bot Service Introduction](https://docs.microsoft.com/azure/bot-service/bot-service-overview-introduction?view=azure-bot-service-4.0) | ||
- [Azure Bot Service Documentation](https://docs.microsoft.com/azure/bot-service/?view=azure-bot-service-4.0) | ||
- [Azure CLI](https://docs.microsoft.com/cli/azure/?view=azure-cli-latest) | ||
- [Azure Portal](https://portal.azure.com) | ||
- [Language Understanding using LUIS](https://docs.microsoft.com/en-us/azure/cognitive-services/luis/) | ||
- [Channels and Bot Connector Service](https://docs.microsoft.com/en-us/azure/bot-service/bot-concepts?view=azure-bot-service-4.0) | ||
- [Spring Boot](https://spring.io/projects/spring-boot) |
Oops, something went wrong.