TIBCO Business Works

TIBCO Business Works

23/02/2012

ANURADHA S (181316) anuradha3.s@tcs.com

Internal Use

TIBCO Business Works

Introduction
TIBCO Business Works is easy to use event driven integration platform that allows developing Enterprise Application Integration projects. TIBCO Business Works includes a GUI for designing business processes and an engine that executes the process. TIBCO Designer allows the user to easily create integration projects for enterprise computing environment. TIBCO Designer is the graphical user interface for defining business processes. The product facilitates complete visibility into business activities, along with the ability to collaborate on the modeling and modification of the rules and flows that define business those activities. TIBCO Business Works Workflow uses TIBCO Designer for configuration of Form Flows processes and for preparing Enterprise Archive files. Overview of Designer: There are four panels which constitute the Designer Project panel - displays the project tree/ projects global variables Design panel displays the resources that are selected in the Project Panel Configuration panel helps in defining configurations Palette panel contains the palette which can be dragged and dropped while designing

Designer with all the panels

Design Panel

Project

Panel

Configuration Panel

Internal Use

TIBCO Business Works

Overview of a Project in TIBCO Designer The TIBCO Designer can be understood clearly with a sample project as illustrated below ORC_RECENCY is the sample project The Crew on Flight Notification is an incoming event that is triggered to trigger another application. The process is defined as shown below.

A Process generally is started with a Start button and ends with an End button. We can also handle the Error scenarios as shown in the previous screenshot. The configuration for the

Internal Use

TIBCO Business Works

selected process can be configured in the Configuration panel. The Perform Notification Orchestration indirectly is a Sub process which calls many webservices which can be seen in the next screen.

The Perform Notification Orchestration indeed calls upon many other webservices (subprocesses) in order to create a request with all inputs to trigger the event. The process WSC_Flight_GetByDep is selected and the input and output attributes are defined in the Configuration panel as shown below. The input from the start is mapped to the required input in the activity and the WSDLs are also mapped to validate the input and output elements.

Internal Use

TIBCO Business Works

This is the Subprocess WSC_Flight_GetByDep which has the activity Call WebService where the inputs are mapped to the activity inputs which accesses the webservice and sends the output and the subprocess ends when the end button is reached.

The output of subprocess WSC_Flight_GetByDep is mapped as input to the next Activity in the process. The next activity being Match Flight Leg which just validates the output of GetByDep and the error scenarios are handled. As shown, the validation of the output can be done by giving the condition in the configuration. The Xpath is where we give the condition to validate that only one unique

Internal Use

TIBCO Business Works

value exists and thus passes on to the next activity. The output of MatchFlightLeg is mapped as input to the next activity WSC_ProvideAircraft.

Setting up Global Variables The Global Variables Tab helps in defining the variables in Global scope. In the subprocess WSC_GetByDep, the global variables are defined for the SOAP Action and the specific version.

Internal Use

TIBCO Business Works

Testing Process Definition

The test case for the sub process WSC_GetByDep is shown below. The testcases are defined under the messages folder. The example has HappyFlow_GetByDep_IN which holds the request and the HappyFlow_GetByDep_OUT holds the response. The GetTestCase activity gets the test case files from the messages folder and the Parse getByDep XML activity parses the XML which maps the values to the response. The Handle Response is the one which validates if the responses match.

The testing process is triggered by running the jobs button which will be present in the tester tab. On clicking run, pop up will be displayed to select the process for which the test cases need to be run. On clicking Load selected the GetByDep process test cases will be run and the results will be displayed.

Internal Use

TIBCO Business Works

The final output of the testcases will be displayed as shown below.

Conclusion: This document explained the TIBCO Designer in a high level view illustrated along with a sample project.

Internal Use