The Change Management Service (CMS) administers the transport of software changes within an SAP Java development landscape. You use the CMS to perform the following tasks:
· Configuring the SAP NetWeaver Java Development Infrastructure
· Transport of software changes in your development landscape
· Packing and delivering software component versions that you have developed in your NetWeaver Development Infrastructure
The functions of the CMS are closely interrelated with the Design Time Repository (DTR), the Component Build Service (CBS), and the System Landscape Directory (SLD). As an administration tool, the CMS covers all these components and links the individual parts together as a single unit for realizing distributed development projects.
The Change Management Service is split into several different subareas.
On the front end, you can view the CMS using the Transport View in SAP NetWeaver Developer Studio (IDE) or in a browser-based Web interface (CMS UI). HTTP is used for communication between the front end and the back end.
On the back end, the CMS runs on a J2EE Engine. Technically, it is split into a Propagation Control Service (PCS) and a Transport Control Service (TCS).
In the PCS, the Configuration Manager is responsible for the configuration of the development landscape. This configuration data is then stored in the central System Landscape Directory (SLD). The PCS also uses the Transport Manager to control the flow of software component versions through the development landscape.
The TCS controls the automatic build process in the CBS and deployments in the runtime systems. The Software Deployment Manager (SDM) is responsible for the actual deployment of your software.
· Configuration of development landscapes and development tracks
· Transport of source code and archives
· Quality assurance measures before the import of software changes into follow-on systems