The build and upload process generates the BPM package, PRT fragment and triggers on the target Integration Server. The required metadata is also inserted into the process audit schema defined for the target Integration Server. The BPM packages can and should be checked into a version control system such as Git or SVN. To support the upload of metadata from an Integration Server running under Docker, during the build and upload of the BPM project, the process "collects" process files, configuration files, and image data from the process editor canvas. When the process model is saved, the JPEG and SVG image files are generated from the canvas and stored in the workspace. During build and upload, the image files are taken from the workspace and written to the generated BPM package on the "default" server together with the process files and configuration files. If a "default" server is not configured, process files are not generated, and a warning is logged during the build and upload process. This warning does not affect the execution of the process model.