Skip to content

Latest commit

 

History

History
67 lines (51 loc) · 2.79 KB

CF_Standard_Enterprise_Plan.md

File metadata and controls

67 lines (51 loc) · 2.79 KB
Raw

IBM Cloud Foundry deployment to an Standard/Enterprise Plan Event Streams for IBM Cloud

Overview

To deploy and run the sample:

  • Create a Cloud Foundry Service Alias for your Standard/Enterprise Service
  • Setup your manifest.yml with your service details
  • Use ibmcloud cf push --no-start to deploy the app to IBM Cloud Foundry
  • Re-configure binding with Manager role
  • Start the app
  • Inspect the application's logs

Set up a Cloud Foundry Service Alias

Before continuing, connect to IBM Cloud with the IBM Cloud command line interface.

The Standard/Enterprise plan is IAM enabled. Therefore the following extra step is required to create a Cloud Foundry alias for your Service:

Create a Cloud Foundry alias for your service's associated CRN:

ibmcloud resource service-alias-create <eventstreams-service-alias-name> --instance-name <eventstreams-service-instance-name>

Having created this alias associated your Service with a Cloud Foundry Organization and Space, thereby enabling your Cloud Foundry application to referrence it and connect to it.

Setup the manifest.yml

  1. Select the Event Streams for IBM Cloud service you would like to bind your application to. Do this by replacing <YOUR_SERVICE_INSTANCE_NAME> with your service instance alias name in manifest.yml:
  services:
    - "<YOUR_SERVICE_INSTANCE_NAME>"
  1. Consider your domain: You might need to change this in the manifest.yml as the domain varies by IBM Cloud region. If unsure, just delete the domain line and IBM Cloud will pick the domain for you.

Build the Sample

Build the project using gradle:

gradle clean build

The command above creates a zip file under build/distributions.

Deploy the Application

Push the app without starting it immediately by running the following command in the same directory as the manifest.yml file:

ibmcloud app push --no-start

Re-configure the binding

A binding between your app and service-alias is created for you automatically, but by default does not have permissions to create topics. This means that we need to delete the existing binding and create a new one with the correct role:

ibmcloud resource service-binding-delete <YOUR_SERVICE_INSTANCE_ALIAS_NAME> kafka-java-console-sample
ibmcloud resource service-binding-create <YOUR_SERVICE_INSTANCE_ALIAS_NAME> kafka-java-console-sample Manager

Start the app

Now it should be safe to start the application:

ibmcloud app start kafka-java-console-sample

Produce and Consume Messages

The sample application should have created the default sample topic and started producing and consuming messages in an infinite loop. View the logs to verify this:

ibmcloud app logs kafka-java-console-sample