From 02d33cf682be45c09b43e90cc4d1e31832c1e1f2 Mon Sep 17 00:00:00 2001 From: sj895092 Date: Wed, 18 Dec 2024 16:48:41 +0100 Subject: [PATCH] refactor --- docs/user-guide/api-mediation/api-mediation-multi-tenancy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md b/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md index f99064b86f..0388e73c70 100644 --- a/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md +++ b/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md @@ -30,7 +30,7 @@ The following diagram illustrates communication between the API Mediation Layers ![Multi-domain architecture diagram](./diagrams/multi-domain_architecture_V2.svg) - As represented in the example diagram of Multitenacy environement where the APIMLs in Domain(2-N) are registered to APIML in Domain-1. The APIML in Domain-1 is running may be on z/OS, or off z/OS, for example in Kubernetes, this API ML serves as a single point of access to all API Mediation Layers registered in this and, by extension, to all services registered in those API MLs . + As represented in the example diagram of Multitenacy environement where the APIMLs in Domain(2-N) are registered to APIML in Domain-1. The APIML in Domain-1 is running may be on z/OS, or off z/OS, for example in Kubernetes, this API ML serves as a single point of access to all API Mediation Layers registered in this and, by extension, to all services registered in those API MLs . The APIMLs in Domain(2-N) are installled on z/OS systems with the standard Zowe API ML running either in HA (sysplex) or non-HA (monoplex). These API MLs are registered to APIML in Domain-1. @@ -76,7 +76,7 @@ Set the `certificatesUrl` property to ensure that only Gateway-forwarded certif ``` components.gateway.apiml.security.x509: - # gateway port + # gateway port in domain-1 certificatesUrl: https://{gatewayHost}:{gatewayPort}/gateway/certificates ```