To include package assets in the composite for deployment, you must manually copy or check in the Integration Server_directory \instances\instance_name\packages folder to the source directory. How you organize the package assets in the source directory depends on what you want to include in the package composite.

If you want to generate composites for all packages in the source directory and package-specific administrative assets, Software AG recommends that you structure the source directory as either:

Or

In the example, you would define SRC_ROOT as the value of the build.source.dir property in the build.properties file. For more information about the build.properties file, see Setting Build Properties.

When run, the build script creates the following:

If you want to generate a composite for a package with services for which you have configured ACL, you must copy or check in all ACL-related configuration files to the Integration Server_directory \instances\instance_name\packages\package_name\config directory. This ensures that the Asset Build Environment generates the package composite ACDL and ZIP files with the correct configuration of the ACL assigned to the services in the package.

In this case, you should structure the source root directory as follows:

SRC_ROOT\package_name\config

Copy all *_pkg.cnf files to the package_name\config directory. You would define SRC_ROOT/package_name as the value of the build.source.dir property in the build.properties file. For more information about the build.properties file, see Setting Build Properties

Example:

A package with name "TestPackage" has a "test" service, for which you have configured ACL. Copy all *_pkg.cnf files, such as aclmap_pkg.cnf and readmap_pkg.cnf, to the TestPackage\config directory. The *_pkg.cnf files should have the ACL configuration for all folders and assets in the "TestPackage" package, such as:

In the build.source.dir property of the build.properties files, specify the location of the package as SRC_ROOT/TestPackage

When run, the build script creates the TestPackage.acdl and TesPackage.zip files in the output repository. The TestPackage.zip archive includes the TestPackage\config\*_pkg.conf files that have the ACL configuration for the services in the package composite.

If your source directory contains several packages and you want to generate composites from only a select number of those packages, you can use the build.source.project.dir property to specify only those packages you want to include. For example, in the following source directory there are three packages: packageA, packageB, and packageC:

You can generate a composite that contains only packageA and packageB by setting the value of the build.source.project.dir property to:

In this example, since the config directory is not located in SRC_ROOT, you must specify the location of config directory in the is.acdl.config.dir property of the build.properties file.

When run, the build script creates a composite named package_name.zip for each package defined for build.source.project.dir, where package_name is the name of the package (with a composite type ID of ispackage).

Using the example, build.source.project.dir is set to “SRC_ROOT/packageA;SRC_ROOT/packageB”. When the build script runs, it will generate composites for packageA and packageB. Since packageC is not defined for build.source.project.dir, the build script ignores it. Since the packages are named “packageA” and “packageB” in the source directory, the build script names the composites packageA.zip and packageB.zip.

For more information about setting properties in the build.properties file, see Setting Build Properties. For more information about building composites for repository-based deployment, see Building Composites.