Introduction to Namespaces | Rinami Knowledge Garden

Overview

Once a tenant has been created and initial setup such as user accounts and Identity Provider (IdP) configuration is complete, the next required step is to create a namespace.

A namespace exists within a tenant and is used to group and isolate configuration in Cantara. Most tenants start with a single namespace. Larger deployments may use multiple namespaces to separate environments such as development, staging, and production.

What Does a Namespace Contain?

A namespace acts as the boundary for all configuration within your Cantara environment. Inside a namespace, you will set up and manage:

Gateways — Connections between Cantara and your JD Edwards environments.
Configuration and Logs — All system configuration and operational logs are scoped to the namespace they belong to.

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

Explore This Section

Configure Your First Namespace

How Namespaces Fit into the Architecture

Cantara follows a hierarchical structure:

A Tenant is your top-level environment in Cantara.
A Namespace sits within a tenant and isolates configuration for a specific purpose (e.g., a development or production environment).
A Gateway is created within a namespace and handles the connection to your JD Edwards environment.

This hierarchy means that each gateway belongs to exactly one namespace, and each namespace belongs to exactly one tenant. Configuration in one namespace does not affect another, providing clean separation between environments.

A namespace is required before you can create a gateway, as gateways are created within a namespace to connect Cantara to JD Edwards.

Note: Creating a namespace is a mandatory prerequisite before continuing with further setup.

What’s next?

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