WSDL soap:address location

Having developed/tested my soap services they are almost ready for shipping as a product.
However, in the WSDL the <soap:address location=""> tag is set to my server - as used in development.
So when I deploy this EAR file from JDev (9.0.5.2) this value is fixed, and will not work for customers.
Is there anyway to make this value dynamic on deployment by customers or am I stuck with having to find out in advance customers server/port settings and then creating individual release per customer?
I have tried using a relative url but this doesnt always work for clients trying to connect, e.g.:
<soap:address location="/webservices/booking"/>
Thanks in advance for any assistance.

For now I have written a program, that is run after deployment. This program edits the web.xml and allows customers to specify the server name and port they are using.
Anyone else have any solutions to this?

Similar Messages

The AQ Service Bus showme a bad wsdl ( soap:address location )from internet

Hi,
first of all, excuse my bad english :-)
I've a problem when I tray to get a wsdl file from Internet.
In Aqualogic I've configured a wsdl file with the next content:
<wsdl:service name="EmailValidation">
<wsdl:port binding="tns:EmailValidationSoap" name="EmailValidation">
<soap:address location="http://www.axonaxis.cl:7001/email"/>
</wsdl:port>
</wsdl:service>
This file is reference from a proxy service.
when I try to get the wsdl file from a browser, showme this:
<service name="EmailValidation">
<port binding="s0:EmailValidationSoap" name="EmailValidation">
<s1:address location="http://server2005:7001/email"/>
</port>
</service>
From a browser, put in "location" the server name (of course, if I try to execute the proxy service, the server not found).
Why is doing this? How can I solve this problem?
I don't have much experience in this so try to help me.
Thank you very much (Muchas gracias!)

ARCHIVO HOST!!!!

Change SOAP Address Location in the WSDL

When deploying a BPEL service the SOAP Address location is automatically generated to have the
http://{SERVER}:{PORT} of the SOA server where you are deploying the service but i need to have a different address location.
I basically needs this because we have a load balancer and firewall restrictions for any external third party that want to invoke our service.
So the WSDL URL we give to the third party who want to invoke our service will be
https://loadbalancer/orabpel/default/TestService/1.0/TestService?wsdl
instead of
http://soasever:soaserveport/orabpel/default/TestService/1.0/TestService?wsdl
The loadbalancer will then strip of the https connection and send it as http request to the SOA server.
So the third party is now able to access the WSDL but he is having issues while invoking the service as the SOAP address location is still having our SOA server name
Any ideas?

This can be achieved through dynamic partner linking.
http://download.oracle.com/docs/cd/E19509-01/821-0017/cnfg_bpel-se-dynamic-ptnrlink_c/index.html
HTH
-ND

JMS transport - weblogic changes soap:address location="jms:.. to http

Hi,
Please help me to configure web service to use only jms transport.
I try to create web service that uses JMS transport.
I started from WSDL where I placed two elements:
<soap:binding style="document"
transport="http://www.openuri.org/2002/04/soap/jms" />
and
<soap:address location="jms://host:7041/contextPathName/serviceUriName?URI=queueName" />
Then in web service implementation I placed following annotation:
@WLJmsTransport(contextPath = "contextPathName", serviceUri = "serviceUriName", portName = "portName", queue = "queueName", connectionFactory = "connectionFactoryName")
Deployment is successful but when I look at generated WSDL (Admin console) I see that weblogic has changed <soap:address location="jms:.. to <soap:address location="http....
And when I look at monitoring I see that port is using JMS transport.
When I try to test my service using Admin console Test client I see that the queue is not used (Admin console/monitoring/Messages total is still 0) and service uses (I suppose) http transport.

Hi,
Please change "http://www.openuri.org/2002/04/soap/jms" to http://www.openuri.org/2002/04/soap/jms/ for soap1.1 or http://www.openuri.org/2002/04/soap12/jms/ for soap1.2.
There must be some mismatch between edoc and implementation.
-LJ

Webservices soap address location url update

Hi,
Is there any way to change the soap address location in the wsdl?
I tried by changing the frontendport and host,But I don't have any option for updating the protocol(http/https) option in weblogic.
advance thanks

