TIBCO EMS :

TIBCO EMS : 

TIBCO Enterprise Message Service™, our standards-based Java™ Message Service (JMS) broker allows any application that supports JMS, whether home grown or third-party, to quickly and easily exchange messages. Fully certified with both the JMS 1.1 and 2.0 specifications ensures compatibility with other applications—as well as a loosely coupled design for less overhead, time, and cost. As part of TIBCO® Messaging, it supports seamless integration for heterogeneous platforms, reduces system bottlenecks, increases scalability, and helps you respond faster to change.

TIBCO EMS will be  Interoperability enabled by standards

Capabilities :

1)  Flexible Qualities of Service
2)  Secure Communication
3)  Secure Communication
4)  Interoperability Across all TIBCO Messaging

TIBCO EMS communicates  through Queue and Topics .
 Persistent : When a manufacturer sends a PERSISTENT message, the producer must wait for the server to reply with a confirmation.
 Non-persistent  : Sending a NON_PERSISTENT message omits the overhead of persisting the message on disk to get better performance.
 Reliable : EMS extends the JMS delivery modes to include reliable delivery. Sending a RELIABLE_DELIVERY message omits the server confirmation to improve        performance regardless of the authorization setting.

TIBCO EMS Acknowledgement Modes

TIBCO EMS Acknowledgement Modes 
    Auto  : When sender sends an message, the message will be acknowledged                          immediately when it is received by the receiver.
     Client  : when the sender sends, the receiver will acknowledge after the receipt of                                message. In process implementation, the message will be acknowledged when                      the confirm activity executes. 
    TIBCO EMS Explicit : It receives all the messages in one session and acknowledges the                                         message after the execution of confirm activity in the process                                                 implementation. If even a single message is not acknowledged,                                               then all the messages will be redelivered.
      TIBCO EMS No   : TIBCO EMS No will never send an acknowledgement for a message                                       received by JMS receiver and will reduce the traffic.
     Dups Ok  :When the receiver has a lot of operations and performance issues, the                               acknowledgement will be sent for all the messages during a convenient timing.           TIBCO EMS Explicit Dups Ok : Unlike Dups Ok ack mode, it acknowledges for the                                                                   individual message at a time.
     Transactional   : Transactional ack mode will be used when a transaction can process                                      JMS messages. It will send acknowledgement when the transaction                                        commits.
     Local Transactional : This ack mode will consider JMS produced messages and                                                       consumed messages as a transaction. It will send a                                                                 acknowledgement based on receipt of messages.

TIBCO EMS : 

TIBCO Enterprise Message Service™, our standards-based Java™ Message Service (JMS) broker allows any application that supports JMS, whether home grown or third-party, to quickly and easily exchange messages. Fully certified with both the JMS 1.1 and 2.0 specifications ensures compatibility with other applications—as well as a loosely coupled design for less overhead, time, and cost. As part of TIBCO® Messaging, it supports seamless integration for heterogeneous platforms, reduces system bottlenecks, increases scalability, and helps you respond faster to change.

TIBCO EMS will be  Interoperability enabled by standards


Capabilities :

1)  Flexible Qualities of Service
2)  Secure Communication
3)  Secure Communication
4)  Interoperability Across all TIBCO Messaging

TIBCO EMS communicates  through Queue and Topics .

EMS Delivery modes :

      Persistent : When a manufacturer sends a PERSISTENT message, the producer must wait for the server to reply with a confirmation
  Non-persistent : Sending a NON_PERSISTENT message omits the overhead of persisting the message on disk to get better performance.
     Reliable :EMS extends the JMS delivery modes to include reliable delivery. Sending a RELIABLE_DELIVERY message omits the server confirmation to improve performance regardless of the authorization setting.


  

TIBCO Integration Introduction

Approaches

TIBCO integrates the applications from below approaches :

1) Point to Point Integration 
2) Hub and Spoke integration 
3) Enterprise service bus

Point to Point Integration features

• Systems communicate directly with each other.
• Basic, Traditional, Easy and Quick.
• Tight coupling.

Hub and Spoke integration

• Direction communication is not needed.
• It will be scalable to some extent.

Disadvantage-
        If Hub is down, it will affect all systems communication.

Enterprise service bus : 

• Light weight, easy to expand.
• SOA friendly.
• Incremental adoption.

Sorting in Mule 4

Sorting the data can be done using dataweave in Mule 4 with orderBy function.

orderBy: Reorders the content of an object using a value returned by a function as the criteria.

Sorting Numbers: In Mule 4 using dataweave.

Ascending order: To sort the numbers in ascending order, use 'orderBy $'.
Example: numberAsc: ([3,8,1,6] orderBy $)

Descending order: To sort the numbers in descending order, use 'orderBy -$'.
Example: numberDesc: ([3,8,1,6] orderBy -$)

Sorting Letters: In Mule 4  using dataweave.

Ascending order: To sort the letters in ascending order, use 'orderBy $' just like in case of sorting the numbers.
Example: letterAsc: (["s","e","p","z","a"] orderBy $)

Descending order: To sort the letters in descending order, there is an extra logic to be used. Arrange the letters in ascending order using 'orderBy $' and on top of that, use '[-1 to 0]', which inverts the ascending order thereby giving the descending order of letters.
Example: letterDesc: (["s","e","p","z","a"] orderBy $)[-1 to 0]

Complete code snippet:
Input Dataweave logic:

Output:

Please feel free to comment your queries/opinions.

Issues in Mule 4

Munit Debug Error

• Currently the recommended version of runtime in Mule 4 is 4.1.5.

When we create Munit for our Mule 4 applications and try to run the test cases in debug mode,  we have an issue at times.

 

One of the solution for this is :

1. Copy the files from "C:\Users\{username}\.m2\repository\com\mulesoft\mule\agent\mule-debugger\4.1.4"

2. Paste them to "C:\Users\{username}\.m2\repository\com\mulesoft\mule\agent\mule-debugger\4.1.5" and rename file from 4.1.4 to 4.1.5

This should solve your problem.

Mule 4

Introduction

• Mule 4 comes with the Anypoint Studio version 7, in simple Studio 7.
• In Mule 4, we have Dataweave Language which replaced Mule Expression Language(MEL).
• Try scope is added for the error handling which helps in handling easily.
• Dataweave has been changed to 2.0.
• Minor changes to Munit, which is easy to use now.
• In mule 4, the code by default is a mavenised code. There is no need of manually mavenising as in case of Mule 3.
• With Mule 4, it is now easy to build/develop the applications.

Will be adding more in detail with common issues faced in Mule 4.