Note that this is a preproduction feature that is available to preproduction Tenants.
The Platform Internal Information Point Service is part of the Platform. It serves Platform Assets and Agent Identities from the Platform's internal data store at higher volume and speed than the original PIP.
The Platform Internal Information Point Service guide is divided into the following sections:
- Platform Assets and Platform Legacy Assets
- How Platform Assets served by the Platform Internal Information Point Service relate to Platform Legacy Assets, and where each can be resolved at runtime.
- Deploying the Platform Internal Information Point Service
- How the Platform Internal Information Point Service runs in Cloud PDP, and how to add it as an optional service in your PAA.
- HTTPS
- How to secure the connection to the Platform Internal Information Point Service, for Cloud PDP and for your PAA.
- Authenticating the Platform Internal Information Point Service
- How the Platform Internal Information Point Service authenticates to the Platform, including Client Key setup for PAA.
Overview
The Platform Internal Information Point Service connects to the Platform's internal data store so Platform Assets and Agent Identities can be resolved quickly at runtime, including under high query volume.
The Platform Internal Information Point Service currently serves two object types: Platform Assets and Agent Identities. Existing PIP Data Sources, Views, and JDBC-based Adapters are unaffected. You continue to manage those separately, as described in the PIP documentation.
The Platform Internal Information Point Service runs in the Cloud PDP by default. You can also deploy it as an optional service in your PAA, which lets the PDP running in your PAA resolve Platform Assets and Agent Identities locally instead of relying on Cloud PDP for those decisions.
Platform Assets and Platform Legacy Assets
Assets served by the Platform Internal Information Point Service are Platform Assets. Assets built the original way, before the Platform Internal Information Point Service, are Platform Legacy Assets. Both are managed as Assets in the Platform. Which one you have determines where it can be resolved at runtime.
| Platform Legacy Assets | Platform Assets | |
|---|---|---|
| Resolved via Cloud PDP | Yes | Yes |
| Resolved via PDP in PAA | No | Yes, when the Platform Internal Information Point Service is deployed in your PAA |
If you are using Internal Assets and want to use them with the new capability, with the Platform Internal Information Point Service on your PAA, create a new Asset Type and rebuild your Assets.
For the general steps to create and configure Asset Types and Assets, see Asset Type Settings.
Deploying the Platform Internal Information Point Service
Cloud PDP
Cloud PDP includes the Platform Internal Information Point Service out of the box.
PAA
You can add the Platform Internal Information Point Service as an optional service in your PAA bundle. When you deploy it:
- It runs in a redundant, scalable configuration for availability.
- It uses the Redis instance already deployed with your PAA.
- It preconfigures Platform Assets and Agent Identities out of the box, including the associated Tenant and Environment information.
- The PDP in your PAA waits until the Platform Internal Information Point Service finishes loading its Data Sources, and its cache where you've configured one, before it starts serving requests through the service.
HTTPS
The Platform Internal Information Point Service connects to the Platform's internal data store, and, when deployed in your PAA, to the PDP that consumes it. How you secure that connection depends on where the service runs:
- Cloud PDP terminates TLS for you. You don't need to set anything up.
- PAA lets you enable native HTTPS the same way you enable it for the rest of your PAA services.
To enable HTTPS for the Platform Internal Information Point Service in your PAA:
- Kubernetes: set
pip2.ssl.enabled: truein your Helm values. - ECS: set
enable_https = truein yourterraform.tfvars, the same pack-wide flag you use for the rest of your PAA. - Standalone: set
export PLAINID_TLS_ENABLED=truebefore runningstart_plainid_paa.
See Enabling HTTPS for PAA Services for how certificates are generated or supplied, and what this setting does and doesn't cover.
Authenticating the Platform Internal Information Point Service
The Platform Internal Information Point Service authenticates to the Platform before it can resolve Platform Assets and Agent Identities, including the Client Key setup for PAA and the network configuration your Tenant needs to allow.
See Platform Internal Information Point Authentication for details.