The MSPro Boomi Collection
Boomi Console
HomeScriptEase For BoomiBoomi Console
Boomi Console
HomeScriptEase For BoomiBoomi 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
  • 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

Last updated 5 months ago

To package and deploy a component from repository to any environment specify the target (/DstEnv) environment, only, and omit the /SrcEnv option - source is always the repository.

The DEPLOY EXEC command will automatically and always create a version for your deployed component:

yyyy-MM-dd-<UserIdent>.<YourSeqNo:00>

SeqNo will be calculated based on your number of deployments from today. The UserIdentcomes from your .

If you use you can pefectly see that all components within a package are packaged and deplyoed using the same (Component) Package version:

Component Set
PreviousEXEC - Deploy componentsNextPromotion to Env
  1. Commands
  2. DEPLOY - Deployments
  3. EXEC - Deploy components

Deployment from Repos

Deploy a component (or Component Package)

user configuration
bc deploy exec -DstEnv 01-DEV 
  {/c <ComponentID> | /p <ComponentPackageFileName>} 
  -DeploymentNote "This is my deplyoment" 
  -PackagedComponentNote "This is a package note"
Deployment History
Packaged Components
Two components in a Component Package, using Component Package deployments