Buttons not enabling for JCO Creation in SLD

Question

Hi Experts,
When i logged in into my Webdynpro Content Administrator with administrative rights, all the button like Create JCo Destination, Maintain JCo Destination and Start assigned SLD are getting disabled expect Check SLD Connection Button.
Moreover, displaying a message : "Connection to System Landscape Directory (SLD) could not be opended successfully." at the bottom of the screen.
When i click on the Check SLD Connection Button and then Test Connection, it gives again the same message i.e "Connection to System Landscape Directory (SLD) could not be opended successfully."
Now, When i click on the Check SLD Connection Button and then Start SLD, SLD server is staring and running.
Another thing is, When i am starting my sld server from logging in into http://<hostname>:<port>/sld, SERVER status is running. I stopped it and again started, then it is starting, but giving an error message as:
"Failed to send start signal for complete cluster, SLD may still be stopped on other cluster nodes."
When saving any parameters like profile information, it is not saving and saying error as:"
Cannot save profile settings CIM_ERR_FAILED: Failed to initialize cluster notification sender."
My setting are correct in SLD Data Supplier in Visual Administrator. I had filled the host/port/user/password information for both "HTTP Settings" and "CIM Client Generation Settings".
It went worked well earlier, i come across this problem recently with my sld.
Another thing that i noticed is when i click on the "CIMClient Test" button, its getting an error message saying "Failed to Generate and Test CIMOMClient Object". But, ealier it came as successfull.
I have full authorization to use admin tools.
What might be the problem.
any help must be appreciated.
regards
sunil kumar

Answer 1

Hi Sunil,
We just had this issue couple of days before, this has to do with the JMS Provider Authorization. We did the following steps to solve our issue:
I. Default security configuration of JMS resources is in place (this is by far the most common scenario) and named anonymous users have been created.
Change the mapping of the "clients" jms role as follows:
1. Start the Visual Admin
2. Browse the tree in the left pane
<SID> -> Server 0 -> Services -> Security Provider
3. The "Policy Configurations" tab should be selected by default on the right hand side
4. Select the "service.jms.default.authorization" node from the "Components" list (should be the nineth entry from the top down)
5. Select the "Security Roles" tab
6. Select the "clients" node from the security roles list
7. You should see on the right hand side "Security Roles" list in which the "guests" node is marked
8. Switch to edit mode by pressing the change button on top (pencil icon). The "Modify" button should now become active
9. Press the "Modify" button
10.Select the "all" entry from the "Security Roles" list. The "Groups" pane should show one entry named "Everyone"
11. Press the "Save" button
12. Restart the cluster so that JMS and applications using it can reliably reinitialize.
Check
Note 971249 - JMSServerSecurityException thrown accessing JMS resources
for more details.
Hope this helps!
Regards,
Preetha Rethinam