TIBCO® Cloud Integration Release Notes
Last updated:
10:33am Jan 25, 2017

January 24, 2016

Release Notes

API Modeling

The API Modeler is one of the starting points for many journeys in our API-led Integration Platform. One of the missing elements was the ability to search your list of API specifications based on name, version, and description. This release adds that new functionality right at the top of our API Modeler.

We did notice that some of our users weren't able to see the new UI. If that happens, please clear the browser cache and log in again to make sure you can use all the cool new features we have to offer.

New Connector Samples

We had an internal hackathon last year where TIBCO employees could create new connectors on TIBCO Cloud Integration in the form of reusable projects for TIBCO Business StudioTM - Cloud Edition. We’ve added those connectors, as Open Source Software, to our Github page at https://github.com/TIBCOSoftware/tci-samples so you can easily use them in your applications.

Changes in Functionality

This release has the following changes in functionality:

“res” Parameter in Microflow Transform Response Stage Renamed to “body”

The "res" parameter passed to Transform Response stage, which represents the "body" of the response, has been renamed to "body". A Microflow application with a Transform Response stage will need to be modified in the Transform Response Javascript code to reflect this change before the application is re-pushed to the runtime. You need to do this only if you want to re-push an existing Microflow application.

Changes to Log levels

For Integration Applications, less informational and debug system log entries are now emitted to reduce the amount of application logs. System log entries with log level of warnings and errors remain. User defined Log Activities in the application of all log levels will not be suppressed.

To reset the behavior, application developers can define an application property TCI_BW_LOGGER_OVERRIDES in TIBCO Business Studio to override or add specific logger log level settings using a space delimiter property value as logger1=log-level logger2=log-level. More details of the logger names can be found in the bwcloud_logback.xml.

Deprecating and End Of Support for TIBCO Business Studio™ - Cloud Edition Versions

With this release we've ended support for TIBCO Business Studio™ - Cloud Edition 1.0.1 and below.

Closed Issues

IPAS-3157 and IPAS-3158

Summary: After replacing a mock app with an Integration app, the ‘Go to Mock app’ and ‘Update Mock app’ links to the Mock app were not removed.


Summary: Fixed an issue where the application properties that were overridden in the TIBCO Cloud Integration Web UI did not take effect during runtime.


Summary: Fetching entity schemas from Microsoft DCRM 2013 resulted in an error while not being able to retrieve the entity. This issue has been fixed. Make sure to install the latest version of the plug-in. Refer to https://integration.cloud.tibco.com/docs/connectors/index.html for instructions on installing the plug-in.


Summary: If the Upsert or Update activity in Salesforce plugin resulted in an unrecoverable exception, the plug-in would fail to process any further records. This issue has now been fixed. Make sure to install the latest version of the plug-in. Refer to https://integration.cloud.tibco.com/docs/connectors/index.html for instructions on installing the plug-in.

Known Issues


Summary: TIBCO® Cloud Integration does not support user-defined SSL parameters for their application. While TIBCO Business Studio™ - Cloud Edition does not stop you from creating an SSL Server Configuration Shared Resource, this resource, if created will be ignored during the application deployment.

Workaround: None


Summary: If the imported API specification contains a content type other than application/json or application/xml, the content type does not display.

Workaround: None


Summary: The required check-box is not added for the body parameter, therefore, you cannot use it to specify whether the body parameter is required as other parameters.

Workaround: None


Summary: If the schema type of the body parameter defined in an API specification is object, the body parameter is lost after importing the API specification.

Workaround: Manually re-add the body parameter


Summary: If the imported API specification contains unsupported attributes, such as enum, maximum, and minimum, and you export the API specification after editing the attributes, the attributes are lost.

Workaround: None


Summary: When importing an API specification in API Modeler, if the file size of the imported API specification is larger than 400 KB, the following error is returned:

The API does not exist in DB.

Workaround: None


Summary: When creating a routing stage in a Microflow application, the stage is not able to route to non-restful endpoints

Workaround: None


Summary: The Marketo plug-in uses absolute file paths in some of the activities. Due to the nature of TIBCO Cloud Integration these activities are not supported

Workaround: None


Summary: After implementing a Swagger specification that has a “basePath” element in the specification the API tester functionality does not work correctly.

Workaround: Manually remove the “basePath” element prior to implementing it in TIBCO Business Studio™ - Cloud Edition. This does not affect the API specifications created in the API Modeler in TIBCO Cloud Integration.


