Deployment overview for endpoints and certificates

Edit online

Plan the endpoint domain, tenant name, group name, and certificate configuration that is used to access DataPower Interact Gateway platform components.

Deployment identifiers

Before you deploy DataPower Interact Gateway, determine the following deployment identifiers.
  • Endpoint domain
  • Tenant name
  • Group name

Endpoint domain

The endpoint domain is the base domain that clients use to access the DataPower Interact Gateway platform. The platform operators use this domain to create the endpoints for each IDIG platform component by combining the endpoint prefix with the defined endpoint domain name. For details on setting the endpoint domain, see, Deploying IDIG cluster.

Table 1. Endpoints
Components Endpoint prefix Description Certificates
DataPower Interact Gateway (IDIG) idig Endpoint URL for IDIG UI and API connectivity. idig
Developer Portal devportal Developer Portal web site URL to access Developer Portal publicly. devportal-web
Analytics ai The analytics-ingestion endpoint is used by DataPower® Nano Gateway to push data to the Analytics component. Requires a TLS profile configured with mutual TLS. mutual TLS
DataPower Nano Gateway *.nanogw This is the endpoint DataPower Nano Gateway uses for network communication. mutual TLS

If ENDPOINT_DOMAIN is set to example.com, the endpoints for the IDIG platform components are created as:

  • IDIG platform: idig.example.com
  • Developer Portal: devportal.example.com
  • Analytics: ai.example.com
  • DataPower Nano Gateway: *.nanogw.example.com

Tenant name

DataPower Interact Gateway is a single-tenant platform. The tenant name identifies the DataPower Interact Gateway environment and is configured during deployment. Each IDIG deployment supports one tenant.

Group name

The group name identifies the gateway group within the tenant. The group name is used when publishing AI assets and is included in the DataPower Nano Gateway endpoint URLs.

Customizing TLS certificates

DataPower Interact Gateway uses TLS certificates to secure communication between platform components and external clients. By default, cert-manager generates and manages certificates for all user-facing endpoints. If your organization requires custom certificates, plan the certificates before deployment. For details, see: