Show TOC

Build IntegrationLocate this document in the navigation structure

Use

You can use automated build services to ensure the integrity and consistency of the build artifacts. No assumption is made regarding the central build environment you are using, or if you are using any at all.

You can:

  • execute the build of SAP development components (DCs) within an existing build infrastructure.

    You can use the command line tool provided with the SAP NetWeaver Composition Environment that allows you to execute the SAP build plug-ins in a scripting environment, and a corresponding ANT task for ANT-based environments.

  • make the build results of non-SAP build projects available for the build of SAP components.

  • make the build results of SAP components available for non-SAP build projects.

    Note

    Advanced NWDI features like the setup, planning and management of the central build environment, the initiation of central builds by developers, the retrieval of build logs, and the storage, distribution and retrieval of build results (artifacts) are not supported.

    Even if your build environment supports such features, the Developer Studio may not be able to use them directly.

Using Command Line Tool

You can use the command line tool to run an automated build on a collection of DCs that belong to a certain development configuration or if you do not have your own build infrastructure with a build engine. The commands it provides can be easily integrated into shell scripts, or run interactively. Furthermore, when run on a collection of DCs, the command automatically determines the correct build sequence. Therefore it can be treated as a simple, but complete build engine for the production of whole software products. The development configuration determines which development components and which versions of that development component are built together in the same context.

All SAP build plug-ins store logs and build results for each component that has been built in the /gen directory inside the components root directory. You can make these logs and build results available for further use. For more information about how to structure your folders in this directory, see Structure of the GEN Folder .

Requirements

The build command requires that all used build plug-ins, used libraries and the source files of the DCs you want to build are already available in the local file system. The corresponding locations must be set to the command using the command's parameters. You have to first set up this environment. You have to retrieve the source code from the version control system, copy the used libraries from the build environment, define a suitable file system layout and so on. For the automated build, you have to integrate these tasks as additional steps in the build script before executing the build command.

Using ANT Build Task

SAP provides a generic ANT task that can be used to embed the build of components into any ANT make script. Since ANT is a standard for Java build technology, and is supported by many frameworks, it is possible to integrated the build of SAP components into a wide variety of build environments.

Requirements

The ANT build task requires that all used build plug-ins, used libraries and the source files of the components you want to build are already available in the local file system. The corresponding locations must be set to the command using the command's parameters. You have to first set up this environment. You have to retrieve the source code from the version control system, copy the used libraries from the build environment, define a suitable file system layout and so on. For the automated build you have to integrate these tasks as additional steps in the build script.

More Information :

DC Command Line Tool

Build Options