e01aef1322
* Fix double brace in botbuilder library * Fix double brace in botbuilder-dialogs library * Fix double brace in bot-schema library * Fix double brace in bot-ai-luis library * Fix double brace in bot-ai-qna library * Fix double brace in bot-azure library * Fix double brace in bot-connector library * Fix double brace in bot-integration library * Fix double brace in sample 3 * Fix double brace in sample 6 * Fix double brace in sample 7 * Fix double brace in sample 8 * Fix double brace in sample 11 * Fix double brace in sample 15 * Fix double brace in sample 17 * Fix double brace in sample 50 * Fix double brace in sample 51 * Fix double brace in sample 52 * Fix double brace in sample 53 * Fix double brace in sample 54 * Fix double brace in sample 55 * Fix double brace in sample 56 * Fix double brace in sample 57 * Fix double brace in sample 58 * Fix double brace in sample 81 * Fix double brace in sample 13 * Replicate change in generator for core bot template |
||
---|---|---|
.. | ||
deploymentTemplates | ||
src | ||
LICENSE | ||
README.md | ||
pom.xml |
README.md
Welcome users bot sample
This bot has been created using Bot Framework, is shows how to welcome users when they join the conversation.
This sample is a Spring Boot app and uses the Azure CLI and azure-webapp Maven plugin to deploy to Azure.
Prerequisites
To try this sample locally
-
From the root of this project folder:
- Build the sample using
mvn package
- Run it by using
java -jar .\target\bot-welcomeuser-sample.jar
- Build the sample using
-
Test the bot using Bot Framework Emulator
Bot Framework 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 Bot Framework Emulator version 4.3.0 or greater from here
-
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
As described on Deploy your bot, you will perform the first 4 steps to setup the Azure app, then deploy the code using the azure-webapp Maven plugin.
1. Login to Azure
From a command (or PowerShell) prompt in the root of the bot folder, execute:
az login
2. Set the subscription
az account set --subscription "<azure-subscription>"
If you aren't sure which subscription to use for deploying the bot, you can view the list of subscriptions for your account by using az account list
command.
3. Create an App registration
az ad app create --display-name "<botname>" --password "<appsecret>" --available-to-other-tenants
Replace <botname>
and <appsecret>
with your own values.
<botname>
is the unique name of your bot.
<appsecret>
is a minimum 16 character password for your bot.
Record the appid
from the returned JSON
4. Create the Azure resources
Replace the values for <appid>
, <appsecret>
, <botname>
, and <groupname>
in the following commands:
To a new Resource Group
az deployment sub create --name "welcomBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" botSku=S1 newAppServicePlanName="welcomBotPlan" newWebAppName="welcomBot" groupLocation="westus" newAppServicePlanLocation="westus"
To an existing Resource Group
az deployment group create --resource-group "<groupname>" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" newWebAppName="welcomBot" newAppServicePlanName="welcomBotPlan" appServicePlanLocation="westus" --name "welcomBot"
5. Update app id and password
In src/main/resources/application.properties update
MicrosoftAppPassword
with the botsecret valueMicrosoftAppId
with the appid from the first step
6. Deploy the code
- Execute
mvn clean package
- Execute
mvn azure-webapp:deploy -Dgroupname="<groupname>" -Dbotname="<botname>"
If the deployment is successful, you will be able to test it via "Test in Web Chat" from the Azure Portal using the "Bot Channel Registration" for the bot.
After the bot is deployed, you only need to execute #6 if you make changes to the bot.