The registration process of models and services is based on IMG activities and underlying repository objects. In order to allow collecting authorizations per data provider class a repository object type is available. This is integrated into transaction SU22 See also Roles in the SAP Gateway Landscape. The following repository object types are available:
Logical transport object for the transport of an OData Channel service in the system where IW_BEP is deployed (applicable for systems based on an SAP NetWeaver release lower than 7.40).
Logical transport object for the transport of an OData Channel model in the system where IW_BEP is deployed, to be in line with the transport concept of an OData Channel service (applicable for systems based on an SAP NetWeaver release lower than 7.40).
The foundation on repository objects has the following impacts:
Models and services are only transported via the transport objects.
The external name of a service is derived from the technical name and cannot be freely defined to ensure a GTADIR connection to guarantee unique Services.
You create service /MYNAMESPACE/MYSERVICE version 0001 which then results in http://host:port/sap/opu/odata/mynamespace/MYSERVICE.
The activities are part of the OData Channel implementation guide (IMG) on the backend system to maintain services / models and services:
In transaction SPRO open the SAP Reference IMG and navigate to and Maintain Services.
In the IMG navigate to Maintain Models and click on the Activity icon.
Enter the Technical Model Name.
Choose Change to assign the model provider class. Enter a model description.
Save the model, specify a package assignment and add it to a valid transport request.
Ensure the model is working fine by choosing .
A success message displays, indicating that the model is correct.
In the IMG navigate to Maintain Services and click on the Activity icon.
Enter the Technical Service Name.
Choose Change to assign a data provider class and enter a service description.
Save the service, specify a package assignment and add it to a valid transport request.
Choose Assign Model to assign the model to the service.
Save your settings. After saving the service / model assignment is finished.
You have now maintained and registered your service in the backend system. You can use the old view cluster display all registered services and models (IMG activity Display Models and Services).
Continue with the activities in the SAP Gateway Hub System.