The MSPro Boomi Collection
About
Boomi Console
Boomi Console
  • Boomi Console
    • What is ...
  • Installation & Setup
    • Download & Install
    • Setup a Workspace
    • Connect your Workspace
    • Test your Workspace
  • Commands
    • COMP - Components
      • GET
      • DOC
    • PACK - Packaged Components
      • PACK GET
      • PACK DOC
    • DEPLOY - Deployments
      • GET - Deployments and Packages
      • EXEC - Deploy components
        • Deployment from Repos
        • Promotion to Env
      • DELETE - Undeploy Components
    • WORKSPACE CONNECT
    • ACCOUNT INFO
    • Arguments
      • Common Arguments
        • The Set Argument in Detail
        • Query Filter
          • Start date or time span
        • Arguments in a file
        • Allow Multi
        • Component Resolution
      • COMP Arguments
        • COMP GET Arguments
        • COMP DOC Arguments
      • PACK Arguments
      • DEPLOY Arguments
        • DEPLOY GET Arguments
        • DEPLOY EXEC Arguments
        • DEPLOY DELETE Arguments
  • Use-Cases
    • Analyze deployed components
    • Components in a Folder
    • Deploy Components
    • Reveal a Process
    • Reveal an API Component
    • Deployed Components Overview
    • Deployment Task Document
    • Create a cSet.jsonc file
  • Library
    • Component Set
      • The Components Set JsonC file
        • Create a package file
      • Set File resolution
    • The Report Engine
      • Render DataSets
        • DataSet Base
        • Component Metadata DataSet
          • Component Metadata Header
          • Component Metadata
          • CompDataSet With Counts
        • Deployed Packages DataSet
        • Package Content DataSet
        • Map Markdown Dataset
      • Components
        • Deployable Components
        • Orphaned Components
    • The Workspace
      • Manage your workspace
      • Components Set Workspace
      • Workspace folders
      • The project database
    • Configuration files
      • Application Settings
      • Workspace configuration file
      • boomiConsole.user.json
    • How to...
      • Use Excel to view CSV files
      • Local metadata and caching
      • Getting help
      • Environments
      • How to get a Component's Id
    • Referenced Pages
      • Lists
      • Documentation Snapshots
  • Download and Release History
  • Help Text
    • Documentation Links
    • Target Path Resolution
    • GitHub Emojis
    • Packaged Component and Versions
    • Components and Versions
    • Component Hierarchy
    • Referenced Components
Powered by GitBook
On this page
  • Deployment
  • Promotion
  • Using Sets
  1. Commands
  2. DEPLOY - Deployments

EXEC - Deploy components

Deploy or promote your components

Last updated 7 months ago

bc DEPLOY EXEC/c <ComponentID> /dstEnv=01-DEV

Deploy or promote your components to an .

Deploy or Promote

A Deployment takes place when a component is packaged and deployed

  • from Repository to an environment (usually to DEV).

We call it a Promotion when

  • a packaged component is 'deployed' from one Environment to another.

Typically, you deploy from Repository to DEV environment and you promote your packaged components from DEV to TEST.

To perform a deployment, you need to specify one or more component(s) which will be packaged first, before it is deployed to the destination environment.

Optionally, you can specify a /DeploymentNote and or a /PackagedComponentNote.

You cannot yet specify a version because this is set automatically to {Date}-{User}.{seqNo:2}.

Deployment

Each component that is a new packaged component is created. All packaged components in a single deployment get the same version number.

Promotion

A promotion copies deployed (packaged) component(s) from one environment /SrcEnv to another /DstEnv. To execute a promotion you refer to the component Ids (not the packaged component ids). Boomi Console automatically gets the required packaged component ids from the source environment to copy them to the target.

Using Sets

After each deployment or promotion you may use DEPLOY INFO to document your deployment state for later evidence.

bc deploy info --componentid <YourCompId> 

The real power of this command comes with the option. This allows you deploy / promote many components (a Component Package) in a single run! This will save you a lot of time and it makes your deployments reproducible!

from Repository to an Environment

from one Environment to the next

Please not,ice, the DEPLOY EXEC command refers to the you have specified in your project configuration. All deployments or promotions are logged in the Logs directory on a daily basis for later reference.

/set
Deploy a Component
Promote a component
Environments
environment
DEPLOY EXEC Arguments
resolved using the command-line arguments