Administration Guide | Rinami Knowledge Garden

Purpose

This guide provides the primary administration and configuration reference for the Cantara Administration Console. It explains how administrators configure, manage, monitor, and maintain Cantara environments after access has been provisioned.

Use the Get Started Guide for first-time onboarding, tenant access, prerequisites, and the initial quickstart path. Use this Administration Guide for the complete configuration and operational guidance for Cantara features and integrations.

Scope

This guide covers administration and configuration of the Cantara Administration Console, including:

Console navigation and usage
Configuration and management of core entities such as Namespaces, Gateways, Environments, Applications, and related Components
Identity, access, token, certificate, and integration administration
Operational monitoring, logging, troubleshooting, and routine maintenance tasks

Intended Audience

This guide is intended for administrators responsible for configuring and operating Cantara in an enterprise environment. Users are expected to have familiarity with enterprise administration and access management concepts, including:

Identity Provider (IdP) systems
SCIM provisioning standards
Oracle JD Edwards (JDE)
Single Sign-On (SSO) concepts and enterprise authentication flows

While integration with IdP and SCIM is commonly used, the Cantara Administration Console also supports manual account configuration where required. This guide assumes a working knowledge of these systems and does not provide introductory material for them.

Access Requirements

Access to the Cantara Administration Console requires valid credentials and appropriate role-based permissions. Available functionality may vary depending on assigned administrative roles.

How Cantara Fits Together

Use the sections below to understand how the main parts of Cantara relate to each other and how they are typically configured, managed, and monitored.

Core Entities

Area	Role in Cantara
Namespaces	The top-level logical partition that isolates configuration, security, users, and agent signing keys.
Cantara Agent	Connects Cantara to internal or hybrid JDE environments and uses namespace-managed signing keys for secure communication.
User Tokens	Manages namespace-scoped user access tokens used for authenticated administration and integration activity.
Components	The console section used to configure integration assets, including Certificates, Gateways, Environments, Applications, MCP Servers, Functions, Queries, Reports, Orchestrations, and Import/Export.
Applications	Configured within the Components section to package services, link them to an environment, and expose them to client systems.
Performance	Tracks response times, throughput, and operational behaviour to help identify bottlenecks or degraded integrations.
Logging	Records transaction history, user sessions, and debug payloads for verification and troubleshooting.

Integration Configuration Lifecycle

For each new Cantara integration, configure the required objects in the following sequence. This is the standard integration lifecycle, not a separate setup guide:

Step 1: Network and Access — Set up Certificates and Gateways.
Step 2: JDE Connection — Create an Environment and choose API Key or SSO/JWT authentication.
Step 3: Define Services — Build or import Queries, Orchestrations, Functions, and Reports in Components.
Step 4: Package and Expose — Group services under an Application and issue client credentials.
Step 5: Verify and Monitor — Check Logging and Performance views to confirm payloads, transactions, and runtime behaviour.