Configuring a service endpoint is necessary to connect Java™ API for XML-Based Web Services (JAX-WS)
and Java API for XML-based RPC (JAX-RPC) web services
clients to any web services among the components being assembled or
to any external web services.
Before you begin
You can develop an HTTP accessible Java API
for XML-based remote procedure call (JAX-RPC) or Java API
for XML Web Services (JAX-WS) web service when you have an existing
JavaBeans object to enable as a web service. For additional information,
see the using HTTP to transport web services requests information.
You
can use either the administrative console or property files to configure
and manage HTTP endpoint URL fragments. To learn about using property
files to set and manage the URL fragments, see the information about
working with web services endpoint URL fragment property files.
This
task describes using the administrative console to configure endpoint
URL information for HTTP bindings.
About this task
You can specify HTTP URL prefixes for web services that
are accessed through HTTP by using the Provide HTTP endpoint URL information
panel in the administrative console. The HTTP URL prefixes provide
location specific information and are used to form complete endpoint
URLs that are included within published WSDL files.
Note: The Provide
HTTP panel in the administrative console displays modules that contain Java API for XML-Based Web Services (JAX-WS)
and Java API for XML-based RPC (JAX-RPC) web services.
You can use the Provide HTTP panel to provide URL information for
both types of web services, however, the panel does not indicate which
type of service that you are working with.
To configure these
prefixes with the administrative console:
Procedure
- Open the administrative console.
- Click Applications > Enterprise Applications > application_instance > Provide
HTTP endpoint URL information.
- Specify the URL prefixes for the web service.
In
this step you specify the protocol (HTTP or HTTPS), as well as the host_name and port_number used
in the endpoint URL. You can select a prefix from a predefined list,
by selecting the default HTTP URL prefix, or you can use a custom
HTTP URL prefix.
- Select Default HTTP URL prefix or Custom
HTTP URL Prefix.
If you select the default HTTP
URL prefix, a list provides you with a choice of endpoint URL prefixes.
The list is a combination of two sets of ports in the module: the
virtual host ports and the application server ports. Use a prefix
from this list if the application server of the web service is accessed
directly. Select a value and also select the check box of the modules
to use the prefix.
If you want to use a custom HTTP URL prefix,
type the value in the field. Select the check box to use in the prefix.
If
you configure a custom HTTP URL prefix, , you must also configure
the custom JVM property, com.ibm.ws.webservices.enableHTTPPrefix
in
the administrative console and set the value to true
.
You must restart the application server after this custom property
has been defined so that this property is used by the system. Setting
this custom JVM property is required so the custom HTTP endpoint prefix
information is correctly displayed in the ?WSDL query that is returned
from the browser and the URL field of the WSDL file that is returned
to the client. If this custom property is not defined with the value
of true
, the custom HTTP URL prefix is not reflected
in the WSDL file that the service returns to the client. To learn
how to configure this custom JVM property, see the documentation on
configuring additional HTTP transport properties using the JVM custom
property panel in the administrative console.
Supported configurations: The com.ibm.ws.webservices.enableHTTPPrefix
custom
property applies to JAX-RPC web services applications only.
- Click Apply.
The URL prefix, whether
default or custom, is copied to the selected module HTTP URL prefix
field.
- Click OK.
The URL information is saved
to your workspace.
Results
You have specified the partial URL information that is used
to form the target endpoint addresses in the WSDL files that are published
using the Publish WSDL files panel.