Summary: The JavaScript code to implement advanced mock responses is not automatically saved

Workaround: To ensure the code is not lost, save the JavaScript code prior to changing methods.


Summary: The API documentation generated from TIBCO Business Studio™ - Cloud Edition which is used to display the endpoints in the API tester will contain all endpoints that are present in the API specification used when implementing the project. The original API specification is passed along to the runtime and does not take into account any non-implemented operations.

Workaround: None


Summary: Two-way SSL Authentication is not supported when using the Salesforce Outbound Listener and the Microsoft Dynamics CRM Entity Event Source Activity. This is because you cannot add your own authentication resources (see IPAS-530).

Workaround: None


Summary: Using XML reserved characters in application properties will result in those overridden values being ignored.

Workaround: None


Summary: On Macintosh systems only: Launching TIBCO Business Studio™ - Cloud Edition by double-clicking TIBCOBusinessStudio.app intermittently fails if Java 6 is not installed on your system


1. Right-click TIBCOBusinessStudio.app and select 'Show Package Contents'

2. Run TIBCOBusinessStudio executable under Contents-> MaCOS folder


Summary: When editing a Microflow App, if you do not push the edited application, you will still be able to scale up the application, which will fail, since the updates are not pushed to the runtime yet.

Workaround: Always push any changes on a MicroFlow App before scaling


Summary: Amazon S3 plug-in does not support relative paths. Hence file type is not supported in the Put and GetObject activities

Workaround: None


Summary: Amazon S3 plug-in is not supported on Mac OS

Workaround: None


Summary: The Put activity (put bucket) throws incorrect error message when the shared resource is configured with invalid Access Key ID

Workaround: None


Summary: Using the API tester view for a Microflow Applications with a header parameter in the Open API specification will lead to error messages with an HTTP 204 status code.

Workaround: None


Summary: The resource name of an API spec is used as the basepath in the URL for REST endpoints that are generated by TIBCO Business Studio™ - Cloud Edition. This causes an inconsistency between the Mock endpoint URL and TIBCO Business Studio™ - Cloud Edition URL when a Mock application is replaced with integration application. This will also have an impact on a Microflow application created based on the Mock application that has been replaced. The Microflow application will need to be re-created based on the new integration application.

Workaround: None


Summary: Installation fails with an Ant task error when TIBCO Business Studio™- Cloud Edition is installed on top of an existing installation with the same version.

Workaround: Uninstall the old TIBCO Business Studio™ - Cloud Edition before installing the new TIBCO Business Studio™ - Cloud Edition or install the new TIBCO Business Studio™ - Cloud Edition in a new TIBCO_HOME.


Summary:  When configuring a Keystore Provider for SSL Client Configuration, if you configure a relative path to a certificate, the test connection will fail. For example, if you try to test the connection for the Mail palette or the MQTT plug-in with a relative path configured, their test connections will fail.

Workaround: None


Summary: In the MQTT plug-in, when the "Clean Session" checkbox is in the unchecked state in the Advanced configuration section of MQTT connection shared resource, support for receiving messages from the previously subscribed topics is not available. The plug-in's runtime will produce the following warning message in the log when it receives a message from a previously subscribed topic:

[MQTT Call: subtopic] c.t.b.p.m.r.MQTTSubscriptionActivity - TIBCO-BW-PALETTE-MQTT-400002:Received message for a topic name <topic-name> not subscribed to in the current instance

Workaround: None


Summary: The following activities in the TIBCO MDM projects are not supported for TIBCO Business Studio™ - Cloud Edition as the relative path does not work:

File type attributes

Upload Datasource activity

Text search activity

Upload and Import activity

Workaround: The recommended approach to build TIBCO MDM projects and work with these specific activities is to use TIBCO® MDM Studio.


Summary: When you push an Integration application that contains a binary shared module to the cloud, the application does not start.

Workaround: None.


Summary: After a Mock app is replaced by an Integration app, the API specification associated with this Mock app doesn't appear when creating another Mock app from the Create App screen.

Workaround: Create the Mock app from API Modeler's API spec list.


Summary: After pushing an app, the status icon of the app will still appear red.

Workaround: Refresh the page.


Summary: Moving applications from one sandbox to another is sequential. You can only move one application at any given moment of time.

Workaround: None


Summary: When moving an application to a different sandbox, the endpoint URLs may show up twice.

Workaround: Refresh the page to remove the duplicate entry (note that both endpoints are identical)