We have a customer who uses an embedded Netweaver Gateway deployment. They have 3 clients in their development system. One is used for customization. One is used for workbench. And the last is their de facto QA system.
The last client ("QA") is set to not modifiable. The first two clients have no master data on them at all, so we cannot test in either of those clients. The Netweaver Gateway configuration is done in 100 and transported across to 110 and 300. So the system aliases are setup.
Development of the service is successful in the workbench client. When we register the service, we get a green traffic signal and are able to test it in the workbench client. Because there is no data, we can only do a metadata test.
However when we log onto the third client ("QA"), and maintain the service, the green traffic signal is replaced by a yellow yield signal. If we click on "register", we are told that the service has already been registered. If we maintain it, there is no system alias assigned to the service. Because fo this, when we test the service, we get an error. We cannot delete the service and re-register it again because of the not modifiable setting.
I realize this setup is a bit unorthodox, but customers are customers. Besides asking the customer to unlock the third client, are there any other suggestions someone would suggest?
Regards,
Gareth