Promoting deployed decision services to another decision runtime

You can promote a decision service archive from the development environment to the production environment.

About this task

For security reasons, the production environment where decisions are executed might need to contain only the decision runtime. In this case, the decision runtime can be isolated from the development environment where decisions are authored and tested.

As a consequence, you might need to promote a deployed decision service archive from the development environment to the production environment. You can promote decision service archives from the decision runtime on one installation to the decision runtime on another installation.

For more information about the decision runtime REST API methods that are used in the procedure, see the Decision runtime REST API reference in Reference.

Procedure

  1. Get the decision service archive from the development environment by using the following decision runtime REST API method:
    GET https://<server>:<port>/deploymentSpaces/{deploymentSpaceId}/decisions/{decisionId}/archive
    • <server> is the hostname of the decision runtime, which is specified in the decision_runtime.ingress.hostname parameter.
    • <port> is the port of the decision runtime.
    For example, you can use a cURL command:
    curl -k -X 'GET' \
    'https://<server>:<port>/deploymentSpaces/{deploymentSpaceId}/decisions/{decisionId}/archive' \
    -H 'accept: application/octet-stream' \
    -H 'Authorization: ZenApiKey <base64(zen_user_id:zen_api_key)>'
  2. Get the metadata from the development environment by using the following decision runtime REST API method:
    GET https://<server>:<port>/deploymentSpaces/{deploymentSpaceId}/decisions/{decisionId}/metadata > /path/to/metadata.json
    For example, you can use a cURL command:
    curl -X 'GET' \
    'https://<server>:<port>/deploymentSpaces/{deploymentSpaceId}/decisions/{decisionId}/metadata' \
    -H 'accept: application/json' \
    -H 'Authorization: ZenApiKey <base64(zen_user_id:zen_api_key)>'\
    > /path/to/metadata.json
    
  3. Deploy them to the decision runtime in the production environment.