SAP DAA Agent Registration

SAP Note 1913837 – How to connect Diagnostics Agent to SLD by using smdsetup script

Symptom

The Diagnostics Agent is not shown in a SLD or there is error message about the connectivity to SLD in the agent log SMDSystem.X.log

Environment

SAP Solution Manager 7.1

EHP1 Solution Manager 7.0

/wp-content/uploads/2015/02/1_652667.jpg

If agent is currently not registered against the SLD, current recommendation from Agent Installation Strategy guide is not to register agents of Managed Systems Hosts against SLD as per note 1365123. Following resolution applies to changing or adding the SLD connection details.

Procedure:

  1. Please login the Operating System with the Diagnostics Agent admin user <SID>ADM e.g. DAAADM.
  2. Stop the Diagnostics Agent.

/wp-content/uploads/2015/02/1_652667.jpg

     3. Go to the directory
           /usr/sap/<SID_AGT>/J<Instance_Number>/script
                               or
           /usr/sap/<SID_AGT>/SMDA<Instance_Number>/script

/wp-content/uploads/2015/02/1_652667.jpg

4.     Run the command in the following format

smdsetup sldconf hostname:”mySLDhost.domain.corp” port:”<SLD HTTP Port>” user:”SLDDSUSER” pwd:”xxxxxx”

     runtime.properties file will generate the SMD agent configuration directory

/wp-content/uploads/2015/02/1_652667.jpg

5. Start the Diagnostics Agent.

/wp-content/uploads/2015/02/1_652667.jpg

6. Check if the Agent is shown in the SLD.

/wp-content/uploads/2015/02/1_652667.jpg

If the Agent-On-the-fly (AOTF) feature is used please see also the SAP KBA 2007621 – SLD user locked by Agent on-the-Fly Diagnostics Agent, when changing the password – Solution Manage 7.10

1907909 – How to connect Diagnostics Agent to Solution Manager system directly by using smdsetup script

  1. Please login the Operating System with the Diagnostics Agent admin user <SID>ADM e.g. DAAADM.
  2. Stop the Diagnostics Agent.
  3. Go to the directory
    /usr/sap/<SID_AGT>/J<Instance_Number>/script
    or
    /usr/sap/<SID_AGT>/SMDA<Instance_Number>/script
  4. Run the command

  smdsetup managingconf hostname:”sapms://myhost.domain.corp” port:”81xx” user:”SMD_ADMIN” pwd:”xxxxxx”

or

smdsetup managingconf hostname:”sapms://myhost.domain.corp” port:”81xx” user:”SMD_AGT” pwd:”xxxxxx”

ABAP Role

The SMD User on the Monitoring System requires the ABAP role SAP_SOLMANDIAG_SAPSUPPORT. It is delivered within SAP standard as of NetWeaver 04 SP Stack 13 (see SAP note 828533).

To create this role manually, refer to Creation of Role for ABAP User [see page 57].

J2EE UME Role

The SMD User on the Monitoring System requires the UME roles SAP_JAVA_NWADMIN_CENTRAL_READONLY, SAP_JAVA_SUPPORT (successor of role SAPSUPPORT) is delivered within SAP standard as of NetWeaver 04 SP Stack 13. To create this role manually, refer to Creation of UME Role for J2EE Engine [see page 58].

J2EE Server Roles

where the hostname is the Solution Manager full host name, and xx in the port is the number of the Solution Manager SCS instance number. As of Solution Manager 7.1 SP10, the user is SMD_AGT instead of SMD_ADMIN.

  1. Start the Diagnostics Agent.
  2. Check if the Agent is shown in the page of Agent Administration in Solution Manager System.

/wp-content/uploads/2015/02/1_652667.jpg

Registration commands:

# Update server name on smd

smdsetup changeservername servername:”servername

# Connect to solution manager

smdsetup managingconf hostname:”servername” port:”5xxxx” user:”SMD_USER” pwd:”xxxxxxx

# Connect to solution manager trough port or P4

smdsetup managingconf hostname:”servername” port:”xxxxx” user:”SOLMAN_ADMIN” pwd:”xxxx

# Connection trought saprouter

smdsetup addsaprouter route:”/H/x.x.x.x/S/3299/H/solman.domain.com/S/3299

# Registration of agent on sld

smdsetup sldconf hostname:”servername” port:”5xxxx” user:”j2ee_admin” pwd:”xxxx

Regards,

V Srinivasan

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply