Once you have built a bot and you feel it is ready to be shared with the public, you can publish it to an engine. This makes your bot available as a service that can be accessed via HTTPS. The SDK's and connectors documented in this section interact with the engine and help you make your bot come alive on various channels.
For a solution to be published in Teneo, it needs to get one or more publish environments. A publish environment specifies various details of the server your solution will be published to, like the type of server (development, QA, production) and, quite importantly, its URL.
In the Teneo Developer sandbox, publishing is limited to 7 bots per team. A publishing environment is automatically added to the first 7 bots.
To publish your bot, proceed as follows:
You might see a warning saying 'Publish to 'Default env' stopped with warnings. '
This is nothing to worry about; the warning is shown when you publish your solution for the first time or when you have made certain global changes. To proceed, just check the checkbox 'Perform full application deployment on Try again' and click the 'Try again' button.
The publication may take a couple of minutes; the video below is sped up slightly. When it has finished, you'll receive a confirmation pop-up.
If you are using Version Flags in your solution, proceed as follows to publish your 'Stable' version:
Time to meet your bot! Click 'Open' in the publication confirmation pop-up. If you have already closed it, you can simply click the URL that is shown in the 'Publish' window instead. This will open a Teneo Web Chat web page where you can try out your bot.
In addition to the features above, a license in Teneo also includes different setups for publish environments. These are known as the three stages of a project: Development, Quality Assurance (QA), and Production. The user has the option to set up these publish environments to make sure the project is running smoothly during the different stages.
It is also possible to publish the solution as a .WAR file. To do this, please select the 'Add Environment' button, followed by 'Local File' inside the Publish page.
Was this page helpful?