Publishing and deploying deploy anywhere projects

Publishing a project generates a deployable package that includes all required components such as services, configurations, and dependencies. Deployment transfers this package to the designated runtime environment, ensuring proper configuration, version alignment, and readiness for execution.

1. Log in to your destination tenant.
2. Go to the Projects page.
   If a new deployment is available for a project, then a message appears on the project card.
3. Click the project card that has the deployment message.
   A confirmation message is displayed.
4. Click Yes.
   The Deployments page is displayed and you can see the list of all pending deployments.
5. Click Deploy.
   The Git Accounts page in the Deployment wizard appears.
6. Select the Git account from the Account details drop-down menu.
   This account is used to retrieve package details from the repository. If you do not want to use an existing account, then create a new account by clicking Add.

   After you configure the Git account, the account is moved to the Configured section.

7. Click Next.
   The Integration Runtimes page in the Deployment wizard is displayed.
8. Select an existing runtime from the Target Integration Runtime drop-down menu.
   • If no runtime exists in the target environment during first-time deployment, you must create a new runtime or select an existing one before you can proceed.
   • For first time deployment, if no virtual runtime exists during first-time deployment, then it is created and mapped to the runtime.
   • For redeployments, the virtual runtime or runtime is selected based on the previous deployment configuration. If a virtual runtime is added in the source environment for the current deployment, then the virtual runtime is created and mapped to the runtime configured for the previous deployment.
9. Select Sync all the target runtimes on deployment if you do not want to reconfigure the package service connections after deployment. Otherwise, after deployment you need to reconfigure the package services connections.
   The Restart Options link is displayed.
10. Click Restart Options.
11. In the Selected target integration runtimes to restart page select the runtimes that must be restarted after a successful deployment.
    Note:

    • Offline runtimes are not listed in the Selected target integration runtimes to restart page.
    • Syncing and restarting happens only for the running runtimes.
    • Cloud Runtime cannot be restarted.
    • The sync and restart operations are asynchronous processes and might take more time even after the project is deployed.
12. Click Done.
    The Integration Runtimes page is displayed.
13. Click Next.
    The Accounts page is displayed.
14. For the remaining pages in the Deployment wizard, follow the steps mentioned in the Deploying projects section in Working with deployments.
    Note:

    • Deployed projects cannot be edited in the target environment as they do not retain any link to the original version control. Instead, make changes in your development environment and redeploy. Likewise, deployment from a higher to lower environment is not supported.
    • After deployment, the projects that are previously linked to an external repository now use the default repository.