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
  • Chinmay Gadre
    What's New
    TIBCO Cloud? Integration
    The new Alerts tab allows you to configure alerts and notifications for any apps you want to monitor using the web UI. (IPAS-22493) The Environment and Tools tab allows you to view webhooks using the web UI.  TIBCO Cloud Integration API
    A new alert rule TIB_APP_INSTANCE_COUNT_0 is added. This triggers an Instance Count alert when the number of instances of an app scales down to 0. (IPAS-22494) Develop / TIBCO Flogo
    You can now add Notes for the Flows, Activities, and Triggers. (FLOGO-10828) The branch lines are now indicated by different colors depending on the condition applied. (FLOGO-10735) You can now open any subflow configured using the Open Subflow icon on the StartaSubflow activity. (FLOGO-10186) You can now open and work with multiple flows in the same Flow designer browser tab. (FLOGO-10185) In the Settings Configuration window of the Invoke Rest Service activity, you can use the newly added Close Connection field to terminate the connection to the server after the response is processed. (FLOGO-10141) A new functionality has been introduced for the mapping of unmapped arrays. You can now configure the array using the source array, the items or the JSON array using the new first class forEach screen. (FLOGO-8942) You can now monitor the Flogo app metrics using OpenTelemetry. (FLOGO-7063)  You can now select the Enum values using a dropdown available on the Input tab. (FLOGO-5120) You can now pass multiPartFormData dynamically in the InvokeRestService activity without defining any data in the multipart Data table. (FLOGO-10727) Develop/TIBCO Flogo® Connectors
    TIBCO Flogo® Connector for Apache Kafka
    Added support for App properties for TLS certificates. (FGKAFKA-123) Added support for Open Telemetry. (FGKAFKA-104) Added support for SASL Oauth. (FGKAFKA-103) TIBCO Flogo® Connector for OData Services for SAP S/4HANA
    There are no new features in this release.
    TIBCO Flogo® Connector for Snowflake
    Added support to override Database Name and Schema Name and perform operations. (WISNFK-168) Added support for delete activity for both Design and Runtime. (WISNFK-164) Added support for merge activity for both Design and Runtime. (WISNFK-163) Added a new authentication type - Okta OAuth with PKCE support. (WISNFK-159) TIBCO Flogo® Connector for Microsoft Azure Service Bus
    Added support for receive modes for queue and topic subscriber. (WIAZSB-314) Added support for Open tracing. (WIAZSB-312) Added support for Ack activity. (WIAZSB-293) Added support for NoAck activity to deliver messages once again. (WIAZSB-291)  TIBCO Flogo® Connector for Microsoft SQL Server
    There are no new features in this release. 
    Integrate/TIBCO BusinessWorks?
    The following method is added to update the log level of TIBCO BusinessWorks app dynamically using the logger platform API under the Monitoring section. PUT /v1/subscriptions/{subscriptionLocator}/apps/{appId}/monitoring/logger This functionality is available for newly pushed and repushed apps. (IPAS-21936)
    Added support for OpenTelemetry for Metrics. TIBCO BusinessWorks app?s metrics for system data and process stats can now be seen on any standard metric-supported data source via OpenTelemetry.  
    Integrate/TIBCO BusinessWorks? Plug-ins
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon S3
    Added support for Hot Update feature for Amazon S3 Shared Resource. (BWAS-652) Added support for Custom Endpoint URL. (BWAS-611) Added support for Session Token field. (BWAS-605) TIBCO ActiveMatrix BusinessWorks? Plug-in for Amazon SQS and SNS
    Added support for Hot Update feature for Amazon SQS and SNS Shared Resource. (AWSM-656) Added support for Custom Endpoint URL. (AWSM-632) Added support for Session Token field. (AWSM-627) TIBCO ActiveMatrix BusinessWorks? Plug-in for AMQP
    Added support for AMQP ActiveMQ Artemis broker. (AMQP-1086) Topic Support: Support for topic entity is provided for the following brokers:  Qpid-1-0 AMQ-1-0 ActiveMQ-1-0 ActiveMQ-Artemis-1-0  
    TIBCO ActiveMatrix BusinessWorks? Plug-in for Change Data Capture
    Added support for the Change Data Capture plug-in in TIBCO Cloud Integration.
    TIBCO ActiveMatrix BusinessWorks? Plug-in for OData Services for SAP S/4HANA
    Added support for SSL Authentication for On-Premise/Private Cloud systems Added support for CDS views for On-Premise/Private Cloud systems Added support for Batch Processing  
    Changes in Functionality
    Develop/TIBCO Flogo®
    IPAS-22449
    The process of changing the service name of the app is shorter now. The service name of the app gets updated after copying or replacing the app. There is no need to push the app now. 
     
    FLOGO-10924
    The 'Array.forEach' functions for mapping of arrays are not available under any array functions. They are now shown in the auto suggestion.
     
    FLOGO-10757
    The ?ReplyToTrigger' activity has now been migrated to the ?General? category.
     
    FLOGO-10823
    The references for triggers and activities in the ?General? category have been moved from git.tibco.com to github.com.
     
    FLOGO-10924
    The 'Array.forEach' functions for mapping of arrays are not available under any array functions. We now have a new first class forEach screen to map arrays.
    Develop/TIBCO Flogo® Connectors
    TIBCO Flogo® Connector for Apache Kafka
    The Topic Whitelist field in the settings for Kafka Consumer Trigger is not supported in TIBCO Flogo® Connector for Apache Kafka as of the TIBCO® Cloud Integration August 2023 release. There is no impact if this field is not used.
    You may observe one of the following:
    If used along with the Topic field, only the topic configuration is used. If used without configuring any topic, an error message is displayed. Workaround: You can add topics configured using the regex in the Topic Whitelist field as a list of comma-separated topics in the Topic field. TIBCO Flogo® Connector for Microsoft SQL Server
    WIMSSS-507 There is a variation in the TIME and XML datatype in MS SQL Server activities at design time.
    The  TIME2 datatype is now displayed instead of the TIME datatype. The XML is replaced with the SS_XML datatype.
    Migration and Compatibility
    TIBCO Cloud? Integration
    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 to ensure the best performance. 
    Develop/TIBCO Flogo® 
    End of Support for Custom Access Key
    If you are enabling the DB Service with a custom access key (starting the agent with a custom access key, creating an on-premises database, and testing the app), then as of this release, the existing apps running will continue to work, even if they are re-pushed. If you disable the DB Service with a custom access key, it uses the system access key automatically, causing the existing DB Connectors to stop working. To fix this, start another agent with the same specifications, without using an access key. Follow the below steps:
    ./tibagent configure agent -p <port> <agent_name> ./tibagent start agent --spec <on-premise port>:<ip/hostname>:<on-premise port>  (FLOGO 11271) Note: This is only applicable for DB Service.
    Deprecating and End of Support
    Integrate/TIBCO BusinessWorks? Plug-ins
    TIBCO ActiveMatrix BusinessWorks? Plug-in for SWIFT
    TIBCO ActiveMatrix BusinessWorks? Plug-in for SWIFT has been removed from TIBCO Cloud Integration. (SWFT-5078) TIBCO ActiveMatrix BusinessWorks? Plug-in for OData Services for SAP S/4HANA
    Removal of Data Direct drivers - The plug-in does not support Data Direct drivers. You can use Native DB drivers, instead. Closed Issues
    Develop/TIBCO Flogo®
    FLOGO-10983 Summary: Common parameters for all operations at the path level are not resolved, hence, they do  not show in the Input settings.
     
    FLOGO-7062
    Summary: After an upgrade, the existing apps display the ?Retry? message on the Error tab. Although it does not display the Count and Interval fields.
     
    FLOGO-10350
    Summary: When we open a flow and click an activity, sometimes it does not open with a single click and a message, saving changes, is displayed.
     
    FLOGO-10803
    Summary:  When you add App Schema and click Rest Trigger, the UI becomes unresponsive. The trigger is removed after you refresh the page.
     
    FLOGO-10821
    Summary:  If any upstream activity is renamed, all the references matching with that activity name are updated. 
    Develop/TIBCO Flogo® Connectors
    TIBCO Flogo® Connector for Microsoft Azure Service Bus
    WIAZSB-286 An error occurs during the processing of messages from the Azure Service Bus queue and does not result in retries/dead letters.
     
    WIAZSB-285
    Trigger connection is lost after an update on the Azure Service Bus topic or queue.
     
    WIAZSB-284
    Only a single message is delivered from the dead letter subscription of a topic subscription.
     

    Chinmay Gadre
    Migration and Compatibility
    TIBCO Cloud? Integration
    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 to ensure the best performance. 

    Deprecating for Development
    Develop/TIBCO Flogo® Connectors
    TIBCO Flogo® Connector for Apache Kafka
    The Topic Whitelist field in the settings for Kafka Consumer Trigger is deprecated from TIBCO Flogo® Connector for Apache Kafka as of the TIBCO® Cloud Integration July 2023 release. There is no impact if this field is not used.
    You may observe one of the following:
    If used along with the Topic field, only the topic configuration is used. If used without configuring any topic, an error message is displayed. Workaround: You can add topics configured using the regex in the Topic Whitelist field as a list of comma-separated topics in the Topic field.

    Chinmay Gadre
    TIBCO Cloud? Live Apps, Refresh 56 (July 2023)
    What's New
    App Configuration Data
    We have added a tab called App Configuration Data in the Data editor in Live Apps. These fields are useful when you want data that is shared by all cases of your application, and that can be modified by an administrator after your application is published. For example, there might be some details that may be need to be changed, such as organization's contact details, opening hours, and so on.
    In such a scenario, App Configuration Data is useful. If the application is already published, you don't have to make changes to the application design and publish it again.
    Closed Issues
     
    CBPM-25939
    Summary: As an application designer, after creating an application with no explicit groups referenced in case action access, you cannot view the cases you created when you go the case manager, but, only an administrator can view them.
    CBPM-26039
    Summary: When you hover over a case data field while selecting the data fields to be displayed on the form, the tooltip is undefined.
     
    Current Known Issues
    No issues have been reported in this release of TIBCO Cloud? Live Apps.

    Chinmay Gadre
    TIBCO Cloud? Live Apps, Refresh 55 (June 2023)

    What's New
    Maintaining TCLA app references in TCI flow after app copying
    When you activate a hard copy of an application in a subscription and also copy a Flogo flow that has tasks that reference that Live Apps application, you don't need to specify these references again.
    That is, when you copy a Flogo application into a target subscription and activate a copy of a Live Apps application into the same subscription, Flogo continues to function using the copy of the Live Apps application in the target subscription without modification.

    However, you must not view or validate the Flogo app before publishing the Live Apps apps it references in the target subscription. If you do so, then the references to Live Apps apps that are not yet published in the target subscription will be considered invalid and will be removed. 
    It is no longer possible to activate a shared Live Apps application twice in the same target subscription, even if it was shared multiple times in the source subscription. To copy a Live Apps application into the same subscription again, you must:
    Create a new copy of the Live Apps application in the source subscription. In the Flogo flow in the source subscription, modify any Flogo application tasks that reference the Live Apps application to use the new copy of the application. Otherwise, on running the Flogo application in the target subscription, these tasks will use the previously copied Live Apps application. Copy the new Live Apps application by using the ?Share Externally? option and activate it in the target subscription, and also copy any new Flogo applications that use it. Closed Issues

    CBPM-25621
    Summary: You get an error on performing a bulk purge because the records are not removed and the logs get filled up.
    CBPM-25759, CBPM-20843
    Summary: Case state selection control is incorrectly included on the form for first form task when there are multiple form tasks in the Initial tasks of a case creator or case action.

    CBPM-25593
    Summary: You get an error on double-clicking the share application option.

    CBPM-25469
    Summary: When company data service task output mapping has nested list content, the individual output properties are not aligned correctly on the screen.

    CBPM-25465
    Summary: Company data services that give null elements in lists as output, can cause case creator and action processes to fail.

    CBPM-25453 
    Summary: In the data editor, Data field name control loses focus just after clicking on it when properties view is open.

    CBPM-24953
    Summary: UI shows the application status as published even when the application publish has previously failed.

    CBPM-25570
    Summary: While configuring a form in an application, when you select specific fields and want to change their order by using the up and down arrows, the fields do not move.

    Current Known Issues
    No issues have been reported in this release of TIBCO Cloud? Live Apps.

    Chinmay Gadre
    TIBCO Cloud? Nimbus?, Refresh 55 (June 2023)
    New feature

    Any maps and drilldowns that you delete are stored in the recycle bin. Deleted maps and drilldowns remain in the recycle bin until a fixed number of days. You can set the number of days from the Settings page. You can delete these maps and drilldowns permanently by purging them. You can also restore a deleted map if it has not been purged.
    Closed Issue

    NIMW-15799
    Summary: In the Web Client, although you enable the Local resources, the Local Resources switch is not visible on the Resources page.

    Current Known Issues

    No issues have been reported in this release of TIBCO Cloud? Nimbus?.

     

    Mrunal Rajendra Sul
    https://confluence.tibco.com/pages/viewpage.action?pageId=280003969
    Prerequisites:
     Mashery Local 5.6.0 images must be built and pushed to the desired registry for deployment. The volumes for tml-nosql, tml-sql, tml-log, tml-cache are reused, so while doing upgrade customer should maintain same number of tml-nosql, tml-sql, tml-log, tml-cache pods configured as the previous release (so all previous volumes will be reused accordingly) The customizations done to the properties files (docker-deploy/properties/*.json) in previous versions must be ported to Mashery Local 5.6.0. For example, tml_papi_properties.json in 5.5.0 has the same structure as 5.6.0, the customized tml_papi_properties.json in 5.5.0 can be copied to 5.6.0.
    An admin must generate the manifest deployment folder, namely the manifest, as per the deployment topology for version 5.6.0 by running the compose command.
    Note:
    Steps applicable for both Single and Multi zone clusters. Some traffic disruptions are expected during upgrade. To minimize disruptions, upgrade the Mashery Local components sequentially, explained as follows. 1) Undeploy and redeploy NoSQL components:
    a) Remove running Mashery Local 5.5.0 NoSQL container. Run the following command: 
    For single-zone deployment:
    ./undeploy-nosql-pod.sh
     
    b) Deploy Mashery Local 5.6.0 NoSQL containers. Run the following command:
    ./deploy-nosql-pod.sh
     
    2) Undeploy and redeploy Log components:
    a) Remove running Mashery Local 5.5.0 Log container. Run the following command.
    For single-zone deployment:
    ./undeploy-log-pod.sh
     
    b) Deploy Mashery Local 5.6.0 Log containers. Run the following command.
    For single-zone deployment:
    ./deploy-log-pod.sh
     
    3) Undeploy and redeploy CM components:
    a) Remove running Mashery Local 5.5.0 CM container. Run the following command.
    For single-zone deployment:
    ./undeploy-cm-pod.sh
     
    b) Deploy Mashery Local 5.6.0 CM containers. Run the following command.
    For single-zone deployment:
    ./deploy-cm-pod.sh
     
    4) Undeploy and redeploy SQL components:
     
    Please use steps mentioned in below page to migrate SQL data from TML 5.5.0 cluster to TML 5.6.0 Cluster.
     
    Dump MySQL Data from TML 5.5.0 Cluster
     
    Login to any tml-sql pod running in TML 5.5.0 cluster, i.e.
    kubectl exec -it mysql-set-0-0 -- /bin/bash
    Run the following command to dump MySQL data (update MySQL password for your cluster):
    mysqldump --no-create-info --complete-insert --single-transaction -u root -p'changeme' --ignore-table=masherysolar.areas --ignore-table=masherysolar.package_key_audit_log --ignore-table=masherysolar.application_audit_log --set-gtid-purged=OFF masherysolar > /tmp/mash_data.sql
    Note:
    If "Duplicate entry" error occurs when importing data to the new cluster, find the table where "Duplicate entry" occurs, prepare MySQL dump data again by ignoring that table. Here is list of tables which could cause "Duplicate entry" error masherysolar.member_activity_log
    masherysolar.member_audit_log
    masherysolar.member_role_audit_log
    masherysolar.method_override_audit_log
    masherysolar.migration_log
    Copy MySQL data file to your host, i.e. kubectl cp mysql-set-0-0:/tmp/mash_data.sql mash_data.sql
    a) Remove running Mashery Local 5.5.0 SQL container. Run the following command.
    For single-zone deployment:
    ./undeploy-sql-pod.sh
     
    Note: Please delete SQL pvc after undeploying the SQL pod.
    kubectl delete pvc $(kubectl get pvc -o=jsonpath='{.items[?(@.metadata.labels.app=="mysql-svc")].metadata.name}')
      b) Deploy Mashery Local 5.6.0 SQL containers. Run the following command.
    For single-zone deployment:
    ./deploy-sql-pod.sh
     
    Copy MySQL Data  dumped from TML 5.5.0 Cluster to TML 5.6.0 Cluster
     
    Run the following command to copy MySQL data file to any tml-sql pod in TML 5.6.0 cluster:
    kubectl cp mash_data.sql mysql-set-0-0:/tmp
    Clear MySQL Data in TML 5.6.0 Cluster In TML 5.6.0 cluster, login to the tml-sql pod  where the MySQL data file is copied to, i.e.
    kubectl exec -it mysql-set-0-0 -- /bin/bash
    Run the following command to clear data in MySQL:
    mysql -u root -p'changeme' -Nse 'show tables' masherysolar | sed -r 's/\b(areas|package_key_audit_log)\b//g' | sed '/^$/d' | while read table; do mysql -u root -p'changeme' -e "truncate table $table" masherysolar; done
    Import MySQL Data  dumped from TML 5.5.0 Cluster to TML 5.6.0 Cluster
     
    In the tml-sql pod where the MySQL data file is copied to, run the following command to import MySQL data dumped from TML 5.5.0 cluster to TML 5.6.0 cluster:
    mysql -u root -p'changeme' masherysolar < /tmp/mash_data.sql
    5) Undeploy and redeploy Cache components:
     
    a) Remove running Mashery Local 5.5.0 Cache container. Run the following command.
    For single-zone deployment:
    ./undeploy-cache-pod.sh
     
    b) Deploy Mashery Local 5.6.0 Cache containers. Run the following command.
    For single-zone deployment:
    ./deploy-cache-pod.sh
    6) Undeploy and redeploy TM components:
     
    a) Remove running Mashery Local 5.5.0 TM container. Run the following command.
    For single-zone deployment:
    ./undeploy-tm-pod.sh
     
    b) Deploy Mashery Local 5.6.0 TM containers. Run the following command.
    For single-zone deployment:
    ./deploy-tm-pod.sh
    7) Undeploy and redeploy Reporting components (Optional: If reporting pod is deployed):
     
    a) Remove running Mashery Local 5.5.0 TM container. Run the following command.
    For single-zone deployment:
    ./undeploy-reporting-pod.sh
     
    b) Deploy Mashery Local 5.6.0 TM containers. Run the following command.
    For single-zone deployment:
    source deploy-reporting-pod.sh "<zone-name>"

    Richard Flather
    Configuring a Kubernetes cluster for TIBCO Messaging Quasar - Powered by Apache Pulsar. The Kubernetes Container can be configured on Azure Kubernetes (AKS), Amazon Elastic Kubernetes Service (EKS), Google Kubernetes Engine (GKE), or a generic Kubernetes environment.  Supported Versions edelivery.tibco.comor Red Hat OpenShift Container Platform 4.x. Recommend latest versions of the container platform Prerequisites How_to_Configure_TIBCO_Quasar_Powered_by_Apache_Pulsar_2.1.1-1_in_a_Kubernetes_Environment.pdf
    tibapd_kubernetes_files_2.11.zip

    Richard Flather
    Document Purpose Creating a Docker® image embedding EMS and hosting it in a Docker registryProvisioning Persisted volume storage for cloud platforms, if requiredConfiguring and creating EMS containers based on the EMS Docker image to run in KubernetesOptionally, EMS can be deployed in Kubernetes via Helm Supported Versions TIBCO EMS 10.2.1 and lateror Red Hat OpenShift Container Platform 4.7. Recommend latest versions of the container platformHow_to_Configure_EMS_10.2_on_Kubernetes_files.pdf
    ems_10.2_files_kubernetes.zip

    Chinmay Gadre
    Migration and Compatibility
    TIBCO Cloud? Integration
    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 to ensure the best performance. 
    Closed Issues
    Develop/TIBCO Flogo®
    FLOGO-10817
    Activities in a flow are overlapping with each other when a non-owner opens up an app before the owner after upgrading.
    FLOGO-10818
    Coercion is not enabled for Params input and schema on HTTP trigger and client..
    Develop/TIBCO Flogo® Connectors
    WIMSSS-454
    "Retry on Error" option does not work as the connection is stopped by Azure. This happens when there is no activity for more than 30 minutes.

×
×
  • Create New...