Additional Blogs by SAP
cancel
Showing results for 
Search instead for 
Did you mean: 
soum_chatterjee
Associate
Associate
0 Kudos

The Repository and Registry for everyone - SAP and non-SAP content support

 

 

By Julia Doll, SAP NetWeaver Product Management - SOA Middleware

 

 

In SOA, the registry and repository together build the central point where all services are stored and managed. The registry and repository can be filled with non-SAP Services, SAP Services or custom built services. These services - SAP or non-SAP can be imported through their WSDL file. SAP Services are delivered with the repository and custom built services can be modeled with simple and intuitive graphical modeling tools in the repository. If customers want to use their old systems they need to service enable those with SAP NetWeaver SOA Middleware - Process Integration tools.

 

 

SOA is based on open standards and so are the registry and the repository used in SAP NetWeaver SOA Middleware. Since Web Services are based on open standards, it is possible to import Services from every provider into the SAP registry and repository as they are based on WSDL. Publishing into the registry is a simple process where the user just needs to enter the WSDL file of the Service. The SAP Services delivered with the repository are categorized and classified in advance. But, all these categories can also be assigned to non-SAP Services during the publishing process. The customer can also create categories on his own and assign those to the services.

 

The repository provides different SOA artifacts (services, routings, mappings, objects…) corresponding to the governance guidelines. Objects are based on the global data type standard.

 

 

The repository can be managed individually. The customer has the control of the repository content and follows certain governance rules. That makes it possible to use it with every non-SAP system. It allows to model third party services and to connect those to the corresponding non-SAP backend by using SAP NetWeaver SOA Middleware.

 

The target of this openness is to enable easy non-SAP A2A and B2B integration. It enables them to integrate all their non-SAP products by using SAP NetWeaver SOA Middleware.

 

 

 

The registry and repository are delivered with services which are based on the applications delivered by SAP. SAP is one of the few middleware providers that also deliver backend applications and Services.