---
title: Deploying the sample configuration archive
description: The data.zip archive configures a PingFederate to work with the sample applications.
component: java
page_id: java:setup:pf_java_ik_deploying_the_sample_configuration_archive
canonical_url: https://docs.pingidentity.com/integrations/java/setup/pf_java_ik_deploying_the_sample_configuration_archive.html
revdate: June 21, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
  result: Result:
---

# Deploying the sample configuration archive

The `data.zip` archive configures a PingFederate to work with the sample applications.

## About this task

In this configuration, a single instance of PingFederate serves both the identity provider (IdP) and service provider (SP) roles by sending messages to and from itself. Although this is a valid scenario for demonstration and testing, it is not applicable to a real situation.

For a more realistic test, you can deploy the configurations into instances of PingFederate running on different hosts and then make necessary configuration updates manually as shown in [Advanced installation and configuration](pf_java_ik_advanced_installation_and_configuration.html).

|   |                                                                                                                                                                                                         |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Deploying `data.zip` overwrites your entire PingFederate configuration. If you have configured adapters, data stores, partner connections, or any other settings, back up your configuration in step 2. |

## Steps

1. Start PingFederate.

2. Back up your current PingFederate configuration as shown in [Configuration archive](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_configurationarchivetasklet_selectimportexportstate.html) in the PingFederate documentation.

3. From the Java Integration Kit `.zip` archive, copy the `sample/data.zip` archive to `<pf_install>/pingfederate/server/default/data/drop-in-deployer/`.

   ### Result:

   PingFederate adopts the new configuration and renames the `data.zip` file with a time stamp.