Lifecycle Management
One of the important aspects of modeling is lifecycle management, which includes componentization, reuse, packaging, storage, source control, and maintenance. Visual Composer provides built-in support of the different component lifecycle aspects, such as versioning, packaging, managing dependencies and compatibility, from which modeled portal content also benefits.
You can store and manage models in the following design-time repositories:
· The shared repository in the AS Java server database, which provides limited source control capabilities
· The local repository, your own dedicated space on the AS Java server, which has no source control capabilities
· The DTR, the NWDI source control system, if it is available in your system landscape
For more information about the DTR, see Working with the Design Time Repository.
To use the
DTR as your source control system, you must configure it to work with Visual
Composer. For more information, see
Configuring Visual Composer.
According to the SAP component model, development projects are organized in these repositories into a nested structure, as follows:
· Software components (SCs) are delivery and installation units that contain development components
· Development components (DCs) are development and build units that contain development objects
· Development objects, such as models, are created in the development components and stored as versioned files
This nested structure does not allow overlapping: a development object can belong only to one development component; a development component can only belong to one software component.
You can use the search mechanism of Visual Composer to locate reusable components in a local or shared repository, and then drag and drop the selected component onto the currently opened model.
More Information
For information about specific lifecycle management tasks, see: