Sunday, March 27, 2011


EXPLICIT_CLIENT_ACKNOWLEDGE is like CLIENT_ACKNOWLEDGE except it acknowledges only the individual message, rather than all messages received so far on the session.


When we receive the messages and put their information in a database and if the database insert operation is slow, you may want to use multiple application threads all doing simultaneous inserts.

As each thread finishes its insert, it can use this mode to acknowledge only the message that it is currently working on.

For EMS message delivery modes Click here.


Sunday, March 20, 2011

TIBCO JMS Message Compression

What is message Compression...?

  • TIBCO Enterprise Message Service allows a client to compress the body of a message before sending the message to the server.
  • Compression option only compresses the BODY content. Headers and properties are NEVER compressed.
  • Compression is specific for individual messages. Not on a per-queue or per-topic basis.
  • EMS supports message compression/decompression across client types (Java, C and C#). For example, a Java producer may compress a message and a C consumer may decompress the message.
  • Message compression is supported in .NET clients when using the install package for Visual C++ 8 / .NET 2.0 or above.

What is the advantage of Message Compression...?

How to add compression property to message...?


When messages are not stored, compression is not a good option. Why?

  • Because, Compression takes TIME…!


Sunday, March 13, 2011

Configuring Generate Error activity and its usage

Usage: If you would like to catch and raise your own error conditions, you can use this activity. This activity generates an error and causes an immediate transition to any error transitions. If there are no error transitions, the process instance halts execution.

Steps to configuring Generate Error activity to raise your own exception

  • Create Error Schema under Error Schema tab in your END activity (each process definition consists START and END activity), then check under generate error activity you will see the schema which you created.

  • Map the process data to this schema or write conditions to evaluate to true so that exception will rise as expected.


Sunday, March 6, 2011

Steps to configure Fault Tolerance mode in TIbco Admin GUI

  1. Create an EAR file using Tibco Designer.
  2. Using Application Management, click New Application to Browse and upload the ear file into Tibco administrator GUI.
  3. Go to Configuration(Application's) and click on process archive.
  4. Click on 'Add to Additional Machines' in General tab to select the machine name. when you add, the FT section (Run Fault Tolerant) will be enabled in FT Group Settings.
  5. Specify the weights to the process instance in FT Weight and time intervals in FT Group Settings.
  6. Using Monitoring tab, we can add Rulebases and Events if needed.
  7. Save and Deploy.
  8. In Service Instances, we observe that one instance gets started in active mode and another would be in Standby mode by starting the application


Popular Posts

  © Blogger templates The Professional Template by 2008

Back to TOP