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
  1. Library
  2. The Workspace

Components Set Workspace

Packages should have their own directory

Last updated 10 months ago

I highly recommend using the following directory structure within your project directory to manage Components Sets:

<ProjectDir>
+--  Sets
     +-- Lib
          + -- Package01
               : cSet.Jsonc
          + -- Package02
               : cSet.Jsonc
     +-- Work
          + -- Sprint April-01
               : cSet.Jsonc     
          + -- Sprint April-02
               : cSet.Jsonc

Create a folder for each package and you use cSet.JsonC as the package filename. The package folder serves a a Workspace and all package output will go to this folder with the same name as the package file.

> C:\MSBoomi
bc COMP GET -p "DBIntegrationSample\cSet.JsonC"

There is no need to specify the Sets, Lib or Work folder because these names are Default names. You can override the defaults by using the --SetLibDir and --SetDir options.

Additional folders

Personally, I use two additional folders, which are not Boomi Commands related. However, this structure helps me to much better organize my Integration work:

Doc takes my Package documentation and Test takes all tests, which are in most cases http files to test REST or SOAP API of integrate. Of course, you may also store SOAP UI and/or other test in such directory.