Solution Manager SMSY automatic update configuration
Remember, this blog is about automation of solution landscape system data in SMSY.The following will not be discussed.
1.) Solution Manager installation.
2.) Basic Solution Manager configuration.
3.) mopz user creation.
You will have to do these before starting. A few general points before starting
1. SMSY in this method will have data source SLD
2. All child systems will push data to Solution Manager SLD
3. SLD is a java program and can be accessed by url: – http://hostname:5$$00/SLD
4. SLDDSUSER is the data supplier user created during Solution Manager installation.
1.) For application server ABAP go to RZ70, point it to your Solution Manager system by giving the hostname & gateway. Activate & execute. You should get a success message. Now the ABAP system data has been pushed to Solution Manager SLD.
2.) For application server java go to visual admin, cluster->server->services->SLD data supplier. Click the runtime tab on top & http settings tab on the bottom, give in the host, port, data supplier user and password for the same. Now hit the “blue bolt” button just above runtime. You should get a success message. You can verify this by clicking on the information tab. Now the java system data has been pushed to Solution Manager SLD.
3.) Now that were done with pushing the data. We move on to check if it reflects in central SLD. Logon to http://hostname:5$$00/SLD where hostname is of your Solution manager. Click on technical systems and you will see your child systems data.
4.) Now that we have confirmed the child system data in SLD, we can move on to know how this data can be pushed to reflect in SMSY. But hold on, we discussed application server ABAP & java. What about stand-alone engines? Non netweaver based software have SLDreg. This is a program that sends data in XML format to the central SLD.
a.) Find out where the SLDreg is.
b.) Go to the path and give SLDreg -usekeyfile -configure /SLDdest.cfg
c.) It will generate 2 files. SLDdest.cfg & SLDdest.cfg.key
d.) Copy these file to ../SYS/global directory
e.) Now the SLDreg will send data in XML format to the central SLD
f.) To check, go to http://hostname:5$$00/SLD administration-> content maintenance and should be able to see it after selecting the appropriate component.
5.) Moving on to automating SMSY, create a rfc destination in visual admin(cluster->server->services->destinations)/NWA & give all login credentials. Let’s name it SLDAPIJCO
6.) Now go to jCo in visual admin (cluster->server->services->jCo rfc provider) set a new rfc listener and give in a program id, host, gateway & server count = 3 (lets name it SLDAPI_TOM). Give in the rfc destination created previously in step 5.
7.) Now login to Solution Manager & go to SM59 in Solution Manager & create rfc with type T & give the program id as created previously i.e. SLDAPI_TOM.
8.) Go to tab, MDMP & unicode. Select unicode & hit save.
9.) Now that we have things setup, we can populate the data into SMSY. For this we need the job “LANDSCAPE FETCH”. T-code SMSY_SETUP, select radio button SLD, select hourly or whatever option suits you and save. Check in SM37 if the job finishes successfully.
10.) Now check SMSY, every single detail about your SAP systems will be automatically entered in. From database versions to number of OS cpu’s, from ABAP support packs to java archives. Even clients & component versions.Limitations: – Assignment to logical component will have to be done manually.
Thank you every one for reading. Do let me know if you have any opinions/questions.