Sap Solution Manager 7.2 Diagnostics Agent
Installation
Which agent version should be used?
Before starting the installation you need to identify the Diagnostics Agent version that complies with the version of the Solution Manager system.
Solution Manager | Managed Version | Diagnostics Agent Version / SAP Note |
---|---|---|
Versions 7.00 (prior to EhP1) | 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1,7.2 | 7.01 SR1 SAP Note 1357812 |
Versions 7.0 EhP1 >= SP 18 | 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1,7.2 | 7.01 SR1 SAP Note 1357812 |
Versions 7.0 EhP1 >= SP 20 (SP4 SP2) | 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1,7.2 | 7.20 SAP Note 1368413 |
Versions 7.1 | 6.40, 7.0x, 7.1x, 7.2x, 7.3 | 7.3 SP02 SAP Note 1448655 |
In case of Solution Manager uprade, it is not mandatory to upgrade the Diagnostics Agent version. This specification applies only to new installations.
More information see SAP Note 1365123 .
Where to install an agent?
Install one Diagnostics Agent per Host (physical or virtual depending on use case). You can find more information on SAP note 1365123 - Installation of Diagnostics Agents (see the file attached to this note -> Agent_Installation_Strategy.ppt)
Where to download the agent installation files?
You can download Diagnostics Agent installation package named "Installation of DIAGNOSTICS AGENT 7.3 SP02 (incl. HostAgent)" 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 of managed>
Installation Step-By-Step
Please check the installation step-by-stephere.
Uninstallation Step-By-Step
Please check the uninstallation step-by-stephere.
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.
- 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
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 theDiagnostic 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 theUser Administration Guide.
- Diagnostics agent system user password: For more information about these user check theUser 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 thishelp.
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 note 1368413 for more information.
Sap Solution Manager 7.2 Diagnostics Agent
Source: http://how2-sapbasis.blogspot.com/2012/10/diagnostics-agents.html