 | Level: Intermediate Yali Wang (yaliwang@ca.ibm.com), Software Developer,
<a href="http://www.ibm.com/developerWorks">IBM</a>
Shiva Mohan (shivam@ca.ibm.com), Software Developer, IBM
12 Sep 2007 This tutorial explains the benefits of migrating WebSphere® Commerce using WebSphere Business Modeler and WebSphere Integration Developer. [an error occurred while processing this directive]In this tutorial
The SOA foundation tooling helps you to easily migrate early-era J2EE applications to service-oriented architecture (SOA). Both WebSphere Business Modeler and WebSphere Integration Developer provide visual interfaces and flexibility. Modeling the processes in Business Modeler enables WebSphere Commerce clients to run simulations and receive runtime feedback on the deployed instance of WebSphere Commerce. For Business Modeler, the simulation functions are a bonus for creating and changing business processes. Using WebSphere Integration Developer yields easier process change. Developers deal with visual processes that are easily re-configured to suit the client's needs. It includes human tasks, such as escalation rules, timeouts, and roles, and the externalization of business policies for increased runtime configurability. This tutorial discusses the benefits of migrating from WebSphere Commerce to SOA by using the SOA foundation tooling.
Objectives - Learn the modeling and simultation capabilities of WebSphere Business Modeler.
- Learn how to extend the release to fulfillment process by using the SOA foundation tools - WebSphere Business Modeler and WebSphere Integration Develoepr.
Prerequisites
System requirements
- Machine with a running instance of WebSphere Commerce v6 (WCToolkit_060420c).
- WebSphere Integration Developer with a working version of WebSphere Process Server v6.0.1.
Duration
3 hours
Formats html, pdf
| | | | [an error occurred while processing this directive]
| |
