Binding service on a specific subnet

[pavel-jares-bcm]

This issue is based on #4408

For each service should be possible to configure network for binding a port. As default services binds on 0.0.0.0 (all network interfaces). It is valid for v3, but not for v2. All except the Gateway are binding always on all interfaces, see -Dserver.address=0.0.0.0 \ in all start.sh scripts.

[achmelo]

What do you mean by "It is valid for v3, but not for v2"? v3 accepts binding address from configuration, it is probably enough to cherry-pick the changes.
-Dserver.address=${ZWE_configs_zowe_network_server_listenAddresses_0:-${ZWE_zowe_network_server_listenAddresses_0:-"0.0.0.0"}} \

[pavel-jares-bcm]

Yes, v3 uses binding addresses from start.sh. But it is not everything. Keep in mind there is infinispan and these ports are missing. They are still binding to all network interfaces. So the aim is to:

• update start.sh scripts by v3 (except GW, see fix: Fix infinispan configuration, exception handling, and the whole cache operation #4408)
• update infinispan.xml and InfinispanConfig to propagate binding adresses (both v2 and v3)

[achmelo]

for the binding itself, there is another issue #4409

[achmelo]

update infinispan.xml and InfinispanConfig to propagate binding adresses (both v2 and v3) should be mentioned in the discription and note that server.address is only missing in v2