Thank you very much,
I followed the same document for updation of endpoint,these settings only updating the host and port ,not the frontend access protocol. End points are generated properly if both the proxy and internal app server mapping uses the same protocol.
Weblogic always using the application server protocol instead of proxy protocol.
Example:wsdl accessed from proxy with https and the internal mapping is http.
https://proxy:443/xxx/xxx?wsdl--->http://appserver:7001/xxx/xxx?wsdl--->web servies end point is http://proxy:80/xxx/xxx?wsdl but the expected endpoint is
https://proxy/xxx/xxx?wsdl.
thanks for providing any other advices

Wsdl soap address errors

Hi,I have a question with web service.
I configured my web service in soamanager and it produced wsdl document.
İtu2019s soap address location <soap:addresslocation =" http://kgtest.calik.com:443/sap/bc/srt/rfc/sap/zor/300/zor/zor " />
But this address is wrong.In other words it produced wrong soap address.
True adress is; <soap:addresslocation =" http://kgtest.calik.com:5000/sap/bc/srt/rfc/sap/zor/300/zor/zor " />
I donu2019t know how I can correct and I donu2019t know why it produce wrong address.
I hope you can help me.
Thank you.

Hi,
Can you check the wsdl options. perhaps you are using an alternate port.
regards,
Bert

SOAP Address Location

Is there any way to tell what the SOAP Address Location on our Netweaver is?
I'm being told by the queryview web service WSDL call that it is
http://<server>:<port>/sap/bw/xml/soap/queryview?sap-client=100
I'm not sure if this is correct, because I can't get the queryview webservice to work correctly with adobe flex and that is the URL string it is balking at.
Any help is greatly appreciated!

when you simply call this url from browser you would get the following messages
- <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
- <soap-env:Body>
- <soap-env:Fault>
<faultcode>soap-env:Server</faultcode>
<faultstring xml:lang="en">SOAP processing failure, error id = 112</faultstring>
</soap-env:Fault>
</soap-env:Body>
</soap-env:Envelope>
Regards
Raja
Consider rewarding points to helpful answers and mark it answered once you question is answered.

Disable the soap address location

Hi,
I wonder if it’s possible to disable the soap:address location in the WSDL?
My problem is that I use a proxy (SOAP) between my WebService Client and the WebLogic
WebService.
When I ask the WSDL through my proxy, it’s work well. But the next call, the client
goes directly to the WebLogic and does not use anymore the proxy. I think the
problem comes from the soap:address location.
Thanks for your help.
Charles

Hi Charles,
You could post your own WSDL, see the docs [1] for details, or you could
use a dynamic client without the WSDL; there are a number of examples of
how to do this such as Manoj's [2].
Regards,
Bruce
[1]
http://edocs.bea.com/wls/docs81/webserv/webxml.html#1007638
[2]
http://manojc.com/?sample25
Charles Desmoulins wrote:
>
Hi,
I wonder if it’s possible to disable the soap:address location in the WSDL?
My problem is that I use a proxy (SOAP) between my WebService Client and the WebLogic
WebService.
When I ask the WSDL through my proxy, it’s work well. But the next call, the client
goes directly to the WebLogic and does not use anymore the proxy. I think the
problem comes from the soap:address location.
Thanks for your help.
Charles

More than one "SOAP address location"

Hi Experts,
Is it possible to have more than one"SOAP address" in wsdl file?
In ORACLE they could able to create a wsdl file with two SOAP address (SOAP 1.1 and 1.2). So, they have two bindings and two SOAP addresses in their WSDL.
Same way, can we have two SOAP address to access the service in XI?
Actually, using two different address we can access the same service.
Regards
Sara

Hi,
A wsdl like a normal webservice is possible to have several operations.
like create, delete, update.... whatever..
Right know one service interface in XI has only one Message type.
With 7.1 one service Interface can have several operations.
So you can use the same interface for different requests. (like. create, delete ...)
Right know a work arround is to specifiy a global message type which includes all possible request message and you do a interface determination by payload.
But i miss the point ... what you try to do ... could you describe your task at all?
regards,
robin

Oracle Reports jax-ws webservice on https port shows soap address on http

