Write Behind Cache Listener Using Gateway Hubs- Early Access

You can now implement a write-behind cache listener in your gateway hubs. This is accomplished by creating multiple gateways in a single distributed system member and configuring one of them with no incoming port specification. The hub with no incoming port will only process events from inside the distributed system, allowing you to run the hub with write-only behavior. Without a port specified, the hub does not start a server socket to listen for incoming communication. It only receives events from inside its own distributed system, notifies its listeners, and sends the events to any configured remote sites.

To support the new multi-hub option, a new Cache API method getGatewayHub(String id) retrieves a gateway hub for a specific ID.