Properties for web services endpoint URL fragments using property files

You can use properties files to work with web services endpoint URL fragments.

The web services endpoint URL fragment is a portion of the endpoint URL that you can specify in each web services module. In a published Web Services Description Language (WSDL) file, the URL fragment is used to create the actual endpoint URL that defines the target endpoint address, which is found in the location attribute of the port soap:address element.

The following property names exist for URL fragments:

ejb

This property is only applicable for Java API for XML-based RPC (JAX-RPC) web services.

Specifies a URL fragment for web services accessed through an Enterprise JavaBeans (EJB) module binding. The URL fragment value entered is a suffix that is appended to the initial part of the URL obtained by examining the deployment information of the web service. The following code snippet is an example of a URL fragment from the deployment information of an EJB:
wsejb:/com.acme.sample.MyStockQuoteHome?jndiName=ejb/MyStockQuoteHome
In this case, by entering the following information in the URL fragment field,
jndiProviderURL=corbaloc:iiop:myhost.mycompany.com:2809
the resulting URL becomes
wsejb:/com.acme.sample.MyStockQuoteHome?jndiName=ejb/MyStockQuoteHome&jndiProviderURL=corbaloc:iiop:myhost.mycompany.com:2809

http

This property is applicable for both Java API for XML-Based Web Services (JAX-WS) and Java API for XML-based RPC (JAX-RPC) web services.

Specifies a URL fragment for web services accessed through an HTTP transport. The URL fragment format is protocol://host_name:port_number, where the protocol is either http or https; for example, http://myHost:9045. The URL fragment is a prefix that is followed by the context-root of the module and the web services url-pattern specified in the published WSDL file; for example, http://myHost:9045/services/myService.

If the web services in a module are accessed directly from the web services application server, use the host name for the application server and one of the ports from the virtual host for the module.

If the web services in a module are accessed through an intermediate node, such as the web services gateway or an IBM® HTTP Server web server, specify the protocol, host, and port_number parameters of the intermediate service. This configuration specifies a custom HTTP URL prefix; therefore, you must also configure the custom JVM property, com.ibm.ws.webservices.enableHTTPPrefix, and set the value to true. Restart the application server for your changes to take effect.

jms

This property is applicable for both Java API for XML-Based Web Services (JAX-WS) and Java API for XML-based RPC (JAX-RPC) web services.

Specifies a URL fragment for web services accessed through a JMS transport. The URL fragment is a prefix to which the targetService property is appended to form a complete JMS URL endpoint. The default value is obtained by examining the deployment information of the installed service; for example: jms:jndi:jms/MyQueue&jndiConnectionFactoryName=jms/MyCF.

You can modify the URL fragment by adding properties; for example:
jms:jndi:jms/MyQueue&jndiConnectionFactoryName=jms/MyCF&priority=5
The URL fragment is then combined with the targetService property to form the complete URL; for example:
jms:jndi:jms/MyQueue&jndiConnectionFactoryName=jms/MyCF&priority=5&targetService=GetQuote

module

This property is applicable for both Java API for XML-Based Web Services (JAX-WS) and Java API for XML-based RPC (JAX-RPC) web services.

Specifies the module name that contains the URL fragments for HTTP, EJB, and JMS protocols.

Avoid trouble Avoid trouble: Ensure that you do not configure multiple URL prefix map sections for the same module. Configuring multiple URL prefix map sections that specify the same module creates ambiguity regarding which updates are being requested. gotcha



Related tasks
Working with web services endpoint URL fragment property files
Configuring endpoint URL information for HTTP bindings
Configuring endpoint URL information for JMS bindings
Configuring endpoint URL information to directly access enterprise beans
Related reference
Provide HTTP endpoint URL information
Provide JMS and EJB endpoint URL information
Reference topic Reference topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 4:16:02 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-dist&topic=rxml_wbs_endptURL_prop
File name: rxml_wbs_endptURL_prop.html