Migration and Compatibility

The following information provides migration procedures and a compatibility matrix for this release of TIBCO Control Plane and capabilities.

TIBCO Control Plane

For more information on upgrading from an earlier version of TIBCO Control Plane to version 1.5.0, see Upgrades.

TIBCO Enterprise Message Service™ Capability

TIBCO Enterprise Message Service™ capability release 1.5.0 uses:

  • TIBCO Enterprise Message Service™ 10.4.0

  • TIBCO FTL® 7.0.1

TIBCO Enterprise Message Service™ capability now requires the activation URLs.

When upgrading an EMS capability provisioned with 1.4.0, it is recommended to use the Redeploy administrative feature with a custom configuration to supply the correct activation URL prior to upgrading. Contact support if assistance with this is needed.

TIBCO Flogo Capability

TIBCO Flogo Capability 1.3.0 and earlier versions are not compatible with TIBCO® Control Plane 1.4.0 and above versions. To ensure proper functionality, both TIBCO Flogo Capability and TIBCO Control Plane must be upgraded to the latest versions.

TIBCO® Messaging Quasar - Powered by Apache Pulsar™

TIBCO® Messaging Quasar - Powered by Apache Pulsar™ capability release 1.5.0 is compatible with Apache Pulsar™ LTS release 3.0.2.

Note: The TIBCO Platform provisioning chart supports a basic pub-sub messaging pod group. Other features, such as Functions, SQL, and additional connectors must be provisioned and administered separately.
When you are provisioning without the support for ClusterRole 'get node' permissions, only messaging groups with greater than or equal to three bookie pods are supported, as node rack assignment information is unavailable.