Multiple Gateways
Overview
A namespace in Cantara can contain multiple gateways. Each gateway provides a secure connection between the Cantara Administration Console and your JD Edwards environment, and may have distinct configuration, access policies, and target systems.
Having multiple gateways allows organisations to isolate environments, separate integrations, and apply granular access control policies per gateway without affecting other connections.
Why Use Multiple Gateways
Multiple gateways can be used to:
-
Separate environments – e.g., production vs. development vs. UAT.
-
Isolate middleware or integration flows – e.g., dedicated gateway for automated service requests.
-
Apply distinct access controls – each gateway can have its own set of permitted services, roles, and groups.
-
Enhance security and monitoring – administrators can manage traffic and troubleshoot issues per gateway.
Administration Considerations
-
Monitoring: Each gateway should be monitored independently to ensure connections to JD Edwards are active and functioning as expected.
-
Certificates: Gateways have their own certificates for secure communication; ensure each gateway’s certificate is valid and up-to-date.
-
Access Control: Access permissions can differ per gateway. Review role and group assignments when configuring multiple gateways.
-
Naming Conventions: Use descriptive gateway names to clearly indicate their environment or purpose.
Key Points
-
Multiple gateways do not share configuration; changes in one gateway do not affect others.
-
A single namespace can host several gateways, but each gateway must belong to exactly one namespace.
-
Use multiple gateways strategically to maintain operational clarity, security, and auditability.