During a build, the project's output folder is populated with a number of build artifacts and intermediate files that are useful to the development process, but not all of these files are essential in a deployment scenario. For native COBOL, mainframe, and PL/I projects, you can configure the build process to additionally copy certain executable types and supporting files, required for deployment, to a specific 'deploy' folder.
This process, which is not enabled by default, is configured from within a build configuration, and so each project can have more than one deploy folder; for example, one build configuration could deploy .exe files to one folder, and anther could deploy .dll files to another folder.
A deploy folder can be local to your workspace, or it can be a linked resource, and more than one project can deploy to it.
To populate the folder, use regular expressions on the Deploy page (in Project Settings) to select the required executable files (.exe, .dll, or .obj files) and any other supporting files required when executing your applications. (The run-time system configuration file is selected by default.) If you are deploying these files to a non-development environment, refer to the Deployment sections for details on how to integrate these files with a COBOL run-time system.
A project's deploy folders are cleaned (that is, deleted) each time the project settings are updated. If your workspace is not set to build automatically and you have multiple projects deploying to a single folder, you should ensure that the Clean the Deploy Folder option is set to No for each project; otherwise, editing the settings for one project will remove the deployed files from other projects.