Skip to Content

Part 11 : SAP Solution Manager 7.2 SR1 (+ SPS03) : Basic System setup:Infrastructure Preparation

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:

  • BUPA_MAIN
  • BUS_TRANS_MSG
  • CRM_IBASE_MESS
  • PRODUCT_INDOBJ
  • PRODUCT_SRV

 

Requirements

 

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

 

Activities

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

 

Activities

 

Activate the following services:

  • AGS_FLP_INTEROP
  • AGS_FLP_PAGE_BUILDER_PERS

 

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.

 

Complete

 

Now system is ready for next step configuration – Basic Configuration

Thank you

Yogesh

 

36 Comments
You must be Logged on to comment or reply to a post.
  • Hello,

    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.

    • AGS_FLP_INTEROP
    • AGS_FLP_PAGE_BUILDER_PERS

     

    • 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.

      Tcode: /n/IWFND/MAINT_SERVICE

      Thank you

      Yogesh

  • 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

     

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

    Can you please name them.

    Thanks in advance

    • 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 …

       

       

       

  • 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.

     

  • 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?

  • 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

     

     

     

     

  • 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

     

     

  • 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

     

  • 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

  • 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.

     

    Regards

     

    M. Surendra

     

     

      • 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

        Regards

        M. Surendra

         

  • 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.

     

    Regards,

    PD

  • 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.

     

  • Dear Yogesh Patel

     

    I have recently Upgrade my Solution Manager AS ABAP Stack from SPS06 TO SPS08, today I had upgraded AS JAVA Stack from to SPS 08, but in Infrastructure Preparation, activity 2.2 Enable Connectivity, Check Java Software Prerequisites is failling. However in AS JAVA components are upgraded to the expected level. I have attached Solman_setup screenshot and spread sheet of AS JAVA components.

    can you please check the attached screenshot and guide me ??

    ADSSAP sap.com SAP AG 1000.7.40.17.0.20171205170700
    AJAX-RUNTIME sap.com SAP AG 1000.7.40.17.0.20171205170700
    BASETABLES sap.com SAP AG 1000.7.40.17.0.20171205170800
    BI-WDALV sap.com SAP AG 1000.7.40.17.0.20171205174900
    CFG_ZA sap.com SAP AG 1000.7.40.17.0.20171205170800
    CFG_ZA_CE sap.com SAP AG 1000.7.40.17.0.20171205170800
    CORE-TOOLS sap.com SAP AG 1000.7.40.17.0.20171205170800
    DI_CLIENTS sap.com SAP AG 1000.7.40.17.0.20171205170700
    ENGFACADE sap.com SAP AG 1000.7.40.17.0.20171201193800
    ENGINEAPI sap.com SAP AG 1000.7.40.17.0.20171205170800
    EP-BASIS-API sap.com SAP AG 1000.7.40.17.0.20171205180900
    ESI-UI sap.com SAP AG 1000.7.40.17.0.20171202081100
    ESP_FRAMEWORK sap.com SAP AG 1000.7.40.17.0.20171205180700
    ESREG-BASIC sap.com SAP AG 1000.7.40.17.0.20171205180700
    ESREG-SERVICES sap.com SAP AG 1000.7.40.17.0.20171205180700
    FRAMEWORK sap.com SAP AG 1000.7.40.17.0.20171205170700
    FRAMEWORK-EXT sap.com SAP AG 1000.7.40.17.0.20171205180800
    ISAGENT sap.com SAP AG 8.2.5.0.20151028173229
    ISAGENT_MIN_J5 sap.com SAP AG 9.7.1.16.20151111165203
    J2EE-APPS sap.com SAP AG 1000.7.40.17.0.20171205170800
    J2EE-FRMW sap.com SAP AG 1000.7.40.17.0.20171205170800
    JSPM sap.com SAP AG 1000.7.40.17.0.20171205170800
    LM-CORE sap.com SAP AG 1000.7.40.17.0.20180108211700
    LM-CTS sap.com SAP AG 1000.7.40.17.0.20171205174900
    LM-CTS-UI sap.com SAP AG 1000.7.40.17.0.20171205170700
    LM-MODEL-BASE sap.com SAP AG 1000.7.40.17.0.20171205174900
    LM-MODEL-NW sap.com SAP AG 1000.7.40.17.0.20171205174900
    LM-SERVICE sap.com SAP AG 1000.7.20.8.0.20181204124900
    LM-SLD sap.com SAP AG 1000.7.40.17.0.20171205174900
    LMCFG sap.com SAP AG 1000.7.40.17.0.20171205174900
    LMCTC sap.com SAP AG 1000.7.40.17.0.20171205174900
    LMNWABASICAPPS sap.com SAP AG 1000.7.40.17.0.20171205174800
    LMNWABASICCOMP sap.com SAP AG 1000.7.40.17.0.20171205174800
    LMNWABASICMBEAN sap.com SAP AG 1000.7.40.17.0.20171205174800
    LMNWACDP sap.com SAP AG 1000.7.40.17.0.20171205174900
    LMNWATOOLS sap.com SAP AG 1000.7.40.17.0.20171205183100
    LMNWAUIFRMRK sap.com SAP AG 1000.7.40.17.0.20171205174900
    MESSAGING sap.com SAP AG 1000.7.40.17.0.20171205180700
    ODATA-CXF-EXT sap.com SAP AG 1000.7.40.17.0.20171205174900
    SAP-XI3RDPARTY sap.com SAP AG 1000.7.40.11.0.20151028105116
    SAP_BUILDT sap.com SAP AG 1000.7.40.17.0.20171205170700
    SECURITY-EXT sap.com SAP AG 1000.7.40.17.0.20180111001000
    SERVERCORE sap.com SAP AG 1000.7.40.17.0.20171205170800
    SOAMONBASIC sap.com SAP AG 1000.7.40.17.0.20171202081100
    SR-UI sap.com SAP AG 1000.7.40.17.0.20171202081100
    SUPPORTTOOLS sap.com SAP AG 1000.7.40.17.0.20171205170800
    UDDI sap.com SAP AG 1000.7.40.17.0.20171205180700
    UISAPUI5_JAVA sap.com SAP AG 1000.7.50.13.0.20180812230000
    UMEADMIN sap.com SAP AG 1000.7.40.17.0.20171205174900
    WD-ADOBE sap.com SAP AG 1000.7.40.17.0.20171205170700
    WD-APPS sap.com SAP AG 1000.7.40.17.0.20171205180500
    WD-RUNTIME sap.com SAP AG 1000.7.40.17.0.20171205170700
    WD-RUNTIME-EXT sap.com SAP AG 1000.7.40.17.0.20171205180500
    WSRM sap.com SAP AG 1000.7.40.17.0.20171205180700

    Please it is urgent, Our Solution manager is productive system due to VAR activities.

     

    I will be really thankful to you.