---
title: Applying changes using dsjavaproperties
description: To apply the changes to the config/java.properties file, edit the file manually, and then run the bin/dsjavaproperties utility.
component: pingdirectory
version: 11.0
page_id: pingdirectory:pingdirectory_server_administration_guide:pd_ds_apply_changes_using_dsjavaproperties
canonical_url: https://docs.pingidentity.com/pingdirectory/11.0/pingdirectory_server_administration_guide/pd_ds_apply_changes_using_dsjavaproperties.html
revdate: September 13, 2023
page_aliases: ["pd_ds_update_java_version_properties_file.adoc", "pd_ds_regenerate_java_properties_file.adoc"]
section_ids:
  updating-the-java-version-in-the-properties-file: Updating the Java version in the properties file
  about-this-task: About this task
  steps: Steps
  example: Example:
  regenerating-the-java-properties-file: Regenerating the Java properties file
  about-this-task-2: About this task
  steps-2: Steps
  example-2: Example:
---

# Applying changes using dsjavaproperties

To apply the changes to the `config/java.properties` file, edit the file manually, and then run the `bin/dsjavaproperties` utility.

The `dsjavaproperties` utility uses the information contained in the `config/java.properties` file to generate a `lib/set-java-home` script, or `lib\set-java-home.bat` on Microsoft Windows systems, which is used by the PingDirectory server and all of its supporting tools to identify the Java environment and its JVM settings. During the process, `dsjavaproperties` calculates an MD5 digest of the contents of the `config/java.properties` file and stores the digest in the generated `set-java-home` script.

The `dsjavaproperties` utility also performs some minimal validation whenever the property references a valid Java installation by verifying that `$(java-home)/bin/java` exists and is executable.

If you make any changes to the `config/java.properties` file but forget to run `bin/dsjavaproperties`, the PingDirectory server compares the MD5 digest with the version stored in `set-java-home` and sends the following message to standard error if the digests differ:

```
WARNING -- File /ds/{pingdir}/config/java.properties has been edited without
running dsjavaproperties to apply the changes
```

## Updating the Java version in the properties file

To change the version of Java that is used by the server and tools, edit the `config/java.properties` file and apply the change by invoking `bin/dsjavaproperties` with no command line options.

### About this task

You must restart the PingDirectory server for the change to take affect.

### Steps

* Inside `config/java.properties`, alter the value of `default.java-home` to point to the Java correct Java Runtime Environment (JRE).

  Any time the `config/java.properties` file is updated, the `bin/dsjavaproperties` tool must be run to apply the new configuration.

  #### Example:

  ```shell
  $ bin/dsjavaproperties
  ```

## Regenerating the Java properties file

The `dsjavaproperties` command provides an `--initialize` option that allows you to regenerate the Java properties file specifically if you set up the PingDirectory server using standard memory usage but opt for aggressive memory tuning after setup.

### About this task

Rather than reconfigure the Java properties file by re-running `setup` or manually editing the `java.properties` file, you can regenerate the properties file for aggressive memory tuning. Any existing file is renamed with a `.old` suffix.

### Steps

* Run the `dsjavaproperties` command to regenerate the java properties file for aggressive memory tuning.

  #### Example:

  ```shell
  $ bin/dsjavaproperties --initialize --jvmTuningParameter AGGRESSIVE
  ```