Preparing to install Automation Decision Services

Before you install Automation Decision Services, you must prepare your environment to make sure you have everything that you need. The prerequisites include defining security and storage.

About this task

Automation Decision Services comes with two main components: a designer and a runtime that can be installed separately. They include the following services:

Decision Designer:
  • Embedded MongoDB database (optional, disabled by default for enterprise deployments)
  • Embedded build service (automatically installed if the runtime service is installed)
  • For 21.0.1 Embedded runtime service (optional)
    Note: The embedded build service allows authors of decision services to publish them to the automation services catalog of Business Automation Studio. From there, the decision services can be invoked by other DBA capabilities for discovery and reuse.
  • Download Service
  • Git Service (file access backed by Git repositories)
  • Parsing Service (compilation)
  • Run Service (validation)
  • Front (front end)
  • REST API (back end)
  • Credentials Service
Important:

If you install Decision Designer, you must also install Business Automation Studio, Application Engine, and User Management Services. Therefore you need to follow the preparing to install steps of each of these capabilities.

Decision runtime:
  • Runtime Service

The services require minimum CPU and memory resources. For details, see System requirements.

In terms of storage, you might want to customize the MongoDB and the Git service persistent volumes. The embedded MongoDB is provided for demo purposes only. It is NOT recommended in production. You must provide an external MongoDB. An external MongoDB allows high availability scenarios and finer control of the database configuration. For more information about supported databases, see Detailed system requirements.

Before you install Decision Designer, you might need to provide:
  • A secret to hide sensitive configuration (mandatory)
  • A secret for the TLS certificate exposed by Decision Designer
  • ConfigMaps that contain a list of certificates to access Git servers, Machine Learning providers, and other servers, if the certificates are not trusted.
Before you install the decision runtime, you might need to provide:
  • A secret to hide sensitive configuration (mandatory)
  • A TLS secret for Ingress
  • ConfigMaps with a list of certificates to access Machine Learning providers, if the certificates are not trusted.