Skip to Content
avatar image
Former Member

Issue in SLD facing lot of isssues in ESS Applications

Hi All,

   we are fcaing lot of major issue in SLD

      We had webdynpro Java Applicayions and Webdynpro ABAP Applications.

My question is : Is it Webdynpro ABAPapplications will use SLD , I don't think so if I am wrorg please correct me

   For Webdynpro ABAP applications each and every standard iview application it consist one standard alia Name which is provided by SAP , we added that alias name to System Object

     in this scenario SLD will come into picture for webdynpro ABAP ?

My assumption is : for  Java applications and connect to backend system(any type of back end system) ,at that time JCO's will come into picture for connect to Back end at that time only SLD will come into picture .  Am I correct ?

    But here Our SLD is maintained as Centralized for our Development  , Quality ,Production Portals using 

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Apr 09, 2012 at 12:06 PM

    Continution for above thread

      But here Our SLD is maintained as Centralized ,Centralized SLD Host , portno for our Development  , Quality ,Production Portals  in Visual j2ee Admin tool - > SLD data supplier  we are maintaining entire details of SLD .

      The JCO S laso will mainatained under centralized SLD only. not in portal level , is it suggestable maintain like this please advise.

      we are facing "500 INERNAL SERVER ERROR" FOR ESS APPLICATIONS even I am not getting Overview page also

        WE checked all the possible ways

    SLD USER unlock , password expiry , every thing is fine , the SLD User is Technical user here so there is no expiry for password.

       But in SLD server , if we click on AS Java threads it is continuosly locking

    if we doing keep on unlock the SLD USER then only , the ESS is coming


      please guys share your knowledge..........



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member


      Check the SLDUSER account when is it being locked , and as well as Data supplier password might be incorrect and locking this account, The account might be locked becuase of incorrect password defined after Refreshed ABAP system or might be a new Java stach where the configuration for SLD datasupplier might have been provided a incorrect value.

      From SLD UME check when is this account being locked. it should help you to narrow down if you check the Last update time underneath the Technical Systems entries once you logged in SLD .