> For the complete documentation index, see [llms.txt](https://boomi.markusschmidt.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boomi.markusschmidt.pro/boomi-console/library/the-workspace/package-workspace.md).

# Components Set Workspace

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"
```

![](/files/AuSbpUWeJ7xI0C5v2K91)

{% hint style="info" %}
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.
{% endhint %}

### 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:

![](/files/D7T3uJd9IfecKCU6bJ8b)

`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.