Using a Service Gateway
The service gateway allows apps that run in a different location than the Services Foundation where the Tanzu GemFire service instance runs to communicate with the service instance. At its core, the service gateway is a TCP router.
There are three locations where an app may run. The locations are defined in The App’s Location.
Apps that run within an App Foundation and apps that run completely outside of any foundation must have a service gateway enabled and running to communicate with the Tanzu GemFire service instance. To enable and run the service instance:
- The operator must Configuring a Service Gateway.
- The developer must Provide Optional Parameters when creating the Tanzu GemFire service instance.
- The app must be given and use properties that authenticate and authorize Communicating with a Service Instance through the service gateway.
If traffic through the service gateway becomes a performance bottleneck, the service gateway may be scaled.
Discover if the service gateway is a bottleneck by first using the BOSH CLI to log in and target your services foundation.
BROKER-DEPLOYMENT-NAMEby running the command:
bosh deployments | grep "^p-cloudcache"
The first column of the output is the
BROKER-DEPLOYMENT-NAMEin the command:
bosh -d BROKER-DEPLOYMENT-NAME vms --vitals
If the CPU usage in the sni-tcp-router VM is high, you can scale the service gateway by altering the Tanzu GemFire tile.
- From the Ops Manager Installation Dashboard, click on the Tanzu GemFire tile.
- Within the tile Settings, click on Resource Config.
- Increase the quantity of TCP Router INSTANCES.
- Click SAVE.
- Review and apply the changes.