on 04-25-2014 11:22 AM
Hello
I am trying to configure Webdynpro contents for ESS MSS but SLD is faulty.
I cannot start SLD on Web Dynpro Content Administrator, it says Connection to System Landscape Directory (SLD) could not be opened successfully but I can open SLD without any problems.
What I did so far;
I set NWA > Destinations > SLD_Client and SLD_DataSupplier to Solution Manager, XI and local SLD, nothing changed. Connection tests were ok and I was able to open all SLD links without any problems.
I updated CIM content to latest version on local SLD and Solman's SLD.
I added SAP server IPs to hosts file.
I updated Netweaver 7.4 to latest Java SP level which was 6.
How can I make webdynpro content work and how can I fix SLD error?
Also current SLD destination is set to Solution Manager's SLD
Best regards
Kaan
Hi Kaan,
do the Connection test in the JCo again and post the Log of:
http://localhost:50000/SLD -> Administration -> Log
Your problem sounds like an authorization problem. If you find a message like:
com.sap.sld.api.builder.app.DefineHostedSystem: CIM exception in SLD ping (CIM_ERR_ACCESS_DENIED: User is not allowed to read any data of CIM domain SLD.).
Then you have to correct the authorizations in JAVA for the SLDDSUSER.
Best regards
Willi Eimler
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
I even gave SAP_J2EE_ADMIN role and SAP_ALL profile to SLDDSUSER on Solution Manager but I am still getting same error webdynpro content admin.
Also as for logs there are nothing new.
#9 04/21/2014 16:09:56.521 [SAPEngine_Application_Thread[impl:3]_38] INFO com.sap.lcr.start.StartDirector: SLD application started successfully.
#8 04/21/2014 16:09:52.20 [SAPEngine_Application_Thread[impl:3]_37] INFO com.sap.lcr.start.StartDirector: SLD application stopped successfully.
#7 04/18/2014 11:17:36.393 [Thread-136] INFO com.sap.lcr.pers.delta.importing.ImportHandler: Finished aggregate import into namespace sld/active: More...
#6 04/18/2014 11:17:36.363 [Thread-136] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 113 ms)
#5 04/18/2014 11:06:02.973 [Thread-136] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 111 ms)
#4 04/18/2014 11:05:49.75 [SAPEngine_Application_Thread[impl:3]_13] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 74 ms)
#3 04/18/2014 11:05:23.826 [Thread-134] INFO com.sap.lcr.pers.delta.importing.ImportHandler: Finished model import into namespace sld/active: More...
#2 04/18/2014 11:04:58.811 [SAPEngine_Application_Thread[impl:3]_16] WARNING com.sap.lcr.jsp.importWarning: The following warning has been reported by import precondition checks, user decision required: More...
#1 04/18/2014 11:04:58.800 [SAPEngine_Application_Thread[impl:3]_16] INFO com.sap.lcr.pers.jdbc.JdbcPersistence: Deleted namespace: sld/import/temp0 (Duration: 185 ms)
#0 04/16/2014 20:28:19.243 [SAPEngine_Application_Thread[impl:3]_37] INFO com.sap.lcr.start.StartDirector: SLD application started successfully.
Hi Kaan,
sap_all is not all authorizations in sap. This was in the beginning of sap.
The user needs the Roles
SAP_J2EE_ADMIN
SAP_SLD_DATA_SUPPLIER
That no logentry exists, points to the fact that the ping doesn't knock the "door of SLD".
Can you please post the parameters of SLD
http://localhost:50000/SLD -> Administration -> Settings -> Section = ALL
Best regards
Willi Eimler.
Hi Kaan,
the profile seems to be ok.
But the user needs SAP_SLD_DATA_SUPPLIER. And I looked at my server docu. I implemented
1617234 - Incorrect SLD security role assignments after upgrade
too.
Group SAP_SLD_DATA_SUPPLIER has the following Roles:
and Role SAP_SLD_DATA_SUPPLIER has the following actions:
Best regards
Willi Eimler
Hello
I finally managed to solve my problem.
I deleted all SLD_Client and SLD_DataSupplier destinations. I deleted all SLD configurations on portal. I created SLD_Client destination as HTTP and used http://localhost:50000 (do not put /sld at the end of link, that shows success but it is the probably main reason). I edited object server as localhost and now it works.
Best regards
Hello,
I completed similar problem with j2ee_admin user authorization for SLD_client destination. User with role sap_j2ee_admin doesn't help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kaan,
Can you try testing the URL:
http://192.168.100.13:50000 or
http://192.168.100.13:50000/sld/cimom
and kindly let us know the result?
Are there errors seen in the SLD log?
My Kind regards,
Grainne.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.