Namespace Setup

Overview

A namespace is a container within a tenant that organises and isolates configuration in Cantara. It defines the boundary for gateways, system configuration, and operational logs, so each environment can be managed separately.

After you register a tenant and configure user access, creating a namespace is the next step before setting up a gateway.

Namespaces let you separate configuration by purpose, environment, or location. For example, you might create separate namespaces for development and production, or place a namespace in a region that is closer to the systems or users it supports.

A namespace can be hosted in a different region from its tenant, depending on where you want that namespace to operate. The namespace still belongs to the same tenant, but its regional placement can be chosen to support performance, data residency, or operational requirements.

Explore This Section

• Configure a Namespace

What Does a Namespace Contain?

• A namespace is the boundary for operational configuration within your Cantara environment. Inside a namespace, you set up and manage:

  • Gateways — Connections between Cantara and your JD Edwards environments. A gateway cannot be created until a namespace exists.

  • Configuration and Logs — All system configuration and operational logs are scoped to the namespace they belong to.

  A namespace does not store customer business data. It contains only the configuration and logs needed to operate the platform.

Before you begin

• You have registered a tenant. See Register a Tenant.

• You have configured user access. See User Access.

How Namespaces Fit into the Architecture

Cantara uses the following hierarchy:

• Tenant — Your top-level environment in Cantara.

• Namespace — Sits within a tenant and isolates configuration for a specific purpose, environment, or region.

• Gateway — Created within a namespace and handles the connection to your JD Edwards environment.

Each gateway belongs to one namespace, and each namespace belongs to one tenant. However, a namespace does not need to be hosted in the same region as the tenant. You can choose the region that best suits the namespace, while keeping it managed under the tenant. Configuration in one namespace does not affect another, which provides clean separation between environments.

What's next?

Once your namespace is set up, it becomes the foundation for everything that follows. Gateways, agent configuration, access control, and logs are all scoped to a namespace.

For details on how to create a namespace, see Configure a Namespace.