remove central gateway reference from the docs for v3

docs/troubleshoot/troubleshoot-apiml-error-codes.md

@@ -531,43 +531,43 @@ The following error message codes may appear on logs or API responses. Use the f
 
 ### ZWEAT500E
 
-  Failed to parse the client certificate forwarded from the central Gateway. Error message %s. The client certificate was %s
+  Failed to parse the client certificate forwarded from the Gateway. Hostname is %s. Error message is %s. The client certificate was %s
 
   **Reason:**
 
-  The string sent by the central Gateway was not recognized as a valid DER-encoded certificate in the Base64 printable form.
+  The string sent by the Gateway was not recognized as a valid DER-encoded certificate in the Base64 printable form.
 
   **Action:**
 
-  Ensure that forwarding of the client certificate is also enabled in the central Gateway. Check for any error messages from the central Gateway.
+  Ensure that forwarding of the client certificate is also enabled in the Gateway. Check for any error messages from the Gateway.
 
 ### ZWEAT501E
 
-  Failed to get trusted certificates from the central Gateway. Unexpected response from %s endpoint. Status code: %s. Response body: %s
+  Failed to get trusted certificates from the Gateway. Unexpected response from %s endpoint. Status code: %s. Response body: %s
 
   **Reason:**
 
   The response status code is different from the expected 200 OK.
 
   **Action:**
 
-  Ensure that the parameter apiml.security.x509.certificatesUrls is correctly configured with the complete URL to the central Gateway certificates endpoint. Test the URL manually.
+  Ensure that the parameter apiml.security.x509.certificatesUrls is correctly configured with the complete URL to the Gateway certificates endpoint. Test the URL manually.
 
 ### ZWEAT502E
 
-  Invalid URL specified to get trusted certificates from the central Gateway. Error message: %s
+  Invalid URL specified to get trusted certificates from the Gateway. URL is %s. Error message: %s
 
   **Reason:**
 
-  The parameter apiml.security.x509.certificatesUrls is not correctly configured with the complete URL to the central Gateway certificates endpoint.
+  The parameter apiml.security.x509.certificatesUrls is not correctly configured with the complete URL to the Gateway certificates endpoint.
 
   **Action:**
 
   Ensure that the parameter apiml.security.x509.certificatesUrls is correctly configured.
 
 ### ZWEAT503E
 
-  An error occurred during retrieval of trusted certificates from the central Gateway. Error message: %s
+  An error occurred during retrieval of trusted certificates from the Gateway. Certificate endpoint is %s. Error message: %s
 
   **Reason:**
 
@@ -579,28 +579,16 @@ The following error message codes may appear on logs or API responses. Use the f
 
 ### ZWEAT504E
 
-  Failed to parse the trusted certificates provided by the central Gateway. Error message %s
+  Failed to parse the trusted certificates provided by the Gateway. Certificate endpoint is %s. Error message %s
 
   **Reason:**
 
-  The string sent by the central Gateway was not recognized as valid DER-encoded certificates in the Base64 printable form.
+  The string sent by the Gateway was not recognized as valid DER-encoded certificates in the Base64 printable form.
 
   **Action:**
 
   Check that the URL configured in apiml.security.x509.certificatesUrls responds with valid DER-encoded certificates in the Base64 printable form.
 
-### ZWEAT505E
-
-  Incoming request certificate is not one of the trusted certificates provided by the central Gateway.
-
-  **Reason:**
-
-  The Gateway performs an additional check of request certificates when the central Gateway forwards the incoming client certificate to the domain Gateway. This check may fail when the certificatesUrl parameter does not point to the proper central Gateway certificates endpoint.
-
-  **Action:**
-
-  Check that the URL configured in apiml.security.x509.certificatesUrls points to the central Gateway and it responds with valid DER-encoded certificates in the Base64 printable form.
-
 ### ZWEAT601E
 
   z/OSMF service name not found. Set parameter apiml.security.auth.zosmf.serviceId to your service ID.

docs/user-guide/api-mediation/api-mediation-multi-tenancy.md

@@ -2,26 +2,27 @@
 
 Zowe supports management of multiple tenants, whereby different tenants can serve different purposes or different customers. The use case for multi-tenant support is when a service provider manages sysplexes/monoplexes for multiple customers. This configuration makes it possible to have a single access point for all customers, and properly route and authenticate across different domains.
 
