2573122 - Diagnostics Agent can't find .sar file

This article discusses several technical aspects related to performing an archive based installation of the Diagnostics Agent.

More details, also on the currently required minimum patch-levels of the SAR-files, which you need when installing with the latest SWPM version, are documented in SAP Note 2253383.

For this example, a directory holding all the below listed SAR-files was constructed.  The directory on purpose holds much more SAR-files than needed, to increase the illustrative value of this example. In directory /SWPM/K_749_U_LINUX_X86_64_JVM8/DBINDEP, we have:

SAR-File Patch-Level Requirements

When providing a set of SAR-files to the SWPM installer, all SAR-files, regardless of their name, will get scanned to determine if the name and the content of the included manifest-file matches the requirements of the selected installation option. SWPM names these requirements "manifest predicate". During the scanning of the SAR-files, "manifest predicate" information is written to the sapinst_dev.log.

In the sapinst_dev.log you will find "Request archive" entries like shown below. These entries print-out which "manifest predicate" the SWPM installer will enforce, for each of the required SAR-files for your current installation option. The SAR-file names which you see below are the assumed default SAR-file names. The SWPM installer will also accept (e.g.) SAR-files which have a patch-level in the name, as we will see later on.

TRACE      2017-11-28 11:48:35.913 (root/sapinst) (startInstallation) com.sap.sdt.ins.component.archive_extraction.SpecifyArchive
Request archive:
 - name: SAPEXE
 - media name: SAPEXE.SAR, part of the Kernel
 - manifest: sapmanifest.mf
 - dependencies: []
 - manifest predicate:
                  @keyname='SAP_KERNEL' and
                  @kernel_os='LINUXX86_64' and
      @compilation_mode='UNICODE' and
     (
      (@kernel_release=721 and @kernel_patch_number>=800) or
      (@kernel_release=722 and @kernel_patch_number>=300) or
      (@kernel_release=749 and @kernel_patch_number>=200)
     )
 
TRACE      2017-11-28 11:48:35.913 (root/sapinst) (startInstallation) com.sap.sdt.ins.component.archive_extraction.SpecifyArchive
Request archive:
 - name: SAPJVM6
 - media name: SAPJVM6.SAR, part of the Kernel
 - manifest: sapjvmmanifest.mf
 - dependencies: [SAPEXE]
 - manifest predicate:
                  @keyname='SAPJVM' and
                  @sapjvm_os='LINUXX86_64' and
                  @sapjvm_release=6.1 and
      (
       ( //SAPEXE/@kernel_release=721   and   @sapjvm_patch_number>=99        )  or
       ( //SAPEXE/@kernel_release=722   and   @sapjvm_patch_number>=99        )  or
       ( //SAPEXE/@kernel_release=749   and   @sapjvm_patch_number>=99        )
      )

TRACE      2017-11-28 11:48:35.913 (root/sapinst) (startInstallation) com.sap.sdt.ins.component.archive_extraction.SpecifyArchive
Request archive:
 - name: SAPDIAGNOSTICSAGENT
 - media name: SAPDIAGNOSTICSAGENT.SAR, part of the Kernel
 - manifest: diagnosticsagent.mf
 - dependencies: [SAPEXE]
 - manifest predicate:
                  @keyname='SAPDIAGNOSTICSAGENT' and
      (
     ( @release=7.10 and   @servicepack=11 and  @patchnumber>=5   )  or
     ( @release=7.20 and   @servicepack>=4 ) 
      )

SWPM UI

Once SWPM has scanned and checked the SAR-files which you have provided, it will only show the accepted SAR-files in the SWPM UI. The below example shows that all required files are found and accepted.

The "info file" link at the screen below, gives you access to detailed analysis results.

The "info file"

The "info file" will help you to understand why SAR-files are accepted or rejected.

Per processed SAR-file, the analyzed candidate files are listed, and if a SAR-file is not accepted, the table in the "info file" lists the reason.

If at least the manifest file-name was correct, the not met "manifest predicate" is shown.

Explanation	Section from the "info file"
SWPM looks for a SAPDIAGNOSTICSAGENT.SAR candidate. Based on manifest-file name (Manifest Check) one file is selected. The "manifest predicate" is fullfilled.
SWPM looks for a SAPEXE.SAR candidate. Based on manifest-file name (Manifest Check) two files are selected. For @kernel_release = 749, the @kernel_patch_number attribute must be >= 200. The "manifest predicate" is not fullfilled for patch_number 100. The "manifest predicate" is fullfilled for patch_number 300.
SWPM looks for a SAPJVM6.SAR candidate. Based on manifest-file name (Manifest Check) four files are selected. The "manifest predicate" requires an @sapjvm_release=6.1. Two SAR-files fullfil that. The "manifest predicate" also requires an @sapjvm_patch_number>=99. Only one SAR-file fullfils that.
SWPM looks for a SAPHOSTAGENT.SAR candidate. Based on manifest-file name (Manifest Check) two files are selected. The "manifest predicate" requires an @hostagent_patch_number >= 22, for all supported kernel versions. Only one SAR-file fullfils that.
SWPM looks for a SAPJVM8.SAR candidate. Based on manifest-file name (Manifest Check) four files are selected. The "manifest predicate" requires an @sapjvm_release=8.1. One SAR-file fullfils that.

Manifest-file Content

If you have trouble finding the correct version for one of the required SAR-files, you may want to check the manifest information which the installer has found in (e.g.) the kernel SAR-file which you provided.

This information can also be found in the sapinst_dev.log.

The below table shows the content of several manifest-files used in this example.

Note that the attributes which you see in the manifest-files are the same attributes which are used to formulate the "manifest predicate".

KBA , SV-SMG-INS-AGT , Installation of Solution Manager Diagnostics Agent , How To