Gopalan Suresh Raj
Web Cornucopia
Gopalan's Profile
Archives
« November 2009
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
     
       
Today
Click me to subscribe Download Open ESB
Syndication
Search

Table of Contents
Tags
bpel choreography ejb esb http integration javacaps javaee javaone jax-ws jbi management openesb orchestration process-oriented rest sca service-oriented soa soap wsdl xml xsd
Links
 
Referrers

Today's Page Hits: 217

Map of Visitors
Locations of visitors to this page
Caveat Emptor
This is my personal weblog. The contents of this Weblog represent my personal opinion which may differ from the official views of my employer, Sun Microsystems, Inc. or any past employers. I do not speak for my employer or any past employers.
View Gopalan Suresh Raj's profile on LinkedIn
« JBI/SOA Tips: Collab... | Main | Sherry Barkodar's... »
Wednesday May 16, 2007
May
16
JBI/SOA Tips: Use Unique Element to ‘Wrap’ Each Business Message

Fine-grained interfaces kill system performance. Coarse-grained interfaces reduce the cost of data processing and improves network latency.

You have to exchange rich business documents that effect complete state changes in the system rather than exchanging  multiple small documents that only effect small state changes in a system.

Business messages may contain one or more business objects that they carry.

When designing global collaborations for wire-centric integration, if you have a complicated interchange that has multiple business objects to it, aggregate these messages together by wrapping them.

Ensure that the container of the wrapped messages has a unique top-level element name.

This wrapper can serve as an open-ended container that sets the business context for what to do with these messages and ensures these messages are self-defining.

 Wrap Message with Unique Element Name

 

  Like this write-up? Subscribe to receive more like it.



Posted at 12:58AM May 16, 2007 by Suresh Gopalan in A Tip a Day  |  Listen to this article Listen to this entry  |  Comments added Comments[0]

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed

Disclaimer: The contents of this Weblog represent my personal opinion which may differ from the official views of my employer, Sun Microsystems, Inc. or any past employers.



View blog top tags

Enter your email address:

Delivered by FeedBurner

[Valid RSS]