Skip to content
Build 9234610

Endpoint & Environment Map

What every environment points to for the systems Camel talks to — OMS, NAV, Cirro, PrintStation, and Camel's own internal services. One place to answer "what host does stage hit for that?"

Source & freshness

This is a point-in-time snapshot, generated 2026-07-06 live from the Config Server — it is not auto-updated.

  • nonprod (dev / qa / stage) was read from the live nonprod Config Server table spring_cloud_service_nonprod.properties.
  • prod was read from the prod Config Server — https://camelconfigserver.corp.popsockets.com/config/<app>/prod (backed by spring_cloud_service_prod) — not the prod-profile rows in the nonprod table, which are stale mirrors (see anomalies).
  • Secrets (tokens, passwords, Service Bus connection strings, app keys) are redacted — they live in Key Vault, never here.

The Config Server is the source of truth. If a value here looks wrong, re-read it live rather than trusting this page.

Environments at a glance

Every service resolves its config from the Config Server for its profile. The cluster, namespace, and API gateway per environment:

dev qa stage prod
AKS cluster int-usw-aks-1 int-usw-aks-1 int-usw-aks-1 int-usw-aks-2
K8s namespace int-dev int-qa int-stage int-prod
Camel APIM base integration-nonprod.popsockets.com/dev integration-nonprod.popsockets.com/qa integration-nonprod.popsockets.com/stage integration-prod.popsockets.com/prod
Config Server camelconfigserver-np.corp.popsockets.com ← ← camelconfigserver.corp.popsockets.com

By system

  • OMS

    Camel → OMS: order sync, fulfillment confirms, NAV-release status acks, PrintStation batches, Gladly. One caller (cm-osor-sys). Hosts run sandbox → prod.

    OMS endpoints →

  • NAV

    Camel → NAV Business Central: packaging-instructions SOAP + page services, and the inbound NAV order-release queue. Each env is a distinct NAV instance.

    NAV endpoints →

  • Cirro / eLogistic

    Camel → Cirro 3PL: order create, prepack plan-orders, auth. Plus per-env warehouse/shipping-method mappings and the inbound Cirro confirmation webhooks.

    Cirro endpoints →

  • Camel internal (APIM)

    Service-to-service calls between cm-* apps, all routed through the APIM gateway: integration-{np|prod}.popsockets.com/{env}/cm-<service>/<path>.

    Internal routes →

  • PrintStation

    Camel → PrintStation / Batch APIs (cm-printprod-sys), REST, no Service Bus. Staging (-s) vs go-live (-g) infra. Nonprod-only today.

    PrintStation endpoints →

Notes & anomalies

Don't read prod from the nonprod Config Server table

The nonprod table spring_cloud_service_nonprod also contains prod-profile rows, but they are stale mirrors and are not what prod actually serves. Always read prod from the prod Config Server.

Proof of divergence: the nonprod-table said prod cirro.shipping-method = Mapping_Transfer; the live prod Config Server serves PPS_PENDING_ROUTING.

Two more gaps worth knowing

  • nav.page.base-url is unset in prod — NAV item-sync (NavPageSoapClient) is a nonprod-only path. See NAV.
  • cm-printprod-sys has no prod profile in the Config Server — PrintStation-via-Camel is nonprod-only today; confirm whether PrintStation prod runs outside Camel. See PrintStation.

How to regenerate

This page is a snapshot. To refresh a value against the live Config Server:

  • nonprod — query the nonprod Config Server: https://camelconfigserver-np.corp.popsockets.com/config/<app>/<profile> (e.g. /config/cm-cirro-sys/dev).
  • prod — query the prod Config Server: https://camelconfigserver.corp.popsockets.com/config/<app>/prod.

The response is the fully-resolved property set for that app+profile, with Key Vault secrets already substituted. Diff against the tables here and update if they've drifted.

Related: Camel topology · EDI B2B pipeline · OMS