Skip to Content

COIL 

 

The two previous blogs of this series – SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Modeling Services (Part 3) and SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – 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:

  • Select an existing Business Object from a SAP (a few are preset in the tool; otherwise consult ES Workplace) or create a new one
  • Create the corresponding Process Component for your Business Object (or simply look at the one that is assigned by SAP for pre-defined Business Objects)
  • Select an interface pattern. All pattern-correlated rules will be automatically generated
  • Select a Service Operation out of the selected pattern

 

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:

image

 

Download the current draft version of the Methodology Wizard:

image

 

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:
1.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Introduction (Part 1)Screencam
2.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Outlining the ‘way to deliver’ services (Part 2)
3.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Modeling Services (Part 3)Screencam
4.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Defining services (Part 4)  – Screencam
5.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Leveraging a wizard to automate Service Creation (Part 5)Screencam + Wizard (This Blog)
6.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing Services in Java (Part 6)Screencam
7.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing Services in .NET (Part 7 – provided by Nakisa)Screencam
8.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing services in ABAP (Part 8)Screencam
9.      SAP Co-Innovation Lab Architecture Series: Custom Development delivered Custom Enterprise Services (Part 9)Screencam
10.    The specified item was not found.Certification

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply