Introduction to EAI

Why Integration?
1. The applications probably run on multiple computers ,which may represent multiple
platforms and may be geographically dispersed
2. Business parteners (or) customers may run some of the applications outside of the
enterprise
3. Share data across applications
. !eep information synchronised across multiple data stores
". #mpro$ed Business process and increased customer satisifaction
#n order to achie$e the abo$e there is need for integration of %nterprise applications.
Integration is the tas& of ma&ing separate applications wor& together to produce a unified set of
functionality
EAI Definition
%'# is the unrestricted sharing of data and business processes among any connected
applications and data processing in the enterprise.%'# has become a sophisticated set of
procedures with newly refined technologies, such as middleware and message bro&ers that
allow users to tie systems together using a common glue code.
There are powerful tools and techni(ues to perform %'# successfully.
Types of EAI
%$ery integration process in an enterprise application will fall in any of the four le$els, such as
data le$el,application interface le$el, method le$el, and user interface le$el in an application.
1. Data-level EAI : transferring data between data stores. This can be described as
e)tracting information from one database, if need, processing that information and
updating the same in another database. Advantage : *ost is $ery less because there
may not be any changes in the application code and hence there is no need for testing
and deploying the application
2. Application interface level EAI :refers to the le$eraging of interfaces e)posed by
custom or pac&aged applications. +e$elopers ma&e use of these interfaces to access
both business processes and simple information.
Advantage : ,sing these interfaces, de$elopers are able to bring many applications
together, allowing them to share business logic and information.
This particular type of %'# is most applicable for %-. applications, such as S'.,
.eopleSoft and Bann, which will e)pose interfaces into their processes and data, do so
in $ery different ways.
3. Method level EAI : is the sharing of the business logic that may e)ist within the
enterprise. 'pplications can access methods on any other application. The mechanisms
to share methods among applications are any including distributed ob/ects, application
ser$ers, and T. 0onitors. 'n 1-B can ta&e the call of one application to methods
stored in other applications. 'n application ser$er can be a shared physical ser$er for a
shared set of applications ser$ers.
Advantage : 0ost of the integration has been happening at this le$el as there are a
number of robust technologies to accomplish this type.
. User interface level EAI :'rchitects and de$elopers are able to bundle applications by
using their user interfaces as a common point of integration. 2or e)ample, mainframe
applications that do not ha$e database or business process3le$el access may be
accessed through the user interface of the application.
Advantage : *ommon point of integration and on many occasions, this is the only way
of approaching integration tas&.
What is MIDDLEWAE
#t is used as simple mechanism to mo$e information and share businesslogic between different
enterprise applications
Advantages of Middle!are
1rgani4es integration
5ides comple)ities of the source and target systems
%ase the maintence and accomadates change seamlessly
*reate common communication protocal
Middle!are " #odels
1 6ogical middleware model
2 .hysical middleware model
1.Logical middleware model
.oint 7 to 7 point
#deal for two applications
e) 8 -pc9s
0any 7 to 7 0any
6in&s many applications to many other applications
e) 8 %'#(Tibco,webmethods,$itria....)
2.Physical middleware model
Bus 0odel
5ub3Spo&e 0odel
0ulti35ub 0odel
Bus Model
#s a +ecentrali4ed 'rchitecture
:et;or& Bus act as the message carrier
*ommunication .attern is peer 7to 7peer
0essages are (ueued by .ublishers
e)8 T#B*1

