OSB: Proxy chains and best practice
990775Feb 13 2013 — edited Feb 16 2013Hi,
We have been developing chains of proxy services on our OSB in the following manner:
Client proxy service (via http) => Enterprise proxy service (via http) => Business Service (via sb) => Oracle DB SP (via jca)
The client proxy services are not always present, only if it was absolutely necessary to give the consumer a friendlier interface.
The enterprise service is almost straight pass-through, only transformation is to maybe translate the db column names into
understandable english ones.
My questions:
1. Can you see any potential problems with this approach?
2. What is the cost (if any) of using http transport between proxy services in a chain as opposed to using the sb protocol?
3. If a client proxy is necessary should that rather become a new unique enterprise proxy service instead of routing to the existing
generic one as above?
I realise these are absolute newb questions but I just need to make sure. Any advice\criticism would be most welcome.
Thanks in advance