Completing Project Context Data

Use

For each proxy-based service implementation you need to complete the Project Context Data to specify the project-relevant context for your service.

For API-based service implementations completing Project Context Data can be optional. This depends on the underlying API.

You complete Project Context Data by entering values for the context variables that the service implementation architect has determined as relevant.

Prerequisites

For proxy-based service creation, you must have created a project (see Creating Projects (proxy-based)).

For API-based service creation, you must have done the following:

  1. You must have created a project (see Creating Projects (API-based).

  2. You must have finished the mapping (see Completing Signatures (Mapping).

  3. You must have generated the service interface in the ES Repository (see Service Creation and Implementation (API-based), point 3.

  4. You must have generated the service proxies in the backend system (see Service Creation and Implementation (API-based), point 4.

Procedure

You are in transaction SIW and have double-clicked on the implementation node of your created project.

  1. To open the Project Context Data, select the Context register tab.

  2. Choose Change mode. Then, the system displays the read-only value fields and all entry-fields in different colors.

  3. Enter your implementation-specific values for the single context variable fields where necessary.

  4. Choose Save.

  5. Select the Apply Context pushbutton to confirm the entered values. The system then checks the status of all objects that you want to generate and sets one of the following statuses for each:

    • New

      The object does not exist in the backend system, yet. The system generates it during the next generation.

    • To Be Adopted

      The object does already exist in the backend. The system adopts it during the next generation.

    • Object Name To Be Changed

      The object does exist in the backend with a different name. The system renames it during the next generation and deletes the object with the previous name in the backend system.

    • To Be Adopted after Renaming

      You have chosen a name for your SIW object, which exists already in the backend. SIW adopts the backend object during generation and deletes the object with the previous name in the backend system.

    • Up To Date

      The object does already exist in the backend. No changes are needed.

    • To Be Deleted

      The object does exist in the backend system. SIW deletes it during the next generation.

    • Generation Impossible

      The generation of the object is not possible. This can happen for example if the implementation is not consistent. In this case, you must check the context parameters and retry to generate the corresponding object.

    In addition to that, the system creates the Object Preview on the Objects register tab and displays all objects that the system creates, changes, and deletes during the next generation.

Result

The system has saved all implementation-specific data of your project. Now, you can generate your service implementation in the backend system. To do so, select Generate in the symbol bar. For more information, see Generating Service Implementations.