Category Archives: Tibco Business Works

Download our TIBCO products and start building innovative applications and solutions with latest versions!

License Type: Developer Evaluation Term: 90 days

TIBCO Rendezvous® Software

TIBCO ActiveMatrix BusinessWorks™

TIBCO Enterprise Message Service™

TIBCO BusinessEvents®

TIBCO ActiveSpaces®


SOAP Event Source process starter

The SOAP Event Source process starter creates a process instance for incoming SOAP requests. SOAP is a standard protocol for invoking web services. This allows you to create a web service using process definitions. At runtime, a client can retrieve the WSDL file for a process containing this process starter using an HTTP request. Once the WSDL file is retrieved, the client can perform a SOAP request to invoke the web service.


Leave a comment

Posted by on November 29, 2012 in Tibco Business Works


SOAP Send Fault activity

The SOAP Send Fault activity sends a SOAP fault to the client if an error occurs during processing of a SOAP request. This activity is used when the SOAP Event Source process starter handles incoming SOAP requests. The WSDL file for the request can have one or more fault messages defined for an operation. The SOAP Send Fault activity can use the fault schema to send application-specific data about the fault back to the client that made the SOAP request. This activity cannot be used if the SOAP request is one way. SOAP faults are required to send the fault code and the fault string. These values are required input items on the Input tab. For example, “Client” can be used for client faults and “Server” can be used for server faults.

Leave a comment

Posted by on November 29, 2012 in Tibco Business Works


SOAP Request Reply activity:

The SOAP Request Reply activity performs a request on the specified web service and optionally expects a reply from the web service. You can invoke both document and RPC web services with this activity.


Leave a comment

Posted by on November 29, 2012 in Tibco Business Works


Difference between soap and service palette – when/how to use?

We can create web services in two ways.

SOAP Event Source
Service Palette

Service Palette offers architectural advantage over SOAP Event Source when you want to develop web services. Service Palette offers multiple operations defined at a higer level while the configuration is scattered when you use SOAP event source to implement multiple operations in the service.

One of the differences between Service palette and soap event source is is when it comes to sequencing. When you use SOAP Even source you have sequencing key in the Misc tab and this field can contain an XPath expression that specifies which processes should run in order. Process instances with sequencing keys that evaluate to the same value will be executed sequentially in the order the process instance was created.

Using the SOAP Event Source, you can run only one operation at a time. While using the Service Palette you can run multiple operations simultaneously

When to use services/soap activity: When you have to use multiple transports, use services to build ur websevices, using soap activity you can configure only one transport.

Steps to create a web service .
1. Define XSD
2. Define the HTTP / JMS Connection
3. Create Abstract WSDL from the XSD
4. Right Click the Abstract WSDL and select “Tools or Multi-User” > “Generate Web Service” > “From WSDL”
5. Select the Transport
6. Generate the Concrete WSDL from the “WSDL Source” of the Service WSDL
7. Define the Logical Operation
8. Create a Client Process and invoke the web service using the “SOAP Request Reply” Activty.
9. Set the “Service” Of the “SOAP Request Reply” to point to the Concrete WSDL

Siva ,


Posted by on November 25, 2012 in Tibco Business Works


what is difference between the SOAP over JMS and SOAP over HTTP?

Consider using SOAP over HTTP for:

• Externally facing web services (e.g. customers or suppliers)
• For simple point-to-point and stateless services
• Where you need a thin client with no MOM installations

Consider using SOAP over JMS for:

• High-volume distributed messaging
• Asynchronous messaging
• Where a transaction boundary is needed in the middleware
• Where the message consumers are slower than the producers
• Guaranteed deliver and/or only once delivery of messages
• Publish/subscribe
• Distributed peer systems that might at times be disconnected

Leave a comment

Posted by on November 10, 2012 in Tibco Business Works


Detecting & handling duplicate process instances

Duplicate messages should be detected and discarded to avoid processing the same event more than once. Duplicate detection is performed when a process instance executes its first Checkpoint activity.

To detect duplicates, a value must be specified for the duplicateKey element in the Checkpoint activity input schema. This value should be some unique key contained in the event data that starts the process.

For example, the order ID value is unique for all new orders or JMS Message ID in case of message is received from JMS.

Duplicate detection can only be done across multiple engines on different machines if a database is used to store process engine data. If you are running fault tolerant process engines (that is, only one process engine is running at a particular time), or if all process engines run on the same machine, you can use a file system for process engine storage.

When a duplicate is detected, the Checkpoint activity fails with the DuplicateException. You can place an error transition from the Checkpoint activity or Catch activity to a series of activities to handle the duplicate message. If no error transition is specified, the process instance terminates and duplicate messages are effectively ignored.



In this example, when a duplicate message is detected, the duplicate message is confirmed so that it is no longer redelivered, then the transition is taken to the end of the process definition.



Posted by on November 4, 2012 in Tibco Business Works


Event Candidate Key & Event time out

Event Candidate Key:

Expression used to evaluate whether the incoming message is appropriate for this process. This expression is specified in XPath, and only data from the incoming event is available for use in this XPath expression.


Event time out
The amount of time a message will wait (in milliseconds) if it is received before this task is reached in the process. If the event timeout expires, an error is logged and the event is discarded.

If no value is specified in this field, the message waits indefinitely. If zero is specified, the event is discarded immediately, unless this has already been reached

Leave a comment

Posted by on October 30, 2012 in Tibco Business Works


Tibco Business Works

TIBCO BusinessWorks is a scalable, extensible, and easy to use integration platform that allows you to develop integration projects. TIBCO BusinessWorks includes a graphical user interface (GUI) for defining business processes and an engine that executes the process.

TIBCO BusinessWorks also works with TIBCO Administrator, a web-based GUI for monitoring and managing run-time components.

TIBCO BusinessWorks Key Components

TIBCO BusinessWorks key components work together as follows:

  • The TIBCO Designer graphical user interface (GUI) supports adapter configuration, process design, and testing of the integration project in one easy to use interface. You can use TIBCO Designer in test mode to incrementally verify your design during development.
  • The TIBCO BusinessWorks engine runs the business processes in test mode and at run-time.
  • TIBCO Administrator supports deployment, security administration, and monitoring and management of processes and machines. TIBCO Administrator consists of the TIBCO Administration Server and the web browser based TIBCO Administrator GUI.
  • The TIBCO Runtime Agent (TRA) runs on each machine and executes scripts, sends alerts, and performs recovery as specified.
  • Optionally, TIBCO BusinessWorks interacts with TIBCO InConcert in its implementation of ManualWork activities.
Leave a comment

Posted by on September 3, 2012 in Tibco Business Works


How you perform performance tuning on BW engine and EMS ?


Performance Tuning in BW engine!!

  • Max jobs
  • Flow limit
  • Activation Limit
  • Java heap size

Performance Tuning in EMS!!

Performance Tuning: Performance tuning can be done at EMS server level/Administrator level
In EMS it can be done using prefetch mechanism,thereby regulating the consumption of messages. The prefetch mechanism is avialable in both queues and topics
In Administrator, performance tuning is done by adjusting the count of the threads.also by setting the flow limit, activation limit, max limit.

Leave a comment

Posted by on August 27, 2012 in Tibco Business Works, Tibco EMS


Get every new post delivered to your Inbox.

Join 40 other followers