Successfully reported this slideshow.
Service Oriented Architecture for  Order Processing in the  IBM Supply Chain Dr. Germán Goldszmidt ( [email_address] ), ST...
Agenda <ul><li>COATS/OMCS project </li></ul><ul><ul><li>business case for the On Demand transformation </li></ul></ul><ul>...
<ul><li>Situation </li></ul><ul><li>COATS application is a shared order entry   service for more than 20 IBM manufacturing...
Business Benefits to COATS <ul><ul><li>reduced analysis, design and code time </li></ul></ul><ul><ul><ul><li>25% reduction...
Use Processes, Workflows, Services, and Components   Process Models &  Modules Services Workflows Distributed Components t...
DEMO
Development of an SOA solution WebSphere  Business Modeler Rational  Software Architect WebSphere Integration Developer Fi...
Create Business Process Model Business Analyst
Business Process Modeling <ul><ul><ul><li>expect a learning curve for transitioning from traditional process  modeling too...
Configure the generated BPEL workflow Resolve partner links Resolve staff activities Modify transaction boundaries (if req...
Staff Activities <ul><li>Steps: </li></ul><ul><li>create staff activity interface </li></ul><ul><li>add activity to proces...
Modify transaction boundaries <ul><li>Long running processes persist business data for each activity/step in the workflow ...
Workflow Development <ul><ul><li>core Java/EJB skills are important </li></ul></ul><ul><ul><li>problems when integrating w...
Capture Business Policies <ul><li>Example: SelectManufacturingPlant </li></ul><ul><ul><ul><li>Select where to route orders...
Business Rules Implementation  <ul><li>choose a business rule approach early in the project </li></ul><ul><ul><li>WebSpher...
Oneida Lifecycle Adapt CEI CBE CBE WPS Dashboard Monitor Executive Operator End Users
Deployment Topology Process Scalability
Scale Out/Horizontal Clustering <ul><li>early phases of the project used a single server deployment environment </li></ul>...
Clustering Considerations: WBI SF <ul><li>properties of a clustered WBI SF environment </li></ul><ul><ul><li>increased wor...
Balance the Messaging Workload/MQ Clustering <ul><li>The OMCS production environment takes advantage  of decentralized Web...
<ul><li>collocate MQ and WBISF to reduce I/O bottlenecks </li></ul><ul><li>cluster the MQ servers  to balance the messagin...
Best Practices <ul><li>even with automated code generation from the model, basic software engineering principles have to b...
Migrate to WebSphere Process Server 6.0
WebSphere Process Server <ul><li>WPS v6.0 requires BI applications to be created by WID </li></ul><ul><li>Migration Wizard...
WebSphere Integration Developer <ul><li>Migration Wizard  </li></ul><ul><ul><li>migrate non-WBI projects first </li></ul><...
WebSphere Business Modeler <ul><li>WebSphere Business Modeler Version 5 </li></ul><ul><ul><li>export to WSAD IE 5.1 </li><...
Conclusion
VIDEO
<ul><li>Lessons learned/best practices </li></ul><ul><li>Reinforce basic software engineering principles for auto generate...
On Demand Business Process Lifecycle developerWorks articles series 1.  Create the foundation for your on demand business ...
Conclusion <ul><li>Built a business case of an SOA transformation of a legacy IBM supply chain application </li></ul><ul><...
Click to edit Master title style QUESTIONS?
Click to edit Master title style THANK YOU!
Upcoming SlideShare
Loading in …5
×

A Service Oriented Architecture For Order Processing In The I B M Supply Chain

2,713 views

Published on

  • Be the first to comment

A Service Oriented Architecture For Order Processing In The I B M Supply Chain

  1. 1. Service Oriented Architecture for Order Processing in the IBM Supply Chain Dr. Germán Goldszmidt ( [email_address] ), STSM, IBM Software Group Carl Osipov ( [email_address] ), Software Engineer, IBM Software Group 2166A Architecting the On Demand Enterprise October 16, 2006
  2. 2. Agenda <ul><li>COATS/OMCS project </li></ul><ul><ul><li>business case for the On Demand transformation </li></ul></ul><ul><li>Technical Demo </li></ul><ul><li>OMCS transformation to a service-oriented architecture </li></ul><ul><ul><li>design </li></ul></ul><ul><ul><ul><li>conceptual framework: business processes, workflows, services </li></ul></ul></ul><ul><ul><ul><li>enterprise service bus: a messaging and mediation pattern </li></ul></ul></ul><ul><ul><ul><li>deployment architecture </li></ul></ul></ul><ul><ul><li>development </li></ul></ul><ul><ul><ul><li>roles and responsibilities </li></ul></ul></ul><ul><ul><ul><li>best practices </li></ul></ul></ul><ul><ul><li>deployment </li></ul></ul><ul><ul><ul><li>WBI SF clustering for increased throughput and availability </li></ul></ul></ul><ul><ul><ul><li>messaging workload balancing using WebSphere MQ clustering </li></ul></ul></ul><ul><li>Migration to WebSphere Process Server </li></ul><ul><ul><li>Migration Wizard </li></ul></ul><ul><ul><li>WebSphere Integration Developer and WebSphere Business Modeler v6 </li></ul></ul><ul><li>Conclusion </li></ul><ul><li>Video </li></ul><ul><li>Q&A </li></ul>
  3. 3. <ul><li>Situation </li></ul><ul><li>COATS application is a shared order entry service for more than 20 IBM manufacturing plants worldwide. It fields hardware orders from IBM customers, IBM business partners, IBM sales professionals and other internal organizations. The l egacy application was a complex batch system running on a mainframe. </li></ul><ul><li>Challenge </li></ul><ul><li>Rigid legacy code difficult to modify, slowing ability to address new business opportunities and requirements </li></ul><ul><li>PL/I programmers difficult to find </li></ul><ul><li>Batch bottlenecks and conflicting data delayed orders and shipments </li></ul><ul><li>“ Big bang” total replacement unaffordable and disruptive </li></ul>Customer Order Analysis and Tracking System order-2-manufacturing z-, p-, i- series, storage, printers, retail, …
  4. 4. Business Benefits to COATS <ul><ul><li>reduced analysis, design and code time </li></ul></ul><ul><ul><ul><li>25% reduction in the cost of deploying a new application release </li></ul></ul></ul><ul><ul><ul><li>concurrent, collaborative and iterative development practices enabled by an integrated tools suite </li></ul></ul></ul><ul><ul><ul><li>improved error tolerance </li></ul></ul></ul><ul><ul><li>reduced discrepancies in delivery scheduling </li></ul></ul><ul><ul><ul><li>real-time processing of transactions, from 4 minutes to 10 seconds </li></ul></ul></ul><ul><ul><ul><li>potential for increased capacity though vertical/horizontal scaling </li></ul></ul></ul><ul><ul><li>improved application adaptability to changing business requirements </li></ul></ul><ul><ul><ul><li>improved existing business processes </li></ul></ul></ul><ul><ul><ul><li>streamlined the transformation of business processes to executable workflows </li></ul></ul></ul><ul><ul><ul><li>introduced business rules adaptable in real time by a business analyst </li></ul></ul></ul><ul><ul><li>introduced sense-and-respond metrics into business processes </li></ul></ul><ul><ul><ul><li>average throughput, success ratio, problem resolution time, invalid orders </li></ul></ul></ul><ul><ul><ul><li>automatic generation of events marked as business relevant at development time </li></ul></ul></ul><ul><li>Win: IBM Supply Chain </li></ul><ul><li>Other Associated Wins for Asset: </li></ul><ul><ul><li>IBM e-care </li></ul></ul>
  5. 5. Use Processes, Workflows, Services, and Components Process Models & Modules Services Workflows Distributed Components transform use expose
  6. 6. DEMO
  7. 7. Development of an SOA solution WebSphere Business Modeler Rational Software Architect WebSphere Integration Developer File System export export WebSphere Process Server deploy BPEL XSD WSDL Java Classes BPEL XSD WSDL Java Classes import J2EE ear J2EE ear XSD import Repository export Potential candidates Reusable Assets Asset Governance Analyst Architect Integration Specialist SME Describe “as-is” Explore ‘to-be” Assign resources Simulate process Establish system requirements Specify services to be implemented Choreograph process workflow Iterate and generate executable Identify and create reusable assets Deployment Manager Deploy application Developer Create adapters, service providers Add details, service implementations
  8. 8. Create Business Process Model Business Analyst
  9. 9. Business Process Modeling <ul><ul><ul><li>expect a learning curve for transitioning from traditional process modeling tools </li></ul></ul></ul><ul><ul><ul><ul><li>processes in WebSphere Business Modeler are visually more complex than what business people expect from Visio equivalents </li></ul></ul></ul></ul><ul><ul><ul><ul><li>processes nested in while loops are not easy to understand </li></ul></ul></ul></ul><ul><ul><ul><ul><li>the change of nomenclature and modeling artifacts is often confusing </li></ul></ul></ul></ul><ul><ul><ul><li>adopt a convention on how to use colors </li></ul></ul></ul><ul><ul><ul><ul><li>nested vs. simple processes </li></ul></ul></ul></ul><ul><ul><ul><ul><li>external business rules </li></ul></ul></ul></ul><ul><ul><ul><li>leave the implementation details out of the business process, focus on services that generate business value </li></ul></ul></ul><ul><ul><ul><li>create the first iteration of the business process design with the groups outside of IT </li></ul></ul></ul><ul><ul><ul><ul><li>deliver a detailed business vision to the IT </li></ul></ul></ul></ul><ul><ul><ul><ul><li>danger of mixing “as-is” with “to-be” </li></ul></ul></ul></ul>Business Analyst
  10. 10. Configure the generated BPEL workflow Resolve partner links Resolve staff activities Modify transaction boundaries (if required) Specify compensation activities (if required) Add systems fault handling Generate events for business performance monitoring Add code to java snippets Workflow Developer
  11. 11. Staff Activities <ul><li>Steps: </li></ul><ul><li>create staff activity interface </li></ul><ul><li>add activity to process </li></ul><ul><ul><li>add staff roles, verbs and parameters </li></ul></ul><ul><li>integrate UI pages </li></ul><ul><li>select staff resolution plug-in and parameters </li></ul><ul><li>deploy the process with appropriate staff resolution plug-in </li></ul>Workflow Developer
  12. 12. Modify transaction boundaries <ul><li>Long running processes persist business data for each activity/step in the workflow </li></ul><ul><li>Persistence of large objects adversely impacts workflow performance </li></ul><ul><ul><li># workflow steps * (DB connectivity overhead + Factor of the object size) </li></ul></ul><ul><ul><li>10^2 order of magnitude performance difference is typical </li></ul></ul><ul><li>Long running processes can often be partitioned into microflows (short running processes) </li></ul><ul><li>Pass “heavyweight” business objects as parameter to invoke new microflows </li></ul>Order Validation and Topology Generation Order Processing
  13. 13. Workflow Development <ul><ul><li>core Java/EJB skills are important </li></ul></ul><ul><ul><li>problems when integrating with existing services, existing schemas need to be updated or modified to stay compatible with WID limitations </li></ul></ul><ul><ul><ul><li>InfoCenter->Reference->Limitations </li></ul></ul></ul><ul><ul><li>absence of the round-trip modeling (WBM-Rational-WID) </li></ul></ul><ul><ul><li>lack of explicit support for defining rules, metrics, role, and deployment requirements and exporting to runtime artifacts (eg: J2EE) </li></ul></ul>Workflow Developer
  14. 14. Capture Business Policies <ul><li>Example: SelectManufacturingPlant </li></ul><ul><ul><ul><li>Select where to route orders based on changing business criteria </li></ul></ul></ul><ul><li>Analysts specify intended policies using WebSphere Business Modeler </li></ul><ul><ul><li>Documented through annotations of a task </li></ul></ul><ul><li>Policies need to be enforced </li></ul><ul><ul><li>implemented as one or more rules external to the workflow. </li></ul></ul>WB Modeler WID WPS <ul><li>Document Policies </li></ul><ul><li>Specify enforcement points in a business process </li></ul><ul><li>Implement Rules for identified policies </li></ul><ul><li>Create Rule service façade </li></ul><ul><li>Connect workflow to rule services </li></ul><ul><li>Deploy Rules </li></ul><ul><li>Administer Rules </li></ul>Deployment Manager Workflow Developer Business Analyst
  15. 15. Business Rules Implementation <ul><li>choose a business rule approach early in the project </li></ul><ul><ul><li>WebSphere Business Modeler cannot export business rules in isolation </li></ul></ul><ul><ul><ul><li>BPEL export tangles the business rules and the flow </li></ul></ul></ul><ul><ul><li>BPEL does not provide a syntax for externalized business rules </li></ul></ul><ul><li>consider a WSDL interface to a rule base </li></ul><ul><ul><li>wsdl:operation per business rule approach </li></ul></ul><ul><ul><li>room to grow from a simple lookup to a service-based implementation </li></ul></ul><ul><ul><li>flexibility of switching a rules engine behind the interface </li></ul></ul><ul><ul><li>in line with WebSphere Integration Developer/SCA approach </li></ul></ul>
  16. 16. Oneida Lifecycle Adapt CEI CBE CBE WPS Dashboard Monitor Executive Operator End Users
  17. 17. Deployment Topology Process Scalability
  18. 18. Scale Out/Horizontal Clustering <ul><li>early phases of the project used a single server deployment environment </li></ul><ul><ul><li>embedded WebSphere MQ </li></ul></ul>MQ GET/ PUT QM MQ <ul><li>the production environment leverages WBI SF horizontal clustering </li></ul><ul><ul><li>external WebSphere MQ </li></ul></ul><ul><ul><ul><li>WBI SF specific queues: GET/PUT </li></ul></ul></ul><ul><ul><ul><li>JMS client, TCP/IP connection </li></ul></ul></ul><ul><ul><li>WebSphere Network Deployment </li></ul></ul><ul><ul><ul><li>centralized administration </li></ul></ul></ul><ul><ul><ul><li>clustering </li></ul></ul></ul><ul><li>additional WBI SF nodes can be added to the cluster as needed </li></ul><ul><ul><ul><li>load balancing </li></ul></ul></ul>pSeries p615, 1 CPU, 2 GB RAM WBI Server Foundation v5.1.1 WAS component for agent for remote server management and monitoring built-in WAS messaging engine: embedded JMS Provider central queue manager can be shared by multiple WBI SF servers WAS Network Deployment manages individual WAS servers via the node agent WBI SF CLUSTER WASND Deployment Manager WBI SF JMS Node Agent WBI SF JMS Node Agent
  19. 19. Clustering Considerations: WBI SF <ul><li>properties of a clustered WBI SF environment </li></ul><ul><ul><li>increased workload capacity </li></ul></ul><ul><ul><li>improved resource utilization </li></ul></ul><ul><ul><li>workload sharing </li></ul></ul><ul><ul><li>high availability </li></ul></ul><ul><ul><li>centralized administration of servers </li></ul></ul><ul><li>drawbacks of centralized messaging </li></ul><ul><ul><li>no balancing of the messaging workload </li></ul></ul><ul><ul><li>single point of failure </li></ul></ul><ul><ul><li>limit to the scalability of WBI SF </li></ul></ul>MQ GET/ PUT QM JMS WBI SF CLUSTER WASND Deployment Manager WBI SF JMS Node Agent WBI SF JMS Node Agent
  20. 20. Balance the Messaging Workload/MQ Clustering <ul><li>The OMCS production environment takes advantage of decentralized WebSphere MQ servers </li></ul><ul><ul><li>the central messaging server eliminated </li></ul></ul><ul><ul><li>an instance of WebSphere MQ is installed on each physical server in the cluster </li></ul></ul><ul><ul><li>send/receive are handled by separate queue managers </li></ul></ul><ul><li>each MQ server can be added to a cluster shared by WBI SF </li></ul><ul><ul><li>improved workload balancing </li></ul></ul><ul><ul><li>improved performance though local binding </li></ul></ul><ul><ul><li>high availability though redundancy </li></ul></ul>MQ MQ PUT QM GET QM PUT QM Deployment Manager Cluster Repository Backup Repository WBI SF JMS Node Agent WBI SF JMS Node Agent GET QM WASND Deployment Manager MQ GET/ PUT QM WBI SF CLUSTER MQ CLUSTER
  21. 21. <ul><li>collocate MQ and WBISF to reduce I/O bottlenecks </li></ul><ul><li>cluster the MQ servers to balance the messaging workload </li></ul><ul><li>minimize use of the key process bottlenecks </li></ul><ul><ul><li>process instantiation </li></ul></ul><ul><ul><li>invoke activity </li></ul></ul><ul><ul><li>assign </li></ul></ul><ul><li>reference the capacity planning and tuning guides </li></ul><ul><ul><li>https://w3.opensource.ibm.com/docman/index.php?group_id=1706&selected_doc_group_id=1524&language_id=1 </li></ul></ul><ul><ul><li>https://w3quickplace.lotus.com/QuickPlace/wasperf/PageLibrary852569AF00670F15.nsf/h_0DD72A0FDA0EFC0785256E010040EEC1/19A28B673F96C2E085256FB000782BBC/?OpenDocument </li></ul></ul>Optimize for Performance MQ MQ PUT QM GET QM PUT QM Deployment Manager Cluster Repository Backup Repository WBI SF JMS Node Agent WBI SF JMS Node Agent GET QM WASND Deployment Manager WBI SF CLUSTER MQ CLUSTER
  22. 22. Best Practices <ul><li>even with automated code generation from the model, basic software engineering principles have to be followed </li></ul><ul><ul><li>change management and tracking </li></ul></ul><ul><ul><ul><li>WebSphere Business Modeler model -> BPEL and vice versa </li></ul></ul></ul><ul><ul><ul><li>XSD data model and the Java-based implementation </li></ul></ul></ul><ul><li>ensure an appropriate skills base for the project </li></ul><ul><ul><li>auto generated code requires solid Java/EJB foundations </li></ul></ul><ul><ul><li>initiate a proof-of-concept as needed </li></ul></ul><ul><li>establish milestones to interlock development artifacts </li></ul><ul><ul><li>ensure that integration specialists sign off on the business process model before it is converted to BPEL </li></ul></ul><ul><li>“ bite the bullet” and migrate from Workbench to WebSphere Business Modeler </li></ul><ul><ul><li>derive visually appealing diagrams as needed </li></ul></ul><ul><li>plan for performance hit of using BPEL vs. Java implementation </li></ul><ul><ul><li>typically 3-5x slower </li></ul></ul><ul><li>design with web service support limitations in mind </li></ul><ul><ul><li>schema, custom serializers/deserializers </li></ul></ul>
  23. 23. Migrate to WebSphere Process Server 6.0
  24. 24. WebSphere Process Server <ul><li>WPS v6.0 requires BI applications to be created by WID </li></ul><ul><li>Migration Wizard </li></ul><ul><ul><li>GUI tool in WID to migrate from BPEL4WS 1.1 to WS-BPEL 2.0 </li></ul></ul><ul><ul><li>each BPEL process becomes an SCA component </li></ul></ul><ul><ul><li>uses source code only </li></ul></ul><ul><ul><ul><li>don’t need to migrate the EAR, EJB and Web projects created by “Generate Deploy Code” in WSAD IE </li></ul></ul></ul><ul><li>Rulelogic Migration Tool </li></ul><ul><ul><li>ftp://rolo.torolab.ibm.com/com.ibm.wbit.br.tools_1.0.2.zip </li></ul></ul><ul><li>Manual verification </li></ul><ul><ul><li>common pitfalls </li></ul></ul><ul><ul><ul><li>Multiple replies per BPEL operation </li></ul></ul></ul><ul><ul><ul><li>Java snippets </li></ul></ul></ul><ul><ul><ul><li>http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/topic/com.ibm.wbit.help.migration.ui.doc/pdf/migrate.pdf </li></ul></ul></ul><ul><li>Assembly diagram of the SCA components </li></ul><ul><ul><li>WSADIE “Generate Deploy Code” equivalent </li></ul></ul><ul><ul><li>optionally define a binding </li></ul></ul>
  25. 25. WebSphere Integration Developer <ul><li>Migration Wizard </li></ul><ul><ul><li>migrate non-WBI projects first </li></ul></ul><ul><ul><ul><li>ensure J2EE 1.4 compliance </li></ul></ul></ul><ul><ul><ul><li>documented in the Rational Software Architect InfoCenter </li></ul></ul></ul><ul><ul><ul><ul><li>http://publib.boulder.ibm.com/infocenter/rtnl0600/topic/com.ibm.etools.rad.migration.doc/topics/tmigratefrom51x.html </li></ul></ul></ul></ul><ul><ul><li>separate the BPEL logic from the service definition </li></ul></ul><ul><ul><ul><li>use a Business Integration Library project to store WSDL & XSD files </li></ul></ul></ul><ul><ul><li>migrate one service/BPEL project at a time </li></ul></ul><ul><ul><ul><li>for each project, follow the steps in the InfoCenter </li></ul></ul></ul><ul><ul><ul><li>http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/topic/com.ibm.wbit.help.migration.ui.doc/topics/tprepsrcart.html </li></ul></ul></ul>
  26. 26. WebSphere Business Modeler <ul><li>WebSphere Business Modeler Version 5 </li></ul><ul><ul><li>export to WSAD IE 5.1 </li></ul></ul><ul><ul><ul><li>requires the Migration Wizard to convert BPEL4WS 1.1 to WS-BPEL 2.0 </li></ul></ul></ul><ul><li>WebSphere Business Modeler Version 6 Enhancements </li></ul><ul><ul><li>BPEL Export </li></ul></ul><ul><ul><ul><ul><li>ability to export multiple input and output sets and correlations </li></ul></ul></ul></ul><ul><ul><ul><ul><li>ability to export process models as BPEL4WS 1.1 or WS-BPEL 2.0 </li></ul></ul></ul></ul><ul><ul><li>Workplace migration: </li></ul></ul><ul><ul><ul><li>run Modeler 6.0 against a Modeler 5.1.x workspace. </li></ul></ul></ul><ul><ul><ul><ul><li>automatic backup of the workspace prior to migration </li></ul></ul></ul></ul><ul><ul><ul><li>import a Modeler 5.1.x project </li></ul></ul></ul><ul><ul><ul><li>check out a project from the team repository </li></ul></ul></ul><ul><ul><ul><ul><li>on the fly migration during the check out </li></ul></ul></ul></ul>
  27. 27. Conclusion
  28. 28. VIDEO
  29. 29. <ul><li>Lessons learned/best practices </li></ul><ul><li>Reinforce basic software engineering principles for auto generated code </li></ul><ul><ul><li>Change management and tracking </li></ul></ul><ul><li>Ensure an appropriate skills base for the project </li></ul><ul><ul><li>Initiate a proof-of-concept as needed </li></ul></ul><ul><li>Establish milestones to interlock development artifacts </li></ul><ul><ul><li>Ensure that integration specialists sign off on the business process model before it is converted to BPEL </li></ul></ul><ul><li>Design and validate web services against a common data model </li></ul><ul><ul><li>Use document/literal </li></ul></ul><ul><li>Powered by </li></ul><ul><li>Software: WebSphere MQ, Portal, WAS, WBI-SF, DB2 </li></ul><ul><ul><li>Migrating to WebSphere Process Server and WebSphere Business Monitor </li></ul></ul><ul><li>Tools: Rational XDE, WBI Modeler, WSADIE, Rational Software Architect, WebSphere Integration Developer </li></ul><ul><li>Patterns: IBM patterns for e-business, SOA, ESB </li></ul><ul><li>Solution </li></ul><ul><li>Flexible architecture that supports the ongoing transformation of COATS into highly adoptable application </li></ul><ul><li>Real time transaction processing </li></ul><ul><li>Legacy business logic converted to externalized business rules and workflows of reusable services to improve adaptability to changing requirements </li></ul><ul><li>Business process modeling and workflow generation - reduced analysis, design and coding time </li></ul><ul><li>Generation of sense-and-respond metrics </li></ul><ul><li>Results </li></ul><ul><li>Affordable incremental migration from legacy </li></ul><ul><li>Order transaction processing time reduced from 4 minutes to 10 seconds </li></ul><ul><li>Ability to make on demand changes to the run time workflow , through easily selectable rules </li></ul><ul><li>25+% reduction in development time/cost </li></ul><ul><li>SOA Reference architecture and best practices that are being replicated across IBM and clients </li></ul>Customer Order Analysis and Tracking System order-2-manufacturing z-, p-, i- series, storage, printers, retail, …
  30. 30. On Demand Business Process Lifecycle developerWorks articles series 1. Create the foundation for your on demand business processes 2. Patterns for e-business recipe 3. Business process modeling using WebSphere Business Integration Modeler 4. Integrate artifacts from Rational XDE and WebSphere Business Integration Modeler 5. Workflow development, deployment, and testing 6. Apply customization policies and rules 7. Monitor business processes and emit events using CEI 8. Business process monitoring -- Create key performance indicators 9. Involve people 10. Develop message adapters for CICS transaction servers 11. Integrate business processes with CICS transaction servers 12. Implement a compensation service 13. Deploy in a clustered environment 14. Use a clustered WebSphere MQ deployment to balance messaging workload 15. Deploy a scalable, secure and stable foundation for a Service-Oriented Architecture
  31. 31. Conclusion <ul><li>Built a business case of an SOA transformation of a legacy IBM supply chain application </li></ul><ul><ul><li>demonstrated value to IBM </li></ul></ul><ul><li>Designed and developed the OMCS application using WebSphere Business Integration tooling </li></ul><ul><li>Refactored the deployment architecture to improve throughput, availability and performance </li></ul><ul><ul><li>WBI SF and MQ clustering </li></ul></ul><ul><li>Began migration to WebSphere Process Server </li></ul>
  32. 32. Click to edit Master title style QUESTIONS?
  33. 33. Click to edit Master title style THANK YOU!

×