Web service is not a callback service and can be invoked using HTTPS Web service is a callback service

Developing WebLogic Web Services 3-23 target Then the URL to view the WSDL of the Web service, assuming the service is running on a host called ariel at the default port number 7001, is: http:ariel:7001complexComplexService?WSDL

3.11 Configuring the Server Address Specified in the Dynamic WSDL

The WSDL of a deployed Web service also called dynamic WSDL includes an address element that assigns an address URI to a particular Web service port. For example, assume that the following WSDL snippet partially describes a deployed WebLogic Web service called ComplexService: definitions name=ComplexServiceDefinitions targetNamespace=http:example.org ... service name=ComplexService port binding=s0:ComplexServiceSoapBinding name=ComplexServicePort s1:address location=http:myhost:7101complexComplexService port service definitions The preceding example shows that the ComplexService Web service includes a port called ComplexServicePort, and this port has an address of http:myhost:7101complexComplexService . WebLogic Server determines the complexComplexService section of this address by examining the contextPath and serviceURI attributes of the jwsc elements, as described in Section 3.10, Browsing to the WSDL of the Web Service. However, the method WebLogic Server uses to determine the protocol and host section of the address http:myhost:7101, in the example is more complicated, as described below. For clarity, this section uses the term server address to refer to the protocol and host section of the address. The server address that WebLogic Server publishes in a dynamic WSDL of a deployed Web service depends on whether the Web service can be invoked using HTTPS or JMS, whether you have configured a proxy server, whether the Web service is deployed to a cluster, or whether the Web service is actually a callback service. The following sections reflect these different configuration options, and provide links to procedural information about changing the configuration to suit your needs. ■ Section 3.11.1, Web service is not a callback service and can be invoked using HTTPS ■ Section 3.11.2, Web service is a callback service ■ Section 3.11.3, Web service is invoked using a proxy server It is assumed in the sections that you use the WebLogic Server Administration Console to configure cluster and standalone servers.

3.11.1 Web service is not a callback service and can be invoked using HTTPS

1. If the Web service is deployed to a cluster, and the cluster Frontend Host, Frontend HTTP Port , and Frontend HTTPS Port are set, then WebLogic Server uses these values in the server address of the dynamic WSDL. 3-24 Getting Started With JAX-WS Web Services for Oracle WebLogic Server See Configure HTTP Settings for a Cluster in Oracle WebLogic Server Administration Console Help. 2. If the preceding cluster values are not set, but the Frontend Host, Frontend HTTP Port , and Frontend HTTPS Port values are set for the individual server to which the Web service is deployed, then WebLogic Server uses these values in the server address. See Configure HTTP Protocol in Oracle WebLogic Server Administration Console Help. 3. If these values are not set for the cluster or individual server, then WebLogic Server uses the server address of the WSDL request in the dynamic WSDL.

3.11.2 Web service is a callback service

1. If the callback service is deployed to a cluster, and the cluster Frontend Host, Frontend HTTP Port , and Frontend HTTPS Port are set, then WebLogic Server uses these values in the server address of the dynamic WSDL. See Configure HTTP Settings for a Cluster in Oracle WebLogic Server Administration Console Help. 2. If the callback service is deployed to either a cluster or a standalone server, and the preceding cluster values are not set, but the Frontend Host, Frontend HTTP Port , and Frontend HTTPS Port values are set for the individual server to which the callback service is deployed, then WebLogic Server uses these values in the server address. See Configure HTTP Protocol in Oracle WebLogic Server Administration Console Help. 3. If the callback service is deployed to a cluster, but none of the preceding values are set, but the Cluster Address is set, then WebLogic Server uses this value in the server address. See Configure Clusters in Oracle WebLogic Server Administration Console Help. 4. If none of the preceding values are set, but the Listen Address of the server to which the callback service is deployed is set, then WebLogic Server uses this value in the server address. See Configure Listen Addresses in Oracle WebLogic Server Administration Console Help.

3.11.3 Web service is invoked using a proxy server