SAP Gateway Service Builder (transaction SEGW) is a design-time environment, which provides you an easy-to-use set of tools for creating services. It supports you throughout the development life cycle of a service.
To use SAP Gateway Service Builder, you must install the Add-On IW_BEP, if your system is based on an SAP NetWeaver release lower than 7.40. Depending on your system landscape, you can install this add-on either in an SAP Gateway system or in an SAP Business Suite system. If you system is based on SAP NetWeaver 7.40 or higher, the core component SAP_GWFND is installed as standard and includes the functional scope of IW_BEP.
Role /IWBEP/RT_MGW_DSP for an SAP Gateway Service Builder developer who wants to import from and map against BOR/RFC data sources is located in SAP Business Suite back-end systems. Add this role to the developer role in the back-end system.
You must implement the following SAP Notes for the Service Builder:
For more information about deployment options and scenarios, see SAP Gateway Master Guide
In one single transaction, SAP Gateway Service Builder caters 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, 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 Gateway runtime artifacts such as model provider class (MPC), data provider class (DPC), model, 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.
For detailed information about the end-to-end service development process, see the Service Builder cookbook, Getting Started with the Service Builder.