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
  • Richard Flather
    This document will provide the steps necessary to build two separate Kubernetes environments with TIBCO Enterprise Message Service (EMS) utilizing TIBCO FTL for data storage. These two Kubernetes environments will be configured in different AWS regions. EMS Disaster Recovery (DR) will then be configured between regions. The examples in this document will help administrators understand how DR works in EMS/FTL on AWS EKS.
     
    Note: This document is designed around AWS Elastic Kubernetes Service (EKS), but can be used as a guideline for setting up EMS/ FTL DR in any Kubernetes environment.

    How to Configure EMS 10.2 with FTL Store for DR on AWS EKS V 1.1.pdf
    ems_aws_dr_1.1.zip

    Ana Bahr
    What's New

    TIBCO Cloud? Integration
    For Integrate/TIBCO BusinessWorks apps, now you can dynamically update app and  module properties if configured via Configuration or Credential Management Service provider using the new Refresh App Properties button on the App Details > Environment Controls > Engine Variables tab. (IPAS-14581)
     
    TIBCO Cloud Integration API
    Uploading SSL certificates when enabling  Execution History for TIBCO Flogo apps is supported by uploading the certificate as a base64 encoded string in the POST /v1/subscriptions/{subscriptionLocator}/exechist  request.  (IPAS-20849) The following methods have been updated to support the Pin, Unpin app feature for TIBCO BusinessWorks apps. Using a pin you can go back to a previous version of an app if necessary. (IPAS-21228) POST /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin DELETE /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin PUT /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin GET /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Develop / TIBCO Flogo
    In Flogo applications, if TLS is enabled for Opentelemetry protocol receiver, you can Encrypt base64 encoded certificate values by using either TIBCO Cloud Integration platform API or by using an app executable and set it the environment variable with the prefix  ?SECRET:?. AWS connection now supports Default AWS Credentials Provider Chain with authentication type as 'Default credentials'. Using the Run all test suites button, you can run all the enabled test suites in the unit testing feature. Also, you can use  the Run all test cases to run all the enabled test cases. (FLOGO-9683, FLOGO-9681) In unit testing, you can mock the data for an activity as part of a test case. (FLOGO-7641) The LogMessage activity?s LogLevel attribute can be assigned from a flow variable. (FLOGO-9810) Develop/TIBCO Flogo® Connectors
    AWS connection now supports Default AWS Credentials Provider Chain with authentication type as 'Default credentials'. This enhancement affects the following TIBCO Flogo Connectors:  (FLOGO-9803)
    Amazon DynamoDB Amazon EC2 Amazon Kinesis Amazon SNS Amazon SQS Amazon S3   TIBCO Flogo® Connector for DocuSign
    Added support for JWT Grant as an authentication type. (FGDUSN-42) Added support for multiple files in an envelope. (FGDUSN-43)  Added support for all document types supported by DocuSign. New activity DocuSignListDocument added to fetch details for single or multiple documents from an envelope. (FGDUSN-41)  TIBCO Flogo® Connector for Oracle Database
    TIBCO Flogo® Connector for Oracle Database has a new activity that allows calling stored procedures from Oracle database. (WIORA-299)
     
    TIBCO Flogo® Connector for Apache Pulsar
    The No Acknowledgement (NOACK)  activity has been added to send a negative ack to the Pulsar broker. (FGPUL-199)
      Integrate/TIBCO BusinessWorks?
    Users can now upgrade TIBCO Business Studio? BusinessWorks? from an existing installation using the new Upgrade Manager. To access the Upgrade Manager navigate to Help > BW Upgrade Manager. (AMBW-45217)
     
    Integrate/TIBCO BusinessWorks? Plugins
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Azure Cloud Services (Azure Data Lake Storage Gen2)
    The Azure Cloud Services (Azure Data Lake Storage Gen2) plug-in is supported for TIBCO Cloud Integration. The following features have been added in this release. (BWAZCS-7)
     Create Activity The plug-in provides a Create activity to perform Create File System, Create
    Directory, Upload Files, and Acquire Lease operations.
    Update Activity The plug-in provides an Update activity to perform the Update ACL and Update File
    operations.
    Read Activity The plug-in provides a Read activity to perform List File Systems, List Directories, Get Properties, and Download File operations.
    Delete Activity The plug-in provides a Delete activity to perform Delete File Systems, Delete
    Directory, and Break Lease operations.
    TIBCO ActiveMatrix BusinessWorks? Plug-in for BusinessConnect
    Added support for the BusinessConnect plug-in in TIBCO Cloud Integration.
     
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Google BigQuery
    Support for Bulk loading of data
    Loads data to BigQuery table from Google Cloud Storage with different file types such as AVRO, CSV, JSON, ORC, and PARQUET sheets that are stored in the drive. (BWGBQ-344)
    Support for authentication with OAuth 2.0
    You can now connect to Google BigQuery with the OAuth 2.0 authentication method. (BWGBQ-348)
    Support for merge operation in Data Updater Activity
    Merges updated or new records from the source table to the Target Table in Google BigQuery using the merge SQL operation. (BWGBQ-272)
    Support for delete operation in Data Updater Activity
    Deletes the records from the source table in Google BigQuery. (BWGBQ-331)
     
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Google Cloud Pub/Sub
    There are no new features in this release. 
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft SharePoint
    The Microsoft SharePoint plug-in now supports Basic Proxy Authentication with the help of Proxy Configuration and Identity Provider. (SPBW-1752)
     
    TIBCO ActiveMatrix BusinessWorks? Plug-in for OData
    In this release, the OData plug-in supports batch requests with UPDATE and DELETE operations as a client to external OData V4 services via the OData Batch activity in OData Palette. (BWOD-661)
     
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Oracle Fusion Cloud Applications Suite
    New Plugin
    TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle Fusion Cloud Applications Suite allows TIBCO ActiveMatrix BusinessWorks? customers to consume REST services and perform Create, Read, Update, Delete  operations for the ERP and HCM modules in Oracle Fusion Cloud, including support for batch processing.
    ActiveMatrix BusinessWorks Plug-in for Oracle Fusion Cloud Apps Connection Shared Resource
    With this feature, you can connect to the Oracle Fusion Cloud Applications Suite using either Basic Authentication or OAuth2.0 Authentication. (BWOCE-25)
    ActiveMatrix BusinessWorks Plug-in for Oracle Fusion Cloud Apps Palette
    The palette supports the Consume Oracle Fusion Cloud Apps Service Activity. This activity consumes the Oracle Fusion Cloud Service that is selected and downloaded. The activity supports DELETE, GET, PATCH and POST operations through the downloaded service. (BWOCE-26)
     
    TIBCO ActiveMatrix BusinessWorks? Plug-in for SMPP
    Support has been added to provide the ServiceType value from the Input tab of the SendShortMessage activity. (BWSMPP-146)
     
    Changes in Functionality
    Develop/TIBCO Flogo®
    FLOGO-9048
    Errors for the ReceiveHTTPMessage trigger are now shown at the Info log level.
    FLOGO-10022
    If the path parameter has a number or boolean data type in the API spec and it is mapped with a string type value then it shows design time validation error after upgrade. You need to manually update the mappings to match the data type of the path parameter.
      Migration and Compatibility
    TIBCO Cloud? Integration
    After transitioning from a Trial Organization to a Production Organization, you must log out and log back into TIBCO Cloud? Integration.  (IPAS-21524) 
     
    TIBCO Cloud Integration only supports the most recent version of the Hybrid Agent and one version back. The most recent version of the Hybrid Agent is version 1.7.0, and the prior Hybrid Agent was version 1.6.0.  If you have a Hybrid Agent installed that is older than version 1.6.0, you should install Hybrid Agent version 1.7.0. 
    Deprecating and End of Support
      TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft SharePoint
    The SharePoint SOAP palette has been removed from the TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft SharePoint in the SharePoint 6.4.0 release. (SPBW-1938)
     
    Closed Issues
      TIBCO Cloud? Integration
    IPAS-19746
    The name of the TIBCO Cloud Mesh service is not getting updated in the Service registry when the app is pushed from the TIBCO Command Line Interface with a modified name.
    TIBCO Cloud? Integration - Connect
    IPAS-19835
    After installing a new TIBCO Scribe Online Connector from the Marketplace the new connector does not display in the "Create a connection" dialog. 
    Develop/TIBCO Flogo®
    FLOGO-8147
    After editing an activity name, the branching label from source to destination activity does not show the updated activity name. It shows the default activity name instead.
    FLOGO-8774
    When an app is pushed from the TIBCO Cloud Command Line Interface (CLI) with a modified name, the name of the TIBCO Cloud Mesh service is not updated in the service registry.  
    FLOGO-8897 
    Path parameter of type number is converted to type string  when the ReceiveHTTPMessage trigger is configured with an OpenAPI spec. 
    FLOGO-9430
    String, number, and boolean types are supported in the ReceiveHTTPMessage trigger when configured with an OpenAPI spec.
    FLOGO-9807
    For unit testing, reconfiguring an activity in a flow that depends on a specific method, such as GET, can cause unit tests to fail if the unit test depends on the output of the selected method.  For example, if you use the shared data activity configured with the GET method, then under the Unit Testing tab you add assertions and run the test, the test runs successfully. If you later change the configured method to SET, the test fails because it depends on the output generated by the GET method.
    FLOGO-9818
    After importing an app with a primitive object array, the mapping for the array is lost and it is converted into array.ForEach.
    FLOGO-10054
    A Base64 encoded SSL certificate can be encrypted using either the TIBCO Cloud Integration API or an app binary and then passed as Engine variable:
    FLOGO_OTEL_TLS_SERVER_CERT=SECRET:<encrypted_base64_encoded_cert_value>
    To encrypt a base64 encoded value using an app executable see:
    https://integration.cloud.tibco.com/docs/index.html#Subsystems/flogo/flogo-all/encrypting-password-.html
    To encrypt a base64 encoded value using the TIBCO Cloud Integration API see:
    https://integration.cloud.tibco.com/docs/Subsystems/tci-api/utils/encrypt-values-fe.html
     
    FLOGO-10269
    In TIBCO Flogo flows, if OSS extensions, such as counter or error, are added from the Recently Used section, some activity tiles show as blank and the user interface becomes unresponsive.
    FLOGO-10427
    TIBCO Flogo apps that connect to Prometheus continue to use deprecated metrics, which consumes all available memory causing the app to stop running.
    Note: After the upgrade, you must regenerate app executables for any apps that connect to Prometheus to resolve the issue.
    TIBCO Flogo® Connector for Amazon Kinesis
    FGAZKS-64
    Added support to access Amazon Kinesis services privately through a Custom VPC endpoint.
     
    TIBCO Flogo® Connector for Amazon S3
    FGAZS3-149
    Added support to access Amazon S3 services privately through a Custom VPC endpoint.
     
    TIBCO Flogo® Connector for Amazon SNS
    FGSNS-39
    Added support to access Amazon SNS services privately through a Custom VPC endpoint.
     
    TIBCO Flogo® Connector for Amazon SQS
    FGSQS-70
    Added support to access Amazon SQS services privately through a Custom VPC endpoint.
     
    TIBCO Flogo® Connector for Microsoft Azure Service Bus
    WIAZSB-278
    When the connection and link are active but no calls (idle state) are made using the link for 10 minutes, the link is closed and cannot publish a message.
     
    TIBCO Flogo® Connector for Salesforce
    FGASFC-350
    When a user imports an app (app that is created on Salesforce version older than 1.3.2) in Salesforce version 1.3.3 and uses imported connection in the app, then the Update and Delete activities generate the following error: 
    "The requested resource does not exist".
     
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Google Cloud Pub/Sub
    BWGCPS-152
    SubscriptionActivity can now receive messages after the network has recovered from a failure.

    Dave Winstone
    1. Summary
    2. Building the BusinessWorks Container Edition Base Image
    3. Building the Application Container Image
    4. Deploying to Kubernetes
    5. Updating the Base Image
    6. Conclusion
      1. Summary
    In this article I want to show you how to upgrade the TIBCO BusinessWorks Container Edition runtime (the BWCE Base Image) for an application/microservice that is deployed in a Kubernetes environment and achieve a Zero Downtime upgrade, without having to rebuild your application EAR file etc. This will significantly reduce the time for you to upgrade your BusinessWorks Container Edition versions and also mean that much less testing is required as you are not changing any of your business logic and the application itself does not need to be rebuilt.
    I?ll be using a simple Greeting microservice that is a REST API that responds with a message, the container hostname and the BusinessWorks runtime version:


      Building the BusinessWorks Container Edition Base Image
    --> There?s lots of instructions and different examples of how to do this at TIBCO?s official github repo here that I?d recommend you take a look at.
    I?m going to start with my application built using version 2.7.3 of BusinessWorks Container Edition, then upgrade the runtime to 2.8.0.
    Once you?ve followed the instructions from the TIBCO GitHub to clone the BWCE repo and downloaded the BWCE runtime from TIBCO?s download site you are ready to build the base image using a command similar to the following from the cloned bwce repo:
    The first argument is the BWCE runtime zip file that you downloaded from TIBCO, and the second argument is the tag we?ll be using. You?ll notice that in my tag I?ve got an ip address and port, and that?s because I want to push this image to a registry ? in this case I?m using microk8s, so when the base image is built, I can push it to the registry using this command:
    Building the Application Container Image
    I?ll adjust my application Dockerfile to include the correct base image tag as follows:
    Now to build the application and push it to the registry too:
    Deploying to K8s (microk8s)
    To deploy my application to K8s, I need to create a yaml file that configures my application, creates a service and also defines the update strategy:
    To deploy the application from the command line, I can execute the following:
    When the application is ready (kubectl get deployments) you can test the application with a curl command (notice we defined the nodeport as 30092 in the yaml file):


    As we have 2 replicas created if we keep issuing the curl command we?ll see that both pods are responding:
    So ? we?re all good ? we have our microservice API up and running, and we?ve got 2 instances available and processing our messages. Now we want to keep the application running and update the base image to a new version of the container runtime.
    Update the Base Image
    To rebuild the base image to use v2.8.0 of BusinessWorks Container Edition, we first need to remove the bwce-runtime-2.7.3.zip from the resources folder under the cloned bwce repo, then run the command (assuming I have downloaded the bwce-runtime-2.8.0.zip file from TIBCO), followed by the Docker Push command:
    Make a small change to our Dockerfile to use this new version (tag is 127.0.0.1:3200/bwce:v2.8.0):
    To rebuild the application use the following (and don?t forget to push to the registry):
    The next job we need to do is update our yaml file that describes the deployment in Kubernetes to point to the new version of the image and then re-apply the yaml file to the deployment using the kubectl command:


    I deliberately left my curl command running so that as Kubernetes is deploying the rolling update ? we can see that when the new pod is instantiated it starts responding with the new version of the BWCE container runtime, whilst another instance of the pod is being started. When completed, you can see that all instances are now running at the latest version:


    Conclusion
    So there we have it ? we have successfully upgraded our BWCE container runtime in a Kubernetes environment without having to upgrade the entire infrastructure ? saving lots of time, effort and of course money.
    When you start applying DevOps principles to this approach ? then you can see how this level of automation can significantly, positively impact your development and operations costs.
    As you can see from the screenshot above ? this approach does not force you to upgrade every microservice to the same runtime version all at the same time ? different versions can co-exist at the same time, which allows you to better plan upgrades alongside existing development and maintenance activities rather than having to plan a separate activity just for upgrading the platform. Co-Existence of containers running different versions of the core run-time is actually a better way of making the best use of developers and operations time.






    Dave Winstone
    1. Summary
    2. Building the BusinessWorks Container Edition Base Image
    3. Building the Application Container Image
    4. Updating the Base Image
    5. Conclusion

    Summary
    I considered an alternative Title ? ?How Containerisation massively reduces your upgrade process?, as this is applicable for any technology that you containerise, but I wanted to show you how to do this specifically with TIBCO BusinessWorks Container Edition as it removes one of the biggest costs/effort of upgrading a BusinessWorks infrastructure.
    Let?s consider a scenario with ?classic? BusinessWorks ? either version 5.x or 6.x. Here, you will have a set of servers (deployed on either physical/virtual/cloud) where you deploy the applications that you build. These applications are tested, running and scaled to the right level to cope with your peak demand.
    Let?s say you have BusinessWorks 6.7.0 running and things are nice and stable (as all things TIBCO are of course!). TIBCO release 3 new versions of BusinessWorks over the next 2 years, let?s call them 6.8.0, 6.8.1 and 6.9.0. This means that you are now 3 versions behind and TIBCO?s support policy means that they will announce an end of support date for 6.7.0 in due course. Once that happens ? if you raise a Support Call ? you are quite likely to be asked to perform an upgrade before support is provided.
    So ? to keep up with support you need to upgrade your TIBCO platform to the most appropriate version in order to stay current and make sure that TIBCO will provide support for your version.
    The above policies are valid for most Enterprise Software Vendors in the market today ? so you can replace TIBCO with any other vendor name to suit your environment.
    What it means though, is that you and your development team must build into your plans the appropriate time and effort as part of your BAU process alongside building new projects and providing maintenance for existing projects to ensure you can upgrade the platform.
    Unfortunately, this doesn?t always happen and it can come as an unwelcome surprise that you are going to have to plan an unscheduled upgrade.
    As TIBCO BusinessWorks runs many of the world?s core businesses ? upgrading a classic BusinessWorks infrastructure means a lot of planning. I know of organisations that process Billions of $ orders EVERY DAY on TIBCO ? so your upgrade can?t go wrong. There?s a lot of planning, testing, re-testing and potential downtime too.
    Alongside this ? you?ve also decided to move to Containerisation as part your digital transformation planning and that includes moving your TIBCO BusinessWorks applications to Container Edition.
    If you are already on BusinessWorks 6.x ? moving those applications to Container Edition is pretty straightforward, from BusinessWorks 5.x TIBCO provide tooling to help as well as a migration factory for large projects ? but I want this article to focus on what it means to upgrade the container runtime for a deployed container edition application as there are other resources and blogs that cover migrating to Container Edition.
    If you?ve seen some of my previous blogs ? you?ll recognise my simple Greeting microservice that is a simple REST API that responds with a message and the container hostname:
     
     
    This application is built using the following Docker File:
    FROM bwce:latest LABEL maintainer="Dave Winstone" ADD greeting_1.0.0.ear / EXPOSE 8081 7777
    You?ll notice the first line tells the docker build command that I?ll be using the latest version of my TIBCO BusinessWorks Container Edition (bwce) base image. Best practice though is to specify a specific version to ensure you are pulling the right image for your deployment. It also means that you should be maintaining your Docker files in source code control too.
    It goes without saying (almost) that you should also be building and deploying your applications with a DevOps pipeline to automate everything and remove human error ? but I want to show you how you would upgrade the runtime manually.
    The greeting application itself is the ?greeting_1.0.0.ear? file. In this example I?ve changed the output very slightly to include the BusinessWorks runtime engine version as part of the output.
    Building the BusinessWorks Container Edition Base Image
    There?s lots of instructions and different examples of how to do this at TIBCO?s official github repo here that I?d recommend you take a look at.
    I?m going to start with my application built using version 2.7.3 of BusinessWorks Container Edition, then upgrade the runtime to 2.8.0.
    Once you?ve followed the instructions from the TIBCO GitHub to clone the BWCE repo. and downloaded the BWCE runtime from TIBCO?s download site you are ready to build the base image using a command similar to the following from the cloned bwce repo:
    ./createDockerImage.sh ~/bwce-runtime-2.7.3.zip bwce:v2.7.3
    The first argument is the BWCE runtime zip file that you downloaded from TIBCO, and the second argument is the tag we?ll be using.
    Building the Application Container Image
    I?ll adjust my application Dockerfile to include the correct base image tag as follows:
    FROM bwce:v2.7.3 LABEL maintainer="Dave Winstone" ADD greeting_1.0.0.ear / EXPOSE 8081 7777
    Now to build the application:
    docker build -f Dockerfile -t greeting-app:1.0 .
    And to run the application:
    docker run -p 8081:8081 greeting-app:1.0
    To see the results, I can issue a simple Curl command and see the response:
       So all good.
    But now we have a new version of the BusinessWorks Container Edition Runtime that we want to use ? but I don?t want to rebuild the original EAR file, as that would result in a code change ? leading to regression testing, UAT etc. Plus usually it means that the whole platform needs to be upgraded ? but we only need this single microservice to be updated as there?s a bug that?s been fixed by TIBCO that we need for this single microservice.
    In this instance, all we need to do is rebuild the base image for BusinessWorks Container Edition, alter the Dockerfile of my application to use that new image and then rebuild the container image and re-run.
    Update the Base Image
    To rebuild the base image to use v2.8.0 of BusinessWorks Container Edition, we first need to remove the bwce-runtime-2.7.3.zip from the resources folder under the cloned bwce repo, then run the command (assuming I have downloaded the bwce-runtime-2.8.0.zip file from TIBCO):
    ./createDockerImage.sh ~/bwce-runtime-2.8.0.zip bwce:v2.8.0
    Make a small change to our Dockerfile to use this new version (tag is bwce:v2.8.0):
    FROM bwce:v2.8.0 LABEL maintainer="Dave Winstone" ADD greeting_1.0.0.ear / EXPOSE 8081 7777
    And to rebuild the application:
    docker build -f Dockerfile -t greeting-app:1.0 .
    And to run the application:
    docker run -p 8081:8081 greeting-app:1.0
    And using my Curl command I can test the new version of the application to see if the BusinessWorks Container Edition runtime has been upgraded:
       Conclusion
    As you can see ? we have successfully upgraded the BWCE runtime within our container for our Greeting microservice.
    This is a huge benefit to containerisation ? particularly where your microservices utilise other frameworks or integration frameworks like TIBCO for your API strategies.
    What?s even more interesting is that this approach does not force you to upgrade every microservice to the same runtime version all at the same time? different versions can co-exist at the same time, which allows you to better plan upgrades alongside existing development and maintenance activities rather than having to plan a separate activity just for upgrading the platform. Co-Existence of containers running different versions of the core run-time is actually a better way of making the best use of developers and operations time.
    If you think about the time, resources and money that you would normally spend on performing this type of upgrade and comparing that to what you save using this approach, I think you?ll agree that taking this approach is well worth the effort.

    MichaelRatovo
    Latest version available for download on eDelivery
    TIBCO EBX® product documentation
     
    Back to the What's New in EBX® landing page
    This page describes the new features and improvements brought by EBX® 6.1.0. Additional content available on:
      - What's New in EBX® 6.1.1
      - What's New in EBX® 6.1.2
      - What's New in EBX® 6.1.3
     
    Table of Contents
    Side Bar & Social MDM Data visualization Data modeling Search Permissions Staging Workflow Integration and Development APIs Matching & Merging enhancements Digital Asset Management Miscellaneous   Side Bar & Social MDM
    Side bar
    Additional information on elements and social features access
    A new bar at the right side of the EBX® window has been added to easily provide contextual information with one click.

     
    At table level it gives information about the displayed table.

     
    At record level it gives information about the current record.
    It also gives access to the social features related to this record (aka Team Up).

    Team Up
    Brand new social features for enriched collaboration
    There was previously no way in EBX® for users to provide feedback on table records (about quality, points for attention, issues, etc), nor to classify records (tags). The 'Team Up' features aim to improve the collaboration and engagement of the EBX® users.  It reuses the new (right) side bar concept. It allows users to interact about data records by commenting, rating and assigning tags to those records. Some metadata can be reused along with EBX® searching (e.g Tags) and sorting features (e.g Ratings).  
    Comments
    Data visualization Tile view
    New visual display mode
    Previously, there were only three display modes to view records in EBX® (i.e. simple table views, hierarchies and graphs). Moreover, if customers wanted to leverage images from the record?s data, they needed to develop specific code in order to render images in such views.

    Now, there is a new display mode called Tile View: Tile views display records as cards which are arranged automatically in rows and columns. It is possible to choose an image for each card to help it to stand out.  Just like the simple table views, it offers the possibility of defining criteria to sort and filter records. Configurable tiles with many zones to summarize a record to its essential info. Contextual menu to operate actions and access services on records.
      Extended Hierarchies
    Group By hierarchies
    In previous versions, grouping data having common values was limited to some data types and to a single field on the selected table.
    Now, the dimension in a Group By hierarchy can be defined using columns located in the same table. Allowed column data types are foreign keys or the following enumerable types: String, Integer, Enumeration, and Boolean.
    A group by hierarchy also provides flexibility when setting the order for dimension levels.
    For example, a Product table might include the following columns: Brand, Segment, Type, and Packaging.
    Use these columns in any order to show products by: Segment --> Type --> Packaging, or Brand --> Segment --> Type --> Packaging.

      Skipped level hierarchies
    In previous versions, except for recursive hierarchies, it was not possible to have unbalanced/ragged hierarchies (i.e. hierarchies including members where their parent skips one level).
    Now, it is possible to create a skipped-level hierarchy, where nodes not having parents can be attached to grandparents.
     
    In our example, Walmart3 store appears under San Francisco node, even if it has no State field being populated. Notes: A ragged hierarchy only supports skipping one level   Timeline
    In previous versions, for tables having a date field, it was difficult to display records in a hierarchy whose nodes would be derived version of the date (e.g. Quarter, Month, etc). 
    Example:
    Considering a project table with a deadline(date) field.
    We could generate a hierarchy ?Project by Category by Date? but sometimes the requirement is to display not by date but by another time dimension (By year, by Quarter, by Month).
     
    Now, for any date field, it is possible to build a configurable time-based hierarchy dimension (using century, year, quarter, month node types).

     
    Current limitations:
    only for date fields no possibility to aggregate records on a date range (e.g. 1900-1950, 1951-2000, etc)   DMDV add-on
    Introducing the Org Chart
    A new graph type is now available inside DMDV : the Org Chart which can display any organizational data such as HR, Companies, Legal entities, or any hierarchical data. All current features of the current graph are also available on the Org chart (Navigation, Export, Zoo-in/Zoom-out,Expand/Collapse nodes).

     
    Configuration is done on the same tables as the current graph.
    New parameters have been added dedicated to the org chart.
    Fields to be displayed on the nodes are configurable.

     
    New nodes customization out of the box:
    Display an image attached to a record on the graph. The image can be managed by the EBX Digital asset manager component Display several fields values on the nodes View node details directly from the graph (right click on the node and select open record).
    Export PDF, SVG and PNG.
     
    Display selected data - Team Up
    360° view of your Team Up data using DMDV. Team up data available on each records to be displayed :
    Comments (light green) Ratings (blue) Tags (green) Overall rating of the record (pink)  
    Display selected data
    The previous limitation has been removed : only nodes coming from the current data space?s children could be hidden. The new algorithm implemented is now using the data model definition by default. It means that by default, only nodes from dataspaces listed in the definition of the foreign keys and associations are displayed which is the most common use case. By clicking on the dedicated button users can activate the display of the nodes coming from children dataspaces.  
    Display data model : Show/Hide links
    Ability to hide & show all the links of the graph with one single click using the dedicated display button added on the top banner.
     
    Display data model : Breadcrumb update after save
    In EBX® 6.0.10 we added an evolution on the data model save feature. However the breadcrumb was not updated after saving a graph. This limitation has been resolved in EBX® 6.1.0.
     
    New global properties
    Two new properties are now available in the configuration inside the ?Global Properties and Options? group to limit the number of records to display when expanding nodes: Expanded nodes limit for display selected data Expanded nodes limit for display data using configuration These options helps prevent readability and performance issues by limiting the number of nodes on the graph.
     
    Data Modeling
    Access to records metadata
    Metadata information usable in queries
    Previously, it was cumbersome to manage a record metadata such as its creation date. Now, some metadata information is available directly in the record structure as the data model now automatically embeds metadata nodes. Hence this information can be accessed using queries (XPath with Java API or REST calls, or SQL).
    The available nodes are:
    Record creator Record creation time Record last updater Record last update time Also when activating Team Up, the comments, the ratings and the tags are included in the queryable metadata information.
     
    Entity Name
    Simpler access to tables for SQL requests and Data Services operations
    Previously, it was only possible to refer to tables by using their paths which could lead to some difficulties (typing errors, long paths, path changes that need to be replicated in multiple locations, ?). 
    Entity names allow to refer to tables in SQL requests and Data Service operations using unique names instead of their paths.
    These names are easily configurable using a mapping table in the Data model configuration.
    They can be retrieved using the Java API.

    Important notes:
    By default, an entity name, based on the last step of the table path, is now automatically set for tables when no name is explicitly defined in the data model.
    If duplicated entity names are present, an error is raised during data model compilation time in order to manually define unique entity names.
     
    Search strategies
    Generalization of advanced search strategies selection
    Previously, Information Search add-on needed to be deployed to select advanced search strategies to be applied on String fields. Now, these strategies can be selected and configured in the data model.
    The available strategies are:
    Levenshtein Soundex Double Metaphone NGRAM  
    Search
    Search based on Association
    Broaden search to Associations
    Previously, search was limited to the selected table content. Now it is possible to select a table association and search on the records labels of this association.

    This feature is available on the UI (Advanced search), in the Java API and through data services (REST calls and SOAP operations).
     
     
    Search based on Team Up information
    Search on tags, comments and ratings
    Team Up information is now available as criterion search. Hence it is easy to retrieve
    categorized records (using tags), records by searching in their comments, and sets of records based on ratings. This feature is available on the UI (Advanced search), in the Java API and through data services (REST calls and SOAP operations). 
     
    Search based on metadata information
    Searchable records metadata information
    Previously, it was not possible on the UI to filter records using their metadata information. Now, as metadata elements are automatically added to records structure, these elements can be used as search criterion.
    It now becomes easy to get the list of records created by a specific user or to see the list of records updated this month.

    This feature is available on the UI (Quick search and Advanced search), in the Java API and through data services (REST calls and SOAP operations).
    Permissions
    Permissions screen enhancements
    Improved UX and records metadata support
    Previously, it was needed to scroll down the list of fields to select the type of permissions to apply for each field, which was not convenient when displaying more than 10 lines. Now the available types of permissions are located on the top of the fields list.
    Record metadata access rights management is available in this screen as well.

    Staging
    New Staging feature
    Out-of-the-box configuration migration
    Previously, there was no native feature to migrate configurations/artefacts between EBX® environments (e.g. from development to testing environment). Customers were mainly performing manual tasks or relying on specific code to ensure such environment staging (data, models, workflows, import/export configurations, etc..).
     
    Now EBX® offers a native staging feature.
    Migration is configured per each domain managed in EBX® (e.g. Products, Employees, Third Parties, etc).

     
    Migrate your import/export configurations
    Data Exchange add-on (DINT) ready for staging
    Elements available in the staging: Templates Configuration for external data sources  
    Migrate your visualization configurations
    Visualization add-on (DMDV) ready for staging
    Visualization elements available in the staging: Data models graphs configurations (on dataset and DMA) Value and relationship graphs configurations Saved graphs Custom graphs  
    Migrate your dashboard configurations
    Insight add-on (DPRA) ready for staging
    Allow migration of all dashboards.
     
     
    Workflow
    New built-in scripts
    Additional scripts to manage data
    Previously, custom development had to be integrated within specific script tasks to execute some actions on the data. Now, a set of new scripts have been added to perform the following actions:
    Update a Record string value Retrieve a Record field value Update a Dataspace label Update a Workflow label New vertical layout
    Layout orientation customization
    Previously, steps and links needed to be manually moved to display them in columns. Now, a new option allows to apply a vertical layout to the current diagram.

     
     
    More flexibility in layout configuration
    Arrange the links as you wish
    Previously, when having many steps displayed it was not easy to clearly distinguish links which were automatically positioned whenever a step was moved. Now, movable link connectors can be easily placed anywhere around the steps boxes allowing to completely customize the layout of the steps and links.

    Prevent loss of unsaved layout changes
    Be warned when unsaved changes are done
    Previously, when changes were performed on the layout and the user added a new step or updated an existing one without saving the layout first, then when going back to the diagram, the displayed layout did not reflect the previous unsaved changes. Now, a pop-up is displayed to warn the user about unsaved changes when he clicks on the link to add a new step or when he clicks on a step to edit its content.

     
    Workflow launcher improvements
    A single activation instance for multiple tables
    Previously, to enable a workflow launcher on multiple tables, it was necessary to create as many activation instances as target tables. Now, it is possible to select multiple tables within an activation configuration form.

     
    An additional way to launch a workflow
    Previously, workflows could be launched from a tabular view using the Action menu or from a record form. Now, it is possible to launch a workflow directly from a table row custom toolbar.

     
    Integration and Development APIs
    Data services
    REST Toolkit APIs
    OpenAPI extension of the ?api? category to generate document for REST Toolkit resource.
     
    Built-in RESTful services
    New mass update and delete operations based on XPATH and/or Views Select operations improved to retrieve records metadata with filtering and sorting URL encoding for REST services improved to comply with RFC-3986 (Percent-Encoding) Built-in SOAP operations
    Select operations improved to retrieve records metadata with filtering Update operation improved to take all data content returned by the select operation even if fields are ignored Simulation of data import
    Data Exchange (DINT) enables the simulation of CSV/EXCEL import
    Allows users to use the current configuration and mapping settings to simulate a data import. The simulation results can include different levels (error, warning, and information) of non-blocking, blocking submission, blocking operator.

    Ability to view errors directly (limited to 100 rows) or to download an error file to analyze errors.
    Uses the result information to make any needed changes before performing the actual import.
    Is available for import on both table and data set levels.
     
    Data filtering accessible within templates
    Data Exchange (DINT) templates allowing data filtering
    Previously, the only way to export filtered data was to use table views. Now, data export templates can be defined embedding custom data filters.
    Hence, for example, these filters can be used by custom workflow script tasks using the appropriate Template ID.

     
    Database connection using Windows credentials
    Data Exchange (DINT) supports SQL connection to MS SQL Server using Windows authentication
    Database can be accessed using Windows authentication by username and password
    Java API
    New development libraries ebx-api.jar and ebx-resource-api.jar
    Compilation and build operations must now use these libraries instead of ebx.jar library whose Java types are now visible. These development libraries ensure the reliability of EBX® custom modules by guaranteeing exclusive use of public API. At runtime, they should not be deployed while ebx.jar remains required.
     
    Blocking access to not fully initialized repository
    New API to block access attempts to a partially initialized repository until it is able to handle data services (SOAP, REST Built-in, REST Toolkit) and UI.  
    Information on custom views
    New API to get information on views such as: the recommended view for a given user the favorite view for a given user the currently applied view Matching & Merging enhancements
    Matching after Business Object Submission
    It?s now possible to execute Business Object (BO) matching once BO is committed
    Previously, only Manual matching option was available for BO. BO Matching trigger can be paused, so that the deduplication is not executed during the BO import.
    Once the batch import is finished, newly created BOs can be matched thanks to the new ?After submission? setting.

    Evaluate matching service for Business Objects
    It?s now possible to execute the Evaluate matching from the EBX tabular view and from Manage group screen of the BO
    Previously, this service has been supported only for the table matching. The Evaluate matching service is reflecting the Matching fields coming from the related objects (for example Phone and Email fields in the below screenshot).

    The service is working in a same way as for the table matching : 2 objects should be selected to simulate the output.
    Manual Merge of Business Objects
    Related tables included in the golden record processing
    Previously, it was not possible to create golden records in the related tables. ?Manual Merge? screen allows a Data Steward to review the related tables and to select the values to include into a golden record.
    A compact preview screen lists all the changes occurred in different parts of the Business Object.

    Manual Merge of BO: New step bar
    Easily follow all the sub-steps of the related table manual merging
    In previous versions the navigation between related tables steps was not explicit. A new vertical step bar has been provided to improve the UX of BO manual merge (based on customers feedback).
    More space is available to display the data.
    Tooltips are available when hovering the step bar.

    Table matching: New Manage group screen
    Leveraged UX for the Data Stewardship for table matching
    Previously, Manage Group screen had limitations related to the screen separation into Match and suspect sections (for example impossible to compare a Match record with a Suspect). The UI has been reorganized based on customers feedback.
    It is possible to perform the actions on Suspect and Match records.
    It is possible to customize the attributes order thanks to the new custom view feature.

    Enhanced UI of the Evaluate matching screen
    More details on the Pre-processing phase output
    The pre-processing used to be a black box, but it is no longer the case. Thanks to the explicit guidance the user can check and adjust the pre-processing parameters (Matching fields, weight, search strategies?).

    In case 2 records have been filtered at the pre-processing step, the user can see why it has happened.
    Hybrid fuzzy algorithm customization
    Users can have several sets of parameters for Hybrid fuzzy algorithm
    Before 6.1 version only default values were available, hence the users were not able to adjust parameters to better meet the business requirements. Now, the configurable parameters (Synonym, Levenstein-1, Levenstein-2) are available at the decision tree node level.
    The customized settings are saved and can be reused.

    New options for Merged records updates management
    More flexibility to manage the merged records update flow
    Previously the records were put out of the group when a matching field was updated. Three options are currently available:
    The records can be always kept in the group The records can be always removed from the group The updated merged records can be removed or kept in the group based on the field that has been updated New Java APIs
    Additional Java APIs have been provided
    API for Evaluate matching service API to get the list of trusted sources API to perform multiple merges in one transaction Digital Asset Management
    Folders to organize the assets within the Drive
    New way to organize the assets in the Drive
    Previously, all the assets were organized at the same level, hence it was not possible to keep the same structure as the external file management systems. Built-in Drive UI has been improved by allowing users to create folders and to move the assets between folders.
    When visualizing the external Drive via EBX UI, the original assets organization can be kept.

    New built-in connectors to third party file management systems
    Out-of-the-box connectors
    Previously, it required a lot of coding to connect to third party file management applications. Now, two additional built-in connectors to the most popular systems Microsoft SharePoint and Google Drive are available for the selection.
    Consequenlty, the user can use EBX® DAMA Drive view as an interface to view the files in Microsoft SharePoint and Google Drive.

     
    UI enhancements for the EBX® DAMA Drive view
    More specific search capability and improved navigation
    Previously, it was not possible to perform advanced search in Drive view. Currently it becomes possible thanks to the advanced mode.

    It is also possible to easier navigate among drives thanks to the new Drive search feature.
    Miscellaneous
    Supported environments
    Browser supportInternet Explorer browser (all versions) is no longer supported.JVM supportJava Runtime Environment is now JRE 11 or 17IBM supportWebSphere Application Server 9 is no longer supported.
    Minimum supported version of WAS Liberty is now 20Oracle supportOracle 12c is no longer supported. Minimum supported version of Oracle is now 19c.PostgreSQL supportPostgreSQL 10 is no longer supported. Minimum supported version of PostgreSQL is now 11.Microsoft supportSQL Server 2012 SP4 10 is no longer supported. Minimum supported version of SQL Server is now 2014.

    Ana Bahr
    For additional information see:
    TIBCO Cloud Integration - Connect Release Notes
    TIBCO Cloud Integration - Connect Known Issues
    TIBCO Scribe Online Connector Release Notes
     
    New And Noteworthy
    SCCORE-3742
    The palette of colors used for the blocks in TIBCO Cloud Integration - Connect flows has been upgraded to a brighter and more distinctive set of colors to help users differentiate one connection from another during the flow design process. 
    SCCORE-8662 Added a new Wait Block to the Control Blocks section of the Flow designer. This block allows you to pause the flow for up to 600,000 milliseconds (10 minutes). Note that if you stop a running  app with a flow that contains a Wait Block, the app does not stop until the Wait Duration has completely elapsed. To use the Wait Block, you must run the latest version of the Agent.
      TIBCO Cloud Integration Connect - API
    SCCORE-8430 Upgraded the Swagger user interface to the latest version. As a result of this upgrade, the Try it out button on the interface is enabled by default and does not display. You can execute commands without having to select Try it out first.
    SCCORE-8662 Added API support for the new Wait Block. This block allows you to pause a flow for up to 600,000 milliseconds (10 minutes). To use the Wait Block, you must run the latest version of the Agent. 
      Migration And Compatibility
    Agent
    If you plan to use the new Wait Block in a flow, your On-Premise Agent must be upgraded to the latest version. If the Agent is not upgraded, you cannot save changes to any flows. (SCCORE-8464)
     
    Closed Issues
    SCCORE-7947
    Attempting to install an Agent on an unsupported operating system now fails with an error message instead of allowing the installation to continue. (Case # 02088715)
    SCCORE-8122 On the Query Block Net Change tab, the Most Recent Record Processed date time value displays as null null if the value contains microseconds. If you attempt to edit the value, "NaN/NaN/NaN NaN:0NaN:0NaN.NaN AM" displays. (Case # 02091445)
    SCCORE-8403 In some cases, Agents were not able to synchronize Solution execution data to the Cloud causing Execution History Detail records to be missing. Failed records could not be retrieved for reprocessing. (Case # 02089362, 02112572, 02114366, 02118156, 02118195, 02118592, 02119664, 02121244, 02124813, 02133531)
    SCCORE-8418
    Internal Agent database tables that exceeded one million records caused performance issues and generated errors in the logs. (Case # 02118235, 02122387, 02129217)
    SCCORE-8982
    Agents could not retrieve metadata for Microsoft Dynamics GP Connections nor could they load cached metadata. Errors similar to the following were generated:  (Case # 02157831, 02157842, 02158348, 02158358, 02158359, 02158363, 02158366, 02158672)
    Error loading cached metadata unexpected end of file.
     
     

    Ana Bahr
    What?s New
    TIBCO Cloud? Integration
    The updated TIBCO Cloud Integration Hybrid Agent allows you to  manage remote apps from the  TIBCO Cloud Integration user interface. Remote apps are auto-discovered by the agent and can be monitored, scaled up or down, stopped or started, and environment variables can be updated. Note that to use this new functionality, the latest version of the agent must be downloaded and run in a Kubernetes Cluster. Existing Hybrid Agents used for Hybrid Connectivity to establish tunnel connections to on-premises resources can continue to run and do not need to be upgraded at this time. (IPAS-20577) You can now download  TIBCO BusinessWorks app templates from the TIBCO Cloud Integration Marketplace and import those templates into TIBCO Business Studio for BusinessWorks . (IPAS-20471) A new  --logStreamPort option has been added to the start command for the Hybrid Agent. In cases where there are two agents on the same machine, you can specify the port to be used for streaming logs using this command: tibagent start agent --logStream --logStreamPort <port number> <agentName>  (IPAS-18585)   TIBCO Cloud Integration API
    We have added the following API methods in this release:
     
    GET ?/v1?/subscriptions?/{subscriptionLocator}?/apps?/{appId}?/testsuite/export
    Use this  method to export TIBCO Flogo Test Suites. Test Suites are a collection of unit tests for the flows in a Flogo app. (IPAS-20552) PUT ?/v1?/subscriptions/{subscriptionLocator}/apps/{appId}/endpoints/{endpointId} Use this method to update the service name and description of an app endpoint.  (IPAS-19959) POST /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Use this method to pin a Flogo app. Using a pin you can go back to a previous version of an app if necessary. (IPAS-20655) DELETE /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Use this method to delete a pin from a Flogo app. PUT /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Use this method to restore a pinned Flogo app. GET /v1/subscriptions/{subscriptionLocator}/apps/{appId}/pin Use this method to get the pin associated with an app ID.  
    Develop / TIBCO Flogo
    Unit Testing
    You can now create, design and run unit tests for your Flogo flows using the integrated Unit Testing feature at any phase of the development cycle to verify whether activities in the flow are working as expected.  
    Create Array in Mapper
    In the mapper, you can create a new primitive or object array of size N.  
    Improved Group Management in App Properties
    The user experience of App Properties is enhanced to allow you to drag the groups from one location to another.  
    Environment Variable for Session Token in AWS AppConfig feature
    If you are using temporary credentials to connect to AWS AppConfig services, a new optional environment variable is available for configuring a session token.  
    Optional Session Token field
    An optional Session Token field on the AWS Connection dialog has been added to support passing an AWS Session token with the AWS access key ID and secret. (FLOGO-9459)  
    Develop/TIBCO Flogo® Connectors
    TIBCO Flogo Connector for Amazon DynamoDB
    There are no new features in this release. TIBCO Flogo Connector for Amazon EC2
    There are no new features in this release. TIBCO Flogo Connector for Amazon Kinesis
    There are no new features in this release. TIBCO Flogo Connector for Amazon S3
    There are no new features in this release. TIBCO Flogo Connector for Amazon SNS
    There are no new features in this release. TIBCO Flogo Connector for Amazon SQS
    There are no new features in this release. TIBCO Flogo® Connector for Apache Pulsar
    A new client authentication method, "OAuth2", has been added in the Apache Pulsar connection. (FGPUL-139) Flogo® Connector for Apache Pulsar now supports Open Telemetry. For more information, see the Tracing Apps by Using OpenTelemetry Collector topic: Tracing with OpenTelemetry Collector. (FGPUL-140) The name of the created producer/consumer now has an operationally useful format that can be seen by using the Pulsar Admin REST API. TIBCO Flogo Connector for Azure Data Factory
    Added support to trigger pipeline with parameters from Flogo. TIBCO Flogo Connector for HTTP
    Added support for a Data mode as a processing mode where the user has more control over input parameters such as path, query, headers, and request schema. OpenTracing is also supported in Data mode. TIBCO Flogo Connector for HubSpot
    There are no new features in this release. TIBCO Flogo Connector for IBM MQ
    This connector has been certified for use with TIBCO Cloud Integration. (FGIBMQ-42) Added support for MQ Client Channel Definition Table (CCDT) files. (FGIBMQ-45) TIBCO Flogo Connector for MongoDB
    Seed lists specified using SRV records DNS are now supported. Added support for the authentication source to specify the database created in the MongoDB database on which the user has to be authenticated. Added support for retry on error for MongoDB activities. TIBCO Flogo Connector for SAP S/4HANA
    The Flogo Connector for SAP S/4HANA now supports OData V2 and OData V4 APIs. An On-premises connection is supported in this release. TIBCO Flogo Connector for Snowflake
    Supports configuring metadata of SQL statements manually. This feature allows the use of separate queries to acquire the metadata associated with the field. The user can manually configure the metadata by setting the Manually Configure Metadata option to True.   Integrate/TIBCO BusinessWorks
    OAS 3.0 enhancements include support for multiple response features. Support has been added to create a top-down REST service with an OAS 3.0 JSON file having multiple response content-types. Support for oneOf/anyOf constructs. You can now generate XSD and create a top-down service or reference binding using an existing OAS 3.0 JSON file with anyOf or oneOf keywords for request and response schemas. Support for inline schema at request and response. An OAS 3.0 JSON file with inline schema in request and response is now parsed when creating a top-down REST service or reference binding. OAUTH 2.0 authentication in ReceiveMail activity. OAuth 2.0 Authentication is now supported for Receive Mail Activity IMAP protocol in the Mail palette. Support has been added for HotUpdate for JDBC Shared Resources. The TIBCO Cloud API Modeler (TCAM) APIs are now available on the TIBCO Cloud APIs website. TIBCO BusinessStudio for BusinessWorks can leverage these to make the API specs from TCAM discoverable in the API explorer.   Integrate/TIBCO BusinessWorks? Plugins
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon Redshift
    Creating and Configuring the Redshift Connection Resource This feature establishes a connection with Amazon Redshift to perform data load and data polling operations. The ActiveMatrix BusinessWorks? Plug-in for Amazon Redshift supports the following types of authentication methods: (BWAR-8) Username/Password Federated Authentication and SSO  Bulk Load Activity The Bulk Load activity performs data loading from a source relational database or other sources to a target Amazon Redshift. The data can also be loaded into the Amazon Redshift table by staging data files in the Amazon S3 bucket. This is done with the help of the appropriate S3 bucket URI and file format. (BWAR-3) Data Change Poller Activity The Data Change Poller activity tracks new and updated records in a given source table. The new or updated record is copied to a reference table for future use. After each polling interval, the changed records are returned as the output. (BWAR-24)   TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon S3
    The Amazon Connection can now retrieve the java client object in inline subprocesses. (BWAS-567) Users can now configure custom VPC endpoints for Amazon S3 activities using a system property.  (BWAS-573) TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon SQS and SNS
    Users can now configure a custom Virtual Private Cloud (VPC) endpoint for Amazon SQS and SNS activities using a system property. (AWSM-610) TIBCO ActiveMatrix BusinessWorks? Plug-in for AMQP
    The AMQPReceiveMessage activity now provides an ?Any? option in the Message Type field. You can receive text and byte type messages using the Any message type. This field is available when Qpid-1-0 is selected from the Broker Type list of the AMQP Connection shared Resource used. (AMQP-851) TIBCO ActiveMatrix BusinessWorks? Plug-in for Apache Kafka
    Smart Engine TIBCO ActiveMatrix BusinessWorks? collects engine data on an AppNode. This plug-in uses the data to provide analysis and recommendations for improving your application performance. (BDKF-938) TIBCO ActiveMatrix BusinessWorks? Plug-in for AWS Common Services
    Container Credentials with Assume Role In AWS Common Services, along with AWS Credentials, the Container Credentials also support the Assume role. (BWAWSC-193) Cross Account Credentials in the GetConnection Activity In AWS Common Services, users can configure Cross Account Credentials from the input schema of the GetConnection activity. (BWAWSC-198) TIBCO ActiveMatrix BusinessWorks? Plug-in for Facebook
    Graph API v13.0 Support for Graph API v13.0 has been added in this release. (BWFB-1676) TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft Dynamics CRM
    There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for Microsoft SharePoint
    There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for NetSuite
    There are no new features in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for OData
    In this release, the OData plug-in supports batch requests as a client to external OData V4 services via the new OData Batch activity in the OData Palette. (BWOD-593) Note: The OData Batch request supports only the Create operation in this release. TIBCO ActiveMatrix BusinessWorks? Plug-in for SAP S/4HANA
    Receive Business Events Activity The new Receive Business Events activity can be used to receive business events from the SAP S/4HANA system. When the business event is sent from SAP S/4HANA, only key information is provided. To get the changed data from SAP S/4HANA, the key information stored in the Business Event is used with the Consume OData Service activity. Note: The Receive Business Events activity supports only SAP S/4 HANA Public Cloud Connection. Support for OData V4 APIs The Consume OData Service activity can now be used to invoke OData V4 APIs in the SAP S/4HANA system. This includes SAP S/4HANA on-premises/private cloud and SAP S/4HANA public cloud. Note: OData V4 APIs are supported only for Production tenant.
    SAP S/4HANA On-Premises/Private Cloud This release supports versions 2020 and 2021 of SAP S/4HANA that are available as an On-Premises or Private Cloud installation.   TIBCO ActiveMatrix BusinessWorks? Plug-in for SAP SuccessFactors
    Support for Batch Processing The plug-in now supports batch processing for OData V2 APIs and supported operations. This allows multiple instances of the same operation in one request. You must configure the number of instances per request at design-time. (BWSS-353 / BWSS-225) Support for Visual Diff You can now use the plug-in to compare two revisions of a process or two revisions of a shared resource, and their artifacts side-by-side visually in TIBCO Business Studio? for BusinessWorks?. In the newer versions, the plug-in highlights changes such as the addition or removal of activities, changes in an activity, and shared resource configuration. The activity and shared resource are as follows: (BWSS-354 / BWSS-297) ConsumeSAPSuccessFactorsODataService Activity SaP SaaS Connection shared resource TIBCO ActiveMatrix BusinessWorks? Plug-in for TIBCO FTL®
    The TIBCO ActiveMatrix BusinessWorks? Plug-in for TIBCO FTL® now supports OpenTelemetry predefined tags. You can use these predefined tags to get more information about the current job being run by any activity in the palette. (BFTL-181)   Changes in Functionality
    Develop / TIBCO Flogo
    Create array in Mapper
    On importing an app with in-line array mappings, the array elements are wrapped into the item object. Elements under existing array mapping which has array foreach without source are wrapped in an item object. On adding empty array.foreach, input mapper turns to non editable.   Changes in Documentation
    To streamline the TIBCO Cloud Integration documentation, we are merging smaller topics together and removing duplicate information, as follows: This Hybrid Agent Overview page has been removed: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/overview.html 
    The information has been merged with the Using the TIBCO Cloud Integration - Hybrid Agent page:
    https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/index.html
    This Hybrid Proxy Connections page has been removed: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/hybrid-proxy/index.html 
    The information has been merged with the Proxy Connection Overview information into this page:
    https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/hybrid-proxy/tunnel-overview.html
    The Monitoring Hybrid Apps page has been removed: https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/hybrid-monitoring/index.html 
    The information has been merged with the Monitoring and Managing Hybrid Apps page:
    https://integration.cloud.tibco.com/docs/index.html#tci/using/hybrid-agent/hybrid-monitoring/monitoring-overview.html
     
    Closed Issues
    TIBCO Cloud? Integration
    IPAS-13301 If you copy or replace an app from the App Details History tab, the content on the History tab is not updated automatically with new information.
     
    IPAS-20941
    Whitelisted open source libraries for Node.js apps were not listed in the TIBCO Cloud Integration documentation.
     
    Automate / TIBCO Cloud Live Apps
    CBPM-22676 An HTTP-400 error is generated when accessing TIBCO Cloud Live Apps Administrator -> Process Administrator  from the TIBCO Cloud Integration Environment & Tools page.
    Develop / TIBCO Flogo
    FLOGO-9426 / FLOGO-9486 When you add a property or group in an app having a large number of flows and nested app properties (for example, 80 flows and more than 100 nested app properties), the API call for the Save button takes time to add properties and groups.
     
    FLOGO-9427
    If you move a property from the root level or from one group to another group in the app properties (using the drag-and-drop feature), at an activity level, existing mappings are not updated in the input data or mapper text field.
     
    FLOGO-9434
    If you remove a property and add the same property under another group or root level, the mappings are not updated in the input data or mapper text field. The changes are visible at the activity level but the input data or mapper text field displays the following error: Property 'Property_name' does not exist in '$Property'
    If you move a property from the root level or from one group to another group in the app properties (using the drag-and-drop feature), at an activity level, existing mappings are not updated in the input data or map?$Prop?$Property?ext field.
     
    FLOGO-9444
    Search in app property does not return a match if that app property does not have any value.
     
    FLOGO-9742
    When using access credentials and a session token generated from the AWS portal, the Queue URL is not shown in the SQS SendSQSMessage activity and SQS ReceiveSQSMessage trigger.
     
    TIBCO ActiveMatrix BusinessWorks? Plug-in for SAP SuccessFactors
    BWSS-205 When using the Tenant Type as Production in the SAP SaaS Connection resource, the HTTP response code 403 error message is displayed.

    Richard Flather
    Creating a Docker® image embedding FTL and EMS, and hosting it in a Docker registryProvisioning Persisted volume storage for cloud platformsConfiguring and creating FTL/EMS containers based on the EMS Docker image to run in Kubernetes through pre-configured yaml configuration files.How to Configure EMS 10.2 with FTL on Kubernetes.pdf
    tibemsd_10.2_ftl_kubernetes.zip

×
×
  • Create New...