|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
WSAS Endpoint IPHello Everyone,
I'm changing my WSAS to production server, but I'm getting several problems. First, I think that is important to tell you that I have WSAS running inside Tomcat 6. I have changed the Server URL on carbon.xml, but the Endpoint on the WSDL files is with the local IP. How can I change this? I want the address to come with the domain name. The other problem is quite different. By default, through the WSAS interface, all the WSDL files are available using HTTP, but I need to change it to HTTPS. How can I change the interface so I can make the WSDL available through HTTPS? There are some configuration files? Thanks for your time. Best Regards, -- David Campos Universidade de Aveiro www.davidcampos.pt.vu __________ Information from ESET NOD32 Antivirus, version of virus signature database 4547 (20091027) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4551 (20091028) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4551 (20091028) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _______________________________________________ Carbon-dev mailing list Carbon-dev@... https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev |
|
|
Re: WSAS Endpoint IPOn Wed, Oct 28, 2009 at 2:07 PM, David Campos <david.campos@...> wrote: Hello Everyone, You need to uncomment the commented out HostName entry in the carbon.xml file.
WSDLs are available on the HTTPS port. Try; https://localhost:9443/services/HelloService?wsdl
-- -- Afkham Azeez azeez@... WSO2 Inc. http://wso2.com Blog: http://afkham.org _______________________________________________ Carbon-dev mailing list Carbon-dev@... https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev |
|
|
Re: WSAS Endpoint IPThanks Afkham,
but I want to make the link available through the WSAS interface. When I click on the link to see the WSDL file, it drives me to the HTTP address. How can I change this to the HTTPS port? Best Regards, David Campos Afkham Azeez wrote: > > > On Wed, Oct 28, 2009 at 2:07 PM, David Campos <david.campos@... > <mailto:david.campos@...>> wrote: > > Hello Everyone, > I'm changing my WSAS to production server, but I'm getting several > problems. > > First, I think that is important to tell you that I have WSAS running > inside Tomcat 6. > I have changed the Server URL on carbon.xml, but the Endpoint on the > WSDL files is with the local IP. How can I change this? I want the > address to come with the domain name. > > > You need to uncomment the commented out HostName entry in the > carbon.xml file. > > > The other problem is quite different. By default, through the WSAS > interface, all the WSDL files are available using HTTP, but I need to > change it to HTTPS. How can I change the interface so I can make the > WSDL available through HTTPS? There are some configuration files? > > > WSDLs are available on the HTTPS port. Try; > https://localhost:9443/services/HelloService?wsdl > > > Thanks for your time. > Best Regards, > > -- > David Campos > Universidade de Aveiro > www.davidcampos.pt.vu <http://www.davidcampos.pt.vu> > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4547 (20091027) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4551 (20091028) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4551 (20091028) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@... <mailto:Carbon-dev@...> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > -- > Afkham Azeez > azeez@... <mailto:azeez@...> > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > ------------------------------------------------------------------------ > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@... > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- David Campos Universidade de Aveiro www.davidcampos.pt.vu __________ Information from ESET NOD32 Antivirus, version of virus signature database 4551 (20091028) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _______________________________________________ Carbon-dev mailing list Carbon-dev@... https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev |
|
|
Re: WSAS Endpoint IPSorry, you cannot change that at the moment. The thinking behind making WSDLs available via HTTP was to make it easy for clients (Java/.Net), to make it easy to get the WSDL and generate code. It becomes a bit more difficult to deal with HTTPS using code.
However, we can add this simple enhancement for a future release. Before generating the WSDL URL, we simply have to check whether the HTTP/S transports are available in the server. However, if both are available, priority will be given for the HTTP URL.
Azeez
On Wed, Oct 28, 2009 at 4:52 PM, David Campos <david.campos@...> wrote: Thanks Afkham, -- -- Afkham Azeez azeez@... WSO2 Inc. http://wso2.com Blog: http://afkham.org _______________________________________________ Carbon-dev mailing list Carbon-dev@... https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev |
| Free embeddable forum powered by Nabble | Forum Help |