remove central gateway reference from the docs for v3 #4038
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
|
💾 The release label is missing. Add a If you have addressed this issue already, refresh this page in your browser to remove this comment. |
|
📌 The subject area label is missing. Add an If you have addressed this issue already, refresh this page in your browser to remove this comment. |
|
🔍 The review label is missing. Add a If you have addressed this issue already, refresh this page in your browser to remove this comment. |
Signed-off-by: ShobhaJayanna <[email protected]>
Shobhajayanna
changed the title
Signed-off-by: ShobhaJayanna <[email protected]>
Shobhajayanna
changed the title
Signed-off-by: Andrew Jandacek <[email protected]>
janan07
approved these changes
Dec 18, 2024
| * [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) | ||
| * [Using the `/registry` endpoint in Gateway in the Central API ML](#using-the-registry-endpoint-in-the-central-gateway) |
There was a problem hiding this comment.
Do we want to keep Central here in Central API ML?
| @@ -4,13 +4,13 @@ Zowe supports management of multiple tenants, whereby different tenants can serv | |||
|
|
|||
| * [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) | |||
| * [Onboarding a Domain Gateway service to Discovery service in the Central API ML](#onboarding-a-domain-gateway-service-to-the-central-discovery-service) | |||
There was a problem hiding this comment.
Do we want to keep Central here in Central API ML?
| @@ -4,13 +4,13 @@ Zowe supports management of multiple tenants, whereby different tenants can serv | |||
|
|
|||
| * [Overview of Central and Domain API MLs](#overview-of-central-and-domain-api-mls) | |||
There was a problem hiding this comment.
We do have Central API MLs mentioned here. What does this term mean now and should we use better one?
| @@ -4,13 +4,13 @@ Zowe supports management of multiple tenants, whereby different tenants can serv | |||
|
|
|||
| * [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) | |||
| * [Onboarding a Domain Gateway service to Discovery service in the Central API ML](#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) | |||
Signed-off-by: ShobhaJayanna <[email protected]>
Shobhajayanna
commented
Dec 18, 2024
taban03
reviewed
Dec 18, 2024
taban03
reviewed
Dec 18, 2024
taban03
reviewed
Dec 18, 2024
versioned_docs/version-v2.18.x/whats-new/zowe-v3-frequently-asked-questions.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Andrea Tabone <[email protected]> Signed-off-by: ShobhaJayanna <[email protected]>
Co-authored-by: Andrea Tabone <[email protected]> Signed-off-by: ShobhaJayanna <[email protected]>
…ked-questions.md Co-authored-by: Andrea Tabone <[email protected]> Signed-off-by: ShobhaJayanna <[email protected]>
Signed-off-by: ShobhaJayanna <[email protected]>
|
|
||
|  | ||
|
|
||
| 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 . |
There was a problem hiding this comment.
Update to one of the following, please:
Domain-1 is running on z/OS, or off z/OS
Domain-1 may be running on z/OS, or off z/OS
Signed-off-by: ShobhaJayanna <[email protected]>
| For routing to work in a multitenancy configuration, the Central API Mediation Layer must trust the Domain API Mediation Layers for successful registration into the Discovery Service component. | ||
| The Domain API Mediation Layers must trust the Central API Mediation Layer Gateway to accept routed requests. | ||
| It is necessary that the root and, if applicable, intermediate public certificates be shared between the Central API Mediation Layer and Domain API Mediation Layers. | ||
| For routing to work in a multitenancy configuration, as represented in the example daigram above where "Domain APIML 2", "Domain APIML 3" are registered to "Domain APIML 1", the "Domain APIML 1" must trust the "Domain APIML 2", "Domain APIML 3" for successful registration into the it's Discovery Service component. |
There was a problem hiding this comment.
example diagram instead of daigram
| The Domain API Mediation Layers must trust the Central API Mediation Layer Gateway to accept routed requests. | ||
| It is necessary that the root and, if applicable, intermediate public certificates be shared between the Central API Mediation Layer and Domain API Mediation Layers. | ||
| For routing to work in a multitenancy configuration, as represented in the example daigram above where "Domain APIML 2", "Domain APIML 3" are registered to "Domain APIML 1", the "Domain APIML 1" must trust the "Domain APIML 2", "Domain APIML 3" for successful registration into the it's Discovery Service component. | ||
| The "Domain APIML 2", "Domain APIML 3" must trust the "Domain APIML 1" Gateway where they are registed to, to accept routed requests. |
There was a problem hiding this comment.
registered to instead of registed to
| It is necessary that the root and, if applicable, intermediate public certificates be shared between the Central API Mediation Layer and Domain API Mediation Layers. | ||
| For routing to work in a multitenancy configuration, as represented in the example daigram above where "Domain APIML 2", "Domain APIML 3" are registered to "Domain APIML 1", the "Domain APIML 1" must trust the "Domain APIML 2", "Domain APIML 3" for successful registration into the it's Discovery Service component. | ||
| The "Domain APIML 2", "Domain APIML 3" must trust the "Domain APIML 1" Gateway where they are registed to, to accept routed requests. | ||
| It is necessary that the root and, if applicable, intermediate public certificates be shared between the these domain API Mediation Layers. |
There was a problem hiding this comment.
remove 'the' before these domain
|
|
||
| The following commands are examples of establishing a trust relationship between a Domain API ML and the Central API ML for both PKCS12 certificates and when using keyrings. | ||
| The following commands are examples of establishing a trust relationship between a API MLs in Multitenancy Configuration for both PKCS12 certificates and when using keyrings. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your pull request here:
This is to remove the 'central' from central gateway in trouble shooting section.
List the file(s) included in this PR:
docs/troubleshoot/troubleshoot-apiml-error-codes.md