My Profile
Active Members
TodayLast 7 Days
more...
Awards & Gifts
Online Exams
Fresher Jobs
Our fresher job section is exclusively for fresh graduates! Find jobs for freshers in major Indian
cities including Bangalore, Chennai, Hyderabad, Pune or Kochi
Resources
Find educational articles, blogs, discussion threads and other resources.
Colleges
Find details about any college in India or search for courses.
|
What are the Types of Interaction in Tibco?
Posted Date:
14 Jun 2008
Total Responses:
1
|
Posted By: aknar2002 Member Level: Bronze Points: 1
|
TIB middleware software supports three distinct kinds of interaction among applications in distributed environments:
• • Request/reply interactions, such as queries or transactions
• • Broadcast request/reply interactions, such as queries that may result in several replies from one or more servers
• • Publish/subscribe interactions, such as general distribution of information from many sources to many consumers
Architectural Benefits
Benefits of a TIB-based architecture include:
• • Easy to create new subsystems – TIB allows developers to create new subsystems, modify existing subsystems, and add new services without having to change the UI or a subsystem’s code.
• • Easy to move subsystems – A subsystem supplying data can be moved to other geographic locations without changing the subsystems that consume the information it supplies. This is important for fault tolerant operation where new subsystems can take over immediately upon the failure of other subsystems.
• • Easier to develop applications – Saves development costs and time because the developers can use a tested API for communications rather than have to design, develop, implement, test, and maintain their own infrastructure code.
• • Faster to develop – Developers can concentrate on applications and business requirements and not have to write and test an infrastructure. Applications will also be faster to develop because they will be linked into existing and well-tested libraries. Developers will not have to create code necessary for inter-subsystem connectivity
• • Easier to maintain – Personnel can concentrate on the application code. The middleware layers are enhanced and maintained by professionals who are specialists in that type of software
• • Easier to change – Changes will be easier to make to subsystems because they will be independent of their data sources and their data consumers
• • Highly scaleable – The system will be far more scaleable because subsystems and hardware can be added easily and quickly to meet new user demands.
• • Location transparency – The system cal exploit TIB’s subject based addressing to allow system components to be located dynamically, rather than being hard-coded. This supports a range of system migration needs.
• • Easier to monitor – The system can use TIB/Hawk for monitoring.
• • Error management – The system will be able to log and respond to system and business level errors by generating TIB-based notifications or advisories.
|
|
|
|
|
Responses
|
| Author: Syed 15 Jun 2008 | Member Level: Diamond | Rating:  Points: 2 | please post this type of informations in resources section, that will help our vistors a lot
|
| Post Reply |
|
|
|
 | | This thread is locked for new responses. Please post your comments and questions as a separate thread.
If required, refer to the URL of this page in your new post. |
|
|
|
|
Watch TV Channels
|