+

Search Tips   |   Advanced Search

Set endpoint URL information for HTTP bindings


Set a service endpoint is necessary to connect JAX-WS and JAX-RPC Web services clients to any Web services among the components being assembled or to any external Web services.

We 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 already have a Java Bean object to enable as a Web service. For additional information, see the using HTTP to transport Web services requests documentation.

We can specify HTTP URL prefixes for Web services that are accessed through HTTP by using the Provide HTTP endpoint URL information panel in the admin console. The HTTP URL prefixes provide location specific information and are used to form complete endpoint URLs that are included within published WSDL files.

The Provide HTTP panel in the admin console displays modules that contain JAX-WS and JAX-RPC Web services. 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 we are working with. To configure these prefixes with the admin console:

 

  1. Open the admin console.

  2. Click Applications > Enterprise Applications > application_instance > Provide HTTP endpoint URL information.

  3. Specify the URL prefixes for the Web service.

    In this step specify the protocol (HTTP or HTTPS), as well as the host_name and port_number used in the endpoint URL. We can select a prefix from a predefined list, by selecting the default HTTP URL prefix, or we can use a custom HTTP URL prefix.

    1. Select Default HTTP URL prefix or Custom HTTP URL Prefix.

      If we 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 appserver of the Web service is accessed directly. Select a value and also select the check box of the modules to use the prefix.

      To use a custom HTTP URL prefix, type the value in the field. Select the check box to use in the prefix.

      If we configure a custom HTTP URL prefix, , also configure the custom JVM property, com.ibm.ws.webservices.enableHTTPPrefix in the admin console and set the value to true. You must restart the appserver 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 admin console.

    2. Click Apply.

      The URL prefix, whether default or custom, is copied to the selected module HTTP URL prefix field.

    3. Click OK. The URL information is saved to your workspace.

 

Results

we have specified the partial URL information used to form the target endpoint addresses in the WSDL files that are published using the Publish WSDL files panel.

 

Next steps

Set any other URL endpoint information for JMS bindings and direct EJB access. Then publish the WSDL files to make the deployed Web services application available to clients.


Provide HTTP endpoint URL information

 

Related tasks


Use HTTP to transport Web services requests for JAX-RPC applications
Use HTTP to transport Web services requests for JAX-WS applications
Set endpoint URL information for JMS bindings
Set endpoint URL information to directly access enterprise beans
Set additional HTTP transport properties using the JVM custom property panel in the admin console

 

Related


HTTP transport custom properties for Web services applications
Java virtual machine custom properties