Diagnostic Agent: Using the SMD Setup Script

The smdsetup script can be used to update configuration parameters for the Diagnostics Agent.

Script Location:

The smdsetup script can be found in following directory:

  • <Drive>:\usr\sap\<DASID>\SMDA<Instance_Number>\script

Restarting the Diagnostics Agent

The smdsetup script will modify one or more of the following configuration files:

  • runtime.properties
  • secstore.properties

 

Script Actions


******************
* Action sldconf *
******************

This action changes the connection settings for the SLD system where the agent will register.
* Register the agent with the SLD system:

> K:\usr\sap\DAA\SMDA97\script\smdsetup sldconf hostname:"sldhost.domain.corp" port:"50000"
> K:\usr\sap\DAA\SMDA97\script\smdsetup sldconf hostname:"solman-mc" port:"50200" user:"SLDAPIUSER" pwd:"Sld.001.2019"

***********************
* Action secstorej2ee *
***********************
This action changes the user credentials used to connect the agent to the configured SAP Solution Manager system.
* Updates the secstore.properties file of the agent:

> K:\usr\sap\DAA\SMDA97\script\smdsetup secstorej2ee user:"SMD_AGT" pwd:"xxxxxx"

**********************
* Action secstoresld *
**********************
This action changes the user credentials used to register the agent with the configured SLD system.
* Updates the secstore.properties file of the agent:

> smdsetup secstoresld user:"SLDDSUSER" pwd:"xxxxxx"

***************************
* Action changeservername *
***************************

This action changes the server name attribute of the agent.
* Updates the runtime.properties file of the agent:

> K:\usr\sap\DAA\SMDA97\script\smdsetup changeservername servername:"solman-MC"


**********************
* Action supportlogs *
**********************

This action creates a ZIP-file holding Diagnostics Agent related configuration files and log files. The ZIP-file can be provided to SAP when creating a support ticket.

* Execute: smdsetup supportlogs
 To create:

> /usr/sap/DAA/<Instance_Number>/SMDAgent/supportLogs_<Timestamp>.zip

The generated ZIP-file will (at least) contain the following:

* Diagnostics Agent check result file:

/usr/sap/<DASID>/<Instance_Number>/SMDAgent/log/AgentSupportToolReport.log

* Diagnostics Agent log files
* Diagnostics Agent profile
* Installer log files
* Content of directory /usr/sap/<DASID>/<Instance_Number>/work
* Relevant files from directory /usr/sap/<DASID>/<Instance_Number>/SMDAgent
* Relevant files from directory /usr/sap/<DASID>/<Instance_Number>/SMDAgent/configuration

The Diagnostics Agent check that is performed will (at least) check for following:

* JDK version
* JVM parameters
* Host name resolution
* TCP port
* P4 protocol
* Java SCS Message Server connectivity


***************** ERROR ********************
 - No agent certificate found.


* Stop the agent
* Notepad K:\usr\sap\DAA\SMDA97\SMDAgent\configuration\runtime.properties
* SAPLOCALHOST = solman-MC
* Save the changes
* Start the agent
* Run the script to connect the agent again

+ + + + +

> K:\usr\sap\DAA\SMDA97\script\smdsetup certificate operation:"DEL" alias:"ssl-certificate" import_type:"generic"


https://help.sap.com/viewer/705868d857a74f7694765312ef11d4f4/CURRENT_VERSION/en-US/34e1805236aa7054e10000000a44176d.html