Integration Gateway: Solution for “Malformed Service”-error in Service Catalog
This blog is about Integration Gateway (IGW) in SAP Mobile Platform 3.0 (SMP), more concrete, about the designtime in Eclipse.
This information Blog is useful for those of you who are
– working with Eclipse
– working with the API toolkit for SAP Mobile Platform
– using the OData perspective
– using the Service Catalog view
– wondering about services that are marked as “malformed”
Working with the Service Catalog view in Eclipse makes sense if you have an ABAP backend connected, if you have OData services there and if you like to view them in Eclipse.
With the view Service Catalog, you can very easily browse the OData services and view the metadata in the OData Modeler
In case you haven’t seen it yet:
Browse OData services
Apply filter to quickly find your service
View details in the property view
View the OData model in the graphical OData Modeler (Read Only) and get an overview in the Miniature View
Execute actions, like importing the model into a project
The “Malformed Service” – error
You may have faced the issue that the service that you’re interested in is marked as erroneous
And even causes an error popup
In such a case you could proceed as follows:
-> refresh this service node by opening the context menu and choosing “Refresh”
However, this might fail.
In such a case it is useful to know what’s happening behind the scene.
When browsing the services of a connected backend, the API toolkit for SMP reads the OData services and caches the metadata.
This cache is located on your file system at:
In this folder, there’s a file for each OData service and the file contains the metadata of the service.
Now, it can occur that such a file is missing or that it is corrupted, both could have been caused by network issues while connecting the backend.
It may be helpful to open the file if it is marked as erroneous, as it contains an error message
The solution is simple:
Go to your file system and open the “.data-storage” folder as mentioned above.
Find the file that represents your service and delete it (alternatively, you can delete the whole folder.)
Afterwards go back to Eclipse and refresh the OData service or the full connection node, by using either the context-menu or the toolbar button.
This brute-force method should solve the problem, you can verify if the metadata file is successfully created in the respective .data-store folder.