Deployer 10.5 | Deploying Assets from a Source Asset Repository | Building Composites | Adding Assets to the Source Directory
 
Adding Assets to the Source Directory
You create assets with a webMethods runtime and store them in a file system or version control system (VCS). The directory of the file system or VCS in which you store the assets is the source directory.
Most webMethods runtimes supply a means of exporting or saving the assets you create to the source directory. You can find details about how a product exports assets to the source directory in the documentation of the respective product. However, to add most of the Integration Server administrative assets to the source directory, you must manually copy or check in the related configuration folders to the source directory. For a complete list of files and directories to copy or check in to the source directory for Integration Server administrative assets, see Adding Administrative Assets to the Source Directory.
When specifying the properties for the build.properties file, you use the build.source.dir parameter to specify the full path of each source directory. When you run the build script, it packages the contents of the source directories into the correct composite file format for deploying those assets to target servers.
Keep the following points in mind when adding assets to the source directory:
*The build script must have access to the source directory.
*If the source directory is a file system on a VCS, you must supply the proper credentials for accessing and checking out the composite files from the source directory. For more information about supplying the VCS checkout properties, see Setting VCS Checkout Properties.