On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
7 rates
This topic describes installing the HTTP SDK automatically. You can install, update, and reinstall the HTTP SDK on every active application server node of the SAP system by using the Automatic SDK Installation program.

Before You Begin

  • To make automatic HTTP SDK installation possible, ensure that a supported operating system (OS) is installed on each application server node. For unsupported or mixed OS, see manual HTTP SDK installation.

  • Create a target directory on every application server node. The default directory is /opt/appdynamics (Linux) or C:\AppDynamics (Microsoft Windows).

  • Provide the OS user, <SID>adm or SAPService<SID>, with full permission on the target directory on each application server node.

  • Install or update the ABAP agent first. It contains HTTP SDK package used for automatic installation.

  • For an HTTP SDK update, stop all running HTTP SDK instances using transaction code /DVD/APPD_STATUS.

  • For Microsoft Windows OS:

    • Install PowerShell on each application server. 

    • Set the execution policy to RemoteSignedExecute the following command as Administrator and confirm with Y + Enter:

      PS C:\> Set-ExecutionPolicy RemoteSigned

Install or Update HTTP SDK

  1. Start the AppDynamics HTTP SDK Installation Manager application by using the transaction code /DVD/APPD_SDK. Alternatively, you can click SDK Installation in the customizing menu to start the application.
    The AppDynamics HTTP SDK Installation Manager screen appears. 

    Before the first SDK installation, a prompt to select custom installation directory appears. The selected directory is used for all application servers. Ensure that the SAP OS user has full access to selected directory. You can recall this prompt from menu Edit > Change Directory at any time.

  2. On the SDK Installation Manager page, click Install SDK.
    When all the installation requirements are met, the application installs the HTTP SDK on all application servers.

Verify if your installation is successful and looks similar to the following installation:

 

 The following table describes the fields and descriptions:

FieldDescription
Status

Global status of the installation for a given node.

  • Green indicates that the node is ready for installation.

  • Red indicates potential errors during the installation pre-check.

Node nameName of an application server node.
HTTP SDK folderA directory on the application server, where you install the HTTP SDK.
Directory Exists
  • Green indicates that a target directory exists on the application server node.

  • Red indicates the absence of the target directory on the application server node.

Write Access
  • Green indicates that the <SID>adm or SAPService<SID> user has the write access on the target directory.

  • Red indicates that the <SID>adm or SAPService<SID> user does not have the write access on the target directory.

SDK Installed
  • Grey indicates that no HTTP SDK version was detected in the target directory.

  • Green indicates detecting an HTTP SDK version in the target directory.

  • Red indicates the presence of an obsolete version of HTTP SDK.

SDK Stopped
  • Green indicates that no HTTP SDK instance is running on a given application server node.

  • Red indicates the presence of an active HTTP SDK instance on the application server node. Stop all HTTP SDK instances before proceeding with HTTP SDK update or re-installation.

CurrentShows the version of SDK currently installed on the application server.
NewShows the newest version of HTTP SDK delivered with latest ABAP Agent transport request.

Install Custom Certificate for Local HTTP SDK

Custom SSL certificate must be installed if you want to use SSL communication with On-premises controller. 

  1. Go to your Controller using web browser.
  2. Download SSL certificate in .crt format and save as custom.crt.
  3. Go to transaction code /DVD/APPD_SDK.

  4. Select Edit > Upload Cust SSL file from menu.

  5. Select the certificate file and click Open.

  6. Go to transaction code /DVD/APPD_STATUS and restart all HTTP SDK instances.

Migration from 4.4.1811

Before 4.4.1812 release, it was not possible to use custom certificate file name. The default file ca-bundle.crt needed to be overwritten with custom certificate.

During installation of newer releases (4.4.1812+), the installer checks for the default certificate. If the file ca-bundle.crt contains custom certificate, it is copied into ca-bundle-cust.crt and customizing will be updated accordingly.

  • No labels