Using Axway AMPLIFY APIM Service Broker to Proxy VMware Tanzu Apps

This topic describes how to use Axway AMPLIFY APIM Service Broker to proxy VMware Tanzu apps. Developers can extend the value of VMware Tanzu by integrating the apps and services running on VMware Tanzu through Axway AMPLIFY™ API Management. The integration is implemented as a VMware Tanzu Service Broker. With this approach, customers can connect to an existing Axway API Management solution, or they can deploy Axway API Manager on their choice of infrastructure (on-premise or cloud) and integrate it with VMware Tanzu.

A high level architecture that is based on the VMware Tanzu Fully-Brokered Service pattern is shown on the following diagram

Axway APIM Service Broker

The benefits of using the service broker pattern are described in the overview section.

Before you can proxy an app, you need to download/install and configure Axway AMPLIFY APIM Service Broker. When you’re done, the Axway AMPLIFY APIM Service Broker will be available on Marketplace of Pivotal Apps Manager as show below

Marketplace

Creating an instance of Axway AMPLIFY APIM Service Broker

To create an instance of Axway AMPLIFY APIM Service Broker, perform the following steps:

  1. Click Axway AMPLIFY APIM in your VMware Tanzu Marketplace.

  2. Select one of the available plans and click the SELECT THIS PLAN button.

    Selecting a plan

  3. Give a unique name to your instance and select a space where this instance will be created, and click the CREATE button.

    Creating an instance Note: Don’t select any app or route to bind in this step. You must do it later.

Binding a route to your app

When your instance is created, you need to bind a route to your app(s):

  1. Click the name of your Service Broker instance.

    Selecting an instance

  2. Click the BIND ROUTE button.

    Bind a route

  3. Select the Select a route to bind radio button and pick your app in the drop down list.

    Configure your route binding

  4. Open the ADVANCED OPTIONS section and provide additional parameters. For example,

       {
        "apiname": "pcfgreeting",
        "type": "swagger",
        "uri": "/api/v3/swagger.json"
       }
    

    The parameter apiName is optional. If apiName is not specified, Service broker fetch the API Name from swagger or WSDL. Possible values of type parameters are wsdl and swagger The URI value will be context name or Fully qualified Swagger / WSDL URL, for example - greeting-app-timely-llama.apps.cf-app.com*/api/v3/swagger.json*. If context name is provided as input, the service broker reads the host name from Cloud Foundry Application.

  5. Click the BIND button. You should see a new route bound under your Service Broker instance.

    Bound route

  6. Now you should see a new API registered in your Axway AMPLIFY API Manager.

    Created API

    You can further configure this API (security, throttling, etc.) per your requirements.

Unbinding a route to your app

To unbind a route to a VMware Tanzu app:

  1. Unpublish an associated API in Axway AMPLIFY API Manager.

  2. Navigate to the Services section of Pivotal Apps Manager and click the name of your Service Broker instance.

  3. Click the x button next to your bound route. Bound route

  4. Click UNBIND in a pop-up window. Bound route