---
title: PingOne Advanced Identity Cloud guide
description: This guide is for customers using an agent-based integration model, with AM on-premise, or another on-premise access management solution. The guide provides an example of how to transition from on-premise access management to Advanced Identity Cloud without changing the architecture of the agent-based model.
component: java-agents
version: 2025.11
page_id: java-agents:identity-cloud-guide:preface
canonical_url: https://docs.pingidentity.com/java-agents/2025.11/identity-cloud-guide/preface.html
page_aliases: ["index.adoc"]
section_ids:
  preface-examples: Example installation for this guide
---

# PingOne Advanced Identity Cloud guide

This guide is for customers using an agent-based integration model, with AM on-premise, or another on-premise access management solution. The guide provides an example of how to transition from on-premise access management to Advanced Identity Cloud without changing the architecture of the agent-based model.

Advanced Identity Cloud is described in the [PingOne Advanced Identity Cloud Docs](https://docs.pingidentity.com/pingoneaic/latest/home.html).

## Example installation for this guide

Unless otherwise stated, the examples in this guide assume the following installation:

* Java Agent installed on `https://agent.example.com:443/app`, in the `alpha` realm.

* An Advanced Identity Cloud tenant with the default configuration, as described in the [PingOne Advanced Identity Cloud documentation](https://docs.pingidentity.com/pingoneaic/latest/home.html).

When using Advanced Identity Cloud, you need to know the value of the following properties:

* The URL of your Advanced Identity Cloud tenant. For example, `https://tenant.forgeblocks.com`.

  The URL of the AM component of Advanced Identity Cloud is the root URL of your Advanced Identity Cloud tenant followed by `/am`. For example, `https://tenant.forgeblocks.com/am`.

* The realm where you work. The examples in this guide use `alpha`.

  Prefix each realm in the hierarchy with the `realms` keyword. For example, `/realms/root/realms/alpha`.

If you use a different configuration, substitute in the procedures accordingly.