1

TIBCO BW Training - 22nd - 24th March, 2006Prepared By: Kishore Tanikella, TCS

2

AgendaAgenda - Day1

1 BusinessWorks Introduction

2

3

4

Processes and Sub Processes

5 Transitions , Groups and Usage

TIBCO BusinessWorks Components

Get Used to Icons and Process Starters

6 Variable in TIBCO BusinessWorks

7

8 TIBCO BW Demo & Installation

Error Handling

9 Case Studies

3

AgendaAgenda - Day2

3 User Management

4 Resource Management

6 Demo on TIBCO Administrator

7 Case Study - Deployment

1 TIBCO Administrator

2 Domain Utility

5 Application Management

4

BusinessWorks - Business Integration

Business Integration

TIBCO BusinessWorks is a scalable, extensible, and easy to use integrationplatform 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.

It provides an integrated user experience for all phases of the integration life cycle, including process Automation, data transformation, adapter configuration, deployment, security and runtime administration and monitoring.

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

5

BusinessWorks Key Components

TIBCO Designer

TIBCO BusinessWorks Engine

TIBCO Runtime Agent

TIBCO Administrator

6

BusinessWorks Key Components

7

BusinessWorks Key Components

Starting the TIBCO Designer

• Click Start>Programs>TIBCO>Designer_version (or ) Navigate to the <tibco_home>/designer/<version>/bin directory.

• Type ./designer

• Select one of the Startup Options.

8

TIBCO Designer Administration

BusinessWorks Key Components

9

BusinessWorks Key Components

Configure Designer Runtime

• Extended Class Path— Classpath to be used by TIBCO Designer. Users can specify file names or directories. If they specify directories then all .class, .zip and .jar files will be loaded.

• Palette Path—Location from which TIBCO Designer loads palettes.

• Maximum Heap Size—Maximum JVM heap size.

• User Directory—Default location for the application to store files.

• Command Line Arguments—Allows command line arguments to be passed to Designer. Currently -d (debug) is supported. If you specify -d, the log that is sent to the Console becomes more detailed.

10

TIBCO Designer Interface Overview

BusinessWorks Key Components

Which palettes are displayed depends on:

• the installed TIBCO products

• the resource selected in the project tree

• preferences set

11

Project Structure

• Not all folders in TIBCO Designer are directories in the file system

• Folders created from a Folder resource in the General Palette (displays a multi-folder icon) become folders in the file system.

• Other folders, such as the Adapter Services folder inside an adapter configuration are

• logical folders

• only exist in memory in the resource that holds them.

• Actual data for these elements is stored in the file of the top-level resource. For example, Adapter Services data is stored in the Adapter Configuration file.

BusinessWorks - Multiple File Structure

12

Using a Version Control System

Multi-file projects support the use of different version control systems because they consist of separate files for each versionable component.

The following version control systems are supported with Designer 5.2

• File Sharing• ClearCase• CVS• Microsoft Visual SourceSafe• Peforce Fast Software Configuration Management System

BusinessWorks - Configuration Management

13

Validating Projects

• During validation, each resource always checks for broken references.

• To validate resource, do one of the following:

• Choose Validate from the right-button menu,

• Select the resource to be validated, then choose Resources > Validate Resource from the menu bar.

• With the resource selected, choose the Validate icon.

• To validate all resources in a project, do one of the following:

• Choose Project > Validate Project for deployment.

• Click the Validate Project icon.

BusinessWorks - Compilation?

14

Overview of Processes

• A Process definition is a graphical representation of your business process

• You can develop and test business processes using TIBCO designer

• The process definition is executed by a TIBCO BusinessWorks process engine

BusinessWorks - Processes

15

Components of a Process Definition

• Activities• Transitions• Groups• Shared Configuration Resources• Subprocesses

Subprocesses

• Subprocesses cannot have process starters as the start activity

• Procedure for creating and calling a sub-process

• Create a process definition for the sub-process

• Specify the input, output and any error schemas on the start and end activity

• Create a process definition that will call the subprocess

• Place a call process activity in the process definition or drag the subprocess into the main process definition

BusinessWorks - Processes

16

Subprocesses

BusinessWorks - SubProcesses

17

Developing Process Definition

BusinessWorks - Process Definition

18

Activity Icons

Get Used to Icons

19

Process Starters• When a process starter is placed into a process definition, it replaces the default Start activity, and becomes the first activity in the process

