SAP diagnostics agents

Diagnostics Agents

Skip to end 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.
• 
  
• 1Installation
• 1.1 General Information
• 1.2 Download Paths
• 1.3 Recommended Reading
• 1.4 Which agent version should be used?
• 1.5 Where to install an agent?
• 1.6 Where to download the agent installation files?
• 2 Connection Configuration
• 2.1Connection options
• 2.1.1SLD Registration - Remotely Connect DIagnostics Agents - Solution Manager 7.1
• 2.1.2Direct Solution Manager Registration
• 3 Connect the Diagnostics Agent to Solution Manager Using SSL
• 4 How to Configure the Different Ciphers on the Diagnostic Agent
• 5 Frequently Asked Questions and Trouble Shooting

Installation

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
• Instructions on how to download the Installation Media
• Instructions on how to patch the Installation Media
• Details on supported kernels
• Description of the unattended/silent installation mechanism
• SMD Setup Script (smdsetup.bat/smdsetup.sh) 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 http://support.sap.com/sltoolset
• Product Availability Matrix/PAM:  search for "Product Availability Matrix"
• Documentation:  System Provisioning  →  System Provisioning Scenarios →  Install a System using System Provisioning Manager →  Installation Option of Software Provisioning Manager 1.0 → Installation Guides - Standalone Engines and Clients → Diagnostics Agent  → download the guide for your  "Operating System Platform"
• "installer":  System Provisioning → Download Software Provisioning Manager → SOFTWARE PROVISIONING MGR 1.0 → DOWNLOADS → → SWPM10SP*.SAR
• For download of individual archives go to SAP Note 2253383
• Check SAP Note 1858920 and the Product Availability Matrix for supported kernel versions

Recommended Reading

• Diagnostics Agent and HA Support
• Diagnostics Agent Maintenance Procedures

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).

Example:

• Connection by Message Server:

smdsetup managingconf hostname:"sapms://" 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.
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//SCS).

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://:/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//SMDAXX/script
   2. Run the smdsetup script as the following examples:

• Connection by Message Server:

     - smdsetup managingconf hostname:"sapms://solman.full.qual.host.name" 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.

Connect the Diagnostics Agent to Solution Manager Using SSL 

Please refer to the configuration wiki: Connect the Diagnostics Agent to the Solution Manager using SSL.

How to Configure the Different Ciphers on the Diagnostic Agent

Please refer to SAP Note 2849162.

Frequently Asked Questions and Trouble Shooting

Please refer to the FAQ Diagnostics Agent.

Connect SAP Diagnostics Agent to Solution Manager using SSL

Перейти к концу метаданных

The aim of this wiki is to help in enabling the configuration to connect the Diagnostics Agents to the Solution Manager 7.10 using SSL, as described in note 1898685. Actually, the focus is narrowed down to prerequisite #2 of step #2, described in the same note.

This configuration is not valid for Solution Manager 7.20.

Prerequisites

The prerequisites are the deployment of the IAIK libraries in the Diagnostics Agent, as described in note 1898685  and the SSL configuration for the Solution Manager Message Server and P4 ports.

Solution 

Configure transport layer security on Solution Manager JAVA Stack

The configuration of the Solution Manager Java Stack to enable secure communication is described in detail in the following guide: 

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/bc/2ee9a2d023d64eac961745ea2cb503/content.htm.

The following setup step needs to be performed to enable secure communication on the Solution Manager Java stack:

Configure SSL on AS Java:

1. Create SSL Credentials: in the Visual Admin(/usr/sap/<SID>/DVEBMGS<xx>/j2ee/admin) of the Solution Manager, select the Key Storage, under Server > Services. Create new credentials or check the validity f the already available credentials for service_ssl:
   
   Detailed information and the how to guide is available under: http://help.sap.com/saphelp_nw70ehp2/helpdata/en/a6/98f73dbc570302e10000000a114084/content.htm.
2. Assign SSL Credentials to HTTPS communication port: Access the SSL provider with the following path: Server > Services > SSL Provider. Select the configured HTTPS port (default is 5xx01) and assign the SSL certificate created in the previous step as "Server Identity".
    
3. Assign SSL Credentials to the P4S communication port: Access P4 provider with the following path: Server > Services > SSL Provider. Select the configured P4S port (default is 5xx06) and assign the SSL certificate created in the frist sttep of this section as "Server Identity".
   
   Further documentation about SSL configuration for Solution Manager Java Stack is available in the following documentation:  http://help.sap.com/saphelp_nw70ehp2/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm.

Configure SSL on Message Server for Solution Manager ABAP and JAVA Stack

This section is relevant if you want to use MS HTTPS and P4S connection.

The executable directory of the message server needs the SAPCRYPTO libraries installed. For a message server running as part of Central Instance of ABAP stack this is already performed in step ”Install SAP Cryptographic Library and set Profile Parameters”. For Message Server on Java Central Service Instance (SCS) and ABAP Central Service Instance (ASCS) execute the same procedure. Also make sure a valid server identity is available in $DIR_INSTANCE$/sec that a valid SAPSSLS.pse. For simplification it is possible to reuse the server identity as created for the Solution Manager ABAP Stack.

Add the following parameters to the Central Services Instance Profile to enable Message Server HTTPS port:

ms/server_port_1 = PROT=HTTPS,PORT=444$$

SAP Host Agent

SAP Host Agent is an agent that can accomplish several life-cycle management tasks, such as operating system monitoring, database monitoring, system instance control and provisioning.

Validity of this Documentation

This documentation is valid for SAP Host Agent 7.21 Patch Level (PL) 004 and higher. SAP Host Agent 7.20 has been deprecated. For more information, see SAP Note 2130510 .

For information about how to check the version of an existing SAP Host Agent installation, see SAP Host Agent Reference - Command Line Options of the saphostexec Executable.

See SAP Note 1907566  about how to update older versions of this documentation within your local SAP Library installations.

SAP Host Agent Usage

SAP Host Agent has installed automatically during the installation of new SAP system instances with SAP kernel 7.20 or higher. SAP Host Agent has upgraded automatically as part of the SAP system instance when you patch or upgrade the SAP kernel. However, you can also install and upgrade SAP Host Agent independently from an SAP system instance.

Recommendation

It is strongly recommended that you regularly upgrade SAP Host Agent to its latest version. See also SAP Note 2219592 .

Features

SAP Host Agent provides you with the following features:

• SAP instance discovery and inventory
• SAP instance control
• Database monitoring and management
• System or instance provisioning:
  • Hosting the infrastructure of SAP Landscape Virtualization Management (LVM), formerly known as SAP NetWeaver Adaptive Computing Controller (ACC)
  • Hosting software lifecycle (SL) tools interfaces
• Operating system monitoring:
  • Using saposcol
  • Using Common Information Model (CIM) based infrastructures
• IBM i-specific features:
• Dynamically adopted authorization for SAP kernel 7.20 and higher
• SAP ILE daemon (SAPILED)
• SAP Database Performance Collector for IBM i
  
  Related Information

Downloading the SAPHOSTAGENT Archive

Upgrading SAP Host Agent from Extracted SAPHOSTAGENT Archive

Upgrading SAP Host Agent Without Extracting the SAPHOSTAGENT Archive

SAP diagnostics agents

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.
Installation

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
• Instructions on how to download the Installation Media
• Instructions on how to patch the Installation Media
• Details on supported kernels
• Description of the unattended/silent installation mechanism
• SMD Setup Script (smdsetup.bat/smdsetup.sh) 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 http://support.sap.com/sltoolset
• Product Availability Matrix/PAM:  search for "Product Availability Matrix"
• Documentation:  System Provisioning  →  System Provisioning Scenarios →  Install a System using System Provisioning Manager →  Installation Option of Software Provisioning Manager 1.0 → Installation Guides - Standalone Engines and Clients → Diagnostics Agent  → download the guide for your  "Operating System Platform"
• "installer":  System Provisioning → Download Software Provisioning Manager → SOFTWARE PROVISIONING MGR 1.0 → DOWNLOADS → → SWPM10SP*.SAR
• For download of individual archives go to SAP Note 2253383
• Check SAP Note 1858920 and the Product Availability Matrix for supported kernel versions

Recommended Reading

• Diagnostics Agent and HA Support
• Diagnostics Agent Maintenance Procedures

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).

Example:

• Connection by Message Server:

smdsetup managingconf hostname:"sapms://" 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.
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//SCS).

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://:/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//SMDAXX/script
   2. Run the smdsetup script as the following examples:

• Connection by Message Server:

     - smdsetup managingconf hostname:"sapms://solman.full.qual.host.name" 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.

Connect the Diagnostics Agent to Solution Manager Using SSL 

Please refer to the configuration wiki: Connect the Diagnostics Agent to the Solution Manager using SSL.

How to Configure the Different Ciphers on the Diagnostic Agent

Please refer to SAP Note 2849162.

Frequently Asked Questions and Trouble Shooting

Please refer to the FAQ Diagnostics Agent.