You can, for example, scale up a cluster by increasing the number of servers.
Previously specified optional parameters are persisted through subsequent updates.
Binding your apps to a service instance enables the apps to connect to the service instance and read or write data to the region.
Run A sample app written in pure Java has been put together to demonstrate how to connect an app to the service instance.
The code is available at https://github.com/cf-gemfire-org/The code assumes that you have already created a region named --- applications: - name: sample_app path: build/libs/cloudcache-sample-app-1.0no-route: true health-check-type: none services: - service0 # replace this with the name of your service.
Please refer # to docs above on how to create a cloud cache service instance.
Your PCF operator can change details of the service plan available on the Marketplace.
Before you can connect, you must create a truststore.Service keys provide a way to access your service instance outside the scope of a deployed CF app.Run $ gfsh _________________________ __ / _____/ ______/ ______/ /____/ / / / __/ /___ /_____ / _____ / / /__/ / ____/ _____/ / / / / /______/_/ /______/_/ /_/ 9.0.1 Monitor and Manage Pivotal Gem Fire gfsh Connecting over HTTPS involves a few more steps than connecting over HTTP, but it is required for some network setups.However, if your operator changes the allowed values of one of the optional parameters, existing instances that exceed the new limits are not affected, but any subsequent service updates that change the optional parameter must adhere to the new limits.For example, if the PCF operator changes the plan by decreasing the maximum value for $ cf update-service my-cloudcache -c '' Updating service instance my-cloudcache as admin...You can test the newly created region by writing and reading values with gfsh: In practice, you should perform these get/put operations from a deployed PCF app.