Configure the agent-manager connection

Edit online

The agent-manager connection links the Datalink (Classic) Agent to the Datalink (Classic) Manager. When you configure the connection, you will be prompted to supply the agent with the manager information.

  1. Open the Datalink (Classic) Agent (https://localhost:8401 for an on-premises installation).
  2. Confirm that the correct URL for the Datalink (Classic) Manager appears. If it does not, navigate to the Datalink (Classic) Manager and copy the URL from the browser address bar.
  3. Enter a name for the agent. This is the name that appears in the Datalink (Classic) Manager.
    TIP: If you will be using an HTTP proxy, select Use Proxy and complete the proxy information.

On-premises agent proxy configuration

If an on-premises Datalink (Classic) Agent is required and network traffic needs to go through a proxy, ensure the following:

  • In the agent configuration page, Proxy Settings section, enter the necessary proxy details.
  • The agent needs to be able to communicate with the Datalink (Classic) Manager and Apptio instance. Make sure both can be reached using a proxy. Based on the proxy configuration, the Datalink (Classic) Manager URL and the Apptio instance URL need to be set to allow traffic through the proxy.
  • If the proxy is configured so that it intercepts the connection, and in the process inserts its own certificates for the HTTP calls, those certificates need to be imported into the dlagent.jks file, located in the installation folder.
  • If the on-premises agent is upgraded to a newer version in the same installation folder, it probably will replace the dlagent.jks file. If certificates have been imported into dlagent.jks , back up this file before doing an upgrade, then restore it after the upgrade.
  • Some example values for the Non-Proxy-Hosts field are: localhost?127.0.0.1|216.161.*|data.mycompany.com|*.mycompanyserver.combr .

Troubleshoot certificate validation error received during connector run

Fix the validation issue if an on-premises agent connector encounters the following error:

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, the Datalink (Classic) service was unable to establish root certificate authority (CA) trust for that certificate from the java key store

  1. Download (or export to a file) the certificate being served.
  2. Navigate to your Datalink (Classic) installation folder.
  3. Run the following command to import the certificate file to dlagent.jks:

    keytool -import -alias <pickAnUniqueAliasNameForCertificate> -keystore <pathTo_dlagent.jks_fileWhereCertNeedsToBeImported> -file <cerficateFileToBeImported.crt> .

  4. Verify the certificate is added to the keystore by running the following command:

    keytool -list -v -keystore <pathTo_dlagent.jks_file> -alias <exampleAlias> .

  5. Restart the Datalink (Classic) Agent.
Note:

When you update your on-premises agent, the new version will overwrite the dlagent.jks file. To avoid this error, you must create a backup of this file and replace any new version with the backup after install.

Next, Register the agent .