Déploiement d'une solution

Deploying a solution means installing a solution package as a new deployment in an Orchestrator folder. For more information about solution deployments, see Understanding the solution development lifecycle.

You can initiate a solution deployment from either Studio Web or Orchestrator. Both surfaces drive the same underlying deployment experience: Studio Web is the originating surface, designed for solution authors who want to package and deploy in a single flow; Orchestrator is the administrative surface, designed for tenant administrators managing deployments at scale. This page documents the Orchestrator flow.

The Orchestrator deploy flow requires a solution package that has already been published to a feed. You can publish a package from Studio Web or Studio Desktop before deploying here.

Cette étape est généralement effectuée par un administrateur.

Open the Deploy workflow

You can open the Deploy workflow from any of the following locations in Orchestrator:

• Deployments tab — Select + Deploy in the upper-right corner.
• Packages tab — Select the Deploy row action for the package you want to deploy.
• Package sidebar — Open a package to expand its sidebar, then select Deploy in the upper-right corner of the sidebar.
• Versions tab of the Package sidebar — Select the Deploy row action for the specific package version you want to deploy.

All four paths open the same Deploy workflow on the Setup form. The breadcrumb at the top reads Tenant > Solutions > Deployments > Deploy.

Complete the Setup form

The Setup form is where you define what to deploy, where it lands, and how it activates. Fill in the following fields:

Champ	Description
Paquet (Package)	Select the solution package to deploy from the dropdown. The list shows all packages published to your tenant feed.
Version	The package version to install. Defaults to the latest published version. Select a different version from the dropdown if needed. The publish date, description, and feed location are shown below the field.
Nom du déploiement	A required, tenant-unique name for this deployment. Auto-filled from the package name.
Emplacement	The folder where the solution folder will be created. Defaults to Install as root folder. Select an existing folder from the dropdown to nest the solution inside it.
Solution folder name	The name of the subfolder created inside the destination. Mirrors the deployment name by default. Edit to use a different name.
Activate immediately	Toggle (on by default). When enabled, triggers in the solution are activated as soon as the deployment completes.
Set up runtime	Toggle (on by default). When enabled, a Default Serverless template is automatically attached to the target folder if one is not already present or inherited. Disable this if you want to configure machine templates manually.

Astuce :

The form pre-fills smartly: the package name flows into Deployment name, and Deployment name flows into Solution folder name. You can override any of these values independently.

Run the deployment

After completing the Setup form, choose one of the following options at the bottom of the form:

• Deploy — validates the configuration and runs the deployment immediately. The workflow progresses through the following steps shown in the left navigation rail:

  Étape	Description
  Configurer	The deployment configuration is validated and applied.
  Déployer	Solution folders are created in the target location and resources are provisioned.
  Activer (Activate)	Triggers and activation are set up, if Activate immediately is enabled.

• Customize (select the dropdown arrow on the Deploy button) — opens the resource explorer so you can review and configure individual solution components before the deployment runs. After reviewing components, select Continue to deploy to proceed.

Re-use existing components (optional)

When you select Customize, the resource explorer shows all components in the solution package. If a component with the same name already exists in the tenant, you can link the solution to it instead of creating a new one.

This option is available for Assets, Storage buckets, Webhooks, and Queues. For each conflict, you can:

• Conservez le composant existant et n'en créez pas un supplémentaire.
• Keep the existing component and add new fields from the solution (existing fields are not altered).
• Renommez la ressource en conflit dans le service concerné.
• Renommez la ressource dans le déploiement de la solution, si possible.

To link an existing component:

1. In the resource explorer, select the component you want to link.
2. Select Link to existing.
3. In the dialog, select the component you want to link to.
4. Sélectionnez Lien.

Surveiller le statut du déploiement

After the deployment starts, you can monitor progress from the workflow view or from the Deployments tab in Solutions. The following statuses are possible:

État (Status)	Description
En cours	The deployment operation is running.
Réussi	The deployment completed and all components are installed.
Échec	The deployment failed and an automatic rollback was performed.
Échec de la restauration	The deployment failed and some components require manual cleanup.

For details about all statuses, see Deployment statuses.

Activer le déploiement

Remarque :

Si la solution contient des applications et qu’elles ne sont pas activées à l’aide du lien fourni, l’activation du déploiement échouera. Consultez la documentation d'Orchestrator et d'Apps pour des instructions détaillées.

After a successful deployment, Orchestrator evaluates activation readiness. The deployment appears in the Deployments tab with one of the following statuses:

• Inactive (Ready to activate): No additional configuration is required. Select the More Actions icon, then select Activate deployment.

• Inactive (Needs setup to activate): Additional prerequisites must be completed before activation:

  1. Select the More Actions icon and choose Set up activation.

  2. Review the activation validation results and complete the required items:

     • Ajouter des comptes et attribuer des rôles.
     • Ajouter des machines aux dossiers de solutions.
     • Définissez des mappages compte-machine, si nécessaire.
     • Définissez les valeurs d'actif par robot, le cas échéant.
     • Activez les apps utilisées dans la solution.
     • Remplissez les liaisons pour les composants de type processus, le cas échéant.
     Remarque :

     When deploying a solution, a Default Serverless template may be automatically attached to the target folder if the Set up runtime toggle was enabled on the Setup form.

     • Cela garantit que la solution peut s'exécuter sans configurer manuellement les modèles de machine.
     • Si un modèle sans serveur est déjà hérité, aucun modèle supplémentaire n’est joint.

  3. Resolve the listed items.

  4. Sélectionnez Valider.

  5. Sélectionnez Activer.