Skip to end of metadata
Go to start of metadata
The diagnostics agent is a central component of the SAP Solution Manager system landscape. This page summarizes all relevant information on the agent and provides detail information on all relevant topics.


General Information

Following documents are most relevant for installing and working with the Diagnostics Agent:

  • Refer to SAP Note 1365123 for the Diagnostics Agent installation strategy. 

  • Refer to SAP Note 1833501 for information on Diagnostics Agent installer versions, and for an overview of SAP Notes related to Mass Deployment / Unattended Installation.

  • Refer to SAP Note 1858920 and the latest Installation and Setup Guide for:

    • Information on how to access the Product Availability Matrix (PAM) for the Diagnostics Agent
    • Differences that exist between the SWPM and 70SWPM installers
    • Instructions on how to download the Installation Media
    • Instructions on how to patch the Installation Media
    • Details on supported kernels
    • SMD Setup Script (smdsetup.bat/ documentation
    • More detailed installation instructions

Download Paths

Artifacts required for Diagnostics Agent installations can be downloaded as follows (for detailed instructions and alternative paths refer to latest Diagnostics Agent Installation and Setup Guides):

  • Go to  →  Software Logistics Toolset 1.0 
      • PAM →  "direct link"
      • Documentation  →  System Provisioning
          • Installation: Diagnostics Agent  →  <back_to_top_button_in_lower_right_corner>  →  "Installation and Setup Guide" for your "Operating System Platform"
      • "installer" (see big table with links)  →  row: System Provisioning  →  column: Download 
          • "download tool"  →  <your_platform>  →  SWPM10SP*.SAR (we recommend the SWPM10SP*.SAR installer)
      • "kernel" (see big table with links)  →  row: System Provisioning  →  column: Download
          • "download Kernel releases delivered for SL Toolset"  →  "Kernel for installation/SWPM"  →  "SAP KERNEL 7.21 EXT 64-BIT UC" (we recommend the 7.21 EXT SAP KERNEL)
              • "Installation"  →  <your_platform>  →  <your_download_object>

Recommended Reading

Which agent version should be used?

Please refer to the above mentioned Diagnostics Agent Installation Strategy SAP Note.

Where to install an agent?

Please refer to the above mentioned Diagnostics Agent Installation Strategy SAP Note.

Where to download the agent installation files?

Please refer to the General Information section above.

Connection Configuration

Refer to the installation procedures contained inside the Diagnostics Setup Guide.

Connection options

Before starting the installation make sure that you have identified which installation strategy you want to use. This means that you need to choose between the two following scenarios:

  • Direct Solution Manager Registration: In this scenario, the Diagnostics Agent establishes a direct connection to the Solution Manager system. Using this type of connection no SLD attachment is necessary especially since Solution Manager 7.1 SP05. Operational issues concerning Diagnostics Agents to Solution Manager connectivity can now be easily resolved via the “Non-authenticated Agents” list. (See Non Authenticated Diagnostics Agents).
    Prerequisite: Diagnostics Agent was connected to a Solution Manager 7.1 SP05 system at least once.
  • SLD Registration: In this scenario, the Diagnostics Agent registers itself into the production SLD assigned to the managed system on which the Diagnostics Agent will be installed. This scenario should be used especially if Solution Manager is not yet installed.

SLD Registration - Remotely Connect DIagnostics Agents  - Solution Manager 7.1

If you choose the "SLD Registration" strategy, the Diagnostics Agent should be visible using SOLMAN_SETUP transaction -> System preparation -> Step "Connect Agents". You must connect the relevant Diagnostics Agents to the current Solution Manager system in order to later be able to use them.

Agent reconnection may require waiting several minutes. It depends on settings which are set on the SMD Agent side. As soon as it detects that the association has been changed the SLD state is updated and the registration should proceed.

Direct Solution Manager Registration

If you want to perform the "Direct Solution Manager Registration" after the installation of the Diagnostics Agent, you will need to perform the smdsetup script action managingconf.

You can perform the direct connection to the solution manager in two ways, using the J2EE Message Server HTTP port (recommended). For more information about the smdsetup script refer to the Diagnostics Agent setup guide attached to the SAP Note for the most recent installer release (see SAP Note 1833501).


  • Connection by Message Server:

smdsetup managingconf hostname:"sapms://<fqn>" port:"<J2EE MsgServer HTTP Port>" [optional user:"<...>" pwd:"<...>"]

To run these script we will need to following information:

  1. Full qualified solution manager hostname.
  2. J2EE Message Server HTTP Port, like 81<SolMan Java SCS Instance>.
  3. Diagnostics Agent system user: For more information about these user check the User Administration Guide.
  4. Diagnostics Agent system user password.

Where to find the J2EE Message Server HTTP port.

  • J2EE Message Server HTTP: This port is usually 81XX (where xx is the SCS instance number: /usr/sap/<DASID>/SCS<xx>).

Make sure that you address the Solution Manager Java SCS Message Server with the above mentioned port number. URL.  Enter in the following URL: http://<solmal_msg_server_host>:<j2ee_msg_server_http_port>/msgserver/text/logon
This shall display a P4 and/or P4S line, like here:

Having all necessary information, you have to perform the smdsetup script to connect the Diagnostics Agent to the Solution Manager system:

   1. Open a prompt command and navigate to the script folder inside of the agent path: usr/sap/<SID_AGT>/SMDAXX/script
   2. Run the smdsetup script as the following examples:

  • Connection by Message Server:

     - smdsetup managingconf hostname:"sapms://" port:"81XX" user:"SMD_ADMIN" pwd:"XXXXXXXX"

  •  Afterwards, the command should finish successfully:

Then check at the “Agent Administration” if the agent is connected to the Solution manager. If the agent does not connect to the Solman system check the SMDSystem log for error. This log file can be found into the log folder at the agent path.

IMPORTANT: Note that SAP recommends to use the connection via the Solution Manager Java SCS Message Server. Trying out a direct connection via the P4 or P4S port, is only relevant in some very specific situations.

Frequently Asked Questions and Trouble Shooting

Please refer to the FAQ Diagnostics Agent.



  • No labels
  1. SAP Note 1878116 - P4 port not reachable

  2. See also the SCN blog "Agent Data in the SAP Solution Manager LMDB" by Wolf Hengevoss:

    Best regards


  3. How to enable this P4 onto my solution manager/message server ?

    this SAP note 1878116 - P4 port not reachable tells nothing to me...


  4. Hello Expert,


    I am facing an issue while registering agent with Solman in windows using below command.

       1) Open a prompt command and navigate to the script folder inside of the agent path: usr/sap/<SID_AGT>/SMDAXX/script
       2. Run the smdsetup script as the following examples:

    R:\>C:\usr\sap\DAA\SMDA98\script\smdsetup.bat managingconf hostname:"Solman_host" port:"50XX4" user:"SMD_agent" pwd:"XXXXXX"

    i have also tried below command also

    R:\>C:\usr\sap\DAA\SMDA98\script\smdsetup.bat managingconf hostname:"sapms://" port:"81XX" user:"SMD_ADMIN" pwd:"XXXXXXXX"


    but getting an error that SMD server or port is not reachable.


    Please suggest.  

    1. Hi,

      I noticed that your example command has port "50XX4" but I think this is usually "5XX04".  If you used "50XX4" then it maybe worth trying "5XX04" instead.


      1. Hello ,

        I have tried 5xx04 , it was not working ... This error I am getting while installing agent ... My installation is not yet completed ..

        I tried to install agent with production Solution manager details and use prod solution manger port which was working fine .... 

        only getting an error while installing agent with pre-prod solution manager details...




          Dear Viral,

          Note that the Diagnostics Agents shall in general always be connected via the Solution Manager Java SCS Message server and not the P4 or P4S port.
          I have updated this page to better highlight this and avoid ambiguities.

          Now, let me answer your question. In general the P4 port looks like: 5NN04. However the Java SCS Message Server HTTP port looks like: 81XX, where XX usually represents the Instance number. Remember also that the Java SCS Java has always a distinct instance number.

          Hope this answers your question.

          Best regards,



  5. Hello,

    do you have any guide or information on how to configure this but through a SAPRouter? It really seems that in the smdsetup sldconf or smdsetup managingconf commands you can't put the SAPRouter route (/H/..../S/...)

    So if I configure it like this:

    smdsetup sldconf hostname:"solution_manager_private_IP" port:"50000" user:"SLDDSUSER" pwd:"password"

    smdsetup managingconf hostname:"solution_manager_private_IP" port:50004” user:"SMD_ADMIN" pwd:"password"

    smdsetup addsaprouter route:"/H/SAPRouter_Public_IP/S/sapdp99/H/solution_manager_private_IP/S/3300"

    it doesn't work... any suggestions?

    thank you