notice

This is documentation for Rasa Enterprise Documentation v1.1.x, which is no longer actively maintained.
For up-to-date documentation, see the latest version (1.2.x).

Version: 1.1.x

Add an Action Server

Disabling the Default Action Server

If you are not running an action server at all, and you don't want the default app service to run as a placeholder, you can disable installation of the action server:

app:
install: false

Adding a Custom Action Server

note

Rasa Enterprise does not communicate directly with the action server. Only Rasa Open Source servers communicate with the action server. Because Rasa Enterprise can start Rasa Open Source servers, it can also start an action server, however it is recommended to start both Rasa Open Source and action server separately using their respective Helm Charts.

To run a custom action server you need a Docker image for your action server. Please see Building an Action Server Image for more information.

To deploy a custom action server, you can either:

  1. Use the Rasa Action Server Helm Chart to deploy your action server. This is the recommended method.
  2. Use the Rasa Enterprise Helm Chart to deploy your action server.

Starting an Action Server using the Rasa Action Server Helm Chart

  1. Follow the instructions on the Rasa SDK docs for deploying an action server using the Rasa Action Server Helm Chart.

  2. Disable installation of the action server by the Rasa Enterprise Helm chart and specify the URL of your separately deployed action server:

    app:
    install: false
    existingUrl: http://myactionserver:5055/webhook

    This will take care of passing the correct action server endpoint to any Rasa Open Source servers started by the Rasa Enterprise Helm chart.

  3. For any Rasa Open Source servers that are started by the Rasa Helm chart, follow the instructions to connect your Rasa Open Source deployments to the action server.

Starting an Action Server using the Rasa Enterprise Helm Chart

  1. Add the image and tag you want to use to the app section of values.yml. If your image is stored in a private registry, please refer to Adding Image Pull Secrets for Private Registries.

    # app (custom action server) specific settings
    app:
    install: true
    name: "<name of your action server image>"
    tag: "<tag of your image>"

    This will also take care of passing the correct action server endpoint to any Rasa Open Source servers started by the Rasa Enterprise Helm chart.

  2. For any Rasa Open Source servers that are started by the Rasa Helm chart, follow the instructions to connect your Rasa Open Source deployments to the action server.