- there is a Oracle Reports jax-ws webservice
- it is working fine on http port
- but on https port the wsdl show the soap address location still on http . Shouldnt it be https port ?
Is there anything end user / webservice developer can do to fix this. then we can contact Oracle Reports webservices developer with the suggestions
https://host:8890/reports/rwwebservice?wsdl
<soap:address location="http://host:8890/reports/rwwebservice"/> # http
TIA

- there is a Oracle Reports jax-ws webservice
- it is working fine on http port
- but on https port the wsdl show the soap address location still on http . Shouldnt it be https port ?
Is there anything end user / webservice developer can do to fix this. then we can contact Oracle Reports webservices developer with the suggestions
https://host:8890/reports/rwwebservice?wsdl
<soap:address location="http://host:8890/reports/rwwebservice"/> # http
TIA

How to control the location of the SOAP:address element in the WSDL

I have an EJB exposed as webservice in WebLogic 10.3. Further, the EJB has been annotated with the WebService annotation as in:
@WebService(name = "S_CALCULATORname", serviceName = "S_CALCULATORserviceName",
targetNamespace = "http://tempuri.org/SCalculator/")
@Stateless(name = "S_CALCULATOR")
public class S_CALCULATOR_Beanxxxxxx
The location attribute of the SOAP:address element in the WSDL document generated by the Test Client facility is of the form
http://host:port/ejb-java-class-name/service-name-attribute-value as in:
<soap:address location="http://123.4.5.678:1234/S_CALCULATOR_Beanxxxxxx/S_CALCULATORserviceName" />
Is there a way to control the value of the context root portion of the URL, ejb-java-class-name in this case, either using annotations or deployment descriptor files?
thanks in advance for any replies,
octavio

Hi,
While building the WebService Application you can use the following ANT task...
<target name="build-service4">
<jwsc
srcdir="src"
destdir="output/TestEar">
<jws file="examples/webservices/jwsc/TestServiceImpl.java">
<WLHttpTransport contextPath ="TestContext" serviceUri="TestServiceUri" portName="TestServicePortHTTP"/>
</jws>
</jwsc>
</target>
Or if you are developing JAXRPC EJB based WebService in that case you can even define the Context root using *@weblogic.jws.WLHttpTransport* annotation....
@WLHttpTransport(contextPath="simple", serviceUri="SimpleService", portName="SimpleServicePort")
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Feb 4, 2010 10:22 PM

Changing location specified using soap:address

Hi there,
How can i change the webservice host address which is shown in wsdl file (in IE).
This tag is under <service name......
what i know is that the wsdl file is generated automatically then how to change that host address in <host address....
example :
<service name="Service">
<documentation>Interface. Version 2.0</documentation>
- <port name="Service" binding="tns:Service">
<soap:address location="http://mynet.tk.com:11001/webapp/webservices/mpp20" />
</port>
</service>
The question is from where it automatically forms the url like...
<soap:address location="http://mynet.tk.com:11001/webapp/webservices/mpp20" />
I am using bea Weblogic for deployment.
Thanks,

