Deployment

The Deployment page is used to manage the deployment of program packages to Hub.

The deployments listed may be filtered by API endpoint, created date, or modified date. Clicking more (...) at the right of the program package row contains the following options: - Edit: Launches the Deployment wizard from which the properties of the selected program package can be modified. - Update to latest: Deploys the latest version of the selected program package. - Delete: Confirms the deletion of the selected program package. - Activate API Endpoint: Activates the deployment of the selected program package. - Deactivate API Endpoint: Deactivates the deployment of the selected program package.

In the Deployment page, click the Deploy Demo button to deploy example programs in the languages of SAS, R, and Python.

Click the New button to launch the Deployment wizard, from which the deployment settings can be defined. The wizard can be used to deploy a program package as an artifact or from a git repository.

If the deployment type, is artefact:

1. Select the Artefact deployment type to deploy programs stored in an artefact, and select the required Execution Profile. and set the Execution profile.
2. Click Next to move to the Select artefact dialog.
   Select the required artefact by specifying the Repository, Group, Artefact name, and Version.
3. Click Next to move to the Deployment path dialog.
   Create a unique name for the Deployment path and specify whether an API endpoint should be created.
4. In the Categories dialog, select the categories for the deployment.
   Multiple categories can be selected, and specifying categories makes it easier to locate programs in the deployment directory.

If the deployment type is from a git repository:

1. Select the Git repository deployment type to deploy programs stored in an git respoitory, and select the required Execution Profile.
2. Click Next to move to the Select Git Repository dialog.
   Enter the Repository URL and Git branch or tag containing the programs.
3. Click Next to move to the Deployment path dialog.
   Create a unique name for the Deployment path and specify whether an API endpoint should be created.
4. In the Categories dialog, select the categories for the deployment.
   Multiple categories can be selected, and specifying categories makes it easier to locate programs in the deployment directory.

When creating the deployment path, an API endpoint must be created to make the deployment available for Synchronous On Demand.
If an API endpoint is not created, the deployment is only available for Asynchronous On Demand.

Each deployment on the page may be edited, for example, to update to a later version or to create an API endpoint for Synchronous On Demand where one did not previously exist.