Hi everyone,
I’ve created an OData service that reads data from a custom table and provides PDF downloads. Everything is fully implemented and working in our development system (DEV). The service also runs fine in the Gateway Client (/IWFND/GW_CLIENT).
After transporting it to QA, I’m getting the following error in the Gateway Client:
500 – No system alias found for service
When I checked the service in QA via /IWFND/MAINT_SERVICE, I noticed that there is no system alias “LOCAL” defined at all.
This confused me because in DEV the service is assigned to the alias “LOCAL”, but in QA it doesn’t exist.
What also makes it strange:
Other OData services in QA and PROD are working fine—even though they also don’t have any system alias assigned. So the system somehow works without explicitly having “LOCAL” configured.
My questions:
Why does “LOCAL” exist in DEV but not in QA/PROD?
Shouldn’t this be consistent?
How is it possible that other OData services work without any system alias at all?
Is the system using some kind of implicit local alias?
What is the correct way to fix this issue for my new OData service?
Do I need to create the alias manually in QA, or is there a better approach?
How can I make sure that existing productive OData services won’t be affected by this configuration?
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.