Palette Process Starter Starts a process when...Adapter SubscriberAdapter Request-Response Server

File File Poller The specified file is created, changed, or deleted.

Timer The specified time interval occurs. You can start processes for one-time events or schedule processes to start on recurring time intervals.

Receive Notification A corresponding Notify activity has executed.

HTTP HTTP Receiver An HTTP request is received.JMS Queue Receiver

JMS Topic SubscriberMail Receive Mail Mail for the specified user is received by

the mail server.Rendezvous Rendezvous Subscriber A TIBCO Rendezvous message is

received.SOAP SOAP Event Source A SOAP web services request is received.

ActiveEnterprise Adapter A message or a request from an adapter is received.

General Activities

JMS Either a JMS queue or topic message is received.

Process Starters

20

Transitions

• Transitions describe the flow of processing

• It is represented by an arrow between two activities or group of activities in a process definition

• The arrows are unidirectional and cannot be drawn to a previously executed activity

• Different condition types for a transition are• Success • Success with condition• Success if no matching condition• Error

Transitions

21

Groups

• To create a set of activities with a common error transition

• To create sets of activities to be repeated (iterations)

• To create set of activities that participate in transaction

• To create critical section that synchronizes process definitions

• To specify that the first activity that completes should determine which transition(s) to take to continue processing. This allows you to wait for one or more incoming events and continue processing based on what incoming event was received first.

Groups

22

Loops

• Loops allow you to execute a series of activities more than once

• Types of loops that are available are:• Iterate Loop• Repeat Until True Loop• Repeat On Error Until True Loop

Activity Output and Groups

• If the group is used for a loop (iterate, repeat until true, and so on), activity output in the group is reset so that activities in subsequent iterations of the group will not have access to output data from previous iterations

• If you wish to store data from each successive iteration of a loop, • Create a process variable and use the Assign activity in the loop to store or alter data for each iteration.• Accumulate the output of each execution of one activity in the group into a list.

Loops and Activity Output

23

Critical Section Groups

• Critical section groups are used to synchronize process instances so that only one process instance executes the grouped activities at any given time.

• Any concurrently running process instances that contain a corresponding critical section group wait until the process instance that is currently executing the critical section group completes.

Critical Section Groups

24

Pick First Groups• Pick first groups allow process execution to wait for one or more events.

• The first event that completes determines which transition to take to continue processing.

• Only request/reply, Wait for ... activities, and activities that have the pause symbol can have valid transitions from the start of the Pick First group.

Pick First Groups

25

Different Types of Variables• Global Variables• Process Variables• Shared Variables

• Global Variables — These variables allow you to specify constants that can be used throughout the project.

Variables in TIBCO BusinessWorks

26

Global Variables

Usage of the global variable in the fields of a resource,

• enter the variable name surrounded by %% on both sides.

•drag from the Global Variable tree in the display into a text field in the configuration panel.

Changing the Global variables at runtime

• By Modifying runtime variables using TIBCO Administrator• By Changing the values in .tra file as below-tibco.clientVar.<variablePathAndName> <value>

Variables in TIBCO BusinessWorks

27

Process Variables

• Process Variables — Allow you to access various data in your project.

• Types of Process Variables

• Activity Output

• Predefined Process Variables

• There are two process variables that are available to all activities that accept input: $_globalVariables and $_processContext (such as process ID, process name and so on)

• Error Process Variables

• When an error occurs in a process, the data pertaining to the error is placed into process variables. The $_error process variable contains general error information. Activities can also have error process variables named $_error_<activityName>.

• User-Defined Process Variables

Variables in TIBCO BusinessWorks

28

Shared Variables• Shared Variables — These variables allow you to specify data for use across multiple process instances.

• Activities

• setSharedVariable

• getSharedVariable

Variables in TIBCO BusinessWorks

29

Error Handling

30

Error Handling

Logger Level

Starter Process Level

Sub-Process Level

31

Demo

TIBCO Designer and TIBCO BusinessWorks

Installation

TIBCO Runtime Agent 5.2.1TIBCO BusinessWorks 5.2.1TIBCO ADB Adapter 4.2.1

Case Study 1Usage of JDBC Palettes

Case Study 2Usage of Adapter Palettes

Case Study 3Usage of XML Palettes and group activities

Focal Point

32

Thanks