Configuring the Web services access path in the Web services connector

The access path of Web services is usually specified in WSDL files as an endpoint address. You can modify the configuration of the attributes of a Web services connector to change the endpoint address of Web services.

For JAX-WS, the endpoint address that is specified in a WSDL file is consumed at run time; however, for JAX-RPC, the endpoint address is used during compile time. For Web services runtime to use the endpoint address that is specified in a WSDL file, do not specify an endpointAddress attribute in the definition of the Web services connector. As shown in the following example definition of a Web services connector, an endpointAddress attribute is not specified:

< JaxWsConnector id=”PeopleService”
namespaceUri=http://mock.dallas.com/
serviceName="PeopleServicesService"
portName="PeopleServicesPort"
serviceEndpointInterface="com.dallas.mock.PeopleServicesDelegate"
wsdlUrl="/WEB-INF/wsdl/PeopleServicesService.wsdl"/>

To override the endpoint address that is defined in a WSDL file, specify a value for the endpointAddress attribute in the Web services connector definition. As shown in the following example definition of a Web services connector, specifying a value for the endpointAddress attribute invokes another Web services server.

Configuring the Web services access path in the Web services connector

You can specify a relative path for the endpointAddress attribute, which makes it easier to switch between different Web services servers. In the following example definition of a Web services connector, the server1 variable in the endpointAddress attribute delegates a Web services server.

To ensure that the server1 variable is understood at run time, the variable for target Web services server needs to be resolved to a real URL address during run time. You can configure a variable resolver implementation class in the btt.xml file as shown in the following example:

As shown in Variable resolver class hierarchy, a variable resolver interface is provided by UDTT. A default implementation class, DefaultVariableResolver, is provided by UDTT. You can implement the IVariableResolver interface to define the order in which variables are resolved.

The default implementation for a variable resolver uses the following order: Firstly, it is verified whether there is a server1 WAS environment variable. If not, it will check whether the server1 variable named is defined in the btt.xml file. The name of the variable is replaced with its value during run time. If the variable cannot be resolved by the variable resolver, the default endpoint address is used.