SAP NetWeaver Gateway Service Builder

SAP NetWeaver Gateway Service Builder (transaction SEGW)) is a design-time environment, which provides developers with an easy-to-use set of tools for creating services. It has been conceived for the code-based OData Channel and supports developers throughout the entire development life cycle of a service.

If your system is based on SAP NetWeaver 7.4 or higher, the core component SAP_GWFND is installed as standard and includes the functional scope of IW_BEP.

For more information about deployment options and scenarios, see SAP NetWeaver Gateway Master Guide.

In one single transaction, SAP NetWeaver Gateway Service Builder caters for the needs of both experienced and less experienced developers who want to expose data for easy consumption using a variety of platforms, frameworks, and devices. While experienced developers have maximum flexibility to define a new service from scratch and integrate their own source code, less experienced developers can reduce the time and effort involved in creating services by importing existing definition files and implementing content generators. In short, the Service Builder provides an OData-compliant modeling environment for the creation and maintenance of OData services without the need for programming. The Service Builder visualizes all development artifacts developers need to create a service including:

• SAP NetWeaver Gateway runtime artifacts such as model provider class (MPC), data provider class (DPC), model, annotation provider class (APC) and service
• OData artifacts such as entity set, entity type, and properties

The Service Builder introduces a new service development concept, which is organized around projects. Projects are used to store all the artifacts developers need to create a service and model together in one place. Since projects consolidate all related data, developers can easily work on multiple projects in parallel and reuse data between projects before generating and activating the actual service. Consequently, projects provide developers with the freedom to interrupt the service development and modeling process at any time, without being bound to runtime artifacts and without risk of losing data. Organizing the service development and modeling process in projects has the advantage that all project data can be transported easily between one system and another for maximum efficiency and reuse.