Skip to content

Commit

Permalink
propogate refactored note
Browse files Browse the repository at this point in the history
Signed-off-by: Andrew Jandacek <[email protected]>
  • Loading branch information
janan07 committed Oct 17, 2024
1 parent 3c54bec commit 4ec396d
Showing 1 changed file with 6 additions and 8 deletions.
14 changes: 6 additions & 8 deletions docs/user-guide/api-mediation/api-mediation-multi-tenancy.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ components.gateway.apiml.service.additionalRegistration:
```

:::note
Ensure that each API ML instance is defined in a separated record. Do not combine multiple API ML instances in a single record. In the case of a high availability setup, the value `discoveryServiceUrls` may contain multiple URLs. We highly recommend to provide all available Discovery URLs in the value `discoveryServiceUrls`.
Ensure that each API ML instance is defined in a separate record. Do not combine multiple API ML instances in a single record. In the case of a high availability setup, the value `discoveryServiceUrls` may contain multiple URLs. We highly recommend to provide all available Discovery URLs in the value `discoveryServiceUrls`.

Always provide the direct address to the system. Do not use the DVIPA address. Using this address could lead to unexpected behaviour.

Expand Down Expand Up @@ -133,14 +133,12 @@ components.gateway.apiml.service.additionalRegistration:
serviceUrl: /
```

:::note
Each API ML instance should be defined in a separated record. Do not mix different API ML instance in one record.
The value `discoveryServiceUrls` could contain multiple URLs in case of HA setup. We highly recommend to provide all
available Discovery URLs in there.
:::note
Ensure that each API ML instance is defined in a separate record. Do not combine multiple API ML instances in a single record. In the case of a high availability setup, the value `discoveryServiceUrls` may contain multiple URLs. We highly recommend to provide all available Discovery URLs in the value `discoveryServiceUrls`.

Always provide the direct address to the system, do not use DVIPA address. It could lead to unexpected behaviour.
Hostnames `sys1` and `sys2` are names of LPAR in the sysplex.
Always provide the direct address to the system. Do not use the DVIPA address. Using this address could lead to unexpected behaviour.

Use hostnames `sys1` and `sys2` for the LPAR in the sysplex.
:::

#### Dynamic configuration: Environment variables
Expand Down

0 comments on commit 4ec396d

Please sign in to comment.