Webservice proxy with fds2

Question

Hello all,
I am struggling with fds2 and currently fail to use a proxy
for my webservice.
Maybe I also misunderstand something, cause what I want to do
is I want to use the fds/webservice as proxy to gather the calls
and forward it to another webservice (who just accepts the
connections from the proxy pc)
So I configured the service_config.xml and put it into the
additional compiler arguments, but for somehow reason it even
didn´t connect to the webproxy.
Maybe I have to learn more about jrun, but from the
documentation I thought the webproxy configuration is easy to
setup.
Did someone has experience in setting up a similar scenacrio
? (maybe with other application servers)
best regards,
kcell

Answer 1

Ah, you've confused what a channel endpoint is, and what the
proxy service
will "proxy" for your when contacting your WebService.
Your channel-definition endpoint should NOT be pointed at
your WebService
- it should be pointed at the FDS server endpoint as it has
the proxy service
that you want to proxy through.
However, you may have complicated things by having an Apache
server and a
JRun server on Server A (unless you've successfully used a
connector so that
Apache redirects requests to JRun?). If you are using a
connector and Apache
and JRun receive web requests on the same port then you could
do this:
<channel-definition id="myWS"
class="mx.messaging.channels.HTTPChannel">
<endpoint uri="
http://{server.name}:{server.port}/helloworld/messagebroker/http"
class="flex.messaging.endpoints.HTTPEndpoint"/>
</channel-definition>
But, if you have different ports for calling your SWF from
apache and sending
data to FDS on JRun, then you can't rely on {server.name} and
{server.port}
tokens, so it would have to look something like this:
<channel-definition id="myWS"
class="mx.messaging.channels.HTTPChannel">
<endpoint uri="
http://yourjrunserver:8100/helloworld/messagebroker/http"
class="flex.messaging.endpoints.HTTPEndpoint"/>
</channel-definition>
But, in order for your SWF loaded from
http://yourapacheserver:8080/yourapp.swf
to contact
http://yourjrunserver:8100/...
you'd need to host a crossdomain.xml
file at
http://yourjrunserver:8100/crossdomain.xml
and setup a policy so
that at least SWFs from yourapacheserver can contact it (I
hope you see why
it's easier to host SWFs on the same web application server
as FDS so that
you can avoid these security sandbox considerations! ).
(...and note you can rely on the {context-root} token instead
of hard coding
"/helloworld" into the endpoint location now that you're
aware of the -context-root
compiler argument).
Then, your proxy-service destination should look something
like this:
<destination id="myWS" adapter="soap-proxy">
<adapter ref="soap-proxy" />
<properties>
<wsdl>
http://anhalt/OMTest/Service1.asmx?WSDL</wsdl>
<soap>
http://anhalt/OMTest/*</soap>
</properties>
</destination>
The reason is that you first need to get the Flash Player to
connect to FDS,
and then FDS's proxy service will end up contacting your web
service.
Another alternative is to just take FDS out of the picture
entirely if you
control the contents of the server hosting your .NET web
service. Simply
setup a /crossdomain.xml policy file on that IIS server and
you don't need
to use a proxy or FDS at all.