3-16 Getting Started With JAX-RPC Web Services for Oracle WebLogic Server
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 not a callback service and can be invoked using JMS Transport
■
Section 3.11.3, Web Service is a callback service
■
Section 3.11.4, 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.
See Configure HTTP Settings for a Cluster in the Oracle Fusion Middleware 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 the Oracle Fusion Middleware 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 not a callback service and can be invoked using JMS Transport
1.
If the Web Service is deployed to a cluster and the Cluster Address is set, then WebLogic Server uses this value in the server address of the dynamic WSDL.
See Configure Clusters in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.
2.
If the cluster address is not set, or the Web Service is deployed to a standalone server, and the Listen Address of the server to which the Web Service is
deployed is set, then WebLogic Server uses this value in the server address.
See Configure Listen Addresses in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.
3.11.3 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 the Oracle Fusion Middleware 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
Developing WebLogic Web Services 3-17
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 the Oracle Fusion Middleware 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 the Oracle Fusion Middleware 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 the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.
3.11.4 Web Service is invoked using a proxy server
