P. 1
Tib Bw Process Design Guide

Tib Bw Process Design Guide

4.5

|Views: 4,893|Likes:
Published by api-3820704

More info:

Published by: api-3820704 on Oct 18, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

You can group a set of related activities, with a common set of transitions into and
out of the group. If you do not wish for the activities in the group to repeat,
specify the group action to be None. No action groups are primarily useful for
specifying a single error transition out of the group so that if an unhandled error
occurs in the group, you only need one error transition instead of an error
transition for each activity. This behavior is similar to a try...catch block in
Java.

Group Action: Critical Section

Scope

Defines the scope of the critical section group.

•Single Group — specifies that all process instances
in the same process engine for the current process
definition will be synchronized on the current
group.

•Multiple Group — specifies that all process
instances for the current process definition and any
other process definition with a critical section group
specifying the same lock resource will be
synchronized. If you are synchronizing across
multiple process engines, you should select the
Multiple Group option. This option requires the
Lock resource to be specified in the Lock Object
field.

Lock Object

The Lock shared configuration resource that
synchronizes critical section groups across process
definitions and potentially across process engines.

Table9 Group Configuration tab

Field

Description

TIBCO BusinessWorks Process Design Guide

80

|Chapter6 Grouping Activities

The following process definition illustrates a no action group that has one error
transition out of the group to process any unhandled errors that occur when the
grouped activities execute.

The process performs the following operations:

1.An FTP Get activity retrieves a file from an FTP server.

2.A Write File activity writes the retrieved file so that its contents are available
at a later time.

3.The contents of the file are used to create an HTTP request to a web server.

4.In the event of an error, a TIBCO Rendezvous message is published so that an
administrative application can be notified of the error. If all activities in the
group succeed, an email message is sent.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->