Question - How are watson-conversation-setup.js and watson-discovery-setup.js used to setup Watson services in IBM cloud?

[ibm]

Question - How are watson-conversation-setup.js and watson-discovery-setup.js used to setup Watson services in IBM cloud?

[stevemar]

Hi @lee-zhg we use watson-conversation-setup.js when the app is initialized for the first time. See

watson-banking-chatbot/app.js

Line 40 in a305473

const WatsonConversationSetup = require('./lib/watson-conversation-setup');

and

watson-banking-chatbot/app.js

Lines 116 to 126 in a305473

	const conversationSetup = new WatsonConversationSetup(conversation);
	const workspaceJson = JSON.parse(fs.readFileSync('data/conversation/workspaces/banking.json'));
	const conversationSetupParams = { default_name: DEFAULT_NAME, workspace_json: workspaceJson };
	conversationSetup.setupConversationWorkspace(conversationSetupParams, (err, data) => {
	if (err) {
	handleSetupError(err);
	} else {
	console.log('Watson Assistant is ready!');
	workspaceID = data;
	}
	});

The intention, for watson-conversation-setup.js, is to upload the conversation dialog (https://github.com/IBM/watson-banking-chatbot/blob/master/data/conversation/workspaces/banking.json) using the Node SDK.

We mainly do this so the user doesn't have to: 1) clone the repo, 2) go through IBM Cloud find their service, 3) launch Watson Assistant tooling, 4) upload the workspace, 5) reload the app. They should be able to just run it, and we do some smart setup in the background.

It's particularly useful when showing demos of this chatbot.

[stevemar]

Oh, and watson-discovery-setup.js accomplishes the same thing (except we push documents to discovery instead of a conversation dialog), and is used around the same time.

The conversation logic works much more cleanly since it's only uploading a single JSON file. For discovery, we've had some issues since discovery supports configuration and data files too.