SAPTechno

Note 1361909 - CM Services in CTS+

Header
Version / Date 5 / 2011-02-17
Priority Recommendations/additional info
Category Consulting
Primary Component BC-CTS-CMS Change Management Service
Secondary Components BC-CTS-TMS-PLS TMS for non-ABAP (CTS+)

Summary
Symptom

Central Note on Change Management Services (CM Services)

Other terms

NWDI, CMS, CTS+, enhanced CTS, non-ABAP, CM Services

Reason and Prerequisites

CM Services are provided as part of AS Java starting with enhancement package 1 for SAP NetWeaver 7.0. CM Services are the successor of CMS. CMS is part of Usage Type DI and is in maintenance mode. CM Services are also delivered starting with SAP NetWeaver Composition Environment 7.2.

Solution

CM Services are delivered as part of any AS Java starting with enhancement package 1 for SAP NetWeaver 7.0. It is recommended to use the CM Services on the NWDI system as of enhancement package 1 for SAP NetWeaver 7.0 or SAP NetWeaver Composition Environment 7.2.
Nevertheless, you can use the CM Services if your NWDI is not on one of these releases, but this is not the recommended set up. In this case, you have to choose another AS Java system where you could run the CM Services. Some functionality is not usable if your NWDI is not on one of the releases mentioned before. You will e.g. not be able to see the transport request within the Activity in DTR.

The CM Services are not delivered with SAP NetWeaver Composition Environment 7.1 and enhancement package 1 for SAP NetWeaver Composition Environment 7.1.

General Remarks for CM Services

  • Development Configurations managed by CTS+ are named like the system in TMS. This means that the name of the development configuration is the same as the SID of the system that you created in TMS. In addition, the name of the development configuration consists therefore out of three letters.
  • Starting with SAP NetWeaver Composition Environment 7.2, you can enable / disable the autodeployment of developed software components in the local settings tab of the Development Configuration Service UI in NWA. If you disabled the auto deployment, the SDAs are still queued for deployment and you can trigger the deployment by using following URL: http://<host>:<port>/DI/Deployer. <host> and <port> are to be replaced by host and port of your CM Services server.
    If you marked a developed software component not to be included in deployment, no deployment will be done for this SC at all - neither automatically nor manually triggered via the URL named above.
  • Do not use the AS Java, on which the CM Services are running, as a runtime system. When you import software components that have offline deployment parts, deployment causes a deadlock. In other words, the CM Services server is restarted by the import.
  • Starting with SAP NetWeaver 7.3, you can also set the SP and patch level for your own software components (where the vendor is not sap.com).



General Recommendations

  • Use your SAP Solution Manager as CTS+ System.
  • Run the CM Services on your NWDI.
  • Create a favorite for the DI Export Web UI in your Browser (http://<host>:<port>/webdynpro/dispatcher/sap.com/tc~di~cts~config~webui/Export) if you need it frequently.
  • If you decide to use the activity transport, use it in combination with the SCA transport. E.g. if you did a lot of changes to very different DCs, you should transport the complete SCA instead of a lot of change lists (activities).




Recommendations for CM Services on enhancement package 1 for SAP NetWeaver 7.0

  • Check whether the CM Services offer benefits for you and if yes, use them. If not, you can continue using CMS. Please keep in mind that there is no new functionality planned for CMS. CMS is in maintenance mode.


Recommendations for CM Services on enhancement package 2 for SAP NetWeaver 7.0 and SAP NetWeaver 7.3

  • Use the CM Services instead of CMS. If you are already usig CMS: CMS is still delivered with enhancement package 2 for SAP NetWeaver 7.0 and SAP NetWeaver 7.3. Please keep in mind that there is no new functionality planned for CMS. CMS is in maintenance mode.



Restrictions for all releases

  • Solution for maintenance tracks described on SDN http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3390 is not supported for CM Services
  • It is not recommended to use the Activity Transport if you are modifying ESS or MSS sources delivered by SAP.
    Why it is not recommended to use the CM Services with ESS / MSS: (the following is based on what is described in the ESS / XSS Cookbook attached to note 872892). If you changed a SCA containing Web Dynpro and would like to import a new SP into the same CMS track, you might receive unresolvable conflicts. The same applies if you use CM Services and import a new SCA delivered by SAP into these systems (by the help of the upload system). The guide describes that you have to create new tracks whenever a new SP has to be installed. Basically, the same would work for CM Services as well. The consequence would be that you have to create new systems in CTS - which would require additional SIDs.


Restrictions for CM Services in enhancement package 2 for SAP NetWeaver 7.0

  • SCA-Export: patch name can be set by customers, SP / patch level only by SAP.



Restrictions for CM Services in enhancement package 1 for SAP NetWeaver 7.0

  • It is not possible to exclude Software Components from deployment
  • It is not possible to define build-options
  • SCA-Export: patch name can be set by customers, SP / patch level only by SAP
  • The SAP NetWeaver Developer Studio uses a direct connection to the CTS System. Therefore user and password have to be the same both for NWDI and the CTS system. This means that the password for the CTS system and the NWDI always have to be kept in sync manually. Single Sign on is not an option as the SAP NetWeaver Developer Studio can't be configured for Single Sign On.



Support for CM Services in NetWeaver Developer Studio (NWDS):

  • If you develop Web Dynpro for a runtime system which is not at least on enhancement package 1 for SAP NetWeaver 7.0 or enhancement package 1 for SAP NetWeaver Composition Environment 7.1, you should use the NWDS on the release that fits to your runtime system for developing and another NWDS which supports CM services for releasing the activities. For details, take a look at note 718949 and the following remarks.
  • NWDS on SAP NetWeaver 6.40 or 7.0:
    • If you would like to use CM Services and have to use an NWDS on SAP NetWeaver 6.40 or 7.0, you can do so, but the automatic import of Development Configurations from SLD is not supported. Instead you can download the Development Configuration from the Development Configuration Service UI and then import it into your NWDS manually (Wizard for Import of Development Configurations -> local development configuration file). Keep in mind that these versions of the NWDS do not support the export of activities or SDAs in the transport view. You have to use an NWDS which supports CM Services.
  • CM Services on enhancement package 1 for SAP NetWeaver 7.0:
    • You can use the CM Services to execute activity transports.
    • To be able to execute the transport from within the NWDS, you need an NWDS at least on enhancement package 1 for SAP NetWeaver 7.0 or enhancement package 1 for SAP NetWeaver Composition Environment 7.1.
  • CM Services on SAP NetWeaver Composition Environment 7.2:
    • In addition to enhancement package 1 for SAP NetWeaver 7.0 you can now transport SDAs based on activities. Details are available on the SAP Help Portal
    • To be able to execute the transport of SDAs from within the NWDS, you need an NWDS at least on SAP NetWeaver Composition Environment 7.2.

Affected Releases
Software Component Release From Release To Release And subsequent
LM-TOOLS7.007.017.02X
LM-CTS7.207.207.20X

Related Notes
1575850CM Services: Export SDA ends with Internal DB Access Error
1570686CM Services: Internal DB Access Error
1563107Error releasing activities to CTS+ (Transport View)
1540515CM services: Change of SLD URL
1532722CM Services in CTS+: Wrong object list content
1531756CTS+ with CM Services: Import ends with return code 12
1530463CM Services: Save not working after system move
1525731Synchronize Service: Software components cannot be imported
1516840Configuration service: Secure Connect to Deploy Controller
1453836DIImport_CommunicationException: ...[DICONF_DEVCONFNOTEXIST]