when you insert credentials in the URL after the scheme ... the http client (curl, the browser, etc) extracts those creds and creates an Authorization header with Basic Authentication. More details here. Not all clients follow this convention. The Chrome browser, for example, recently removed support for doing this. I think the http client used by the Apigee Service Callout policy does not provide this "syntactic sugar" assistance. You have to set the header yourself, explicitly.
You will be able to use the BasicAuthentication policy to do what's necessary. You said you tried "sending the credentials using the Basic Authentication policy". To be precise, the BasicAuthentication policy doesn't send credentials. The only thing it does is encode or decode a Basic Auth header. You need a complementary policy like ServiceCallout or a JS to "send" the header that was thus encoded.
I suspect that when you used the BasicAuthentication policy, you had some other problem or glitch in either how you're using the policy or how the variable you set with that policy is being propagated into the request being sent by ServiceCallout or JS, to the NetWeaver endpoint.
Double check everything and give it another shot. If you can't figure it out, maybe try an echo endpoint. Use the same policies to send (FAKE!) credentials to an echo endpoint (like this one) to verify that your policies are sending what you think they should be sending. That echo service will just send back to you in a response, some data indicating what the endpoint received.
This is a handy tool for diagnosing many questions like "Why is my backend responding the way it responds?"
LinkedIn
Twitter
