SMD not communicating with SOLMAN

[shelby_may2]

Hi,

The SMD instance on our portal servers is supposed to talk to SOLMAN. This was working fine until I had to change the J2ee_admin password on SOLMAN. After that, the SMD instances will not start because they can not communicate due to the password being changed. I have no way of knowing the old password. How can I update the password for these SMD instances? I found note 903080 which mentions a URL (.../smd/admin URL) but I can not access this URL. I've tried http://servername:50000/smd/admin but the page is not found.

Any ideas?

Thank you very much.

Shelby

[Former Member · Accepted solution]

Hi,

Basically, the SMD agent registers itself with solman using the SMD_ADMIN user. I think that you may have given J2EE_ADMIN user earlier and thats why when the password for J2EE_ADMIN was changed, the issue happened.

You can try and register the agent again using one of the following ways:

1. On solman host, go to Solman Diagnostics workcenter and under Agent Administration, in the Agent Credentials panel, fill the previous login of the Diagnostics Agents and enter the new one (or enter the same login with a new password). Click on the Update all agents button.

2. If the previous step is not possible, reregister the SMD agent on the portal server using the following command:

smdsetup managingconf hostname:"sapms://<J2ee_Message_server_hostname>" port:"<http_port_message_server>" user:"<SMD_ADMIN or J2EE_ADMIN>" pwd:"xxxxxx"

This will reregister the SMD agent with the new user credentials.

Please try and let me know if this works.

Regards,

Shitij

[shelby_may2]

Shitij,

Thank you very much for the answer. I used method 2 and it worked perfectly.

Thanks,

Shelby

[Former Member]

Hi Shitiz/Shelby,

I had the same type of issue from the newly installed portal app server and after doing the method 2 i did get the agent to be visible from agent administration as well as from the diagnostics setup. But for the central instance of the portal which got upgraded, the agent is showing as running in Agent Administration but from diagnostics setup it is still showing as not connected,,,, any idea ?

Thanks,

Murali.