As you might know on the SCN Wiki page ‘Resources on CTS+’ (https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=448469096) you can find guides to configure CTS+ on specific landscapes. Among others you can find there two How-To Guides (CTS+ for SAP Neo und CTS+ for SAP Cloud Foundry) in the area ‘SAP Cloud Platform’.
My bloq post goes a step further. It describes the important configuration you need to perform to combine SAP Solution Manager 7.2 Change Request Management to a CTS+ landscape with SAP Neo or SAP Cloud Foundry on the SAP Cloud Platform.
This blog post is not describing the normal setup of Change Request Management on SAP Solution Manager 7.2. There are different guides existing which are describing that.
Realization
When you finished the setup of CTS+ with one of the guides mentioned above you need to add the systems from TMS to LMDB.
Adding and Maintaining Systems in LMBD
You already created 3 Non-ABAP Systems in your communication system (in many cases it is the SAP Solution Manager system itself).
With transaction RZ70 you can register these systems to your SLD (if you are still using an SLD). After adding them to SLD you go into LMDB “Technical Systems” and open your communication system (e.g. the SolMan):
In edit-mode you synchronize the SLD with LMDB by using the Sync Job:
Before using the systems within ChaRM you must create an external service for each system (DEV, QAS, PRD) in LMDB to represent the transport nodes in the SAP Cloud Platform Transport Management service.
There please read the SAP Note 2712590 – “SAP Cloud Platform and SAP Solution Manager ChaRM scenario” and go on reading this blog post 🙂
Here comes these steps for the DEV system in your landscape:
A guided procedure will be open.
Please be sure that Application Domain is selected to “others”:
In a second step you have to maintain the identifier from SAP Neo or from the SAP Cloud Foundry Space (in my case it is ChaRMDEVSystem for the development system, ChaRMQASSystem for quality system and ChaRMPRDSystem for the poduction system):
Click on “Next”:
Here please enter the Extended System ID (the same SID which you was using in TMS for this system) and click on “Next”.
At the end you have to “Save”:
Perform these steps also for you QAS and PRD system in your system landscape!
Linking the TMS-Systems with LMDB-Systems
After creating the systems and external services in LMDB you can switch to “Transport Domains” on LMDB Start Screen.
Here you enter the Transport Domain where you made the CTS+ setup and click on “Edit”:
Now you go to tab “Non-ABAP Systems” and you can see,the system (here: CFD, CFQ, CFP) which you created before. But the link to external service for each system is still missing:
With the Button “Assign Technical System” you can create the link by the upcoming guided procedure.
Maintain “External Service” as Technical System Type and enter your SID like in the TMS:
When you did that for all your systems in the landscape (DEV, QAS and PRD) it should look like this:
After that you can create the normal ChaRM stuff (where you are familiar with 😉 like Logical Component Group, Change Control Landscape and ChaRM cycle.
Summary
This blog post explained the necessary steps to combine a CTS+ configuration for a SAP Neo or SAP Cloud Foundry landscape on the SAP Cloud Platform together with ChaRM on your SAP Solution Manager 7.2 system. These steps took me a while to find out and in order to save YOUR time I wanted to share it with you 🙂
If you are interested in more content around SOLMAN Change Control Management, follow the tag: https://answers.sap.com/tags/250948378054223096392454848767354 to receive notifications.
Subscribe
Login
Please login to comment
0 Comments