M
Matt
I have what seems like an interesting issue...
We have some 3rd-Party enterprise PLM software here, which uses a web
services interface to go between the GUI client and the server...
I'm interested in putting some kind of proxy service between the client and
the server (a secondary server application which could catch requests,
inspect them, and pass them on to the actual web service)... I have limited
ability to change the client application - so I probably have to replicate at
least the names of the 5-6 services...
Can anyone give me recommendations on how to approach this problem? I feel
like I have to attack it higher in the stack than I'm currently working (I
replicated one service, but I had to implement each webmethod individually -
I'd like something higher level where I could just catch the SOAP request and
forward it).
Thanks in Advance,
Matt
We have some 3rd-Party enterprise PLM software here, which uses a web
services interface to go between the GUI client and the server...
I'm interested in putting some kind of proxy service between the client and
the server (a secondary server application which could catch requests,
inspect them, and pass them on to the actual web service)... I have limited
ability to change the client application - so I probably have to replicate at
least the names of the 5-6 services...
Can anyone give me recommendations on how to approach this problem? I feel
like I have to attack it higher in the stack than I'm currently working (I
replicated one service, but I had to implement each webmethod individually -
I'd like something higher level where I could just catch the SOAP request and
forward it).
Thanks in Advance,
Matt