Business Continuity for TIBCO Cloud integrations within public runtime cloud API Management


As TIBCO Cloud services are beyond Boomi’s direct control, there is a risk of potential disruptions that could affect your API integrations within public runtime cloud API Management (formerly Mashery). 

To ensure uninterrupted access to your critical services, we strongly recommend all customers review their use of any of the below TIBCO Cloud integrations configured within the public runtime cloud API Management product today. Details on steps you can take to maximize service continuity are noted below.

  1. TIBCO Cloud™ Mesh API endpoint visibility
  2. TIBCO Cloud™ Mesh for Call Transformations within Cloud API Management
  3. TIBCO Cloud™ Mesh discovered API Endpoints managed within Cloud API Management

TIBCO Cloud™ Mesh API endpoint visibility

Within TIBCO Cloud, and managed by public runtime cloud API Management, API endpoints can be set as either Public or Private. TIBCO Cloud Mesh allows users to discover any private REST endpoint exposed within TIBCO Cloud domains, within your Cloud API Management organization or related organizations. Additional information regarding Cloud Mesh can be found here.

 

TIBCO Cloud Mesh private endpoints are exposed only to applications in the TIBCO Cloud™ and cannot be reached by any external system. Should they remain private, access to these resources may be disrupted should TIBCO Cloud Mesh become inaccessible for whatever reason. Visibility of the endpoints can be reviewed and edited via TIBCO Cloud. Further details can be found here.


To change the visibility of an endpoint - from private to public - complete the following steps:

  1. Log in to TIBCO Cloud™ Integration.
  2. Click the Apps tab.
  3. Hover over the app you want to change, and click the shortcut menu.
  4. Edit “Endpoint Visibility” to “Public” and click “Update”
  5. Copy the updated endpoint address and path details
  6. Update and/or set up a new Endpoint definition within public runtime cloud API Management to access the API through the new public URL path 

TIBCO Cloud™ Mesh for Call Transformations within public runtime cloud API Management

The public runtime cloud API Management Call Transformations feature provides the capability to apply pre and/or post processing logic to defined API endpoints. 

The pre and post processing logic can originate from one of two sources:

  1. Via public runtime cloud API Management Connectors and Processors that are published and made available for all customers here.
  2. Through use of TIBCO Cloud™ Mesh by discovering and calling out to published applications within TIBCO Cloud.


In the event that a Cloud API Management API endpoint is configured to leverage a TIBCO Cloud-hosted application for a pre and/or post processing transformation, and that application becomes unavailable, the configured API endpoint will no longer process API requests as designed. 

To ensure configured API endpoints within Cloud API Management continue to process API requests as expected without external platform dependencies, such as TIBCO Cloud, customers should review how they can leverage Cloud API Management Connectors and Processors, as documented here. Where customized logic is required, Cloud API Management provides customers with the ability to deploy their pre and/or post processing logic into AWS Lambda, so that the Function As a Service can be implemented as a part of the transformation. 

More documentation on Cloud API Management’s ability to leverage AWS Lambda for pre and/or post processing transformations can be found here.

TIBCO Cloud™ Mesh discovered API Endpoints managed within Cloud API Management

TIBCO Cloud Mesh APIs are available for discovery and management via public runtime cloud API Management. Should TIBCO Cloud become inaccessible, the integrated endpoint may no longer function as expected.

To ensure the integrity and accessibility of your downstream resource, customers should review all backend endpoint configurations for potential TIBCO Cloud dependencies and address accordingly. More information regarding this configuration and implementation can be found here.


To review and make changes to an API’s endpoint configuration, complete the following steps:

  1. Login public runtime cloud API Management.
  2. Navigate to Design > APIs.
  3. Select the API Definition you wish to review.
  4. Select Endpoint.
  5. Select “Domains & Traffic Routing” in the left-side navigation.
  6. Review the TIBCO Cloud Mesh drop-down and the selected discovered service.

NOTE: To safeguard against potential service disruption, the implemented mesh service must be manually configured rather than selected from TIBCO Cloud Mesh.

  1. In the drop-down, change “TIBCO Cloud Mesh” to “Manual Entry”.
  2. Configure your “Endpoint Address” to specification.
  3. Click “Save”.