You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Mayur Shetye <Ma...@realtydata.com> on 2005/10/03 20:51:25 UTC
Forwarding to the appropriate port
Hello all
I have some webservices deployed using axis in the oracle 10G application
server. I actually wanted to some advice from the group.
1. If it advisable to run webservices in oracle 10g Application server as
opposed to Tomcat? (They do run, but I want to know if anyone thinks that
this should not be done)
2. My configuration is as follows
Requests are
internet -> APACHE HTTP server (port 80) -> 10g App Server (port
7780)
Response is
10g App server (port 7780) -> Apache HTTP server (port 80) ->
internet
Entry point is the apache web server on port 80.
Now, the webservices work fine in this configuration except when I try to
get to the WSDL file. The url to which it goes is like
http://abc.xyz.com:7780/service/abc?wsdl
I want to know Why it goes directly to port 7780, I am sure some of you have
faced this problem in apache-tomcat configuration too. Currently I am not
able to see the WSDL file itself.
Let me know what can be done so that wsdl file appears on port 80. Also
interestingly if I invoke the webservice on port 80 it WORKS. Suggesting
that apache forwards the request properly to the 10g App server instance,
the WS is invoked and a corresponding response is sent.
I have got VERY poor tech support from oracle with this.
Regards
Mayur
Re: Forwarding to the appropriate port
Posted by Tom Oinn <tm...@ebi.ac.uk>.
Mayur Shetye wrote:
> I want to know Why it goes directly to port 7780, I am sure some of you have
> faced this problem in apache-tomcat configuration too. Currently I am not
> able to see the WSDL file itself.
>
> Let me know what can be done so that wsdl file appears on port 80. Also
> interestingly if I invoke the webservice on port 80 it WORKS. Suggesting
> that apache forwards the request properly to the 10g App server instance,
> the WS is invoked and a corresponding response is sent.
Hi Mayur,
It's not really an answer as such but the best thing to do is take the
WSDL file, remembering to re-write the bindings if required to point to
your external address (we have a similar problem in house with the
autogenerated WSDL quite reasonably pointing at the node in our blade
farm which hosts it, unsurprisingly this is not a public address) and
put it up as a static page like any other. Note that when I say 'rewrite
the bindings' I mean load the thing into a text editor and do a search
and replace, no need for anything more complex.
Last time I checked the recommendation was to disable autogeneration in
a production environment in any case, but someone from the Axis team can
confirm or deny that I'm sure.
> I have got VERY poor tech support from oracle with this.
I'm shocked and amazed....
Cheers,
Tom
Re: Forwarding to the appropriate port
Posted by Jim Azeltine <ja...@sbcglobal.net>.
I think your problem may be due to the fact that oracle 10G application
server can process web service transactions by itself, without axis. The port it listens on is configurable. When you speak of the apache webserver, it is actually the Oracle HTTP server, which is processing and redirecting the ws transactions, apache is encapsulated.
Jim
Mayur Shetye <Ma...@realtydata.com> wrote:
Hello all
I have some webservices deployed using axis in the oracle 10G application
server. I actually wanted to some advice from the group.
1. If it advisable to run webservices in oracle 10g Application server as
opposed to Tomcat? (They do run, but I want to know if anyone thinks that
this should not be done)
2. My configuration is as follows
Requests are
internet -> APACHE HTTP server (port 80) -> 10g App Server (port
7780)
Response is
10g App server (port 7780) -> Apache HTTP server (port 80) ->
internet
Entry point is the apache web server on port 80.
Now, the webservices work fine in this configuration except when I try to
get to the WSDL file. The url to which it goes is like
http://abc.xyz.com:7780/service/abc?wsdl
I want to know Why it goes directly to port 7780, I am sure some of you have
faced this problem in apache-tomcat configuration too. Currently I am not
able to see the WSDL file itself.
Let me know what can be done so that wsdl file appears on port 80. Also
interestingly if I invoke the webservice on port 80 it WORKS. Suggesting
that apache forwards the request properly to the 10g App server instance,
the WS is invoked and a corresponding response is sent.
I have got VERY poor tech support from oracle with this.
Regards
Mayur