IBM conversation still works with botframework?

Question

I followed this tutorial chatbot with watson conversation + botframwork to build a chatbot using bot framework with watson conversation. It worked just fine in the emulator, however when I add the Microsoft App Id and Password it stops responding. When I am working on the Azure Portal the bot ceases responding on web chat testing when I change the message endpoint (https://[myapp].bluemix.net/api/messages). Is there still a problem going on with the endpoint messages or the emulator?

I haven't looked at the code recently, but there was an SDK change for conversation where message_input was changed to input for argument on the message call. — Simon O'Doherty

JJ_Wailes JJ_Wailes · Accepted Answer · 2018-08-14T17:23:35

I recently had a similar issue with changing messaging endpoints on bots via the Azure Portal, though I was just trying to use ngrok. If you change the endpoint, the bot does in fact, cease to respond. The work around for this is to put your Microsoft AppId and AppPassword in your bot code, to validate it.

I'm not sure how Watson works, but for BotBuilder node.js bots, the code below is what you have to do to connect the non-azure code to the bot endpoint:

var builder = require('botbuilder')
var connector = new builder.ChatConnector({
    appId: process.env.MICROSOFT_APP_ID,
    appPassword: process.env.MICROSOFT_APP_PASSWORD
});

Here is the link to bot-builder's ChatConnector in the documentation so you can see exactly what it does, and find a way to implement it in your Watson code.

IBM conversation still works with botframework?

1 Answers