--- title: Installing PingAccess on your system description: Install PingAccess on Linux, on Windows through an installation wizard, or on Windows through the command-line interface (CLI). component: pingaccess version: 9.0 page_id: pingaccess:installing_and_uninstalling_pingaccess:pa_installing_pa_on_your_system canonical_url: https://docs.pingidentity.com/pingaccess/9.0/installing_and_uninstalling_pingaccess/pa_installing_pa_on_your_system.html revdate: May 6, 2024 section_ids: before-you-begin: Before you begin installing-pingaccess-on-linux: Installing PingAccess on Linux about-this-task: About this task steps: Steps next-steps: Next steps installing-pingaccess-on-windows-using-the-installer: Installing PingAccess on Windows using the installer about-this-task-2: About this task steps-2: Steps next-steps-2: Next steps installing-pingaccess-on-windows-from-the-command-line: Installing PingAccess on Windows from the command line about-this-task-3: About this task steps-3: Steps next-steps-3: Next steps --- # Installing PingAccess on your system Install PingAccess on Linux, on Windows through an installation wizard, or on Windows through the command-line interface (CLI). ## Before you begin * Ensure you've met the [installation requirements](pa_installation_requirements.html). * Ensure you're signed on to your system with appropriate privileges to install and run an application. | | | | - | -------------------------------------------------------- | | | On Linux, install and run PingAccess as a non-root user. | * Install a [supported Java runtime](pa_installation_requirements.html). * The system or user environment variable `JAVA_HOME` must exist and be set to a value that represents the location of your Java installation, such as `usr/java/jdk 1.8.0_74`. * Add the relevant Java directory path to the `PATH` variable so it's available for scripts that depend on it: * On Linux: Add the Java Runtime Environment (JRE) *(tooltip: \
\

A software layer that provides the class libraries and resources needed for a Java program to run.\

\
)* `/bin` directory path (for example, `usr/lib64/jvm/jre/bin`). * On Windows installer: Add the `javapath` directory path (for example, `C:\Program Files\Oracle\Java\javapath`). * On Windows CLI: Add the `javapath` directory path (for example, `C:\Program Files\Oracle\Java\javapath`). * You must have a `pingaccess.lic` license file. | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | | If you do not have a PingAccess license, you can request an evaluation key at . During the first run of PingAccess, you will be prompted to upload the license file.If you are using an existing configuration file to configure the system, copy the configuration file to the system and rename it `data.json`. For more information about exporting the configuration from an existing system, see [Exporting PingAccess configurations](../pingaccess_user_interface_reference_guide/pa_exporting_pa_configs.html). | - Linux - Windows installer - Windows CLI ## Installing PingAccess on Linux ### About this task To install PingAccess on a Linux system: ### Steps 1. Download the distribution `.zip` archive from the [PingAccess downloads page](https://www.pingidentity.com/en/resources/downloads/pingaccess.html). 2. Extract the distribution `.zip` archive into your installation directory. 3. **Optional:** If you are using an existing configuration file to configure the system, move the `data.json` file to the `/data/start-up-deployer` directory. | | | | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | When you start PingAccess for the first time, if this configuration is present it will be imported. After a successful import, the `data.json` file is deleted. If the configuration is present but cannot be imported, PingAccess is not started. | | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | | If you're deploying PingAccess in a cluster configuration, see the [configuration documentation](../reference_guides/pa_configuring_a_pa_cluster.html). | ### Next steps [Access the administrative console to complete the configuration](pa_accessing_the_admin_console.html). ## Installing PingAccess on Windows using the installer ### About this task To install PingAccess on a Windows system using the installer: ### Steps 1. Download the PingAccess Windows installer from the [PingAccess downloads page](https://www.pingidentity.com/en/resources/downloads/pingaccess.html). 2. Double-click on the installer icon to launch the PingAccess setup wizard. 3. Click **Next** and follow the prompts to complete the installation using the following information for your selected operational mode. | Operational Mode | Requirements | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Standalone | Ports:- PingAccess administrative console: TCP 9000 - PingAccess agent protocol: TCP 3030 | | Clustered admin node | Ports:- PingAccess administrative console: TCP 9000 - Configuration query port: TCP 9090 | | Clustered replica admin node | Ports:- PingAccess administrative console: TCP 9000 - Configuration query port: TCP 9090Prerequisites:- You must install and configure a clustered admin node. - You must have a configuration data archive file available for the replica admin node. For more information, see [Clustering in PingAccess](../reference_guides/pa_clustering_ref_guide.html) in *Reference Guides*. Install the clustered replica admin node on a separate machine in the same network. | | Clustered engine node | Ports:- PingAccess agent protocol: TCP 3030Prerequisites:- You must install a clustered admin node. - You must have a configuration data archive file available for the clustered engine node. For more information, see [Clustering in PingAccess](../reference_guides/pa_clustering_ref_guide.html) in *Reference Guides*. | 4. Copy the Uniform Resource Locator (URL) *(tooltip: \
\

Identifies a resource according to its internet location.\

\
)* of the PingAccess administrative console that is displayed on the final page of the PingAccess setup wizard, then click **Finish**. 5. To customize and finalize the PingAccess setup, paste the URL you copied into your web browser and connect to the administrative console of the instance you have just installed. ### Next steps [Access the administrative console to complete the configuration](pa_accessing_the_admin_console.html). ## Installing PingAccess on Windows from the command line ### About this task To install PingAccess on a Windows system from the CLI: ### Steps 1. Download the distribution `.zip` archive. 2. Extract the distribution `.zip` archive into your installation directory. 3. **Optional:** If you are using an existing configuration file to configure the system, move the `data.json` file to the `/data/start-up-deployer` directory. | | | | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | When you start PingAccess for the first time, if this configuration is present it will be imported. After a successful import, the `data.json` file is deleted. If the configuration is present but cannot be imported, PingAccess is not started. | ### Next steps [Access the administrative console to complete the configuration](pa_accessing_the_admin_console.html).