Versions Compared

Old Version 4

changes.mady.by.user Gardner, I.V. (Bella)

Saved on

compared with

New Version Current

changes.mady.by.user Koen Hindriks

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are two parts to getting your conversational agent up and running. The first part consists of launching the basic SIC infrastructure. We need to launch the Dialogflow and web server components of the infrastructure, which are both used in this project. The second part consists of launching your MARBEL agent, which implements the dialog manager and webpage, and connecting it to the SIC infrastructure.

Info

Once you have the SIC infrastructure up and running, you do not need to relaunch SIC every time. You can thus skip the first part once that has been done. For each change that you make to your MARBEL agent, of course, you need to restart it to see the effects of those changes.

First part: Launch the SIC infrastructure

  • Open a command terminal in your machine and navigate to the folder (called docker by default) where you cloned the SICproject.

Note

Make sure you have Docker up and running before you proceed!

  • Enter docker-compose up dialogflow webserver and hit enter.

  • Open a second terminal and navigate to the subfolder sic-local in the docker folder.

  • Enter java -jar computer-browser.jar and hit enter. After running java -jar computer-browser.jar a pop-up should appear like the one in the left-hand corner of the picture below. Click okay without filling in a username and password.

  • Then a Google Chrome window should open. It should say it is being controlled by automated test software and displays a long string of random characters. In your terminal, it should say ‘ChromeDriver was started successfully’ in one of the lines.

    (If you have entered flowkey and flow agent)
Note

Do not close the terminals you used for launching the SIC infrastructure. You can inspect these terminals too to see what is going on with Dialogflow, for example.

If the Chrome browser shows Disconnected, you need to relaunch the SIC infrastructure. You can use the docker-compose down command in a terminal to clean up your docker engine.

Second part: Launch the MARBEL agent

  • Launch the .mas2g file in your agent project, for example, by right-clicking on it and choosing Debug As → MARBEL from the menu. A popup should appear like the one in the left-hand corner of the picture below. The empty box in the popup next to the browser code should be ticked. Note that the : The browser code should match the code that is displayed in the Google Chrome window used by the agent. Finally, hit OK.

...

Note

If you want to restart your MARBEL agent, make sure your previous agent has been terminated before you restart it!

You can do this by checking the Debug perspective in Eclipse. If the agent is still up and running, select the MARBEL Debugging Engine, and press Terminate (red button). Press ‘xx’ to Remove All Terminated Launches to clean up the perspective.