Service Registration and Discovery

The service registration and discovery mechanism lets TIBCO BusinessWorks™ Container Edition services announce their availability and lets clients dynamically find these services.

  • Cloud Foundry

    Service registration and discovery on Cloud Foundry is done using one of the following options:

    • Support for service registration and discovery is provided through an integration with the Eureka Service Registry service.

      You first create an instance of the service using the Pivotal Platform Apps Manager and then bind this service instance to your application.

    • Support for Consul service registration and discovery is provided using the CONSUL_SERVER_URL environment variable. For more information, see Environment Variables for Cloud Foundry.
    Note:

    TIBCO BusinessWorks™ Container Edition communicates with Spring Cloud® Services using HTTPS. If your Cloud Foundry installation uses a self-signed SSL certificate, this certificate should be added to the buildpack before your application can be deployed. For more information, see Customize the Buildpack in Certificate Management to add self-signed SSL certificate to the buildpack.

  • Docker and Docker based platforms
    • Support for Eureka service registration and discovery on Docker and Docker based platforms is provided using the EUREKA_SERVER_URL environment variable. For more information, see Environment Variables for Docker or Docker based Platforms.
    • Support for Consul service registration and discovery on Docker and Docker based platforms is provided using the CONSUL_SERVER_URL environment variable. For more information, see Environment Variables for Docker or Docker based Platforms.
    • To discover services registered on Eureka Server using IP, the bw.servicediscovery.eurekaclient.useIP java property is used. The default value of the java property is False. This property needs to be a part of BW_JAVA_OPTS environment variable.
Service Registration Configuration

For information on configuration see HTTP Connector in the Shared Resources section of the Palette Reference.

Note: On Cloud Foundry to use the direct registration mode set the ENABLE_SERVICE_DIRECT_REGISTRATION environment variable to true.

For more information, see Environment Variables for Cloud Foundry.

Service Discovery Configuration

For information on configuration see HTTP Client in the Shared Resources section of the Palette Reference.

Support for Security Enabled Service Registry

Connection to Consul/Eureka via HTTPS (SSL) for Docker: For security enabled service registry for Docker, you need to copy the SSL certificate to the resources/addons/certs folder and create a base docker image.

Connection to Consul/Eureka via HTTP (SSL) for Pivotal Platform: For security enabled service registry for Pivotal Platform, you need to copy the SSL certificate to the resources/addons/certs folder in the buildpack.