Hub-Spoke Model
a centrali4ed configaration
The 5ub acts li&e a ser$er
'll 0essages throw the 5ub
'll 0essages are (ueued in the ser$er
*ommunication protocol is pulisher to ser$er and ser$er to subscriber
e)8 ;%B0%T51+S
Multi-Hub Model
0ultiple 5ubs are lin&ed together
6oad sharing
pro$ide fault3safe ser$ice
*omple) to *onfigure and maintain
Middle!are "$o#ponents
0essage
3 ' unit of data ,which may (or) may not contain header (or) additional information
0essage <ueue
3 ;here the message is stored=persisted 2or certain amount of time
.ublicsher
3 .ublishes the messages from an application
Subscriber
3 Subscribes the message and send it to application using '.# (or) to the database
Middleware-features
2aciltate the asynchronous and Synchronous communication
Message %us architecture
#n this architecture, each application connects to a message bus. %ach integrated application
associates with an integration node (also &nown as adapter) connected to the multicast networ&.
%ach integration node uses multicast ot broadcast information to other integration nodes. ;hen
an application wants to share information with its peers, it sends a integration nodes pic& up the
message on the networ&. %ach message has an associated sub/ect. .articipating integration
nodes pic& up the message and chec& whether they are interested in the sub/ect. #f they are, the
integration node processes the message by in$o&ing some business logic on the application it is
integrating. The message bus architecture is common with Tibco -ende4$ous.
2igure8 0essage bus architecture
Advantages:
;ith message bus architecture, you can propagate a single message to multiple clients. ;hen
a multicast pac&et goes out, any interested application can pic& up and process the pac&et. #f
multiple clients re(uire e)actly the same data, you can send the data once, and each interested
application will pic& up and process the information.
Disadvantage:
0essage bus architectures often ha$e security problems. #t is difficult if not impossible to
support authori4ation 3based access to multicast pac&ets. 0ulticast 3 based integration
architectures drop pac&ets on a networ& that any networ& member can see.
0essage bus architectures also increase networ& traffic. 0ulticast pac&ets negate the
intelligent routing beha$ior of switches and bridges. %$ery client in the same networ& as
the integration nodes processes multicast pac&ets to the application layer of the open
system interconnection (1S#) model. *lients then waste *., cycles processing and
discarding in$alid pac&ets.
's another disad$antage, consider the proprietary nature of message bus architectures.
*urrently, Tibco is the only $endor that implements the message bus architecture.
2inally, multicast pac&ets cannot cross networ& boundaries without help from protocol
con$erters. #f another application to be integrated resided in a separate networ& or
subnet, another process must pic& the multicast pac&ets, con$ert them to unicast
pac&ets, and then forward the pac&ets to another process in the other networ&. That
process in the remote networ& con$erts the unicast pac&ets bac& to multicast pac&ets for
the integration nodes on the remote networ& to recei$e.
6ac& of centrali4ed management. %ach integration node must utili4e some type of -'#+
(redundant array of ine)pensi$e dis&s) configuration to support message log file integrity
3 an e)pensi$e proposition.
&U'I(E'' W)*s
> T#B*1 Business;or&s is a scalable, e)tensible, and easy to use integration platform that
allows you to de$elop integration pro/ects.
> T#B*1 Business;or&s includes a graphical user interface (?,#) for defining business
processes and an engine that e)ecutes the process.
> T#B*1 Business;or&s also wor&s with T#B*1 'dministrator, a web3based ?,# for monitoring
and managing run3time components
&usinessWor+s *ey $o#ponents
> T#B*1 +esigner
> T#B*1 Business;or&s engine
> T#B*1 -untime 'gent (T-')
> T#B*1 'dministrator +omain
TI&$) Designer
> The T#B*1 +esigner graphical user interface (?,#) supports adapter configuration, process
design, deployment configuration, and deployment of the integration pro/ect in one easy to use
interface..
TI&$) Designer Interface
> 0ain ;indow
> .ro/ect .anel
> .alette .anel
> +esign .anel
> *onfiguration .anel
,ro-ect ,anel
> ' pro/ect contains resources that implement the enterprise integration. This includes ser$ices
(producers and consumers of information), any business logic that may be applied to that
information, and deployment information.
> The pro/ect panel allows you to $iew the .ro/ect +isplay Tab @;ith the .ro/ect tab selected,
the pro/ect panel displays the pro/ect tree ?lobal Aariables +isplay @?lobal $ariables are
associated with each pro/ect
,alette ,anel
> .alettes organi4e resources and allow you to add them to your pro/ect. Bou select resources in
the palette panel and drag and drop them into the design panel to add them to your pro/ect.
Design ,anel
> The design panel displays the current resource selected in the pro/ect panel.
$onfiguration ,anel
> The configuration panel allows you to specify $arious configuration options for each resource
> 'fter you ha$e added the configuration information, you must clic& the 'pply button for each
tab. #f you decide you do not want to add the configuration information, clic& -eset before you
apply any changes to return to the pre$ious $alues for each field in the tab.
)vervie! of ,rocesses
> ' process definition is the graphical representation of your business process.
> Bou de$elop and test process definitions using T#B*1 +esigner.
> The process definition is e)ecuted by a T#B*1 Business;or&s process engine.
,rocess Definitions
> ' process definition is a graphical representation of your business process model.
> Bou create process definitions by dragging and dropping a .rocess +efinition resource from
the .rocess palette to the design panel.
,rocess definitions co#ponents
> 'cti$ities
> Transitions
> ?roups
> Shared *onfiguration -esources
Activities
> 'cti$ities are the indi$idual units of wor& within a process definition
> 'cti$ities are a$ailable on the $arious palettes within T#B*1 +esigner.
> ' process definition can begin with a Start acti$ity, but some palettes contain acti$ities that can
start a process. These acti$ities, also &nown as process starters %C8 2#6% .166'- 'cti$ity from
2#6% .alette
Transitions
> Transitions describe the flow of processing within a process definition.
> ' transition is represented by an arrow between two acti$ities.
> The arrows are unidirectional
> *ontrol flow in a process definition must proceed se(uentially beginning with the Start acti$ity
(or a process starter) and ending with the %nd acti$ity.
> Transition can optionally specify a condition. The condition determines if the transition is ta&en
when an acti$ity completes processing. 'fter an acti$ity completes
> %ach acti$ity in a process definition must ha$e a transition to it, or the acti$ity is not e)ecuted
when the process e)ecutes
.roups
>?roups are used to specify related sets of acti$ities
>To create sets of acti$ities that are to be repeated. Bou can repeat the acti$ities once for each
item in a list, until a condition is true, or if an error occurs
>To create sets of acti$ities that participate in a transaction. 'cti$ities within the group that can
ta&e part in a transaction are processed together, or rolled bac&, depending upon whether the
transaction commits or rolls bac&.
'hared $onfiguration esources
>Shared configuration resources are specifications that are shared among acti$ities.
>These are resources, such as database connections, ;S+6 files, schema definitions, and
connections to other ser$ers.
>Shared configuration resources are created outside of process definitions, but they are used
when specifying the *onfiguration tab of some acti$ities
'u%processes
>Business processes are often $ery comple) and it is difficult to diagram the complete process
in one process definition. Bou can create se$eral smaller process definitions instead of one
monolithic process definition.
>Bou can then call each process definition from another process definition, when necessary.
;hen you call a process definition, the called process is &nown as a subprocess
>,sing subprocesses helps to ma&e more readable process diagrams and you can reuse
subprocesses across many process definitions
TI&$) &usinessWor+s engine
> The T#B*1 Business;or&s engine runs the business processes in test mode and at runtime
> ' process engine creates instances of process definitions. These process instances automate
your business processes by e)ecuting the business process described by the process definition.
> .rocess engines are started using T#B*1 'dministrator after you deploy your pro/ect
TI&$) unti#e Agent /TA0
> The T#B*1 -untime 'gent (T-') runs on each machine and e)ecutes scripts, sends alerts,
and performs reco$ery as specified
TI&$) unti#e Agent
> The T#B*1 -un3time 'gent (T-') pro$ides basic connecti$ity between the adapter and other
T#B*1 infrastructure tools.
> The T-' is re(uired on any machine on which an adapter is installed.
> The T-' runs on each machine on which an adapter runs and e)ecutes scripts, sends alerts,
and performs reco$ery as specified.
TA 1U($TI)('
> Supplies an agent that runs in the bac&ground on each machine.
D The agent is responsible for starting and stopping processes that run on a machine
according to the deployment information.
D The agent monitors the machine. That information is then $isible $ia the T#B*1 'dministrator
?,#.
> Supplies the run3time en$ironment, that is, all shared libraries including third3party libraries
re(uired by the adapter.
TI&$) Ad#inistrator
> T#B*1 'dministrator supports security administration as well as monitoring and management
of processes and machines.
> T#B*1 'dministrator consists of the T#B*1 'dministration Ser$er and the web browser based
T#B*1 'dministrator ?,#.
TI&$) Ad#inistrator Modules
> ,ser 0anagement
> -esource 0anagement
> 'pplication 0anagement
User Manage#ent2
> This module allows you to set permissions for adapter users.
> Bou define authentication, users and groups, and assign access control lists to users.
> This includes security for ser$er3based pro/ects at design3time and for deployed applications at
runtime.
esource Manage#ent
> This module allows you to monitor machines and all running applications in a T#B*1
administration domain.
> 'lerts can be created,
for e)ample, to notify an administrator if the number of processes or dis& usage e)ceed a
certain number.
Application Manage#ent2
> This module allows you to upload %nterprise 'rchi$e (%'-) files, and create, configure, and
deploy adapters.
> This console is also used to start and stop adapters
3ersions of TI&$) Ad#inistrator
>Two $ersions of T#B*1 'dministrator are a$ailable
1 -epository %dition
2 %nterprise %dition
>%nterprise %dition includes the 'pplication 0anagement moduleE -epository %dition does not.
#f you ha$e not purchased the %nterprise %dition, you can manage security for design3time
pro/ects and $iew machine information, but you cannot perform deployment configuration and
deployment management
TI&$) Ad#inistrator $o#ponents
> T#B*1 'dministration +omain
> T#B*1 'dministration Ser$er
> T#B*1 'dministrator ?,#
TI&$) Ad#inistration Do#ain
> ' T#B*1 administration domain is a collection of users, machines, and T#B*1 Business;or&s
components that a T#B*1 'dministration Ser$er monitors and manages.
> There is only one 'dministration Ser$er for each administration domain.
> *omponents within an administration domain can communicate with systems outside the
domain, but the administration domain is the administrati$e boundary of an enterprise
integration pro/ect.
TI&$) Ad#inistration 'erver
> The T#B*1 'dministrator Ser$er pro$ides a central storage and distribution point for
configuration data and schema data needed by an adapter. The ser$er is included in both
'dministrator editions.
> %ach administration domain has one and only one T#B*1 'dministration Ser$er. The T#B*1
'dministration Ser$er is the machine process that handles the stored pro/ect and re(uests to
manage the T#B*1 administration domain.
>The T#B*1 'dministrator Ser$er contains its own web ser$er ('pache Tomcat) that can be
accessed $ia a the T#B*1 'dministrator ?,# for configuration and monitoring information.
>The T#B*1 'dministration Ser$er supports centrali4ed authentication and authori4ation. ,sing
the T#B*1 'dministrator ?,#.
> AuthenticationFThe $erification of the identity of a person or process.
> Authori4ationF.ermission to $iew or e)ecute. 'n administrator gi$es users access rights to
the pro/ects.
TI&$) Ad#inistrator .UI
>Bou can access the T#B*1 'dministration Ser$er using the web3based T#B*1 'dministrator
?,#.
>The ?,# allows you to create users and assign access to pro/ects managed by the
'dministration Ser$er.
>Bou can in$o&e the ?,# from any machine in a T#B*1 administration domain
More ifo o !"#
If you thin+ that an i#portant EAI intervie! 5uestion is #issing or so#e ans!ers are
!rong in the site please contri%ute it to suneel+u#ar6678g#ail2co#
TI&$) &U'I(E''W)*'
Why Ti%co?
Tibco pro$ides completely neutral,standards 7 based and e$ent 7 dri$en platform for
integrating and orchestrating e)isting data and business process across pac&aged and legacy
applications as well as G2%%, .net ,webser$ices and mainframe en$ironments.
Which areas Ti%co ,roducts use?
1. Business 1ptimi4ation
2. Business .rocess0anagement
3.Business #ntegration
. %nterprise Bac&bone
&usiness )pti#i4ation
This s=w that enables people to access, analy4e ,and act on data ,participate in processes and
analy4e business performance
&usiness ,rocess#anage#ent
This s=w that helps companies coordinate the e)ecution of the tas&,acti$ities and transactions
that ma&e up their uni(ue way of doing business
&usiness Integration
This s=w that gi$es companies the ability to connect and coordinate applications throughout
their organi4ation across their e)tended enterprise and with in their customers
Enterprise &ac+%one
This s=w helps companies establish and manage highly efficient and scalable flow of
information across their enterprise
Ti%co ,roducts
D ,nderstand how business can automate processes using Tib='cti$e%nterprise
D ,nderstand how business can reach their people using Tib='cti$e.ortal
D ,nderstand how business can support partnerships and the mar&et place using
Tib=acti$e%)change
Ti%co ActiveEnterprise 927
T#B=-%:+%HA1,S 0essaging #nfrastructure T#B='+'.T%-S +ata Translation
T#B=0%SS'?% B-1!%- +ata Transformation T#B=-%.1S#T1-B 0etadata -epository
T#B=#:T%?-'T#1: 0':'?%- .rocess 0anagement T#B=5';! 0onotoring and 0anagement
T#B=#:*1:*%-T ;or&flow 0anagement
Messaging " TI&:3
Tibco '% pro$ide a common messaging platform with one connection to each application
and no central ser$er
D 6ocally enables applicationa to send and recei$e messages
D %)tremely high degres of fle)ibility and scalability
D %$ent3+ri$en communications (or) traditional -e(uest=-eply
Data trasalation " Adapters
'dapters that connect applications by con$erting internal e$ents into messages.
D 1ff 7 the7 Shelf adapters for %-. ,*-0 and B2B applications and database.
D 'dapters for de$elopment models and other messaging models.
D +e$elopment !it for (uic&ly creating custom adapters
Data transfor#ation " TI&:M&
Tibco '% trasforms messages so applications can resol$e structural and content differences
D #ncreases efficiency and reduce errors
D Cml pro$ides common structure for data
,rocess #anage#ent " TI&:IM
Tibco '% messages business process
D 'utomated se(uencing of operations performed by applications and databases
D 0anagement of the wor&flow of tas&s performed by people
TI&:;AW*
Tibco '% pro$ides monotoring and management capabilities that &eep e3 business systems
running smoothly at all times.
D 'utomated response to system problems
D #nstant alerting of system administores.
D -emote management of applications and networ& resources.
TI&:E,)'IT)<
1. #t9s #ntegrated with '% products
D 'dapters,0B,#0 2. .ro$ides robust common metadata storage facility
D *onfiguration of adapters
D +ata schemas for messages, files and database tables.
D Business .rocess models 3.'llows #mport=%)ports of Binary and )ml file
Ti%co AE Advantages

D Scalable
D +istributed
D +ecoupled
D +ecentrali4ed
D -ealtime and %$ent dri$en
Ti%co Active ,ortal
Tib=.ortal Builder #ntegrated, personali4ed content $ia web and wireless de$ices
Tib=.ortal.ac& 'ggregation and distribution of 3 rd 7party content and ser$ices Tib='lertSer$er
0essage deli$ery to wireless de$ices
Ti%co Active,ortal Advantages
D #ntegration from enterprise and 3rd3party sources .ersonali4ation
D user management of specific content
D 'dminstrati$e management of design and access pri$ileges +eli$ery
D -ealtime,%$ent dri$en
D web and wireless .
Ti%co ActiveE=change
Tib=Business*onnect
D 2ull3featured sophisticated integration ser$er Tib=Business*onnect for -osettanet
D 2ull support for the -osettanet standard T#B=.artener%)press
D Browser based 'pplication for small parteners to connect to the trading :=;
Ti%co ActiveE=change Advantages
D 'utomating cross company business process communcating with trading parteners
effecti$ely,efficiently,inn real time
D Secure e)change of commerce documents o$er the internet and pri$ate networ&s
D 0anagement of trading partener member ship for all parteners.
TI&$) ende4vous
#troductio to $ede%&ous Software
-ende4$ous software suite includes two main components
-ende4$ous programming language interface ('.#)
-ende4$ous daemon
The -ende4$ous daemon runs on each participating computer on your networ&. 'll information
that tra$els between program processes passes through the -ende4$ous daemon as the
information enters and e)its host computers. The daemon also passes information between
program processes running on the same host.
'ecouplig ad 'ata #depedece
-ende4$ous software allows looser coupling between the components of a distributed system.
6oose coupling decreases costs for de$elopment, operation and maintenance, and increases
system longe$ity. -ende4$ous self3describing data messages promote data independenceE
producers and consumers of data can communicate e$en if they do not share the same internal
representations for data. *ommunicating programs can run on different hardware architectures,
e$en though they use different bit order, byte alignment or numeric representations.
Locatio (rasparecy
-ende4$ous software uses sub/ect3based addressingI technology to direct messages to their
destinations, so program processes can communicate without &nowing the details of networ&
addresses or connections. Sub/ect3based addressing con$entions define a uniform name space
for messages and their destinations.
"rchitectural !mphasis o #formatio Sources ad 'estiatios
+ecoupling distributed components eliminates much of the comple)ity traditionally associated
with networ& programming. -ende4$ous software frees you to de$ote more resources to sol$ing
application problems.
$eliable 'eli&ery of )hole Messages
-ende4$ous software pro$ides reliable communications between programs, while hiding the
burdensome details of networ& communication and pac&et transfer from the programmer.
-ende4$ous software ta&es care of segmenting and recombining large messages,
ac&nowledging pac&et receipt, retransmitting lost pac&ets, and arranging pac&ets in the correct
order. Bou can concentrate on whole messages, rather than pac&ets.
$ede%&ous *peratig !&iromet
+etworkig Basics
To better understand the concept of -A, lets go thru some of the :etwor&ing Basics 7
,oectio-*rieted ad ,oectioless Protocols
$onnection-)riented ,rotocols:
These protocols re(uire that a logical connection be established between two de$ices before
transferring data. This is generally accomplished by following a specific set of rules that specify
how a connection should be initiated, negotiated, managed and e$entually terminated. ,sually
one de$ice begins by sending a re(uest to open a connection, and the other responds. They
pass control information to determine if and how the connection should be set up. #f this is
successful, data is sent between the de$ices. ;hen they are finished, the connection is bro&en.
%)ample 8 tcp=ip, ftp, telnet
$onnectionless ,rotocols:
These protocols do not establish a connection between de$ices. 's soon as a de$ice has data
to send to another, it /ust sends it.
%)ample 8 udp
insert >nd i#age here
Unicast? &roadcast and Multicast Messages
1. ,nicast 0essages8
These are messages that are sent from one de$ice to another de$iceE they are not
intended for others.
2. Broadcast 0essages8
's the name suggests, these messages are sent to e$ery de$ice on a networ&. They are
used when a piece of information actually needs communicating to e$eryone on the
networ&, or used when the sending station needs to send to /ust one recipient, but
doesnJt &now its address.
3. 0ulticast 0essages8
These are a compromise between the pre$ious two types8 they are sent to a group of
stations that meet a particular set of criteria. These stations are usually related to each
other in some way, such as ser$ing a common function, or being set up into a particular
multicast group. (:ote that one can also consider broadcast messages to be a special
case of multicast, where the group is Ke$eryoneL.
T$, and UD,
Transmission *ontrol .rotocol (T*.)8
' full3featured, connection3oriented, reliable transport protocol for T*.=#. applications.
T*. pro$ides transport3layer addressing to allow multiple software applications to
simultaneously use a single #. address. #t allows a pair of de$ices to establish a $irtual
connection and then pass data bidirectionally. Transmissions are managed using a
special sliding window system, with unac&nowledged transmissions detected and
automatically retransmitted. 'dditional functionality allows the flow of data between
de$ices to be managed, and special circumstances to be addressed.
,ser +atagram .rotocol (,+.)8
' $ery simple transport protocol that pro$ides transport3layer addressing li&e T*., but
little else. ,+. is barely more than a KwrapperL protocol that pro$ides a way for
applications to access the #nternet .rotocol. :o connection is established, transmissions
are unreliable, and data can be lost.
TD, " TI&$) elia%le Datagra# ,rotocol
-A runs on T-+. 7 T#B*1 -eliable +atagram .rotocol.
#t is implemented by r$d. T-+. is built on top of ,+. and adds a se(uence number to
each outbound pac&et. T-+. uses buffer to store outbound messages for specific
inter$al (Typically MN sec.) #f message pac&et is lost, the consuming r$d re(uests
retransmission.
#n contrast to T*.=#. which is pessimistic, T-+. is optimistic8 it assumes messages will
arri$e at their destination. #f the message is lost, then T-+. sends negati$e
ac&nowledgement (:'!) re(uesting retransmission.
#f stronger deli$ery assurance is re(uired, -A *ertified (-A*0) or -A Transactional
(-ATC) is used.
-A*0 uses ledger files at both .ublisher and Subscriber ends. These ledger files stores
messages, and these messages sit in ledger file until it gets confirmation from all
recei$ers.
TI&$) &U'I(E''W)*'
@: What is &usinessWor+s Architecture?
'8 Business;or&s retains T#B*1 pro$en distributed architecture based on -A, while supporting
a number of industry standards such as8 S1'., 5TT., S0T., 2T. and G0S. #t pro$ides a
simplified, integrated en$ironment for business process integration from installation and
configuration, through process design and test, to deployment, monitoring and administration,
using /ust an intuiti$e designer ?,# and a power administrator ?,#.
@: What are the different &usinessWor+s co#ponents?
'8 Business;or&s consists of T#B*1 'dministrator, T#B*1 -untime 'gent, Business;or&s
%ngine, and T#B*1 +esigner.
@: What is TI&$) Designer?
'8 T#B*1 +esigner is a ?,# tool for designing your business process integration. #t is used for
adapter configuration, process design, test, and deployment. T#B*1 +esigner is a component
of T#B*1 Business;or&s.
@: What is an activity?
'8 'n acti$ity is an indi$idual unit of wor& within a process definition in the T#B*1 +esigner.
'cti$ities are operations that interface with e)ternal systems or perform internal processing.
'cti$ities are a$ailable on the $arious palettes in the T#B*1 +esigner, e.g. an '% adapter
palette contains '% publish acti$ity, '% subscription process starter acti$ity, and '% respond
acti$ity.
@: What is a palette?
'8 ' palette is a collection of resource templates or acti$ities that can be used to populate a
pro/ect in the T#B*1 +esigner, e.g. you can use S1'. palette to create process definitions that
implement web ser$ices. 1ther palettes include8 '% 'dapter, 2T., 2ile, 5TT., G+B*, G0S,
Ga$a, 0ail, -A, C06 and ?eneral.
@: What is a transition?
'8 ' transition is an arrow on a process definition between acti$ities. Transitions describe the
flow of processing. 'n acti$ity in a process definition must ha$e a transition to it, or the acti$ity is
not e)ecuted when the process e)ecutes.
@: What is a condition?
'8 ' condition is used to control the flow of acti$ities in a process diagram. *onditions are
specified on transitions to determine whether to ta&e the transition to the ne)t acti$ity or not.
C.'T5 is used to specify a transition type of success with condition.
@: What is a pro-ect?
'8 ' pro/ect is a collection of all the ob/ects in your integration. #t includes adapters, acti$ities,
machines, processes, etc. Bou create and sa$e pro/ects using T#B*1 +esigner.
@: What is A,AT;?
'8 Cpath is a scripting language de$eloped by the ;orld ;ide ;eb *onsortium (;3*) for
addressing parts of C06 documents. #t pro$ides basic manipulation functions for strings,
numbers and Booleans. T#B*1 +esigner, a Business;or&s component, uses Cpath as the
language for defining conditions and transformations. ' complete description of Cpath is
a$ailable O http8==www.w3c.org
@: Does &W ;TT,' feature chec+ !hether the client is authori4ed to access the server
application ?
'8 B; ".1.2 5TT.S feature $erifies whether the client certificate is signed by a trusted *' but it
doesnJt chec& whether the client is authori4ed to access the ser$er application, which app
ser$ers li&e ;eblogic and Bi4tal& do by chec&ing the client cert against some '*6 or trusted
client list. *urrently B; ".1.2 supports only basic authentication. #f the user is defined in the
administrator and has the right credentials, it will allow the 5TT. re(uest. 5TT. 'uthentication
field on the 5TT. recei$er can be used for this purpose. 5owe$er, B; does :1T support '*6
authentication based on sub/ect3name in the client cert.
@: ;o! does &W handle 1T, connections? B 1T, C
'8 B; creates a seperate 2T. connection for each Gob. 5owe$er, all the 2T. acti$ites within a
Gob will uses the same 2T. connection. The connection gets closed only when the Gob ends.
@: ;o! can I specify the AML na#espace prefi=es generated %y the ender AML activity
!ithin &W D2E2>?
'8 ;ith 5ot2i) " of B; ".1.2, you can specify namespace prefi)es used by each process
definition for C06 rendering. This has the added benefit of putting all of the namespaces at the
root of the C06 document, which can simplify the appearance and si4e of the document in
certain cases.
Bou ha$e to do two things to enable this8
1. 5ighlight a specific process definition and then clic& the :amespace button in the
configuration pane for the process definition. 5ere is where you set your desired prefi)es for
each namespace.
2. 1n the specific acti$ity you want to affect, go to the input pane of the mapper and highlight
the root element and choose Jedit statementJ. *hec& the %)clude -esult .refi)es bo). Bou can
also add a whitespace separated list of namespaces (by prefi)) that you donJt want to appear in
the output, assuming they are not re(uired.
@: @uery Designer in a FD&$ @uery activity is ta+ing E7 to ED #inutes to co#e up ? ho!
can I resolve this?
'8 ;hen you clic& on <uery +esigner, in bac&ground it is issuing a S<6 (uery if you use T#B*1
G+B* +ri$er S%6%*T username 'S T'B6%PS*5%0, null 'S T'B6%P*'T'61? 2-10
allPusers 1-+%- BB T'B6%PS*5%0 #f you ha$e lot of Schemas in +B then it will ta&e a time
to run abo$e schema and then it has to go thru each of abo$e T'B6%PS*5%0 and then display
them. ;e ha$e seen if you use 1racle G+B* +ri$er *lasses12.4ip , then it issues (uery li&e 8
S%6%*T username 'S tablePschem 2-10 allPusers 1-+%- BB tablePschem 'nd, that ta&e a
shorter time to run and it brings up <uery +esigner in 1N to 1" seconds.
@: ;o! can I deter#ine ho! #any records !ere returned %y a FD&$ '@L 5uery?
'8 Bou ha$e an )3path Qcount(RR node3set SS)Q under JSetJ in the )3path editor which you can
use. %)ample8 count(TG+B*3<uery=resultSet=-ecord)
@: What are the hard!are reco##endations for &usinessWor+s?
'8 Business;or&s $ersion 2.N.3 is a$ailable for ;indows :T, ;indows2NNN, Solaris U, and
5.=,C 11.N, The minimum recommended hardware for ;indows is a V33 054 #ntel .entium ###
*lass *., with 2"M 0B of random access memory (-'0) and 1"N 0B of fi)ed dis& space for
installation. 2or ,ni), minimum memory is 2"M0B of -'0 and 1"N0B of dis& space. #f
additional 'dapters are to be installed, additional dis& space will be re(uired. Bou should
allocate additional dis& space for pro/ects and trace files.
@: The &W ti#er event source doesnGt ad-ust the cloc+ for daylight savings ti#e !hen
the user chooses the ;ours:Milli'econds units2
'8 The timer will ad/ust for daylight sa$ing time when the inter$al unit is day or larger. ;hen the
units are less than a day it assumes you mean e)actly that number. 2or e)ample, if you say fire
the timer e$ery 2 hours then you want it to do it e$ery 2 hours. But if you say you want the
timer to fire e$ery 1 day, then you want it to ad/ust for +ST as the time ad/usts twice a year.
@: What #essaging protocols are supported natively !ithin &usinessWor+s?
'8 S1'., G0S, -A, 5TT., 2T., and S0T..
@: What Adapters are availa%le and supported %y &usinessWor+s?
'8 Business;or&s 2.N.3 supports all 'cti$e%nterprise .2 'dapters, including8 'dapterS+!
'dapter for Siebel 'dapter for -3 'dapter for .eopleSoft 'dapter for 2ile 'dapter 2or 'cti$e+B
'dapter 2or S;#2T 'dapter for 1racle 'pplications 'dapter for #nfranet 'dapter for 0etaSol$
'dapter for %GB 'dapter for 6otus:otes 'dapter for 0<Series 'dapter for *1-B' 'dapter for
G+% 1ne;orld 'dapter for G+% 1ne;orld Ce 'dapter for 'rbor=B. 'dapter for 6+'. 'dapter
for Teradata 'dapter for -emedy This is not an e)hausti$e list. There are more adapters
coming.
@: Is it possi%le to i#ple#ent &usinessWor+s along !ith adapters that are not
&usinessWor+s co#pliant? e2g2 ActiveEnterprise 92= or H27 adapters?
'8 Bes, Business;or&s will interoperate with any T#B*1 'dapter regardless of Business;or&s
compliance. 5owe$er, 'dapters that do not fit into the Business;or&s framewor& will lose
certain types of Business;or&s functionality, specifically, the ability to be configured from the
Business;or&s +esigner ?,#, deployed from the +esigner, and managed from the T#B*1
'dministration Ser$er. Business;or&s 2.N.3. pro$ides a resource &it under T-' for adding
custom adapters built with 'dapter S+! .2 to the domain. Both the documentation and utility
are included in the T-' tools directory.
@: Is &usinessWor+s pre-pac+aged !ith so#e adapters?
'8 :o. Business;or&s installation does not include adapters. Bou will need to install '% .2
'dapters separately.
@: What security is availa%le !ith &usinessWor+s?
'8 Business;or&s supports user authori4ation and authentication. ,ser authori4ation can be
specified for administrator user interface access and also for pro/ect data access. ,ser
authentication is performed when users access the domain using browser3based administrator
and also when they access the pro/ect instance using the designer.
@: What data description and sche#a standards does &usinessWor+s support?
'8 C06, CS+ and +T+.
@: What transfor#ation standards does &usinessWor+s support?
'8 Business;or&s data transformation is based on CS6T. C.ath is used for data manipulation
and formula constructions.
@: ;o! does &usinessWor+s support ')A, and W'DL integration?
'8 Business;or&s pro$ides ;S+6=S1'. integration in a ser$er and a client mode, which
integrates directly into the .rocess #nstance. Business;or&s pro$ides three different
components8 S1'. %$ent Source, S1'. Send (-e(uest) 'cti$ity, and S1'. Send=-ecei$e
(-e(uest=-eply) 'cti$ity. #n Business;or&s 2.N, we will only support document3centric calling
con$ention and not a procedure3oriented communication. ' future $ersion of Business;or&s will
pro$ide support for ,++# as well.
@: Does &W support load %allancing !hen using ')A,? Is there any section on the
product docu#ent that discusses this issue?
'8 B; will support load balancing o$er S1'., but B; does not handle the S1'. load
balancing itself. Bou will ha$e to select one of the following e)ternal mechanisms8 1. 5ardware
6oad Balancer (eg. 6ocal +irector) 2. Software 6oad Balancer (eg. -esonate Software) 3. +:S
-ound -obin (0ost +:S Ser$er will support this). 1f the abo$e options 1 is the most e)pensi$e
and 3 is the cheapest.
@: .et E): IE) Metadata UL 1olderI Iesources and esourceeferences
#ust refer to $lasses 1oldersI !hile opening repository2
'8 *hec& if the JStartupJ T'B in the 'dapter *onfiguration has the J0eta+ata Search ,-6J
specified. #f this ,-6 is missing you could see the abo$e mention error.
@: What is ')A,?
'8 S1'., or Simple 1b/ect 'ccess .rotocol, is a lightweight protocol for the e)change of
information between web ser$ices. Business;or&s has a S1'. palette in T#B*1 +esigner that
can be used to create process definitions that implement web ser$ices.
@: What is W'DL?
'8 ;S+6, or ;eb Ser$ices +efinition 6anguage, is an C06 format for describing networ&
ser$ices as a set of endpoints operating on messages containing either document3oriented or
procedure3oriented information. The operations and messages are described abstractly, and
then bound to a concrete networ& protocol and message format to define an endpoint. -elated
concrete endpoints are combined into abstract endpoints or ser$ices.
@: ;o! does &usinessWor+s support FM'?
'8 Business;or&s supports G0S as it does with other transport standards through a palette. #t is
$endor neutral and it has been certified for T#B*1 G0S Ser$er.
@: What progra##ing languages does &usinessWor+s support?
'8 Business;or&s does not re(uire programming, howe$er, users can integrate Ga$a code in
the Ga$a acti$ity.
@: What TI&$) products are re5uired for &usinessWor+s?
'8 :one. Business;or&s comes pac&aged with e$erything you need. Bou may purchase and
install additional 'cti$e%nterprise 'dapters for your business process integration.
@: Does &usinessWor+s support LDA,:Active Directory i#port?
'8 Business;or&s 2.N does not support 6+'.='cti$e +irectory import.
TI&$) ende4vous
E=plain %riefly !hat do you understand %y ende4vous?
'. tibco rende4$ous software ma&es it easy for distributed applications to share information
across a networ&. #t also enables the de$elopment of e$ent dri$en applications. -$ supports
nearly all platforms, enabling, distributed applications to cooperate. -A wor&s with common
networ&ing protocols and pro$ides reliable messaging . #t communicates using broadast ,
multicat and unicast interactions . -$ messages are produced and consumed based on logical
sub/ect names.
What are the different types of ende4vous transports?
'. :etwor&, intra3process, or Airtual circuit.
What are the three para#eters passed to 3D? What are the default values for the#?
'. Ser$iceWV"NN, :etwor&W, +aemonWV"NN,
What are the t!o protocols used %y ende4vous? E=plain each one %riefly?
'.T-+. T#B reliable data protocol. ' reliable transport protocol for ordered, duplicate free, data
deli$ery with in a single subnet. .?0 pragmatic general multicasting. ' reliable transport
protocol for ordered, duplicate free, data deli$ery o$er a group of interconnected subnets.
Descri%e different types of co##unication ena%led %y 3?
T#B*1 -$ supports the following four types of communication interactionsL Broadcast3one to
many Broadcast re(uest=reply 7one re(uest to many, then many one to one replies. .oint to
point re(uest=reply3one re(uest, then one reply. .oint to point3one to one
E=plain ende4vous architecture? $o#pare it !ith that of #essage 5ueue?
'.Ti%co 3 is a %us %ased architecture with no centrali4ed component or ser$er to bro&er
message flow. it is a pure peer to peer architecture with publishers and subscribers fully
responsible for message production and consumption. 2ully distributed, no single point of
control :o single point of failure ' message tra$els the networ& only ones regardless of the
number of subscribers. %$ent or demand dri$en A #essage 5ueue is a hu% and spo+e
architecture with a centrali4ed ser$er that controls message flow. *entrali4ed component %asy
to control message traffic Single point of failure ' message tra$els the networ& at least twice.
+emand dri$en only.
What does the call%ac+ handler do?
The callbac& handler is responsible for ta&ing the recei$ed message from the -A+ and
presenting to the application for processing callbac& functions perform the actual application
specific wor& of responding to incoming messages. 'lthough different communication
paradigms, in a simplified way an incoming e$ent can be seen as the re(uest and the call bac&
as the reply.
List the ende4vous co#ponents2 Descri%e the responsi%ilities of each co#ponent in
%rief?
The daemon and the '.# are the two primary components of tibco -A. The -$ daemon
implements the T-+. protocol or uses the .?0 protocol and, as such is responsible for
+eli$ering messages reliably, including message se(uencing ,retransmission and buffering
2iltering messages by sub/ect name The -A '.# is responsible for pro$iding the message data
structure, for determining the communication mode and for passing messages to and from the
r$d.
What is 3D? ;o! is it different fro# 3D?
-A-+ is rende4$ous routing daemon. -A+ is used to send messages with in a subnet . But
-A-+ can send and recei$e messages beyond the subnet.
E=plain the 3$M agree#ent2
'.-A*0 in$ol$es a handsha&e agreement among senders and listeners to e)change
messages. #n order for senders and listeners to enter into *0 agreement they must identify
each other on the networ&. This is done by gi$ing each of them a uni(ue name. ;e can either
specify this name oursel$es or lea$e it up to the software to generate a name. The generated
name can be different e$ery time it is generated. So it doesn9t pro$ide persistence. This
handsha&e can be set up automatically by the parties in$ol$ed or we can pre3register the
listeners. #t is also possible for a *0 sender to deny registration to a *0 listener, in which case
the *0 listener continues to recei$e messages with /ust reliable (uality of ser$ice.
E=plain A$ID properties2
'. 'tomicity8 the transaction components act as a single unit. %ither all ta&e place or none of
them ta&e place. *onsistency8 system data is maintained in a consistent $iewE intermediate
actions are not posted until the transaction is complete. #solation8 #ntermediate acti$ities are only
$isible to the transaction master. +urability8 once the transaction has been committed, it cannot
be undone.
$o#pare 3D !ith 3D2
'.-A+ deli$ers messages to application on computers within a single networ&. ;hereas r$rd
deli$ers messages beyond 6': boundaries. -$rd forwards messages between networ&s
allowing application on one networ& to listen for and recei$e messages from application other
networ&s. -$rd subsumes r$d functionality so it is not necessary to run both on the same host
What is 3D'? ;o! it addresses the re5uire#ents of data security?
T#B*1 -ende4$ous +ata Security is an add3on product that le$erages standard r$ functionality
to deli$er secure data communications in the T#B enabled distributed en$ironment. !ey
re(uirements of secure communications include data pri$acy, data authentication, data integrity
and access control. .ri$acy8 -A+S pro$ides data encryption controls that authori4e who may
read a message 'uthentication8 -A+S pro$ides digital signatures and certificates to $erify the
identify of the message sender. #ntegrity8 -A+S pro$ides digital signature and message integrity
codes to guard against message tampering. 'ccess control8 -A+S controls the rights of users
to send=recei$e messages with specified tags that themsel$es specify the security methods
applied.
What is the difference %et!een 3$M and 3TA?
#n -A*0 the messages are deli$ered Kat least onceL where as in -ATC en$ironment messages
are deli$ered and consumed Ke)actly onceL.
In 3$M #ode? !hat happens if?$ertified sender sends #essage Dropped %y net!or+
outage for D7 seconds
'8#f a certified sender sends a message that gets dropped for "N seconds , standard
rende4$ous reliability resends the message. Because its within the MN default buffer window.
-A*0 is not acti$ated.
What co#ponent in present in 3$M %ut not Distri%uted @ueue?
*0 6istener ledger file is present with -A*0 but not +istributed <ueue.
;o! does rvcache differ fro# D&?
,pdates to r$cache are implicit whereas +B updates are e)plicit. 'lso r$cache stores only
current $alue.
What is direct co##unication? What is the advantage of it over 3D usage?
'. Two application programs can conduct eligible point3to3point communications without
intermediary rende4$ous daemon processes. This arrangement can decrease message latency
and conte)t switching for point to point messages. #n the path through r$d each the daemon can
a add a small delay. The direct path a$oids these sources of potential delay.
When !ill a #essage %e eligi%le for direct co##unication?
'. ' message is eligible for direct communication if it meets all of these conditions8 The
message has an inbo) destination sub/ect. #ts sending transport ob/ect is eligible and enabled.
#ts recei$ing transport ob/ect is eligible and enabled. The networ& path between the sender and
the recei$er does not cross through rende4$ous routing daemon.
E=plain ;eart %eat interval? Activation interval and preparation interval2 What is the
relationship a#ong the#?
%ach -A2T group member must specify a heartbeat inter$al. This inter$al is used t determine
the inter$al at which an acti$e member will publish its heartbeat message. The acti$ation
inter$al is the inter$al that an inacti$e member waits before becoming acti$e when no heartbeat
signal is obser$ed. 'll member of a 2T group must specify the same acti$ation inter$al. The
member of a 2T group may specify preparation inter$al. This parameter specifies how long an
inacti$e member needs to prepare before becoming acti$e. What is 3AD? When it is
used?
'8-ende4$ous relay agent daemon. -$rad supports *0 in situations where correspondents
connect only intermittently to the networ&. ' common implementation of r$rad is to support *0
deli$ery among laptop computers that connect to the networ& intermittently. #n such situations
r$rad collects messages on behalf of disconnected clients. ;hen the correspondent reconnects
to the networ& , r$rad forwards the stored messages
TI&$) Ad#inistrator
@: What is TI&$) Ad#inistrator?
'8 T#B*1 'dministrator is a browser3based interface used for monitoring and managing
resources in a T#B*1 +omain. The 'dministrator as it is sometimes referred to in
Business;or&s documentation is a collecti$e term for an 'dministration Ser$er, a ser$er
process, and 'dministrator, its browser3based ?,#. 'dministration Ser$er consists of a
repository ser$er that stores domain resource information and ser$lets that run on an 'pache
Tomcat ser$er that pro$ide the http3based interface. 'dministrator ?,# can be accessed using
0icrosoft #nternet %)plorer "." or :etscape :a$igator M.1.
@: $an one #achine %elong to t!o different do#ains?
'8 :o. %ach machine can belong to one domain only. Bou may consider merging the two
domains together as one domain if you need to use the same machine.
@: $an one adapter %elong to t!o different do#ains?
'8 :o. %ach adapter can only belong to one domain. Bou may consider merging the two
domains together as one domain if you need to use the same adapter.
@: $an I change the do#ain for one #achine to another later?
'8 Bes, you can add=remo$e machine from domain using +amain ,tility.
@: $an I change the adapter fro# one do#ain to another?
'8 Bes, but you will need to uninstall the e)isting adapter that has /oined the current domain and
then reinstall the adapter and /oin it to the new domain. Bou will also be able to change the
domain info directly using +omain ,tility .
@: $an I run #ultiple ad#inistrators in the sa#e do#ain?
'8 :o. 1nly one administration ser$er is installed and configured for use per domain.
@: $an I -oin a do#ain after I have already installed an adapter?
'8 Bes. Bou may use the domainutility under T-' tools to add the adapter to the domain.
@: Why is there a restriction that one #achine can only %elong to do#ain?
'8 'nalogous to the +:S notion of a machine, a machine cannot belong to two different
domains at the same time. This allows a more robust architecture for monitoring and
management.
@: $an I change the do#ain na#e after I have co#pleted the installation?
'8 :o. 1ne should plan and select a uni(ue and meaningful domain name prior to the
installation.
@: Is the concept of Do#ain specific to &usinessWor+s?
'8 Business;or&s is the first T#B*1 product to ta&e ad$antage of the T#B*1 administrator and
hence the use of T#B*1 +omain. 2uture $ersions of other T#B*1 products will also support
T#B*1 'dministrator.
@: Will I %e a%le to !or+ offline if the ad#inistrator is not running?
'8 Bou may use T#B*1 +esigner to create and test process definitions offline. 5owe$er, you will
not be able to access or sa$e your pro/ects in the administration ser$er. #n addition, you will not
be able to ma&e and sa$e changes to deployments.
@: What is a TI&$) Do#ain?
'8 +omain is a collection of hardware and software components that are used for business
process integration. The domain defines the T#B*1 Business;or&s en$ironment. %ach domain
must contain one and only one administration ser$er. %ach domain must ha$e a uni(ue domain
name. %ach domain may contain one or more machines but no single machine can belong to
multiple domains. %ach machine may ha$e more than one type of software component
(Business;or&s process engine, 'cti$e%nterprise .2 'dapters, etc.) installed. By definition,
software components can only be deployed in the same domain that the machine belongs to.
@: What is a deploy#ent?
'8 ' deployment is a completed configured instance of an integration or pro/ect. T#B*1
+esigner is used to configure pro/ects and deployments in current $ersion. #n the future, T#B*1
'dministrator will be used to manage deployment of pro/ects.
@: What +ind of #onitoring can I do !ith Ad#inistrator?
'8 T#B*1 'dministrator is used to monitor all Business;or&s components, which includes
'dministration Ser$er, Business;or&s engine and 'dapter processes. Bou will be able to
monitor all the deployed components, state of the associated processes, and $arious process
statistics. #n addition, you can re$iew any of the trace files generated by any of the components.
Starting and stopping the components are also performed from the administrator well.