|
Blogs
The two previous blogs of this series - Modeling Services (Part 3) and Defining Services (Part 4) - showed the path from creating the model entities (process component model, business object, etc.) down to the actual service definition (service interfaces, operations, Message Types, Message Data Types, ...) from the model ultimately receiving a design time WSDL.
In the course of the preparation of the coming certification around synchronous A2X service interfaces I have implemented a wizard that automates the process of building methodology compliant services. In short, the wizard is a java standalone tool that does roughly 80% of the modeling and 20% of alle the definition work required for building A2X services. The wizard boosts service creation from a matter of weeks to a couple of days through governance and methodology automation. It guides step by step through the generic methodology and ensures consistent terminology by generating names according to the methodology's naming conventions. In the following the single steps are outlined:
This wizard is still a draft version and will be enhanced over time. Stay tuned for more information to come on SDN.
The attached screencam is targeted to guide you through exactly these steps. By using the example of the "Read Sales Order" service again, you can directly compare the modeling and definition process to the two previous blogs of this series.
So continue on your PdES journey and have a look at the screencam:
Download the current draft version of the Methodology Wizard:
Ride in the tube of SOA and learn how to deliver your services based on SAP's modeling and definition methodology. Stay tuned for more information and move on in your PdES journey with the next blog on "Implementing Services in Java".
In the following the links to all blogs and screencams from the PdES Architecture Series:
Mischa Keil joined SAP in 2006 and studies Business Information Technology. Add to: del.icio.us | Digg | Reddit
|