Using Hazelcast IMDG Enterprise for PCF

This topic describes how developers use Hazelcast IMDG Enterprise for Pivotal Cloud Foundry (PCF).

After your PCF operator installs the Hazelcast IMDG Enterprise for PCF tile, it automatically registers itself to the Marketplace.

Follow these steps to create an instance of the Hazelcast service based on an available plan and bind it to your app. The plans available to you are determined by your PCF operator. For more information about configuring plans, see Installing and Configuring Hazelcast IMDG Enterprise for PCF.

  1. To check availability of Hazelcast IMDG Enterprise for PCF, enter the following command:

    $ cf marketplace

    For example,

    $ cf marketplace
    Getting services from marketplace in org system / space system as admin...
    service plans description app-autoscaler bronze, gold Scales bound applications in response to load (beta) hazelcast t2.micro, t2.small, m3.medium Hazelcast Service

  2. Create a file named hazelcast.json using this sample Hazelcast JSON file as a template.

  3. Replace YOUR_LICENSE_KEY with the active Hazelcast Enterprise License or a trial license. For more information, see License.

  4. To create a cluster, enter the following command:

    $ cf create-service hazelcast PLAN SERVICE_INSTANCE_NAME -c hazelcast.json

    For example,

    $ cf create-service hazelcast t2.micro micro-cluster -c hazelcast.json
    Creating service instance micro-cluster in org system / space system as admin...
    Create in progress. Use 'cf services' or 'cf service micro-cluster' to check operation status.

  5. To bind the service to your app, enter the following commands:

    $ cf restage MY-APPLICATION

    For example,

    $ cf bind-service myapp micro-cluster
    $ cf restage myapp

  6. Start using the Hazelcast in-memory data grid (IMDG). Necessary parameters are passed to your application in VCAP_SERVICES environment variable. See this sample Hazelcast Spring Boot application for further information.

Create a pull request or raise an issue on the source for this page in GitHub