-* [Overview of Central and Domain API MLs](#overview-of-central-and-domain-api-mls)
-* [Multitenancy component enablement settings](#multitenancy-component-enablement-settings)
-* [Onboarding a Domain Gateway service to the Central Discovery service](#onboarding-a-domain-gateway-service-to-the-central-discovery-service)
-    * [Dynamic configuration via zowe.yaml](#dynamic-configuration-via-zoweyaml)
-    * [Dynamic configuration via Environment variables](#dynamic-configuration-via-environment-variables)
-    * [Validating successful configuration](#validating-successful-configuration)
-* [Establishing a trust relationship between Domain API ML and Central API ML](#establishing-a-trust-relationship-between-domain-api-ml-and-central-api-ml)
-  * [Commands to establish trust between Domain and Central API MLs](#commands-to-establish-trust-between-domain-and-central-api-mls)
-* [Using the `/registry` endpoint in the Central Gateway](#using-the-registry-endpoint-in-the-central-gateway)
-  * [Configuration for `/registry`](#configuration-for-registry)
-  * [Authentication for `/registry`](#authentication-for-registry)
-  * [Authorization with `/registry`](#authorization-with-registry)
-  * [Requests with `/registry`](#requests-with-registry)
-  * [Response with `/registry`](#response-with-registry)
-  * [Response with `/registry{apimlId}`](#response-with-registryapimlid)
-  * [Response with `GET /gateway/api/v1/registry/{apimlId}?apiId={apiId}&serviceId={serviceId}`](#response-with-get-gatewayapiv1registryapimlidapiidapiidserviceidserviceid)
-* [Validating successful configuration with `/registry`](#validating-successful-configuration-with-registry)
-* [Troubleshooting multitenancy configuration](#troubleshooting-multitenancy-configuration)
-  * [ZWESG100W](#zwesg100w)
-  * [No debug messages similar to apiml1 completed with onComplete are produced](#no-debug-messages-similar-to-apiml1-completed-with-oncomplete-are-produced)
+- [Multitenancy Configuration](#multitenancy-configuration)
+  - [Overview of Central and Domain API MLs](#overview-of-central-and-domain-api-mls)
+  - [Multitenancy component enablement settings](#multitenancy-component-enablement-settings)
+  - [Onboarding a Domain Gateway service to the Discovery service in Central API ML](#onboarding-a-domain-gateway-service-to-the-discovery-service-in-central-api-ml)
+    - [Dynamic configuration via zowe.yaml](#dynamic-configuration-via-zoweyaml)
+    - [Dynamic configuration via Environment variables](#dynamic-configuration-via-environment-variables)
+    - [Validating successful configuration](#validating-successful-configuration)
+  - [Establishing a trust relationship between Domain API ML and Central API ML](#establishing-a-trust-relationship-between-domain-api-ml-and-central-api-ml)
+    - [Commands to establish trust between Domain and Central API MLs](#commands-to-establish-trust-between-domain-and-central-api-mls)
+  - [Using the `/registry` endpoint in the Gateway](#using-the-registry-endpoint-in-the-gateway)
+    - [Configuration for `/registry`](#configuration-for-registry)
+    - [Authentication for `/registry`](#authentication-for-registry)
+    - [Authorization with `/registry`](#authorization-with-registry)
+    - [Requests with `/registry`](#requests-with-registry)
+    - [Response with `/registry`](#response-with-registry)
+    - [Response with `/registry{apimlId}`](#response-with-registryapimlid)
+    - [Response with `GET /gateway/api/v1/registry/{apimlId}?apiId={apiId}&serviceId={serviceId}`](#response-with-get-gatewayapiv1registryapimlidapiidapiidserviceidserviceid)
+  - [Validating successful configuration with `/registry`](#validating-successful-configuration-with-registry)
+  - [Troubleshooting multitenancy configuration](#troubleshooting-multitenancy-configuration)
+    - [ZWESG100W](#zwesg100w)
+    - [No debug messages similar to apiml1 completed with onComplete are produced](#no-debug-messages-similar-to-apiml1-completed-with-oncomplete-are-produced)
 
 ## Overview of Central and Domain API MLs
 
@@ -38,7 +39,7 @@ Domain-1 to Domain-N are z/OS systems with the standard Zowe API ML running eith
 
 In the multitenancy environment, certain Zowe components may be enabled, while others may be disabled. The multitenancy environment expects one Central API ML that handles the discovery and registration as well as routing to the API ML installed in specific domains. 
 
-## Onboarding a Domain Gateway service to the Central Discovery service
+## Onboarding a Domain Gateway service to the Discovery service in Central API ML
 
 The Central API ML can onboard Gateways of all domains. This service onboarding can be achieved similar to additional registrations of the Gateway. This section describes the dynamic configuration of the yaml file and environment variables, and how to validate successful configuration.
 
@@ -47,7 +48,7 @@ The Central API ML can onboard Gateways of all domains. This service onboarding
 
 ### Dynamic configuration via zowe.yaml 
 
-1. Set the following property for the Domain Gateway to dynamically onboard to the Central Discovery service.
+1. Set the following property for the Domain Gateway to dynamically onboard to the  Discovery service in Central API ML.
 
     `components.gateway.apiml.service.additionalRegistration`
 
@@ -72,12 +73,12 @@ The Central API ML can onboard Gateways of all domains. This service onboarding
 
 2. (Optional) Configure the Gateway to forward client certificates.   
 Use this step to enable the domain gateway to use this client certificate for authentication. .  
-Set the `certificatesUrl` property to ensure that only  Gateway-forwarded certificates are used for client certificate authentication. This URL returns a certificate chain from the central gateway.
+Set the `certificatesUrl` property to ensure that only  Gateway-forwarded certificates are used for client certificate authentication. This URL returns a certificate chain from the gateway.
 
     ```
     components.gateway.apiml.security.x509:
-        # central gateway port 
-        certificatesUrl: https://{centralGatewayHost}:{centralGatewayPort}/gateway/certificates
+        # gateway port 
+        certificatesUrl: https://{gatewayHost}:{gatewayPort}/gateway/certificates
     ```
 
 ### Dynamic configuration via Environment variables
@@ -107,9 +108,9 @@ This Zowe configuration transforms the zowe.yaml configuration file into the env
 
 ### Validating successful configuration
 
-The corresponding Gateway service should appear in the Eureka console of the Central Discovery service. 
+The corresponding Gateway service should appear in the Eureka console of the Discovery service in Central API ML. 
 
-To see details of all instances of the ‘GATEWAY’ application, perform a **GET** call on the following endpoint of the Central Discovery service:
+To see details of all instances of the ‘GATEWAY’ application, perform a **GET** call on the following endpoint of the Discovery service in central API ML:
 
 ```
 /eureka/apps
@@ -307,7 +308,7 @@ The following commands are examples of establishing a trust relationship between
 
 You completed certificates setup for multitenancy configuration, whereby Domain API MLs can trust the Central API ML and vice versa.
 
-## Using the `/registry` endpoint in the Central Gateway
+## Using the `/registry` endpoint in the Gateway
 
 The `/registry` endpoint provides information about services onboarded to all Domain Gateways (all domains and the central one). This section describes the configuration, authentication, authorization, example of requests, and responses when using the `/registry` endpoint. 
 
@@ -318,7 +319,7 @@ environment variable `APIML_GATEWAY_REGISTRY_ENABLED=TRUE` to enable this featur
 
 ### Authentication for `/registry`
 
-The `/registry` endpoint is authenticated by the client certificate. The Central Gateway accepts certificates that are trusted. The username is obtained from the common name of the client certificate.
+The `/registry` endpoint is authenticated by the client certificate. The Gateway accepts certificates that are trusted. The username is obtained from the common name of the client certificate.
 
 Unsuccessful authentication returns a 401 error code.
 
@@ -493,15 +494,15 @@ Use the `/registry` endpoint to validate successful configuration. The response
 Cannot receive information about services on API Gateway with apimlId 'apiml1' because: Received fatal alert: certificate_unknown; nested exception is javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
 
 **Reason**  
-The trust between the domain and the central Gateway was not established. 
+Cannot connect to the Gateway service. 
 
 **Action**  
-Review your certificate configuration.
+Make sure that the external Gateway service is running and the truststore of the both Gateways contains the corresponding certificate.
 
 ### No debug messages similar to apiml1 completed with onComplete are produced
 
  **Reason**  
  Domain Gateway is not correctly onboarded to Discovery Service in Central API ML. 
 
  **Action**  
- Review Gateway static definition. Check the Central Discovery Service dashboard if the domain Gateway is displayed. 
+ Review Gateway static definition. Check the  Discovery Service dashboard in Central API ML if the domain Gateway is displayed. 

docs/user-guide/api-mediation/configuration-multi-tenancy-routing.md

@@ -1,7 +1,7 @@
 # Configuring routing in a multi-tenant environment
 
-In addition to the domain-specific Discovery Service, which is typically in the same LPAR, in a multi-sysplex environment, the API Gateway may also need to register with a Central Discovery Service which gathers information about all installed API Gateways
-in isolated sysplex environments. Data from the Central Discovery Service can then be used by the Central Gateway for routing to individual API Gateways.
+In addition to the domain-specific Discovery Service, which is typically in the same LPAR, in a multi-sysplex environment, the API Gateway may also need to register with the Discovery Service in central API ML which gathers information about all installed API Gateways
+in isolated sysplex environments. Data from the Discovery Service in the central API ML can then be used by the Gateway in the central API ML for routing to individual API Gateways.
 
 Follow these steps to register with additional Discovery Services:
 
@@ -11,7 +11,7 @@ Follow these steps to register with additional Discovery Services:
    **Example:**
    ```
    components.gateway.apiml.service.additionalRegistration: 
-       <!-- central APIML -->
+       <!-- APIML on System 1  -->
        - discoveryServiceUrls: https://sys1:10011/eureka/,https://sys1:10021/eureka/ 
      <!-- APIML on System 2 -->
        - discoveryServiceUrls: https://sys2:10011/eureka/,https://sys2:10021/eureka/

docs/whats-new/zowe-v3-frequently-asked-questions.md

@@ -94,7 +94,7 @@
 
 3. Can you speak about the migration from Zuul to Spring Cloud Gateway? Today there are two separate gateway services in API ML with separate configurations.
 
-   Spring Cloud Gateway is replacing Zuul as the technology to provide the API Gateway. The configuration for the API Gateway remains in the `components.gateway` namespace. If you were using Spring Cloud Gateway in V2 for the multi-tenancy scenario, you need to update the configuration for the central gateway and move this configuration from `components.cloud-gateway` to `components.gateway`.
+   Spring Cloud Gateway is replacing Zuul as the technology to provide the API Gateway. The configuration for the API Gateway remains in the `components.gateway` namespace. If you were using Spring Cloud Gateway in V2 for the multi-tenancy scenario, you need to update the configuration for the central gateway (refered as gateway from v3 onwards) and move this configuration from `components.cloud-gateway` to `components.gateway`.
 
 4. If I have a legacy gateway deployed, how will I migrate to the new gateway? Will the old gateway be removed?
 

versioned_docs/version-v2.18.x/whats-new/zowe-v3-frequently-asked-questions.md

@@ -94,7 +94,7 @@
 
 3. Can you speak about the migration from Zuul to Spring Cloud Gateway? Today there are two separate gateway services in API ML with separate configurations.
 
-   Spring Cloud Gateway is replacing Zuul as the technology to provide the API Gateway. The configuration for the API Gateway remains in the `components.gateway` namespace. If you were using Spring Cloud Gateway in V2 for the multi-tenancy scenario, you need to update the configuration for the central gateway and move this configuration from `components.cloud-gateway` to `components.gateway`.
+   Spring Cloud Gateway is replacing Zuul as the technology to provide the API Gateway. The configuration for the API Gateway remains in the `components.gateway` namespace. If you were using Spring Cloud Gateway in V2 for the multi-tenancy scenario, you need to update the configuration for the central gateway (refered as gateway from v3 onwards) and move this configuration from `components.cloud-gateway` to `components.gateway`.
 
 4. If I have a legacy gateway deployed, how will I migrate to the new gateway? Will the old gateway be removed?