Harmonizing RFC communication infrastructure for CHARM
How do you switch from using RFC/TMS communication for CHARM to RFC communication only? A number of SAP notes explain how to do this. It comes down to implementing the relevant SAP notes on the Solution Manager system (if not already present) and on the managed SAP systems and configuring the RFC connections to the clients used by CHARM for the managed SAP system.
Relevant SAP notes
Why do you want to use RFC only?
If you use RFC communication, you will know where to troubleshoot as where if you use the “old” way RFC/TMS communication mixture you would have to first find out in which of those communication parts the problem resides. You no longer need RFC connections to client 000 of your managed SAP systems when you use RFC communication only.
There is no need to create TMS domain links in between different TMS domains that are to be used in CHARM.
The SAP Basis teams are often not so fond uon making a lot of changes to their TMS domains. It depends how the TMS domain(s) have been set up. One of the things that can get in the way is the TMSADM user-id: 1568362 – TMSADM password change
When you place a lot of systems in a single TMS domain or you link a lot of TMS domains, it means each managed system connected in those domains which are connected together gets an update pushed towards the system. If any of the system(s) is unavailable due to ongoing operations (or a issue of some sort) you can have an inconsistent landscape configuration.
All in all good reasons to move away from using the combined communication method TMS/RFC and going for RFC communication.
What do I need to do further?
You need to configure the RFC connections towards the clients used by CHARM for your managed SAP system (through SOLMAN_SETUP). The trusted RFC connection is used so don’t forget to also set up trusted RFC.
Customers often already have these connections in place after the integration of a managed SAP system in SAP Solution Manager.
RFC user authorizations
The RFC users use the standard authorizations according to SAP Note 1572183 – Authorizations for SAP Solution Manager RFC users
This SAP note is updated frequently which also means your SAP Basis or SAP Authorization team (depending on who handles this, often SAP Basis does) should also update the roles in the SAP Solution Manager system in order to have the latest additional authorization objects added to the roles.
I’m not so fond of this mechanism to be honest, the way of delivery and the continuous effort needed at customer side. I hope SAP comes up with a better solution in the future.
How do I check if it works?
Make sure you have the corrections in place along with the RFC destination(s) & correct authorizations.
Navigate to SOLAR_PROJECT_ADMIN (or go through the Solution Manager workcenter). Edit the CHARM enabled project of your choice (or create a new project & enable it for CHARM). I assume the prerequisites are in place, the correct logical component (related to the managed SAP system) is in the project and the project is CHARM enabled.
Go into tab System Landscape – Change Management as displayed in the screenshot above.
Under Change Request Management, hit the “Check” button.
Expand The System overview for project <your Solution Manager project> in this example “CHARM_MAIN”
You can see in the actual result(s) that the new TMS remote functionality is active which means you are using RFC communication to handle CHARM related actions. Underneath you can see the information on the needed RFC connections and settings.
Note that I blanked out the SID in the above screenshot.
An attention point but a valid one in general is that it should be ensured that the RFC destinations keep working properly. The best way to ensure is to monitor it. Solution Manager has a RFC connectivity monitoring scenario which can be used. Another possibility is doing daily checks on the SOLMAN_SETUP – managed system setup configuration list where you also get the current RFC configuration status with traffic lights (make sure that the list is up to date, if needed refresh it). This is mostly an attention points for SAP Basis, you should inform them of the importance that these RFC destinations are configured correctly and keep working properly. Otherwise, you will end up having issues in CHARM.