installing.html.md.erb

---
title: Installing and Configuring Dynatrace Full-Stack Add-on for PCF
owner: Partners
---

This topic explains how to install and configure the Dynatrace Full-Stack Add-on for Pivotal Cloud Foundry (PCF).


## <a id='create-mfest'></a> Create the Dynatrace Manifest

Follow these steps to create the Dynatrace manifest for your deployment:

1. Create a Dynatrace manifest file called `runtime-config-dynatrace.yml`, using the code below as a template to get started.
<pre>releases:
  \- {name: dynatrace-oneagent, <strong>version</strong>: 1.0.4}<br>  
  addons:
  \- name: dynatrace-oneagent-addon
    jobs:
    \- <strong>name</strong>: dynatrace-oneagent
      release: dynatrace-oneagent
    include:
      stemcell:
      \- <strong>os</strong>: ubuntu-trusty
      \- <strong>os</strong>: ubuntu-xenial
    exclude:
      lifecycle: errand
      jobs:
      - {name: smoke-tests, release: cf}
      - {name: push-apps-manager, release: push-apps-manager-release}
      - {name: deploy-notifications, release: notifications}
      - {name: deploy-notifications-ui, release: notifications-ui}
      - {name: push-pivotal-account, release: pivotal-account}
      - {name: deploy-autoscaling, release: cf-autoscaling}
      - {name: register-broker, release: cf-autoscaling}
      - {name: nfsbrokerpush, release: nfs-volume}
      - {name: bootstrap, release: cf-mysql}
      - {name: rejoin-unsafe, release: cf-mysql}
      - {name: broker-registrar, release: cf-mysql}
      - {name: deregister-and-purge-instances, release: cf-mysql}
      - {name: smoke-tests, release: cf-mysql}
      - {name: install-hwc-buildpack, release: hwc-buildpack}
    properties:
      dynatrace:
        <strong>environmentid</strong>: &lt;environmentid&gt;
        <strong>apitoken</strong>: &lt;token&gt;
        ###
        # optional properties below
        ###
        # Replace with your Dynatrace Managed URL, including the environment ID.
        # An example URL might look like the following
        <strong>apiurl</strong>: https://{your-managed-cluster.com}/e/{environmentid}/api
        # Set to 'all' if you want to accept all self-signed SSL certificates.
        sslmode: all
        # Specify a direct download URL for Dynatrace OneAgent.
        # If this propery is set, BOSH will download OneAgent from this location.
        downloadurl: https://direct-download-url-for-agent
        # Specify the proxy to be used for communication.
        proxy: https://your-proxy-url
        # Specify in which hostgroup the VMs in this deployments belong
        hostgroup: example_hostgroup
        # Define host tags for the VMs in this deployment
        hosttags: landscape=production team=my_team
        # Define custom properties for the VMs in this deployment
        hostprops: Department=Acceptance Stage=Sprint
        # Enable cloud infrastructure monitoring mode.
        # Set this to 1 to activate it
        infraonly: 0
        # Enable validation of the download via certificate
        # Set this to true to active it
        validatedownload: false<br>           
  \# optional: extra addon configuration for Windows cells
  \- name: dynatrace-oneagent-windows-addon
    jobs:
    - name: dynatrace-oneagent-windows
      release: dynatrace-oneagent
    include:
      stemcell:
      \- <strong>os</strong>: windows2012R2
    properties:
      dynatrace:
        <strong>environmentid</strong>: &lt;environmentid&gt;
        <strong>apitoken</strong>: &lt;token&gt;
        # All of the optional properties for the Linux addon shown above (for example, apiurl, hostgroup) can also be used here.
    </pre>

1. Replace the values listed in the template as follows:
  * `releases: - version`: Specify the version number of your Dynatrace Full-Stack Add-on for PCF download from Pivotal Network.
  * `jobs: - name`: Do not change the name of this job. It must be `dynatrace-oneagent` for Linux VMs.
  * `include: stemcell - os<`: Do not change the OS type.
  * `environmentid`: Replace with your Dynatrace environment ID.
  * `apitoken`: Replace with your PaaS token from the Dynatrace UI.
  * `apiurl`: Replace with your Dynatrace Managed URL, including the environment ID. An example URL might look like the following: `https://{your-managed-cluster.com}/e/{environmentid}/api`

1. (Optional) The add-on supports additional configuration properties:
  * `sslmode`: Set to `all` if you want to accept all self-signed SSL certificates.
  * `downloadurl`: Specify a direct download URL for Dynatrace OneAgent. If this propery is set, BOSH will download OneAgent from this location.
  * `proxy`: Specify the proxy to be used for communication.
  * `hostgroup`: Specify hostgroup for VMs in this deployment.
  * `hosttags`: Specify host tags for VMs in this deployment.
  * `hostprops`: Specify custom properties for VMs in this deployment.
  * `infraonly`: Set to `1` to enable cloud infrastructure monitoring mode. This disables all deep process monitoring.
  * `validatedownload`: Set to `true` to enable validation of the download via certificate.

1. If you also want to deploy Dynatrace to Windows Diego cells, configure a second add-on section for the `dynatrace-oneagent-windows` job. The properties for `environmentid`, `apitoken`, and `apiurl` remain the same as with the normal Linux configuration.
  * `jobs: - name`: For Windows cells, this must be `dynatrace-oneagent-windows`.
  * `include: stemcell - os`: For Windows cells, this must be `windows2012R2` and/or `windows2016`.

<p class="note"><strong>Note:</strong> To modify the configuration of an existing deployment, you must update the manifest file and redeploy.</p>


## <a id="download-deploy"></a> Download and Deploy the Dynatrace Full-Stack Add-on for PCF

After deploying Ops Manager, do the following to download and deploy the Dynatrace Full-Stack Add-on for PCF:

1. Download the Dynatrace Full-Stack Add-on for PCF software binary from [Pivotal Network](https://network.pivotal.io/products/dynatrace-fullstack-addon) to your local machine.

1. Copy the software binary to your Ops Manager instance.
<pre class="terminal">$ scp -i PATH/TO/PRIVATE/KEY dynatrace-release.tar.gz ubuntu@YOUR-OPS-MANAGER-VM-IP:</pre>

1. Copy the Dynatrace manifest file to your Ops Manager instance.
<pre class="terminal">$ scp -i PATH/TO/PRIVATE/KEY runtime-config-dynatrace.yml ubuntu@YOUR-OPS-MANAGER-VM-IP:</pre>

1. SSH into Ops Manager.
 <pre class="terminal">$ ssh -i PATH-TO-PRIVATE-KEY ubuntu@YOUR-OPS-MANAGER-VM-IP</pre>

1. On the Ops Manager VM, navigate to the software binary location in your working directory.
<pre class="terminal">
$ cd PATH-TO-BINARY</pre>

1. Log in to the BOSH Director.
  * **For Ops Manager v1.11 or v1.12:**
  <ol type="i">
    <li>
      On the Ops Manager VM, create an alias in the BOSH CLI for your BOSH Director IP address. For example:
      <pre class="terminal">$ bosh2 alias-env my-env -e 10.0.16.10</pre>
    </li>
    <li>
      Log in to the BOSH Director, specifying the newly created alias. 
      For example:
      <pre class="terminal">$ bosh2 -e my-env log-in</pre>
    </li>
  </ol>
  * **For Ops Manager v2.0 or later:**
  <ol type="i">
    <li>
      On the Ops Manager VM, create an alias in the BOSH CLI for your BOSH Director IP address. For example:
      <pre class="terminal">$ bosh alias-env my-env -e 10.0.16.10</pre>
    </li>
    <li>
      Log in to the BOSH Director, specifying the newly created alias. 
      For example:
      <pre class="terminal">$ bosh -e my-env log-in</pre>
    </li>
  </ol>

1. Upload your release.
  * **For Ops Manager v1.11 or v1.12:**
  <pre class="terminal">$ bosh2 -e my-env upload-release PATH-TO-BINARY/dynatrace-release.tar.gz</pre>
  * **For Ops Manager v2.0 or later:**
  <pre class="terminal">$ bosh -e my-env upload-release PATH-TO-BINARY/dynatrace-release.tar.gz</pre>

1. (Optional) From the command line, you can confirm that upload of the Dynatrace software binary is complete. You should see the Dynatrace binary file.
  * **For Ops Manager v1.11 or v1.12:**
  <pre class="terminal">$ bosh2 -e my-env releases</pre>
  * **For Ops Manager v2.0 or later:**
  <pre class="terminal">$ bosh -e my-env releases</pre>

1. Update your runtime configuration to include the Dynatrace Add-on for PCF.
  <p class="note"><strong>Note</strong>: If you installed other BOSH add-ons, you must merge the Dynatrace manifest into your existing add-on manifest. Append the contents of <code>runtime-config-dynatrace.yml</code> to your existing add-on YML file.</p>
  * **For Ops Manager v1.11 or v1.12:**
  <pre class="terminal">$ bosh2 -e my-env update-runtime-config PATH/runtime-config-dynatrace.yml</pre>
  * **For Ops Manager v2.0 or later:**
  <pre class="terminal">$ bosh -e my-env update-runtime-config PATH/runtime-config-dynatrace.yml</pre>

1. Verify your runtime configuration changes match what you specified in the Dynatrace manifest file.
  * **For Ops Manager v1.11 or v1.12:**
  <pre class="terminal">$ bosh2 -e my-env runtime-config</pre>
  * **For Ops Manager v2.0 or later:**
  <pre class="terminal">$ bosh -e my-env runtime-config</pre>
    For example: 
    <pre class="terminal">
    Acting as user 'admin' on 'micro'

    releases:
    <span>-</span> {name: dynatrace-oneagent, version: 1.2.1}

    addons:
    <span>-</span> name: dynatrace-oneagent-addon
      jobs:
      <span>-</span> name: dynatrace-oneagent
        release: dynatrace-oneagent
    ...
    </pre>

1. Navigate to your **Installation Dashboard** in Ops Manager.

1. Click **Apply Changes**.