Versions Compared

Old Version 1

changes.mady.by.user Chitra Borker

Saved on

compared with

New Version Current

changes.mady.by.user Chitra Borker

Saved on

Key

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

Use an Orchestration Server if you're using unsupported NLP services, building a custom backend, implementing rich authentication, or requiring flexible data analytics. Orchestration servers are useful when you are using unsupported NLP services, designing a custom backend, implementing rich authentication, or need flexible data analytics. 

To view the configuration fields, navigate to Configure Deployment section within Digital DNA Studio and expand the Orchestration Server option. Fill in the fields as required to establish the connection to your Orchestration Server. 

Using a Custom UI with an Orchestration Server

If you are using a Custom UI specifically to support an Orchestration Server, you can create a duplicate of your project within Studio, set it to use the Default UI, and specify your Orchestration Server details. Once deployed, you can utilize the new Digital Person and deprecate the old one.

If you are using a Custom UI for other purposes, you should continue in the same manner. If you are doing any local development, you need to specify only your Public IP, while leaving the server URL blank.

Info

Notes:

  • There is no limitation in using the same Orchestration Server for different projects, e,g, Orchestration Servers can be referenced from multiple Digital DNA Studio projects.

  • You need to use a subnet mask when developing locally. Typically a /32 subnet mask can be appended to your IP to satisfy this requirement.

Further information about implementing an Orchestration Server to work with Digital DNA Studio can be found in the Orchestration Configuration Guide.

Contents

Table of Contents