Enabling SOA Using WebSphere Messaging

108 Enabling SOA Using WebSphere Messaging

There is no silver bullet for dealing with older system modernization. The

approach taken always depends on factors like cost and time budget, team skills,

quality of the older system, and required flexibility.

4.7 For more information

For more information about this topic you may find the following useful:

򐂰 WebSphere MQ Application Programming Guide, SC23-6595

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pb

i.cgi?CTY=US&FNC=SRX&PBL=SC34659500

򐂰 Patterns: Service-Oriented Architecture and Web Services, SG24-6303

򐂰 Enterprise Integration Patterns Web site

http://www.eaipatterns.com/index.html

򐂰 Pattern Solutions Web page on IBM developerWorks®

http://www-128.ibm.com/developerworks/rational/products/patternsolutions/

Service enablement by

wrapping

򐂰 Production proven

functionality

򐂰 Low risk

򐂰 Low cost

򐂰 Suboptimal granularity

and reuse

򐂰 Suboptimal

performance

򐂰 Often temporary

solution

򐂰 Difficult to maintain

Service enablement by

componentization

򐂰 Production proven

functionality

򐂰 Easy to maintain

򐂰 Good performance

򐂰 High cost

򐂰 Suboptimal granularity

Approach Advantage Disadvantage