Hi all,
I have found now a bit tricky way to solve this after investigating in jax-ws and tomcat source code...
on external proxy server you have to use apache2 as a reverse proxy with the modules mod_proxy, mod_rewrite and mod_headers activated.
In your configuration for your virtual hosts (below only shown for Port 443) you have to set ProxyPreserveHost to On (to set external hostname in proxied request), further you have to modify request header to set the right port, external used:
for example with following directive "RequestHeader set Host externalhost:443".
HTTPS requests you have to route to internal server on second port 8082, HTTP requests you have to route, as usually, on port 8080, look at the directives ProxyPass and ProxyPassReverse as shown below.
On tomcat server you have to enable second port 8082 with "wrong" settings enabled: scheme="https" and secure="true"
the webservices are now able to show the right scheme, too, external used.
Possible configuration of apache2 virtualhosts:
<IfModule mod_ssl.c>
#NameVirtualHost *
<VirtualHost *:443>
        ServerName externalhost:443
        ServerAdmin webmaster@localhost
        Protocol https
        UseCanonicalName On
        DocumentRoot /var/www/
        ErrorLog /var/log/apache2/error-ssl.log
        SSLEngine On
         # Possible values include: debug, info, notice, warn, error, crit,
         # alert, emerg.
         LogLevel warn
         CustomLog /var/log/apache2/access-ssl.log combined
         ServerSignature On
         <IfModule mod_proxy.c>
            #turning ProxyRequests on and allowing proxying from all may allow
            #spammers to use your proxy to send email.
            ProxyRequests Off
            <Proxy *>
                  AddDefaultCharset off
                 Order deny,allow
                 #Deny from all
                 #Allow from .example.com
                 Allow from all
            </Proxy>
            # Enable/disable the handling of HTTP/1.1 "Via:" headers.
            # ("Full" adds the server version; "Block" removes all outgoing Via: headers)
            # Set to one of: Off | On | Full | Block
            ProxyVia Off
            ProxyErrorOverride Off
            ProxyPreserveHost On
            <IfModule mod_headers.c>
               <Proxy *>
                  RequestHeader set Front-End-Https On
                  RequestHeader set Host externalhost:443
               </Proxy>
            </IfModule>
            ProxyPass                /ws-foo/ http://internalhost:8082/ws-foo/
            ProxyPassReverse /ws-foo/ https://externalhost:443/ws-foo/
         </IfModule>
</VirtualHost>
</IfModule> Configuration of tomcat: <tomcat-base>/conf/server.xml:
    
    <Connector URIEncoding="utf-8" acceptCount="100"
               connectionTimeout="20000"
               disableUploadTimeout="true" enableLookups="false"
               maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150"
               minSpareThreads="25" port="8080" redirectPort="8443"/>
    <Connector URIEncoding="utf-8" acceptCount="100"
               connectionTimeout="20000"
               disableUploadTimeout="true" enableLookups="false"
               maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150"
               minSpareThreads="25" scheme="https" secure="true"
               port="8082" redirectPort="8443"/>Hope, that helps you all - this had cost me a lot of time... ;-)
Regards.

How is wsdl generated? Wrong soap:address...

We're using Apache in front of WLS and when the WSDL is generated for the service (i.e. from http:/URL/Service.jws) is contains a soap:address with port=80 instead of port=443 as it should.
This is a workshop generated jws.
I'm wondering how this soap:address in the generated WSDL is constructed. It must be some combination of wlw-runtime-config.xml, frontend host, etc. So far we haven't been able to find the right combo to make it work.
Thanx,
Max

If the WSDL file is a workshop generated one, then the soap:address port number must be the same as your Apache/WLS development server's port number when the WSDL file was generated. You will need to update it during the production move to point to your production server port.
<service name="MyService">
<port name="MyserviceSoap" binding="s0:MyServiceSoap">
<soap:address location="http://localhost:80/ctx/MyService.jws"/>
</port>
</service>

EndpointURI property is not overriding WSDL address location

Hi all.
We're running into an issue regarding a reference component configured in a composite SOa app:
<reference name="AutenticarUsuarioExternoFSGuev1"
ui:wsdlLocation="AutenticarUsuarioExternoFSGuev1.wsdl">
<interface.wsdl
interface="http://www.claro.com.br/EBS/Claro/v1#wsdl.interface(AutenticarUsuarioExternoFSGuev1PortType)"/>
<binding.ws
port="http://www.claro.com.br/EBS/Claro/v1#wsdl.endpoint(AutenticarUsuarioExternoFSGuev1/AutenticarUsuarioExter
noFSGuev1PortSOA)"
location="AutenticarUsuarioExternoFSGuev1.wsdl"
soapVersion="1.1">
<property name="weblogic.wsee.wsat.transaction.flowOption"
type="xs:string" many="false">WSDLDriven</property>
<property
name="*endpointURI*">http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1</pr
operty>
</binding.ws>
</reference>
As we see above, we have an endpointURI property configured, which according to my experience in 10g version, I
assume it should override any endpoint configuration in the reference's WSDL.
The WSDL of the reference component mentioned above has an adress location property configured inside it:
     <wsdl:service name="AutenticarUsuarioExternoFSGuev1">
          <wsdl:port name="AutenticarUsuarioExternoFSGuev1PortSOA"
