Exciting times ahead for the SAP Community! We've outgrown our home, so we'll be migrating to a new platform later this year. Let's continue the journey together!
I have a question about creation of technical system in LMDB for these non-abap systems. Let me give an example:
ABAP SID is 'ABC'
Corresponding HANA DB SID is 'ABC' as well.
Technical systems for both these systems are available in the production solution manager.
Development solution manager is the domain controller here.
In this system ABC is created as a virtual system 'ABC' on the STMS and routes, parameters are all configured and CTS+ works perfect.
Now we are trying to consume CTS+ service that is enabled on Development solution manager on our Production solution manager via ChaRM functionality.
How do i represent these non-abap virtual systems in LMDB of production solution manager? What SIDs should i use? I'm guessing if i try to create a virtual system with the same SID again, then there were be three systems with same SIDs 'ABC' in the production solution manager.
Quick question on CTS+ integration with ChaRM..Once this integration is done, will the status based import strategy be used to control import of Non-ABAP trnasports or status based import will work only for ABAP transports.
Your very informartive blog seems to have disappeared during the makeover of SDN..... It now linked to a post"SCNOTTIES 2011 LAS VEGAS STYLE"..... It would be nice to restore it... 🙂
Hi Dolores. As always very good information !! Thanks a lot.
Hi Dolores
Thanks a lot for this very good blog !
We need your advice concerning a trouble on our own configuration.
We build a SAP solman landscape with dev qal prod where prod is a domain controller.
On Qal we have connected a non abap landscape SO1 SO2 SO3 (PO Systems), and we try to activate charm project.
In TMS configuration, we defined QAL like Communication System.
Charm project has been activated successfully.
We would hope that QAL will be the transport organizer, driving cts project and transport request.
And not !!! We are surprised to see that solman prod(domain controller) was the transport organizer and cts project.
So we are confused because the parameter "Communication_system" is not respected.
maybe we missed something.
Thanks a lot for your return.
Happy to read you.
Wilfried
Very informative blog. Thanks
Dolores,
I have a question about creation of technical system in LMDB for these non-abap systems. Let me give an example:
ABAP SID is 'ABC'
Corresponding HANA DB SID is 'ABC' as well.
Technical systems for both these systems are available in the production solution manager.
Development solution manager is the domain controller here.
In this system ABC is created as a virtual system 'ABC' on the STMS and routes, parameters are all configured and CTS+ works perfect.
Now we are trying to consume CTS+ service that is enabled on Development solution manager on our Production solution manager via ChaRM functionality.
How do i represent these non-abap virtual systems in LMDB of production solution manager? What SIDs should i use? I'm guessing if i try to create a virtual system with the same SID again, then there were be three systems with same SIDs 'ABC' in the production solution manager.
Is there a different way to do this?
Appreciate your help.
Best Regards,
Aravind Kumar Jagannathan
Hi Dolores,
Quick question on CTS+ integration with ChaRM..Once this integration is done, will the status based import strategy be used to control import of Non-ABAP trnasports or status based import will work only for ABAP transports.
Appreciate your guidance.
Regards,
Imran
Very informative document.
Hello Dolores,
Your very informartive blog seems to have disappeared during the makeover of SDN..... It now linked to a post"SCNOTTIES 2011 LAS VEGAS STYLE"..... It would be nice to restore it... 🙂