Charm Cutover and Activation Guide in Solution Manager For Managed System Landscape
Charm Cutover and Activation Guide in Solution Manager For Managed System Landscape
Charm Cutover and Activation Guide in Solution Manager For Managed System Landscape
Contents
1) Purpose of this documentation:- .............................................................................................................. 3
2) SLD Update: .............................................................................................................................................. 3
3) RFC generation:......................................................................................................................................... 4
4) STMS Configuration in managed system : ................................................................................................ 6
5) Establish Domain Link ............................................................................................................................... 7
6) Create Logical Component in Solution Manager .................................................................................... 11
7) Create CHARM project in Solution Manager: ......................................................................................... 13
Page |3
2) SLD Update:
Managed system data should be pushed from managed system to the solution manager (SOP)
SLD.
Use transaction RZ70 for abap, NWA/Visual admin for java (If local SLD is configured, a SLD bridge needs to be
configured between solution manager (SOP) and managed system SLD.
No impact to the existing functionality if we create a bridge between managed system and solution manager SLDs.
i. Goto transaction rz70(in managed system). Provide the hostname and the service name
of the solution manger system.
v. In transaction sldapicust, provide the host name, port, SLD user and the password.
Page |4
3) RFC generation:
Generation of RFC to managed systems will be done from SOP using solman_setup/lmdb and not
through smsy. The roles required for users to be used in the RFCs are assigned from solman_setup only
and not manually.
Below users would be created in all the managed system clients while performing the RFC generation
activity in the solution manager system.
SM_<SID> SOLMAN_READ
SOLMAN_READ_620
SOLMAN_READ_70
SAP_SM_S_RFCACL
SMTM<SID> SOLMAN_TMW
SOLMAN_READ
SOLMAN_READ_620
SOLMAN_READ_70
SAP_SM_S_RFCACL
Goto Technical systems tab and enter the SID of the managed system for which you need to generate
the RFCs
Select the relevant client and enter the user details and click on execute to generate the RFC
destinations.
Page |6
Transports are supported in the standard transport layer of each client. When you configure transport
routes, note that only consolidation routes that are assigned to the standard transport layer of the
relevant exporting client are taken into consideration. For each exporting client, exactly one target client
and one target group are permitted.
The transport route should be configured as in other landscapes (example: WTD landscape) to ensure
that the routes are defined in the recommended manner. Also, ensure that the routes are defined as
client specific.
1. Log on to the SAP system that functions as the transport domain controller.
To find out which system is the domain controller, call transaction STMS and choose Overview ->
Systems. In the Cat column (with the quick info text TMS system type), look for the icon with the quick
info text Controller.
2. Call transaction STMS.
3. Choose Overview -> Systems.
The system overview appears.
4. Choose Goto -> Transport domain.
The Display TMS Configuration: Domain <Domain name> screen appears.
5. Select the Management tab page.
6. Switch to change mode.
7. In the Security options group box, select Activate Trusted Services.
8. Save your changes and distribute the configuration.
Enter the system name, host name and system number of the domain controller you want to link to, and
then confirm your entries.
For security reasons, you now need to confirm the link between the two domains in the other controller.
Position the cursor on the domain controller where you requested the domain link and choose SAP
System → Approve.
P a g e | 10
Assign the product version of the system to the logical component by clicking on the “maintain”
Now assign the technical systems and maintain the relevant role as shown below.
P a g e | 13
Take into account that all systems that belongs to the TMS landscape must be assigned to the same
logical component, because all system must have the same product version (exception in case of an
upgrade).
P a g e | 14
Always define here the same landscape that you have defined in the STMS of the real landscape, if not
the Charm scenario cannot be activated.
- In IMG project tab: define always a project in the development system ONLY! You need to define this
project in the development system in order to assign to this project all transport orders that you are
going to create via a Change request in the solman system, this is a prerequisite for Charm scenario!
Select the name of your Maintenance Cycle also called Project Cycle.
P a g e | 16
P a g e | 17
Note: Choose Lock/Unlock Group/Subsequent Groups to unlock the tasks in the task list.
If all is working correctly a Task List and a Maintenance transaction type SDMN (called Service Desk
Transaction in the screenshot) is being created.