Deploy a Decision Service

A decision service project can be deployed at any time from Intelligent Advisor Hub by Managers and Authors. (Note that only Managers can activate a deployment.) To do this:

  1. In Intelligent Advisor Hub, navigate to the Projects Page.
  2. Select the Decision services tab.
  3. Click the decision service project name. The project opens.
  4. In the Actions menu in the project header, select Deploy. (Note that this will deploy the draft or latest version. If you want to deploy a different version, select that version in the Version history panel before selecting Deploy.)
  5. In the Deploy dialog:
    • in the Deployment field, enter a name for the deployment. Note that the deployment name cannot contain any of the following characters: \ / : * ? " < > | ; % + @
    • in the Workspace drop-down, select the workspace for the deployment (you can deploy to any workspace for which the user has the Manager role)
    • in the Comments field, enter any notes about the deployment
    • select the Activate check box if you would like to activate the deployment as well. The Activate option is not available for Authors.
    • Click the Download the references report for this deployment link to generate a report of which projects and deployments are using the decision service

    The Deploy dialog for a decision service project in Intelligent Advisor Hub

    If you are deploying a draft version of the project, a new version of the project will also be published.

  6. Click Deploy. Confirmation is shown if the deployment has been successful. Note that:
    • If the deploy was not successful, an error will be shown with advice as to how to resolve. If an unexpected error occurs, contact Oracle customer support.
    • If the project is referenced from another decision service or from a Policy Modeling project and you have made a change to the decision service that is incompatible with any existing deployments, a warning will be shown. Click Deploy to continue with the deployment or Cancel to return to the project to fix the incompatibility. For more information, see Deployment validation below.

Successful deployments are listed on the Deployments page.

If the project was also activated, you will see on the deployment details page that the project has been deployed on the Web services - Assess channel. On this page you can click the Endpoints link to view and copy the decision service deployment endpoints.

You can allow the deployed decision service to be referenced from different workspaces by selecting All workspaces in the Allow references from drop-down list.

Deployment validation

Deploying a new version of a decision service or modifying an existing one can break other deployed decision services or deployed Policy Modeling projects.

This can happen in one of the following ways:

  • You deploy a new version of a decision service which has a contract that is incompatible with a decision service reference of another project.

  • You deploy a new version of a decision service which either directly or indirectly references itself. A direct reference would be where decision service deployment "A" contains a direct decision service reference to "A". An indirect reference would be where A references B which references A.

  • You delete or undeploy a decision service that is referenced by another deployment.

  • You modify the workspace or "allow references from" a decision service such that it can no longer be accessed by a deployment that references it.

When you attempt to perform an action that will break another deployment, you will be warned of any existing deployments that will be broken, either directly or indirectly (that is, the deployment is broken because one of the decision services it references is broken). If you proceed with the action all the broken deployments will be flagged in the Hub. Once a deployment is broken it will not be usable until the error is addressed. Specifically:

  • If you attempt to start or resume an interview on a broken deployment in Web Determinations, you will get an error with a response code of 503. The error message is controlled by the RulebaseBrokenError message text setting in the Policy Modeling project. The default message is "The interview cannot be started due to errors in the deployment. For further assistance please contact support." .

  • If you attempt to use a broken deployment in the SOAP services (Assess, Answer or Interview), then you will get a SOAP fault with message code com.oracle.determinations.server.exceptions.BrokenDeploymentException advising that the deployment is broken.

  • If you attempt to use a broken deployment in the Batch or OpenAPI service, you will get a 503 error advising that the deployment is unavailable because it is broken.

Tip: If you get a 503 response with a message saying that the interview cannot be started because it has errors or is broken, go to that deployment in the Hub to see exactly what is broken.