Connectors and Adapters

Connectors are TIBCO Cloud API Management's integration features that have been developed and provided ready to use for Cloud customers. Connectors have been carefully envisioned to address common use-cases, such as: content injection, content filtering, content transformation, call authentication using third-party IDP, IP-based call filtering, domain-based routing, geo-location based routing and HTTP header manipulation.

TIBCO Cloud API Management-built Connector vs Adapter

The following table explains the differences between TIBCO Cloud API Management-built connectors and TIBCO Cloud API Management-built adapters.
Connector Adapter
Mashery-built features for TIBCO Cloud API Management Mashery built for both TIBCO Cloud API Management and TIBCO Cloud™ API Management - Local Edition
Strategic integration feature generally available out of the box for any TIBCO Cloud API Management customer. Custom in nature and tailored to fit a particular customer specific need.
Available without additional cost to TIBCO Cloud API Management customers. Customer may incur fee for engineering and development work done by TIBCO.
Note: API Management - Local Edition customers can use the SDK to build their own adapters.
Can be ported to a Local Edition customer upon request in Mashery Local 4.X. Needs to be engineered and developed for Local Edition customer.

FAQs

Does TIBCO ship TIBCO Cloud API Management Connectors out of the box?

Yes. TIBCO Cloud API Management Connectors are available out of the box for TIBCO Cloud API Management customers.

Can TIBCO Cloud API Management Connectors be made available or ported to Local Edition customers?

Yes. TIBCO Cloud API Management built Connectors can be ported to Local Edition customers upon request.

How can I get a TIBCO Cloud API Management built certified Connector?

In order to get TIBCO Cloud API Management Connectors ported, a Local Edition customer needs to make request to the TIBCO Support team.

TIBCO will release it to the Local Edition customer specific area. Once TIBCO Cloud API Management Connectors are promoted to customer specific area, they will be available to deploy via Local Edition user interface. For more information see "How to Get the TIBCO Cloud API Management-Built Connectors and/or Adapters" topic.

Why aren't TIBCO Cloud API Management Connectors available out of the box to prospects/leads?

  • TIBCO Cloud API Management built Connectors are packaged and ported specifically to the Local Edition customer area.
  • TIBCO prospects/leads do not get assigned a TIBCO Cloud API Management production area unless they are formally on-boarded in TIBCO Cloud API Management.
Note: In certain cases, prospects/leads may get a trial area, but one that is temporarily assigned for evaluation period.

What are some best practices for a Local Edition customer who needs to migrate to newer version of Local Edition and consumes TIBCO Cloud API Management built Adapters and/or Connectors?

Here are best practices and guidance for smoother migration to newer version of Local Edition 4.4.X.
Note: (Applies to customers who consume TIBCO Cloud API Management built Connectors or Adapters)
Normal Flow
  1. It is always good practice and TIBCO recommends to release TIBCO Cloud API Management built Connectors or Adapters certified for a particular Local Edition 4.4.X release in a non-production area/environment first.
    1. Migration of Local Edition product and TIBCO Cloud API Management built Connectors or Adapters that is needed for a particular Local Edition 4.4.X version must happen in lock step.
  2. Customer should deploy TIBCO Cloud API Management built Connectors or Adapters build once they are available in their non-production environment for a particular Local Edition 4.4.X version.
  3. Customer must perform UAT and confirms/sign off that TIBCO Cloud API Management built Connectors or Adapters are functioning as expected for Local Edition version.
  4. Customer should update support case once they sign off UAT. TIBCO will release Connectors or Adapters to customer Local Edition production area.