OSB Exposing Proxy Service as Web Service to external consumers

Question

Hi all,
I am trying to expose my proxy service which I have defined in OSB11g to be exposed to external applications and consumers, rather than listening to a queue or using a business service to receive the traffic. What would be the best approach and practice to this issue? Needless to say that since I mentioned this proxy needs to be exposed as web service, I'll be expecting back response. The endpoint that I am getting as result of creating this proxy comes to be in following format:
/<project_name>/Services/ProxyServices/MyProxy
This fine for apps deployed on the same domain, but not if they are not deployed on the same domain.
thanks in advance

Answer 1

From the information shared you, looks like you want to create a SOAP over HTTP webservice in OSB which will be the one exposed to external consumers.
1. So to create such a Proxy service, you will need to define the interface using a WSDL (as mentioned by Pierluigi) first.
2. Once done, you can create a Proxy (SOAP/HTTP) based using the above WSDL. Then implement your business logic in the message flow.
3. As a part of the configuration, you can define the context root of the service. (by default you might be getting /<project_name>/Services/ProxyServices/MyProxy)
You can customize as required, for e.x change this to /services/MyProxy
4. The final URL that can be used to access the above proxy will be as follow:
http://<hostname>:<port>/services/MyProxy for HTTP
https://<hostname>:<port>/services/MyProxy for HTTPS accordingly.
Depending on the way your domain is configured (managed servers) you can change the hostname and port.
So irrespective of where this service is deployed, you should be able to access it.
Do let me know in case my understanding is incorrect.
Thanks,
Patrick