Service Creation and Implementation (API-Based with Repository)

Use

This process supports you in creating and implementing enterprise services in an inside-out approach, that is that the system derives the signature of the service operation from an existing ABAP Application Programming Interface (API). For more information about other SIW service creation types, see Services within SIW.

Prerequisites

A configuration class defined for the API-based creation type must be available. You have made the appropriate Customizing settings SAP NetWeaver Implementation Guide under Start of the navigation pathApplication Server Next navigation step Basis Services Next navigation step Generic Business Tools Next navigation step Service Implementation Workbench Next navigation step Define LandscapeEnd of the navigation path and Start of the navigation pathDefine ConfigurationEnd of the navigation path.

Process

The process consists of the following process steps:

API-based Service Creation and Implementation (with Repository)

  1. Creation of a Project in SIW

    You start the process by creating a project in Service Implementation Workbench (see Creating Projects) based on a configuration of the API-based creation type.

  2. Completion of Signature (Mapping)

    You complete the draft signature in SIW by entering names for the fields, structures, and tables and by assigning global data types from the ES Repository for the fields of the project tree (see Completing Signatures (Mapping)). Furthermore, you can specify which fields, structures, and tables you want to use and which ones you do not want to use for the service signature. During this mapping process, the system reads information about the GDTs that are available in ES Repository and provides this information as mapping proposals. When you start the generation after you have completed the mapping, the system automatically checks the mapping. For more information, how you can manually start the Mapping check, see Executing Mapping Check.

  3. Generation of Service Interface in ES Repository

    After you have completed the mapping, you trigger, also in SIW, the creation of the service in ES Repository. To do so, choose the Generate ES Repository pushbutton in the menu tab of the SIW transaction. SIW then creates the service interface in ES Repository by writing the complete service definition to the ES Repository.

  4. Generation of Service Proxies in Backend System (Transaction SPROXY)

    When SIW has created the service interface in ES Repository, you trigger, again in SIW, the creation of the service proxies in the backend system. To do so, select the Generate Proxies pushbutton in the menu tab of the SIW transaction. Then, the system creates the service proxies in the backend system that is defined in the configuration (Customizing activity Defining Configurations).

  5. Completion of Project Context Data

    Additionally, you enter the project specific context data (values of context variables). Thereafter, you choose Apply Context to confirm the values and to create the generation preview (object preview). In this preview the objects that the system will create, change and delete during generation are displayed. For more information, see Completing Project Context Data.

  6. Generation of Service Implementation

    After completing the project specific context data, you trigger the generation of the single objects that make up the service implementation by choosing the Generate toolbar in the dropdown menu.

  7. Completion of Coding (Code Slots)

    When SIW has generated the objects of the service implementation, you call the To-do Browser in the Generated Objects register tab. You check for which objects you need to enter additional coding and complete the project specific code slots for these objects. You activate the coding changes in the Class Builder. For more information, see Completing Coding.

Result

As result of this process, SIW has created an enterprise service definition within ES Repository and an enterprise service implementation in the backend system that is ready to be used within a business process.

It can be necessary to update a service implementation at a later stage, for example, when the Service Implementation Architect modifies the configuration after the objects of a project have already been generated. You can update a service by regenerating the objects of a project, either one by one or all objects of a project at the same time. For more information about how to update a service implementation, see Regenerating Projects.

To check whether an implementation of one ore more enterprise service is up to date and for transporting projects, you can use the SIW Monitor report. For more information about this report, see its system documentation (transaction code SIW_MONITOR).