http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents#DiagnosticsAgents-Whichagentversionshouldbeused%3F

Diagnostics Agents

Attachments:8
Added by Michael Kloeffer, last edited by Pieter Bloemendaal on Mar 11, 2013 (view change)

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.

1 Installation

2 Connection Configuration

2.1 Connection options

2.2 SSL Communication

3 Frequently Asked Questions and Trouble Shooting

Installation

Which agent version should be used?

Please refer to SAP Note 1365123 - Installation of Diagnostics Agents

Where to install an agent?

Please refer to SAP Note 1365123 - Installation of Diagnostics Agents

Where to download the agent installation files?

You can download Diagnostics Agent installation from SAP Service Marketplace at: http://service.sap.com/swdc -> Software Downloads -> Support Packages and Patches -> Browse our Download Catalog SAP -> Technology Components -> SAP SOLUTION MANAGER -> SAP SOLUTION MANAGER 7.1 -> Entry by Component -> Agents for Managed systems -> DIAGNOSTICS AGENT 7.3 -> <choose operating system>

Connection Configuration

Please 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:

SLD Registration: In this scenario, the SMD Agent registers itself into the production SLD assigned to the managed system on which the SMD Agent will be installed. This scenario should be used if Solution Manager is not yet installed. With Solution Manager 7.1, this is the recommended option.
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, neither the link "Agent Candidates Management" needs to be used in the "Agent Administration".

SLD Registration - Agent Candidates Management - Solution Manager 7.0 EHP1

If you choose the "SLD Registration" strategy, the Diagnostics Agent should be visible using SOLMAN_SETUP transaction -> System prerequiste -> listed in the Agent Candidates Management. You must attach this agent to the Solution Manager in order to use it.

Access the Agent Administration by:

http://<SOLMANHOST>:<SOLMANPORT>/smd/AgentAdmin

And assign an Agent via the Agent Candidates Management, and assign an Agent via the Agent Candidates Management.

Select "Custom SLD Connection Parameters" check box and enter the connection information of the production SLD to which the SMD Agents are registered.

Click on Apply" Button.

At this point, two tabs are available:

SLD View - displays information retrieved from the SLD. A table displays the list of SMD Agent Candidates. If no SMD Agents are registered to the SLD the list is empty.

SMD View - allows checking the list of SMD Agent registered to SLD and already connected to the Managing System.

How to bind a candidate SMD Agent

On the SLD View tab, select one of the candidate SMD Agents, and then click on “Attach”
A new frame is displayed in the bottom of the screen. It allows to provide the User and Password to connect to the SAP Solution Manager.

The information is automatically send to the SMD Agents when pressing the apply button.
SMD Agent connects itself to the SAP Solution Manager.

Once the registration is over the agent is visible in the regular Agent Administration UI and its state in the list of candidates is (associated).

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 or Solution Manager P4 port. For more information about the smdsetup script refer to the Diagnostic agent troubleshooting guide.

Example:

Connection by Message Server:

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

Connection by P4 port:

smdsetup managingconf hostname:"<fqn>" port:"<p4 port>" [optional user:"<value>" pwd:"<value>"]

To run these script we will need to following information:

Full qualified solution manager hostname.
J2EE Message Server HTTP Port or Solution Manager P4 port:
Diagnostics agent system user: For more information about these user check the User Administration Guide.
Diagnostics agent system user password: For more information about these user check the User Administration Guide.

Where to find the J2EE Message Server HTTP port or Solution Manager P4 port.

J2EE Message Server HTTP: This port is usually 81XX (where xx is the SCS instance number: /usr/sap/<DASID>/SCS<xx>).
Solution Manager P4 port: Enter in the following URL: http://<solmal_msg_server_host>:<j2ee_msg_server_http_port>/msgserver/text/logon

You should get a page like this:

You can see the solution manager P4 port listed. To find the P4 port you can also refer to this help.

Having all necessary information, we just have to perform the smdsetup script to connect the diagnostics agent to the solution manager:

   1. STOP the SMD Agent using the command stopsap or by the SAP MMC.
   2. Open a prompt command and navigate to the script folder inside of the agent path: usr/sap/<SID_AGT>/SMDAXX/script
   3. Run the smdsetup script as the following examples:

Connection by Message Server:

- smdsetup managingconf hostname:"sapms://solman.full.qual.host.name" port:"8101" user:"SMD_ADMIN" pwd:"XXXXXXXX"

Connection by P4 port:

- smdsetup managingconf hostname:"solman.full.qual.host.name” port:"5004" user:"SMD_ADMIN" pwd:"XXXXXXXX"

Afterwards, the command should finish successfully:

4. START the diagnostics agent using startsap or by the SAP MMC.

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.

SSL Communication

Starting with Diagnostics Agent 7.20, the connection to the Solution Manager system can be based on SSL. You can specify the Route between the Diagnostics Agent and Solution Manager. Please refer to the "Diagnostics Setup Guide" attached to SAP note 1368413 for more information.

Frequently Asked Questions and Trouble Shooting

Please refer to the FAQ Diagnostics Agent.

Child Pages (2)

Hide Child Pages | View in Hierarchy

Installation of SMD Agent

Uninstallation of SMD Agent
After successfuly installation of SMD agent using NW installation CD configure the following.

Now it’s connected to the PM1.

I have done the following actions:

In the DPF (580) à RZ70 changed RFC to PM1 (SRPDBS301097) and ran the SLD update trigger again.

On the PM1 hosts (all 4 servers), manually put the hostname + ip-adress in the host file.

On the PM1 , updated the tnsnames with the DPF, did a TNSPING DPF (1527) from the host, ran succesfull.

On the server of the DPF (host), created the thes sapadm (local), updated the windows services SAPHostcontrol, with the correct password and started the 2 services for the hostcontrol.

How services file looks like

sapmsDPF    3600/tcp    # SAP System Message Port
sapmsSMP         3600/tcp       # SAP System Message Port SMP
sapdp00s    4700/tcp    # SAP System Dispatcher Security Port
sapgw00s    4800/tcp    # SAP System Gateway Security Port
sapdp01s    4701/tcp    # SAP System Dispatcher Security Port
sapgw01s    4801/tcp    # SAP System Gateway Security Port
saphostctrl    1128/tcp    # SAPHostControl over SOAP/HTTP
saphostctrl    1128/udp    # SAPHostControl over SOAP/HTTP
saphostctrls    1129/tcp    # SAPHostControl over SOAP/HTTPS
saphostctrls    1129/udp    # SAPHostControl over SOAP/HTTPS
sapmsPM1    3612/tcp    # Solman7.1

Basis and others