Skip to Content

Hello Friends,


System Preparation step is completed and now time to start Infrastructure Preparation steps


Step: SLD Connections


Create Connection

Note: You can connect your PI SLD in here

In my case below are the connection

Step:LMDB Synchronization

1704643 – Getting “No such namespace: Active” error message

1.Please do not use the Host Name of Solution Manager as LMDB Object Server Name.

2.Instead use ‘<SID>_LMDB’ as LMDB object server name.




 On configuration check your requirements and configure Rank of SLDs



Step: LMDB Content Check



Step: Define HTTP connectivity





Step:Enable Connectivity


Automatic steps


Step: Diagnostic Agent Authorization


 Generate certificate and set validity



Step: Setup BW


I am using BW on SAP Solution Manager


Step: Confirm SAP BW


Step: Maintain User

Create required users


Step: Enable SAP BW

 Automatic Activity



Step: Define Introscope Enterprise Manager


Note: Before this step Make sure you have installed DAA in to your system with all HTTPS Connectivity



Step: Setup E-Mail Communication



Execute the RSCONN05 report and activate the required SAPconnect secure E-mail session.

Since SAP_BASIS 7.31 SP2, an integrated encryption solution is available. See SAP Note 1637415.


For more information about secure e-mail encryption, see SAP Note 149926.


Step: Configure CRM Basics




In this activity, you deactivate the creation of Business Document (BDoc) messages.


A BDoc is a document that contains information on changes made to business objects.


The SAP Solution Manager system exchanges BDoc messages with other SAP systems, such as the SAP ERP system, using CRM middleware.


SAP Solution Manager creates BDOc messages for the following BDoc types:





Check whether your SAP Solution Manager scenarios use BDocs and which BDOcs you want to deactivate.



1.To deactivate the BDoc creation, in the Navigation column, start transaction BDoc Type Customizing: Details (SMW3_00).

2.Choose New Entries.

3.In Short Name, enter the BDoc type.

4.Select Do Not Send.

5.Save your entries.


For more information, see SAP Note 635697.






Step: Enable Gateway Services




Activate the following services:



1.From the Navigation column, start transaction /N/IWFND/MAINT_SERVICE.

2.Select one of the above mentioned services.

3.In the ICF Nodes section, choose the ODATA entry.

4.Choose ICF Node and then choose Activate.




Now system is ready for next step configuration – Basic Configuration

Thank you



To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member


    I have upgrade system from SolMan 7.1 to 7.2 SPS04. In Activate Gateway Service step, I don’t see following services. Do we have to create it manully first and then activate or it comes by default.



    1. Yogesh Patel
      Post author

      Hello Dharmin,

      As I remember services was there after upgrade. I don’t think you need to do anything extra.

      Look carefully it must be there in the list.


      Thank you


  2. Daniel basis

    Hi Yogesh,

    Its a nice blog..Thank you

    Can you please explain more on the “select/deselect gateway services ” and preparation activities..

    Is it mandatory to run it…for only using techincal and BPMON ..what scenarios and services to be activated.

    Thanks in advance


  3. Daniel basis

    Thanks for the reply..What services are mandatory for techincal and Bpmon functionalities.

    Can you please name them.

    Thanks in advance

    1. Yogesh Patel
      Post author

      There is window coming called : List of Gateway services

      second last screen shot in this document will tell you all services as per required functionality …




  4. Daniel basis

    Hi Yogesh,

    Thanks for the reply.

    It has services for all the scenarios. I don’t see anything specifically with the name “technical monitoring and BP monitoring. Please list the needed services.

    Thanks in advance.


    1. Pinyada Kaorop

      And when i try to check ping web service of  CO_DIAG_WILY_WS_MANAGED_SETUP  on SOAMANAGER. It’s show “Web service ping failed (RC=401). Service Ping ERROR: Unauthorized ”  and I dont know which user unauthorized.

  5. Former Member

    Hi Yogesh,


    I am doing Infrastructure preparation for first time. Just want to check what is runtime SLD ? is it compulsory to add runtime SLD  or source for LMDB is sufficient?

  6. Daniel basis

    Hi Yogesh,

    Thanks for the nice blog..I have a few questions on SLD connection set up.

    In your case, you are using the local SLD as Solution manager 7.2  SLD.

    If I have configured local SLD on newly installed solution manager 7.2 system, but don’t want use it. Instead Can I assign the “runtime SLD” and “Source of LMDB” roles to the PI system  Central SLD during the connection set up.

    Should I still configure LMDB object server name for this scenario?

    Any precautions while setting up connections to the PI system central SLD?

    Thanks in advance





  7. Daniel basis

    Hi Yogesh,

    if you are using Local SLD for solution manager..why did you define the Runtime SLD role along with “source for LMDB”.

    Is runtime SLD role mandatory to local SLD of the solution manager 7.2?

    Thanks in advance



  8. Daniel basis

    Thanks for your reply..

    Still I am unclear. Please clarify.

    The System data information ( received thru data suppliers) is already going to be provided by the SLD which has the SLD role “source of LMDB” to Solution manager local SLD.

    then why do we need to assign the “Runtime SLD” role also to the same SLD.

    I want to understand Runtime SLD should be used for which cases.

    Thanks in advance


  9. Daniel basis

    thanks again…

    To reflect the technical systems data from local SLD to LMDB..

    just creating the connection with “source for LMDB” role to the local SLD would be fine and sufficient?

    Thanks in advance

  10. Former Member

    Dear Mr. Yogesh,


    It was nice to the total implementation and configuration of Solution Manager 7.2. Your blogs are very useful and very informative.

    We have installed ABAP and JAVA solman 7.2 SP03 in a single system, In infrastructure preparation, Upto LMDB synchronization every thing is correct. In LMDB Content check, we are getting error like

    Application Server ABAP : <not found in LMDB>

    I have checked note 1951213 regarding parameters SAPDBHOST and SLDSYSTEMHOME. Both the parameters are available.

    Please help us to resolve the issue.




    M. Surendra



      1. Former Member

        Issue is resolved. in RZ70, Data collection programs were not running. After executing the same. I was able to connect the ABAP application server. Now the issue has moved to next step, “Define http Connectivity”. I am looking into the issue. If not resolvable by me, I will contact you.

        Thank you


        M. Surendra


  11. License CyberTech

    Hi Yogesh,


    I have upgraded our solman 7.1 to 7.2 SP06, now i am trying to do managed system.

    but when i am trying to push abap system data through rz70 i m getting RFC failed error.

    when i tried to ping SLD_UC rfc (SM59) but failed with internal error

    i have checked so many blog but not found anything plz help.




  12. Petrica Avdei-Mina

    Hello Yogesh,

    Very nice and useful information!

    I have encounter an error in Define HTTP Connectivity step. The rfc tests are fine, the UME ping RFC is successful, but the configuration cannot be saved: Error when saving. Message No. AGS_SIZE_FRWK_MSG001. Ping the logical  port TEST_CONNECTIVITY_J2EE (note 2584685) is failing with 401 error, as described in the note, but UMEBackendConnection is fine. I dont know how to proceed further.

    I have followed all the note I have found. I have also opened a incident at SAP. 

    Any hint for me?

    Thank you in advance!

    Best regards,

    Peter A.



Leave a Reply