binding="tns:AutenticarUsuarioExternoFSGuev1PortTypeSOAP">
               <soap:*address*
location="http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1" />
          </wsdl:port>
     </wsdl:service>
The problem is: When service endpoint defined by the endpointURI property is called and it fails for some
reason, the WSDL address location is used as a second try (kind of failover mechanism).
What I expected: There should not be a failover process here, It´s not supposed to happen. Only the endpoint
defined by the endpointURI property should be used, that is, it should override any other endpoint.
I tried to work around the problem by removing the location property, according to the SOA Suite documentation,
but it continues to use both endpoints.
Any point on this will be appreciated.
Regards.
Denis

Hi all.
We're running into an issue regarding a reference component configured in a composite SOa app:
<reference name="AutenticarUsuarioExternoFSGuev1"
ui:wsdlLocation="AutenticarUsuarioExternoFSGuev1.wsdl">
<interface.wsdl
interface="http://www.claro.com.br/EBS/Claro/v1#wsdl.interface(AutenticarUsuarioExternoFSGuev1PortType)"/>
<binding.ws
port="http://www.claro.com.br/EBS/Claro/v1#wsdl.endpoint(AutenticarUsuarioExternoFSGuev1/AutenticarUsuarioExter
noFSGuev1PortSOA)"
location="AutenticarUsuarioExternoFSGuev1.wsdl"
soapVersion="1.1">
<property name="weblogic.wsee.wsat.transaction.flowOption"
type="xs:string" many="false">WSDLDriven</property>
<property
name="*endpointURI*">http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1</pr
operty>
</binding.ws>
</reference>
As we see above, we have an endpointURI property configured, which according to my experience in 10g version, I
assume it should override any endpoint configuration in the reference's WSDL.
The WSDL of the reference component mentioned above has an adress location property configured inside it:
     <wsdl:service name="AutenticarUsuarioExternoFSGuev1">
          <wsdl:port name="AutenticarUsuarioExternoFSGuev1PortSOA"
binding="tns:AutenticarUsuarioExternoFSGuev1PortTypeSOAP">
               <soap:*address*
location="http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1" />
          </wsdl:port>
     </wsdl:service>
The problem is: When service endpoint defined by the endpointURI property is called and it fails for some
reason, the WSDL address location is used as a second try (kind of failover mechanism).
What I expected: There should not be a failover process here, It´s not supposed to happen. Only the endpoint
defined by the endpointURI property should be used, that is, it should override any other endpoint.
I tried to work around the problem by removing the location property, according to the SOA Suite documentation,
but it continues to use both endpoints.
Any point on this will be appreciated.
Regards.
Denis

Virtual address location in process WSDL

Hi,
now we use following approach:
We refer to default WSDL at http://<server>:<port>/orabpel/<domain>/<process name>/<process name>?wsdl
Where address location is the default revision of the process: http://<server>:<port>/orabpel/<domain>/<process name>/<revision>
Is there any possibility to refer to WSDL with 'virtual address location' that always refers to default revision?
We want that our partner has one WSDL with address location
and we can transparently change process revisions without notifying our partner to clear wsdl caches and refresh address location?
Are there any possibilities?
(we use BPEL 10.1.2.0.0 )
Thank You and Reagrds
Karel

Hi,
To always use the latest revision of a process you need to exclude the <revision> part of the Location url. To dynamically set the url's at runtime you can use the following in a assign activity:
<copy>
<from expression="string(bpws:getVariableData('urlVariable','/ns1:ParameterCollection/ns1:location'))"/>
<to partnerLink="RunUcmJasperReport" bpelx:property="location"/>
</copy>
<copy>
<from expression="string(bpws:getVariableData('urlVariable','/ns1:ParameterCollection/ns1:wsdlLocation'))"/>
<to partnerLink="RunUcmJasperReport" bpelx:property="wsdlRuntimeLocation"/>
</copy>
Make sure you assign both wsdlLocation and Location and that the <from> part explicitly is a string. This works in 10.1.3 but i do not know if it also was available in 10.1.2
Kind Regards,
Andre

WSDL soap:address location

Similar Messages

Maybe you are looking for