Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • Manoj Chaurasia
    What?s New 
    Develop/TIBCO Flogo®
    Set-Cookie Header in InvokeRESTService Output: 
    For the InvokeRESTService activity, the Set-Cookie header is now available in the output headers.
    Improved User Experience While Importing an App: 
    A completely revamped user experience for importing an app has been introduced in this release. You can now use a drop-down list and the Search field to narrow down the flows, triggers, and connections displayed. 
    Timer Trigger Enhancements:  
    Use the Timer Trigger to set a cron job that executes a flow at fixed times, dates, or intervals. You can build a cron expression manually or use the Cron Expression Builder provided. 
    When running a flow multiple times at a specified interval, you can now delay the first execution of the flow using the Delayed Start option. Subsequent runs of the flow are triggered at the scheduled time interval. 
    Additional Trigger Output Parameters in REST Trigger:
    For the ReceiveHTTPMessage trigger, on the Map to Flow Inputs tab, the requestURI and method trigger output parameters are now available for mapping.
    NOTE: For existing triggers, you must click Sync Schema to make the requestURI and method parameters available to the flow input. 
    Support for PATCH Method in REST Trigger: 
    The ReceiveHTTPMessage REST trigger now supports the HTTP PATCH method. 
    Additional Flow Details in Mapper
    Flow details such as current flow name, ID, whether the flow is called as a sub-flow,  parent flow name, and parent flow ID are now available in the mapper. These details can be used for logging as well as activity mappings.
    New Mapper Functions
    The following mapper functions are included under the Data category: 
    GetValue: Gets the value of the function from the mapper reference. When undefined, the default value is used.
    isDefined: Checks whether the mapping reference is available and returns a True or False response.
    Support for Configuring a Server or CA Certificate in SendMail Activity
    When a secure connection type is set to SSL, you can now upload a server or CA certificate to be used for the SSL connection.
    Integrate/TIBCO BusinessWorks?
    Added support for handling nested multipart/mixed MIME parts as responses for Send HTTP Request activity.
    Binary project support for custom xpath function project: BW design-time providing support to create binary project from Custom Xpath function project. So that it can be added as module dependency.
    Added support for new log details in SmartMapper: For a better user experience, more details have been added in the logs for SmartMapper.
    Added support for Custom Xpath function using TIBCO ActiveMatrix BusinessWorks Plug-in for Maven: This release adds support for Custom Xpath function as a module dependency in pom.xml using TIBCO ActiveMatrix BusinessWorks Plug-in for Maven.
    Develop/TIBCO Flogo® Connectors
    TIBCO Flogo® Connector for PostgreSQL Database 
    The connector now supports connectivity to Greenplum and Amazon Redshift. 
    Integrate/TIBCO BusinessWorks? Plugins
    We have updated connectivity for the following plug-ins: 
    Confidentiality - New in TIBCO Cloud Integration!
    Changes in Functionality
    Develop/TIBCO Flogo®
    Validations for Fields with Restrictions in JSON Schema: 
    Flogo now validates fields that have restrictions defined in the JSON schema. An error message is displayed if invalid values are entered. 
    Improved User Experience While Importing an App: 
    A completely revamped user experience for importing an app has been introduced in this release. You can now use a drop-down list and the Search field to narrow down the flows, triggers, and connections displayed. 
    Change in Format of formatDatetime() Function
    The format of the formatDatetime(<datetime>, <format>) function has changed to the following:
    The format is case-sensitive.
    For example:
    TIBCO Cloud? Integration - Connect
    Third-party TIBCO Scribe Online Connector developers should note that the list of .dlls installed on an agent is changing with this release. For the updated list, see TIBCO Scribe Online Connector Certification & Release on the TIBCO Support site. (SCISV-255)
    The backlog of queued messages for a Request/Reply flow is limited to 100 messages. When the queue contains 100 or more unprocessed messages, the system generates errors with HTTP Status Code 429 and does not accept any more messages in the queue. When enough queued messages have been processed, new messages are accepted again. (SCCORE-1475)
    TIBCO Cloud? Integration - Connect throttles the number of inbound messages processed by the agents to 20 messages per batch for both the Connect cloud agent and the Connect on-premise agent. When the batch is complete, the agent requests another batch of messages until the Message Queue is empty. (SCCORE-6532)
    If the Flow designer is left idle for more than 30 minutes, any changes to the flow are saved automatically and you are logged out of the system. The revision of the flow that is auto-saved is marked in the Revisions dialog with the comment: Flow autosaved due to an inactivity logout. The last revision of the flow with this comment represents the latest auto-saved flow. The next time you open that flow, a message displays to alert you that it was saved automatically. (SCCORE-7655)
    If scheduled maintenance is in progress and the software being deployed involves changes to the Agent, Agent installations are temporarily disabled and a message similar to the following is displayed: 
    Agent installs are disabled temporarily. Check the TIBCO Cloud Services status page for more information. 
    Once maintenance is complete, you can install Agents as needed. (SCCORE-7704)
    Cloning large apps using the TIBCO Cloud Integration - Connect API sometimes generates HTTP Status Code 504 Gateway Time-out errors even though the server was not busy. (Case # 01942975, 02035644)
    To address this issue we have added a new API method that clones apps asynchronously. The clone is created in a thread and, using a second method, the status of the clone command can be polled.
    POST ?/v1?/orgs?/{orgId}?/solutions?/{solutionId}?/cloneAsync
    GET ?/v1?/orgs?/{orgId}?/solutions?/{solutionId}?/cloneAsync?/{cloneId}
    Note: The existing POST ?/v1?/orgs?/{orgId}?/solutions?/{solutionId}?/clone method will be deprecated in a future release. Best practice is to begin using the new API methods to clone apps as soon as possible. (SCCORE-6824)
    Deprecating for Development
    Develop/TIBCO Flogo® Connectors
    TIBCO Flogo® Connector for Amazon Redshift
    The TIBCO Flogo® Connector for Amazon Redshift is deprecated as of the TIBCO® Cloud Integration March 2022 release. (WIARSF-213)
    With this release, access to the Amazon Redshift connector will still be available and current users will remain connected. There is currently no end of life date, however, the best practice is to use the TIBCO Flogo Connector for PostgreSQL to connect to Amazon Redshift. 
    The PostgreSQL will provide all capabilities of the existing TIBCO Flogo Connector for Amazon Redshift. To migrate follow the steps mentioned below:
    Create a new connection using the PostgreSQL connector. Choose Redshift as the database type.
    Within your flow(s), you can now replace your Redshift activities with the corresponding PostgreSQL activities and select the connection created in the previous step.
    Feature requests for connecting to Amazon Redshift will only be considered for the PostgreSQL Connector.
    TIBCO Flogo® Connector for Greenplum Database
    The TIBCO Flogo® Connector for Greenplum Database is deprecated as of the TIBCO® Cloud Integration March 2022 release. (WIGPLM-118)
    With this release, access to the Greenplum Database connector will still be available and current users will remain connected. There is currently no end of life date, however, the best practice is to use the TIBCO Flogo Connector for PostgreSQL provided with your subscription to connect to Greenplum Database.
    The PostgreSQL will provide all capabilities of the existing TIBCO Flogo Connector for Greenplum Database. To migrate follow the steps mentioned below:
    Create a new connection using the PostgreSQL connector. Choose Greenplum as the database type.
    Within your flow(s), you can now replace your Greenplum activities with the corresponding PostgreSQL activities and select the connection created in the previous step.
    Feature requests for connecting to Greenplum Database will only be considered for the PostgreSQL Connector.
    Closed Issues
    TIBCO Cloud? Integration
    The following error is displayed when trying to enable API access for the child organization using the OAuth access token from the parent organization.
    Error: API access is disabled.
    Develop/TIBCO Flogo
    When using the TIBCO Flogo PATCH method in conjunction with TIBCO Cloud MESH, the InvokeREST activity does not retrieve the body element, preventing anything from being mapped to that element.
    After the upgrade, the "Auto Create PushTopic" field changes to True even though before the upgrade it was set to false.
    Apps designed in 2018 or before having Triggered flows, cannot be exported from the User Interface.
    Develop / TIBCO Flogo Connectors
    TIBCO Flogo® Connector for Snowflake
    Entering invalid connection details including an invalid warehouse, database, or schema name, does not generate an error. 
    Configuring a flow for Snowflake that contains an Insert with multiple rows of data generates an error at design-time, but executes successfully at runtime.

    Manoj Chaurasia
    Welcome to TIBCO Cloud? Integration
    TIBCO Cloud? Integration offers capabilities matching users of various skill levels, so you can quickly connect cloud apps, build hybrid integration flows across on-premises systems, and develop microservices and IoT edge applications. Using an intuitive drag-and-drop and API-led design approach, and a deploy-anywhere model, our enterprise iPaaS can get your apps connected more quickly and easily than ever before.
    This page is a quick start guide for users who are looking to interconnect everything and everyone. Any data, any system, any device, any technologies can be connected and leveraged in new developments of applications, processes or APIs. The capabilities covered in this page are:
    Connect (powered by TIBCO Scribe) Integrate (powered by TIBCO BusinessWorks) Develop (powered by TIBCO Flogo)   Key Purpose of This Orientation
    This orientation provides new customers with a variety of recommendations to quickly move from first login to first implementation.
    You will gain three types of benefits:
    Guidance on getting access to your products and setting them up Recommendations and best practices for starting usage Awareness of the many additional resources available to help you and your organization achieve your goals If you have questions along the way, use the Q&A section below.

    Let's get started!
    Step 1. Gain Access
    TIBCO Cloud? makes it easy for users to create a central set of services to manage accounts, manage teams, and purchase domains with a single sign-on TIBCO Cloud account.
      Fulfillment & Access
      There are 3 steps to get started with TIBCO Cloud:
    Sign Up by either: Starting a Trial Buying a subscription using a credit card Subscribing as part of a Purchase Order Activate your TIBCO Cloud Account: Receive Welcome Email Notification (sent to the account owner / administrator). Click on the Activate button in email to set up the account. Sign In to TIBCO Cloud. Create a team to delegate administration. Once you have enabled access to TIBCO Cloud, sign in and do the following: Review your Subscriptions Click on the Integration icon on the Home tab to get started using the feature.
    If you have any questions or issues while setting up your access to TIBCO Cloud, please reach out to TIBCO support here:
    Step 2. Use the Product
    TIBCO Cloud Integration provides a tailored experience for different use cases and personas whether you are a Citizen Integrator / Business Analyst connecting two SaaS business applications; an Application Developer developing custom applications and microservers; or an Integration Specialist integrating enterprise applications across on-premise and cloud deployments. To quickly enable your work:
    Click on one of the personas below and we will guide you through using the TIBCO Cloud Integration capabilities to best meet your skill set and your requirements. Access documentation, product resources and more TIBCO Cloud Integration PersonasConnectIntegrateDevelopManagePowered by TIBCO ScribePowered by TIBCO BusinessWorksPowered by TIBCO FlogoTIBCO Mashery       
    Citizen Integrator / Business Developer

      Integration Specialist     
      Application Developer   
      API Program Manager Documentation, Product Resources and Community
      Go to for comprehensive documentation on all products For documentation on individual TIBCO® Cloud Integration capabilities, go to: Connect (powered by TIBCO Scribe) Integrate (powered by TIBCO BusinessWorks) Develop (powered by TIBCO Flogo) Release Notes

    Product Resources
      Emerging use cases for Cloud Integration TIBCO Cloud Integration Security Overview Datasheet for TIBCO Cloud Integration The Forrester Wave?: the Strategic iPaaS And Hybrid Integration Platforms, Q1 2019 Community Access
      Answers - Read, Ask and Answer Article - Read, Learn & Contribute Exchange - Extend & Build Ideas - Suggest & Influence Documentation - Learn from TIBCO Step 3. Summary & Next Steps
    The purpose of this page has been to orient new customers of TIBCO Cloud Integration to the extensive amount of resources to get you started and be successful on your digital transformation journey.
    As a summary:
    Set up access for you and your team to TIBCO Cloud Ensure that you have the right capabilities and features enabled Begin work using the desired Integration capability based on your user persona or use case Setup your access to the TIBCO Support Portal so you can submit a support request to get help with any issues Use the Community Q&A if you need questions answered or use the ideas portal to submit any proposals

    Manoj Chaurasia
    What?s New 
    Our new TIBCO Cloud? Integration - Hybrid Agent extends App Monitoring to include your remote apps. Along with aggregated stats on the Dashboard  and the App Peek view in the Apps List, the agent  provides app execution metrics on the App Details view.  The Hybrid Agent can be downloaded, configured, and run on-premises or in the private cloud where it automatically connects to the TIBCO Cloud Integration environment. Remote TIBCO BusinessWorks and TIBCO Flogo apps can be registered with the Hybrid Agent on startup allowing them to be monitored. 
    TIBCO Flogo®
    In Flogo, when using the Mapper you can use the output of an activity generated by the last iteration as an input for the next iteration. You can see this output as part of ?Upstream Output?. For example, assume  you have a loop with three  iterations. In iteration zero you there is no value from that output because the activity has not run yet, but on the next iteration you can access the output of the activity from the previous run. App version support - The TIBCO Cloud Integration user interface displays app versions that can be modified at any time. When a new app is created, the default version displayed is 1.0.0. Automatically generated HTTP response, return activities and mapping configuration - When creating triggers and flows from an API (Swagger) specification, the app's Configure HTTPResponse, Return activities, and mappings are now automatically configured. Additional configuration fields for the "Send email" activity - Input fields have been added to the "Send email" activity to support HTML body and CC/BCC configuration. TIBCO Flogo® Connector for TIBCO Cloud? Messaging
    TCMMessageAck has been added to the connector with the following modes:  Auto: messages are auto acknowledged as soon as they are received from the TIBCO Cloud Messaging service. Explicit: messages can be acknowledged by using the new activity TCMMessageAck within the flow. The MessageSubscriber trigger now supports standard durables. TIBCO BusinessWorks?
    For newly pushed BusinessWorks apps, users can see the app version in the App Details page. This is a read-only value.
    TIBCO BusinessWorks? Plugins
    HL7 with FHIR  Added the following resources:  List , MedicationKnowledge,  Endpoint. Refer to the release notes for the plugin for more information.  MongoDB SWIFT TIBCO Flogo® Connectors
    Amazon DynamoDB Amazon Kinesis Hubspot Microsoft SQL MQTT Oracle MySQL PostgreSQL Salesforce TIBCO Cloud AuditSafe TIBCO Cloud Messaging Changes in Functionality

    TIBCO Cloud Integration
    The new Apps List Deployment column indicates where an app is deployed. In this scenario the agent/deployment definitions are as follows: A TIBCO Cloud deployment indicates that apps are executed in the  TIBCO Cloud. A Hybrid deployment indicates that apps are executed on a server that is not managed by TIBCO. This can be a local server or other infrastructure.  None indicates that the app has been configured in the TIBCO Cloud but is not running.  TIBCO Cloud Integration - Connect apps with an Incomplete or Disabled status are not included in App Totals on the Dashboard. 
    TIBCO Cloud? Integration - Connect Agent
    TIBCO Cloud Integration - Connect Agents displayed on the Agents page have been renamed as follows: 
    Cloud Agent is now Connect Cloud Agent On-Premise Agent is now Connect On-Premise Agent
    TIBCO Flogo
    When a Flogo app is created from a Swagger API specification, Flogo REST Trigger and flows are now auto-configured with trigger and flow input/output mappings and, wherever applicable, with Return and Configure HTTP Response activities.

    Migration and Compatibility
    TIBCO Flogo®  Connector for Amazon DynamoDB
    After importing a Flogo app into TIBCO Cloud Integration that uses a Flogo Connector for Amazon DynamoDB Query activity, the Output Schema in the OutputSettings section is empty and you will need to reconfigure the schema. Add row populates the cached state of variable/s in the table. Add a space in the Query section to prevent this issue. 
    TIBCO Flogo®  Connector for Salesforce
    For older apps imported with the latest Salesforce connector version, users can see one more new field in the Salesforce connection,  "WI_STUDIO_OATH_CONNECTOR_INFO".

    TIBCO Flogo® Connector for Salesforce Einstein Analytics
    Salesforce connections with Custom OAuth2 Credentials set to True are not supported for the Salesforce Einstein Analytics connector.

    Closed Issues
    IPAS-10417 / FLOGO-5311
    The implementation of a TIBCO Flogo® app cannot be viewed in TIBCO Cloud Integration when deployed using the TIBCO CloudTM? Command Line Interface.
    Added the option --impose for the app push command in the TIBCO CloudTM? Command Line Interface, which allows you to push an app without receiving an overwrite warning for an existing app with the same name. 
    The description for Custom Environment variables can not be updated.
    The Replace application dialog refers to TIBCO BusinessWorks as bw.
    Searching for a Connection by name on the Connections page using an underscore (_) brings up Connection names that do not contain an underscore.
    In TIBCO Cloud Integration - Connect a user who is not an Admin cannot unlock a flow that they locked. 
    Summary: In TIBCO Cloud Integration - Connect the Copy Error option on the Execution History Details dialog does not copy the error to the clipboard. 
    Subscription errors are not generated for Node.js apps when attempting to increase the number of instances beyond the limit of a trial plan. 
    The app password property is not updated in the user interface after the app is pushed from the TIBCO Cloud Integration - Command Line using the -r option. An error similar to the following is generated: Detail: Error while encrypting the app id '<app id>' properties overrides with privacy service: Error while re-encrypting one or more overrides properties for appId '<app id>': see logs
    When the browser language is set to a language other than English (United States), TIBCO Cloud Integration - Connect users cannot configure a run date on the App Details Schedule tab. 
    When an app in a failed state switches to a running state, the last started date on the App List page is not updated.
    The data in the columns on the View Statistics dialog for TIBCO Cloud Integration - Connect Data replication apps does not display under the correct column heading. Data should be displayed in the next column to the right.
    After a TIBCO Cloud Integration upgrade users have to clear their browser cache and cookies to display the User Interface correctly.  Occurrences of this issue have been reduced and are being monitored. 
    Sometimes when switching to a different Organization, the objects for the Organization do not display and require the use of an Incognito or Private browser window to resolve the issue. 
    TIBCO BusinessWorks client for TIBCO Cloud Mesh fails in Debugger at runtime when the TIBCO Cloud Mesh Service is running in the European or the Australian region. 
    Test connection hangs for users with multiple organizations because currently the AuditSafe plugin does not support multiple organizations.
    While mapping arrays, validation errors are displayed on the UI when the source array comes from a fixed array child such as: $flow.input[0].test.arraysource.
    The application/xml response is not supported in Flogo. Any method that produces an application/xml response is omitted when configuring a service from TIBCO Cloud Mesh in the Invoke Rest Activity.
    When a Flogo app is pushed, COPY, REPLACE, and Set endpoint visibility options are not available in the menu.
    If an app-level schema is attached in the request or response schema of the  AWSAPIGatewayLambda trigger, the API gateway is not created.
    If you do not click the Save button while configuring an activity and then move to Flow Inputs & Outputs Tab, the flow is greyed out.
    In the input and output of a flow, if you change the parameter type and then select another type as Required, the parameter type changes to the previous type again.
    You cannot import the tester launch configuration. The following error is displayed: Configuration already exists.
    After importing an app enabled for service discovery from the TIBCO Cloud Mesh, if you only reselect the service name to reconfigure the new service, a 404 Resource Not Found error is generated.
    The Send Email activity is not working with Office365 mail server.
    For Flogo, if a Producer service and a Consumer app both are imported into a new environment, the Service name is not changed in the InvokeRest drop down and nor is it showing any error because the Producer Service is available. Directly pushing the consumer app and invoking the private endpoint service gives an error.
    The Add row option is present for path parameters, which causes confusion because the path parameters cannot be added from Input Settings.
    App level schema is not available for the Request/Response for Plain/text, application/xxx-urlformEndcoded and Other types, because they have default non-editable schemas.
    For any old REST triggers where the API Specification upload feature is not enabled, adding a new handler fails.
    At runtime, the Flogo engine generates an error when an app property is configured with the "Delay" field in "Repeat Until True" loop.
    In Flogo, users cannot map empty arrays in activity mappings.
    Some privately managed connectors hosted in the TIBCO Cloud Integration Azure environment do not display in the Connections tab for Connect Apps.

    Manoj Chaurasia
    What?s New 
    This update is a maintenance release to close a couple of Known Issues and to provide you with some important updates. 
    We have improved the use of session cookies to address issues where some users received  a ?Bad Request? message from TIBCO Cloud Integration and were required to delete cookies or use an Incognito Window to continue. (IPAS-15162)
    Closed Issues
    TIBCO Cloud? Integration - Connect Agent logs cannot be downloaded from the user interface. 

    Manoj Chaurasia
    What?s New 
    TIBCO Cloud? Integration
    TIBCO Cloud Integration now has an updated dialog for Creating and Importing Apps! This new dialog is designed to provide users with recommendations for which Integration App types are available based on the desired use-case and subscription. The dialog also includes the following new features:
    A list of each supported App type by use-case A recommendation of the optimal App type choice by use-case Importing an App (or template) from the Marketplace Creating a new application by importing an exported App, Node.JS app, OpenAPI Specification, or importing a GraphQL Schema Ability to remember and present your commonly used App types For example, if you want to build an API, you are provided a list of App types that support this use-case. The recommended App type is to import an existing API Specification from your organization and generate an App. (IPAS-19235)
    See Creating an App in the online help.  
    Develop/TIBCO Flogo®
    Improved user experience for creating and importing an app TIBCO Cloud? Integration now provides an improved and unified experience for creating and importing an app.
    Develop/TIBCO Flogo® Connectors
    TIBCO Flogo® Connector for Apache Kafka
    We have updated connectivity for the following connector:
    Apache Kafka Integrate/TIBCO BusinessWorks? Plugins
    We have updated connectivity for the following plug-ins:
    Files for Unix and Windows Twitter Changes in Functionality
    TIBCO Cloud? Integration
    When adding a new item to a Lookup table, the user's selection remains on the first row of the first page of the table. New data is not sorted until you move to a new page using the arrows at the bottom, you close and reopen the dialog, or you click the Sort icon next to the Value 1 column. Note that the Sort icon is only enabled when a new item is added and takes you to the top of the first page of the list of items. Data is sorted in binary order, for example, 1, 11, 12, 2, 20, 3. (IPAS-18188) Develop/TIBCO Flogo®
    When mapped to the Return activity, Response headers are honored by the ReceiveHTTPMessage trigger. You must repush existing apps to pick up  the runtime changes. Change in location of expand or collapse option in mapper 
    In the mapper, the option to expand or collapse the tree has been moved from the right to the left. 
    Handling connections while importing an app 
    When importing an app, if the connection with a matching name and type existed in the environment, the Connections in the current environment drop-down is set to the existing connection by default. Prior to this release, the Connections in the current environment drop-down was set to create a new connection even if the connection used in the app existed.
    Closed Issues
    TIBCO Cloud? Integration
    In some cases, TIBCO BusinessWorks? Apps stopped while scaling or failed to start and generated an Application Container Error.
    TIBCO Cloud Integration BusinessWorks hybrid app fails to start when connecting to on-premises EMS.
    When you update the password properties of a Node.js copied app, password properties are not decrypted in the response.
    In some cases, Hybrid Agents using Hybrid Proxy connections do not log auto-discovery of remote on-premises apps and app instance ids in the associated log file.
    Develop/TIBCO Flogo®
    When opening a flow, validation takes a long time to complete.
    When using the TIBCO Flogo PATCH method in conjunction with TIBCO Cloud MESH, the InvokeRESTService activity does not retrieve the body element, preventing anything from being mapped to that element.
    For a valid running Timer trigger that has a Repeating set to True and a valid app property or calendar entry for the Start Time, if you bind an invalid app property and push the changes, you can still view or get the logs from an earlier run. The logs are executed based on conditions set in the earlier run.
    On unbinding an app schema from the request schema, the Save button is disabled.
    Newly added User Interface configurations for any activity, trigger, or connection do not reflect in the existing apps after a production refresh.

    Manoj Chaurasia
    What?s New 
    TIBCO BusinessWorks? Plugin Updates
    HL7 with FHIR Large XML LDAP OData Closed Issues
    If the application with an LDAP listener was scaled up or down, the listener used to receive all the records that were earlier published from LDAP.
    The Input and Output tabs were restored to the CDSServices PatientView activity. 
    HAPI libraries were updated from version 3.7.0 to version 4.1.0.

    Manoj Chaurasia
    What?s New 
    We've added new features and some updated Connectivity.
    Hybrid Agent - now provides the streaming functionality for logs, giving you one download to provide monitoring, connectivity, and streaming of logs making it easier to use TIBCO Cloud Integration. This feature also provides communication with on-premises resources for apps running in the cloud, for example databases, etc. App Tagging - Allows you to define and apply tags to any app type and use those tags for filtering. For example, a tag could be created based on the type of app, such as ecommerce apps, or by department, such as Sales, to group them together. App tags are created on-the-fly as you configure an app. (IPAS-15114, IPAS-15115) Develop - Organization-Level Connections - Previously, Connections were saved at the user level. Now they can be promoted to the organization level where they can be used across different Develop apps by more than one user in the organization. This makes it easier for the users in the same organization to work together. (IPAS-11964) Develop / Integrate - OAS 3.0 Support - OpenAPI Specification 2.0 was previously supported. OAS provides a standard OpenAPI Specification (formerly Swagger Specification) as an API description format for REST APIs. An OpenAPI file allows you to describe your entire API. This allows TIBCO Cloud Integration - Develop to provide this definition for endpoints as a starting point for a flow. (IPAS-15043) Supplements - Improved Supplement management with a new Supplements page under Environment & Tools, which displays a list of supplements and associated connectors. You can also upload Supplements from the User Interface instead of the Command Line Interface. (IPAS-13967, IPAS-15099) Agent info icon - On the Agents page, Hybrid Agents now have an info icon that displays the names and the number of remote apps registered with that agent. (IPAS-14828) TIBCO Cloud? ? Command Line Interface
    The following new commands and options were added: 
    Added an option to filter the app list by one or more app tags. (IPAS-15253) 
    Example: tibcli app list --tag apple --tag orange
    The app copy command also copies app tags associated with the source app. (IPAS-15325) The app delete command removes the association between the app and any tags linked to that app. (IPAS-15326) TIBCO BusinessWorks? 
    The Export to Consul check box and tokenization button are now available for Cloud edition projects. (AMBW-40796) Added support for the credential management system for application properties that are type password in TIBCO Cloud projects. (AMBW-41184) TIBCO Flogo®
    The SendEmail activity now supports: Sending file attachments Setting Reply-To configuration Using the enhanced Flow Tester, you can: See the flow execution and the progress made in the execution of the flow. In the new Flow Tester interface, when an activity is being executed, a blue animation is displayed around it. See errors displayed at the activity-level. Select an activity after its execution to see the inputs and outputs. Change the inputs to other valid values and start the execution of the flow from that point onwards. When you import an app that contains one or more activities or triggers that are not installed in your environment, a warning is displayed in the Import App dialog but you can still import those activities and triggers. Activities and triggers with a missing extension display an error until you upload the extension.  Database connectivity For all complex queries that needed manual mode, metadata generation is significantly enhanced to use standard query parsing leading to a better user experience. Secure connection support for TIBCO Flogo® Connector for Microsoft SQL Server, TIBCO Flogo® Connector for PostgreSQL, and TIBCO Flogo® Connector for Oracle MySQL is now provided. For the TIBCO Flogo® Connector for TIBCO Cloud? Messaging, the MessageSubscriber trigger now supports standard durables. (FGTCM-26, FGTCM-16)  TIBCO Flogo® Connectors
    Amazon Kinesis Apache Pulsar (New) Data Conversion HubSpot Microsoft SQL Server Oracle Database Oracle MySQL PostgreSQL TIBCO BusinessWorks? Plugins
    Amazon SQS and SNS Apache Cassandra Apache Kafka Microsoft Dynamics CRM MongoDB OData SAP S/4 Hana BusinessWorks? Plug-in for Apache Cassandra
    Connection Pooling for Shared Resource Connections - Apache Cassandra connections are pooled in memory. Each Shared Resource establishes and stores two TCP connections in a single pool connection to the Apache Cassandra database, regardless of the number of activities using the resource. The exception is for Get Cassandra connection, which creates a new connection every time it is invoked.
    Changes in Functionality
    TIBCO Cloud? Integration - Hybrid Agent
    The tibagent configure monitor command used to configure the Hybrid Agent has been changed to tibagent configure agent. (IPAS-15919)
    TIBCO Flogo®
    You can no longer see the output of a Flogo flow in the debugger logs. (FLOGO-6438) For database connectors, metadata populated in the table now displays generic data types. (WIDBSV-394) Tools
    The TIBCO® Cloud - Command Line Interface commands for log streaming and access to on-premises systems have been moved to the Hybrid Agent. To use the logStream command to stream app logs, see Installing, Configuring, and Running the Hybrid Agent in the TIBCO? Cloud Integration documentation. (IPAS-15212)
    Important: You can continue to use the existing  TIBCO Cloud? ? Command Line Interface, but if you download the latest TIBCO Cloud? ? Command Line Interface these commands are accessed via the Hybrid Agent.  
    Closed Issues
    If using a MongoDB connection shared resource, use a host port number between 1024-9999.
    In the Swagger API test page, TIBCO Flogo® apps with REST trigger  with Response Codes set to True do not display all response headers in the Swagger UI. 
    When using the app list or app detail command from the TIBCO Cloud?? Command Line Interface, the information returned displays N/A for the app version number.
    When apps are pushed or re-pushed using the TIBCO Cloud? ? Command Line Interface and TIBCO Businessworks Studio, the status "Scaling" is never shown on the User Interface only the "Running" status is displayed. 
    Occasionally, the total number of log messages displayed on the App Details Logs tab is incorrect.
    Added a Copy button to the App List Status Details popup to copy the contents of that popup to the clipboard.
    In App Details on the Logs tab, when selecting a custom date time filter the am/pm portion of the date/time field is not updated correctly. This issue affects both the log filters and the download logs dialog.  
    In some cases, the App Peek option is disabled on the Apps list for apps with an error status. 
    Empty apps created prior to the May 2020 TIBCO Cloud Integration upgrade do not display in the Apps list, however, because they still exist their names cannot be reused in a new app. 
    App name is displayed instead of organization  name when a BusinessWorks app is copied in TIBCO Cloud Integration. 
    Updates to app names sometimes do not display on the Apps List page immediately.
    In some cases, if you reconfigure a BusinessWorks  app such that some app properties are deleted, when repushing the app an error similar to the following is generated that references the deleted properties.  Detail: Error while updating application configuration : Cannot override properties because one or more of those properties is not set for that application. 
    If you reset metadata for a Connection used in a TIBCO Cloud Integration - Connect Data replication app and the data set returned is very large, when you open the Manually Selected option in the app to select the entities for replication, the dialog is blank.
    If you select an access key for a Hybrid Database Connection, the user interface does not allow you to immediately choose a different one.
    The Hybrid agent executable, tibagent.exe, does not run on a Windows platform if the debug option is used. 
    A Cloud app and a Remote app could end up with the same name and both display on the Apps List page.
    The App list and Environment & Tools pages do not store user preferences when the  Hybrid filter is selected. When you leave one of those pages and return, the page is refreshed. 
    In the App Details Monitoring tab, the ?Last 2 hrs? filter is selected by default. If no app executions have occurred since the latest TIBCO Cloud Integration upgrade, no data is shown on the graph. Execution data for the last 24 hours can be displayed only when the ?Last 24 hrs? filter is selected.
    When users attempt to log in through the TIBCO Cloud? ? Command Line Interface and set the HTTP_PROXY or HTTPS_PROXY environment variables, the TIBCO Account server generates an error and does not allow the user to log in.  
    In some cases where the volume of errors is very large and may not have been synchronized with the Cloud, Execution History cannot display failed records or Error details.
    The Connections page only displays a maximum of 100 Connections. 
    The output of the "current-dateTime()" function is not the same when the function is used in TIBCO Cloud Integration  and TIBCO Business StudioTM.
    While adding elements in the array.flatten() function, the mapper becomes slow and the page becomes unresponsive after some time.
    When creating a new trigger, you cannot use the Bind an application property button to bind a property to the port.
    After  the May 2020 TIBCO Cloud Integration upgrade, the names of some existing connections are not displayed in the connection list.
    In TIBCO Flogo, sometimes the datetime.currentDate() cannot be formatted or parsed  by the datatime.parse or datatime.formatDate() function.
    FLOGO-6020 / IPAS-13949
    App Details tabs become unresponsive after clicking the Monitoring tab for Flogo apps that only have a trigger without activities in the flow.
    Multiplying a float64 with a json.number generates a runtime  error when using a multiply operation in mapper for the number field.
    For DBConnectors (MySQL,Postgres, SQLServer,Oracle) when manual mode is switched to true, if you enter a query and click the fetch button, the table is populated with metadata. After that, when you click the Add row button, all previous metadata disappears.
     For database connectors with manual mode set to true, after you hit the "Clear Table" widget, the subsequent fetch query fails.
    After renaming a Flogo app, the app name field is not editable. 
    In the TIBCO Flogo Connector for Oracle Database, query parsing fails when a ROWNUM clause is present in the Select query.
    In the TIBCO Flogo Connector for Oracle Database, query parsing fails with a mismatch error when using a LIKE keyword for FLOAT and NUMBER data types.
    In the TIBCO Flogo Connector for Oracle Database, when the alias used in a query contains a period (.), only a part of the name is displayed in the table schema.
    In the TIBCO Flogo Connector for Oracle Database, query parsing fails when INSERT ALL is used.
    Metadata is not displayed under the ?Table Schema? field when connecting to an Oracle RDS database.

    Manoj Chaurasia
    One of the hardest and most time consuming parts of building and maintaining a migration or integration solution is providing accurate documentation. To help with this problem, we have released a documentation tool using Google Docs. With this tool, you can quickly and easily generate documentation all of your integrations. It produces a report that includes data about the TIBCO Cloud Integration organization, connections used and metadata from your solution, including filters, related entities, and field mappings for each map in the solution.
    Benefits of the Documentation Tool
    There are many potential use-cases for this tool. Here are some examples where the documentation tool would save significant time and/or effort:
    Project Documentation ? Create detailed documentation of an integration to demonstrate your progress or use as a final description of the work that you delivered (great for your boss or your client). Version Control ? Compare saved reports to find differences between solutions and maps over time. Branding and Customization ? Customize the report output to match your company image. You can change colors/backgrounds, add a company logo and more. Integration Maintenance ? Once your integration is up and running, you may need to change mappings. With this tool you can document your solution and quickly find all of the places where changes need to be made. Enable API Access
    Now that you have an idea of what the tool can do for you, let?s take a look at how to get started using it. Following the instructions on the Developer Portal, you can quickly set up the documentation tool to work with your organization(s).
    The first step is to enable API access to your organization(s). For each organization where you will want to use the documentation tool, simply go to the More > Security menu and look at the rules under the Security page. Click on the add button (+) and edit the new rule to give it a name, check off the API Access checkbox and add the following IP range:

    Once you?ve added the rule, it may take a few minutes to take effect in the documentation tool.
    Using the Documentation Tool
    Note: This set of instructions assumes you are in the AWS US East (N. Virginia) region. If your organization is in a different region or data center, see the documentation on the Developer Portal for information on updating the region in the Documentation tool. 

    The next step is to save a copy to your own Google Docs environment. Go to the Scribe Labs ? Google Docs ? Documentation Tool link from your Google account. Then click File > Make a Copy and save it. Once you have saved a copy, please close the Scribe Labs copy so that it is not changed.
    Now we have to connect to your TIBCO Cloud Integration account from the tool. Click on Scribe > Solution Documentation in the Google Docs menu. The first time you run it, you may get a pop-up asking for authorization. If you see that, click the Continue button and then the Allow button on the following screen.
    You should now see the TIBCO Cloud Integration login from your Google Docs screen:

    Then enter in your TIBCO Cloud Integration username and password and hit Submit. This will connect to your TIBCO Cloud Integration user account. Once the tool loads your account, select the organization and solution you wish to document:

    Finally, hit the Submit button again and it will begin documenting. Once the tool starts to run close the login window and you can watch the report being updated in real time.
    Upon completion, the first thing you should see is a tab called ?Org Details?. This tab will have information on the selected Organization in TIBCO Cloud Integration. Next there will also be a tab with information about the solution, including connections, status and scheduling information. Finally, there will be a tab for each map in the solution.
    For each map tab, the documentation tool will go through the map and give all the configurations for each block:

    You can see on the above sample the steps of the map documented, including mappings.
    Extending the Tool
    If you have developer resources available, you can also edit the code that runs the tool. From your copy of the documentation tool, simply click on Tools > Script Editor. Here you?ll find the code that runs the documentation tool, and you can make changes as needed. If you want to have a reference into the Scribe Online API, take a look at our Developer Portal. 
    First Published  May 02, 2017
    Author: Scott Hansen

    Manoj Chaurasia
    Operating with the speed, agility, and innovation of a digital business requires you to integrate applications and data quickly. The TIBCO® Cloud? Integration enterprise integration platform-as-a-service (iPaaS) accelerates the integration process. Using any integration style, empowers your people to quickly and easily connect their information assets no matter where they are. Connect cloud apps and hybrid integration flows across on-premises and cloud environments, develop cloud-native apps using microservices, and process IoT data on edge devices.
    To accelerate your digital business initiatives, your integration teams need the right tools to help them get their jobs done quickly and easily. The TIBCO® Cloud Integration iPaaS not only helps you accelerate the integration of all your applications, data, and devices, it?s more efficient and cost-effective than competing products.
    The TIBCO® Cloud Integration Enablement Hub is designed to get you skilled up quickly and easily, no matter what level of experience you have. There are videos split into sets: 
    , New Capabilities,   to help users across different levels and various needs.  Dr Integration Office Hours provides interactive presentations for helping new and advanced practitioners of integration and messaging. Platform Capabilities - TIBCO® Cloud

     TCI - New Customer Orientation
    This section is designed for new users looking forward to experiencing TCI. Try to familiarize yourself with the TCI platform before moving on to Active User engagement.
    TIBCO® Cloud Integration: New Customer Orientation
    This video provides an overview of the self-service resources that are available from TIBCO.

    Download the presentation, "getting_started_with_tibco_cloud_integration.pdf" from Resources below, and use it as a guide that contains links to the resources referred to in the video.

    Disclaimer: Digital Customer Success is in the pilot phase and all the customers may not receive the emails mentioned in the video. Please feel free to provide feedback in the comments section at the end of this page.
     Quickstart Demo
    These videos are designed for users with 0 hours of experience with TIBCO® Cloud Integration. This is 10 minutes in total duration. Learning by doing is the best way to retain knowledge. After viewing this content, be sure to try TIBCO® Cloud Integration for yourself before moving on to Fundamentals.
     (48:48) (9 Videos)  TIBCO® Cloud Integration New Capabilities
    This section is designed for users with over 5 hours of experience with TIBCO® Cloud Integration. This demonstration provides a general overview of the new capabilities introduced in TIBCO® CLoud Integration 2.0. Try to familiarize yourself with these new capabilities of TIBCO® Cloud Integration 2.0 before moving on to Active User.
    TIBCO® Cloud Integration Demo - New Capabilities in 2.0 (17:41)
     Fast Track Workshop
    The TIBCO® Cloud Integration platform-as-a-service (iPaaS) increases business agility and accelerates connectivity, but it also empowers users to play an active role in creating connections between apps, data sources, or devices in a cloud or hybrid environment. Users can make connections quickly without a significant underlying knowledge. With just a click, they?re on their way, connecting with confidence.
    Take this free workshop to learn how to solve common integration challenges with the help of an experienced TIBCO solutions engineer. In just 90 minutes you will be ready to get the most out of your TIBCO® Cloud Integration iPaaS.
     (1:44) Watch this video to see how the TIBCO® Cloud integration iPaaS impacts your entire business by empowering a wide range of users outside the IT department to quickly connect anything anywhere
    Take the first steps towards digital transformation and seamless connectivity across your applications, data, and devices? Learn more about TIBCO® Cloud integration to get started.
    Enable your business to adapt quickly to rapidly changing market conditions by evolving to a flexible and scalable application architecture that lets you reconfigure your digital platform to meet any challenge. Streamline processes, increase productivity and insight development, and transform the customer experience. 
    TIBCO® Cloud Integration: Getting Started with Develop Introduction to   (9:58) TIBCO®   (4:43) What's New in TIBCO®   (3:50) Connect
    Accessing, improving, and getting data to the right employees, channels, processes, and devices unlocks opportunities. Connect all your data sources?systems, employee apps and documents, customer touchpoints and devices, and partner and cloud applications?in the cloud, on-premises, or on-device with API-led integration. Enable developers and business users to build event-driven applications faster using new architecture patterns and low-code visual design tools to enable digital transformation.
    TIBCO® Cloud Integration - Getting Started with Connect TIBCO® Cloud Integration - Getting Started with Mashery TIBCO® Cloud Integration - Event-driven Architecture TIBCO® Cloud Integration Demo - What's New for Connect Users (6:58) TIBCO® Cloud Integration Demo - Introducti - on to Connect for New Trial Users (5:43)  (14:07)  (5:19) Integrate
    With TIBCO Software, you can easily connect to virtually any endpoint across your IT ecosystem with a wide variety of commercial and community developed connectors for modern business suites and platforms as well as legacy technologies. We offer 200+ connectors that are supported across the integration capabilities within TIBCO® Cloud Integration: Connect, Integrate, and Develop, as well as 200+ Enterprise SaaS/Cloud & App Adapters and 30+ NoSQL, RDBMS, and Data Warehouses that are supported within TIBCO Data Virtualization. Our broad connector portfolio allows you to focus more on developing business logic, and less on connectivity details.
    TIBCO® Cloud Integration: Getting Started with Integrate TIBCO® Cloud Integration Demo - What's New for Integrate Users (15:49)  (2:36)  (7:21)  (27:38)  (8:34)  (4:14) TIBCO® Cloud Integration - List of Connectors TIBCO® Cloud Integration Release Notes
    Vist this page to access release notes and Known Issues for TIBCO Cloud? Integration releases.
     Continue Your Learning
    There's tons to do in TIBCO® Cloud Integration! These are some of our favorite ways to continue your learning.
    TIBCO® Cloud Integration: How it works - DataSheet TIBCO Cloud? Integration iPaaS - Whitepaper Free Integration Knowledge Kit : TCI Outperforms the competition in integration time and cost TIBCO Mashery® API Primer Dr. Integration Office Hours Similar Articles
    TIBCO Cloud? Known Issues

    TIBCO Security Information

    Spotfire Enablement Hub Getting Started Videos


  • Create New...