---
title: Deploying the integration files
description: If you operate PingFederate in a cluster, the following steps refer to the console node.
component: sdg
page_id: sdg:sdg_cts_token_translator:pf_sdg_cts_tt_deploying_integration_files
canonical_url: https://docs.pingidentity.com/integrations/sdg/sdg_cts_token_translator/pf_sdg_cts_tt_deploying_integration_files.html
llms_txt: https://docs.pingidentity.com/integrations/sdg/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: October 28, 2026
section_ids:
  steps: Steps
---

# Deploying the integration files

|   |                                                                                          |
| - | ---------------------------------------------------------------------------------------- |
|   | If you operate PingFederate in a cluster, the following steps refer to the console node. |

## Steps

1. Download the SDG CTS Token Translator `.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/coreblox-token-translator).

2. Stop PingFederate, if it's running.

3. If you're upgrading an existing deployment, delete any existing SDG CTS Token Translator files (`coreblox-token-translator-*.jar`) from the `<pf_install>/PingFederate/server/default/deploy` directory.

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

5. Start the PingFederate server.

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