Services within SIW

Definition

You can use Service Implementation Workbench (SIW) to implement enterprise services in different ways that are represented by different service creation types in SIW. Each configuration determines the used service creation type and therefore the service creation process. The tool distinguishes between the following service creation types:

• Proxy-based service creation

  The service development process follows the outside-in approach for this service creation type: You start to describe the service by designing a process model and the service signature outside SIW in a repository (such as ES Repository). Then you create the proxies in the corresponding backend using the SPROXY transaction. SIW is not involved in these modeling steps. With proxy-based service generation, you use SIW only to create the service implementation in the ABAP backend system. For more information about this process, see Service Creation and Implementation (Proxy-based).

• API-based (with ES Repository) service creation

  For this service creation type, service creation follows the inside-out approach. You use an existing application programming interface (API) to derive the signature and implementation of the service.

  SIW creates the service operation in the repository (such as Enterprise Services Repository) including service interface, message types using existing data types. It also triggers the proxy creation. Finally, SIW creates the service implementation in the backend system. For more information about this process, see Service Creation and Implementation (API-based with Repository).

• Non service-related

  You can also use SIW to generate objects that are not service-related.