---
title: Deploying the integration files
description: To get started with the integration, deploy the Magic Link Integration Kit files to your PingFederate directory.
component: pingone
page_id: pingone:magic_link_integration_kit:pf_magic_link_ik_deploying_the_integration_files
canonical_url: https://docs.pingidentity.com/integrations/pingone/magic_link_integration_kit/pf_magic_link_ik_deploying_the_integration_files.html
revdate: June 10, 2024
section_ids:
  steps: Steps
---

# Deploying the integration files

To get started with the integration, deploy the Magic Link Integration Kit files to your PingFederate directory.

## Steps

1. Download the Magic Link Integration Kit `.zip` archive from the [**Add-ons** tab of the PingFederate downloads page](https://www.pingidentity.com/en/resources/downloads/pingfederate.html) or the [Ping Identity Marketplace](https://marketplace.pingone.com/item/magic-link-integration-kit).

2. Stop PingFederate.

3. If you're upgrading from a previous deployment, do the following:

   1. Back up any Magic Link Integration Kit files that you've customized in the `<pf_install>/pingfederate/server/default/conf/` directory.

   2. Delete the `pf-magic-link-adapter-<version>.jar` file from the `<pf_install>/pingfederate/server/default/deploy` directory.

   3. Delete the `pf-authn-api-sdk-<version>.jar` file from the `<pf_install>/pingfederate/server/default/lib` directory if it's older than the version in the integration files.

4. Extract the `.zip` archive and merge the contents of the `dist` directory with your `<pf_install>/pingfederate/server/default/deploy` directory.

5. To use the SMTP Notification Publisher, merge the contents of the `pingfederate-smtp-magiclink-messages.properties` file into the `<pf_install>/pingfederate/server/default/conf/language-packs/pingfederate-email-messages.properties` file.

6. If you backed up any templates or messages from a previous deployment, modify the new files with your customizations.

7. Start PingFederate.

8. If you operate PingFederate in a cluster, repeat steps 2 - 7 for each engine node.
