Merge pull request #3589 from zowe/add-ports

Additional ports used in Caching Service (infinispan mode) - keyExchange port updated
zowe · Apr 5, 2024 · 02fa0b7 · 02fa0b7
2 parents e5d78d7 + f35ad6a
commit 02fa0b7
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/docs/user-guide/address-network-requirements.md b/docs/user-guide/address-network-requirements.md
@@ -10,6 +10,8 @@ For more information about variable names in the following table, see the [Zowe
 
 | Port number | zowe.yaml variable name | Purpose |
 |------|------|------|
+| 7098 | zowe.components.caching-service.storage.infinispan.jgroups.port | Bind port for the socket that is used to form an Infinispan cluster.
+| 7118 | zowe.components.caching-service.storage.infinispan.jgroups.keyExchange.port | The port at which the key server in Infinispan is listening. If the port is not available, the next port is probed, up to port+5. Used by the key server (server) to create an SSLServerSocket and by clients to connect to the key server.
 | 7552 | zowe.components.api-catalog.port | Used to view API swagger / openAPI specifications for registered API services in the API Catalog. 
 | 7553 | zowe.components.discovery.port | Discovery server port which dynamic API services can issue APIs to register or unregister themselves.
 | 7554 | zowe.components.gateway.port | The northbound edge of the API Gateway used to accept client requests before routing them to registered API services.  This port must be exposed outside the z/OS network so clients (web browsers, VS Code, processes running the Zowe CLI) can reach the gateway.