Skip to Content
Technical Articles

Diagnostics Agent provisioning with LaMa – my experiences

Solution Manager Diagnostics Agent installation and uninstallation is part of SAP Landscape Management (LaMa) – both Standard and Enterprise editions. However, to make provisioning easy, there are some configuration steps required. Let me share my experiences, how I could manage to install Diagostics Agent for an SAP System on Linux.

Source of knowledge

What was required?

  1. Software provisioning Manager (SWPM) – latest version
  2. Archives for the installation (SAPEXE*.SAR, SAPJVM*.SAR, SMDA*.SAR, SAPHOSAGENT*.SAR)
  3. Well prepared NFS share
  4. Well prepared NFS client
  5. Well prepared folder structure for the SWPM and archives
  6. LaMa, at least Patch03 for Support Package 09 – see SAP Note 2713517 – SAP Landscape Management 3.0 SP09 Documentation Updates (login required)

First of all, I downloaded SWPM – Software Logistics Toolset > System Provisioning > Download Software provisioning Manager. There downloaded SOFTWARE PROVISIONING MGR 1.0 > SWPM 1.0 SPXX for NW higher than 7.0x (SWPM10SPXX_Y-NNNNNNNN.SAR)

Then, I downloaded following archives (as I have Linux on X86_64 the below archives are valid for that; patch level and numbering may be different for other platforms):

  • SAPEXE_1200-10011360.SAR
  • SAPHOSTAGENT41_41-20009394.SAR
  • SAPJVM8_52-80000202.SAR
  • SMDA720_SP04_1-80003641.SAR

After I finished with downloading, I logged on to the NFS server and prepared the repository. I call the NFS server “nfs-server” this time. Below structure was required:

  • /export_data/DA/InstMaster
  • /export_data/DA/Archives

I exported /export/DA. I usually use below options to make my life easier:

  • rw,no_root_squash,sync

I extracted SWPM*.SAR in InstMaster, like below:
/usr/sap/hostctrl/exe/SAPCAR -xvf /path/to/SWPM.SAR -R /export/DA/InstMaster

After that I copied SAPEXE, SAPHOSTAGENT, SAPJVM8, SMDA720 SAR archives in /export/DA/Archives, as they were. They did not have to be extracted!

Afterwards, I logged on to the NFS client (let’s call it “nfs-client”) and mounted nfs-server:/export/DA under /mnt/lamarepo/DA. There I had the same structure as on nfs-server:

  • /mnt/lvmrepo/DA/InstMaster
  • /mnt/lvmrepo/DA/Archives

And here I reached the point where I had to log on to LaMa and perform the configuration and installation. I’m illustrating it with screenshots – clink on the pictures to enlarge them.

Step 1: Create repository



Step 2: Add configuration


Important was to select “Export Path” otherwise mounting on another host did not work:


And here I had the configuration:

Step 3: Provisioning (this time: installation)

I ignored the warning for this step and continued:



Used Validate Step to get the configuration:


Summary screen:

Execution:

Provisioning finished with success:

Installation finished with success.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.