Installing and Configuring the EDB Postgres Service Broker

This topic describes how to install and configure the EDB Postgres Service Broker tile, as well as how to create an instance of the EDB Postgres service from the Marketplace of your Pivotal Cloud Foundry (PCF) deployment.

Install the EDB Postgres Service Broker Tile

  1. Download the product file from Pivotal Network.
  2. Log in to Ops Manager.
  3. From the Ops Manager Installation Dashboard, click Import a Product and upload the product file.
  4. When the upload completes, EDB Postgres appears in the Available Products list. Click Add.

    Add tile

  5. Click the newly added EDB Postgres tile to provide configuration information.

    Dashboard

  6. From the Settings tab, click EDB PostgreSQL.

    Edb tile sections

  7. Enter the Java Database Connectivity (JDBC) URL for your master PostgreSQL database server. For example, jdbc:postgresql://ec2-23-21-53-234.compute-1.amazonaws.com:9999/postgres?user=postgres&password=postgres.

    Edb tile config

  8. Click Save.

  9. Return to the Installation Dashboard and click Apply Changes to install the EDB Postgres Service Broker tile.

Create a EDB Postgres Database in Apps Manager

After installing the EDB Postgres Service Broker tile, EDB Postgres appears as a service in the Marketplace of your deployment. Developers can provision PostgreSQL databases by creating service instances using Apps Manager or the cf Command Line Interface (CLI).

Follow the instructions below to create a EDB Postgres service instance using Apps Manager.

  1. Navigate to Apps Manager in a browser and log in.
  2. Click Marketplace.

    Marketplace

  3. Click EDB Postgres.

    Add plan

  4. Click Select this plan. You can also navigate to the documentation at the EnterpriseDB website by clicking Docs, and sign in to the EDB Customer Portal by clicking Support.

  5. In the Configure Instance form, enter an Instance Name to identify the service instance in the deployment and click Add.

  6. Once you have created your service instance, you can bind it to an application. For more information on binding services instances, see Managing Apps and Service Instances Using the Apps Manager.

    Binding a service instance to an application triggers credentials to be provisioned for the service instance and delivered to the application runtime in the VCAP_SERVICES environment variable. To view these credentials, navigate to an application with a bound service instance in Apps Manager and click Env Variables. The credentials provided to the EDB Postgres Service Broker tile have the following format:

    "credentials": { "uri":"postgres://USERNAME:PASSWORD@HOSTNAME:PORT/DATABASE" }

Was this helpful?
What can we do to improve?
Create a pull request or raise an issue on the source for this page in GitHub