Modifying an existing endpoint listener configuration

Modify the additional properties for an endpoint listener that has been configured for use with inbound services.

Before you begin

You cannot use this task to modify the general properties of an existing endpoint listener. The reason for this is that, when you create a new endpoint listener, an associated endpoint listener application is automatically installed that uses the same general property values. Therefore if you subsequently change the general properties, you break the link between the configuration and the underlying application. If you have to change the general properties, you must delete and recreate the endpoint listener configuration.

About this task

To list the endpoint listeners, and to view and modify their configuration details, complete the following steps.

Procedure

  1. Start the administrative console.
  2. In the navigation pane, click one of the following paths:
    • Servers -> Server Types -> WebSphere application servers -> server_name -> Endpoint listeners
    • Servers -> Clusters -> WebSphere application server clusters -> cluster_name -> Endpoint listeners
    A list of endpoint listeners is displayed in an endpoint listener collection form.
  3. Click the name of an endpoint listener in the list.
    The current endpoint listener settings for this endpoint listener are displayed.
  4. View the following general properties. If you are modifying an endpoint listener that is supplied with WebSphere® Application Server, you might want to use the values given in Example values for endpoint listener configuration.
    Name
    View the name by which the endpoint listener is known. If this is your own endpoint listener, rather than one that is supplied with WebSphere Application Server, then this name must match the name given in the endpoint listener application that you have installed (that is, the display name of the endpoint module within the endpoint application EAR file).
    DescriptionDescription
    View the (optional) description of the endpoint listener.
    URL root
    View the address at which external clients access the endpoint listener endpoint. The URL root is the context root of the endpoint listener application, and provides the root of the web address that is used to build the endpoint addresses within WSDL files to direct requesters to this endpoint listener.
    If external clients access the endpoint listener through an HTTP server or server cluster, by using default port 80, then specify the HTTP server name and no port number. For example (for SOAP over HTTP endpoint listener 1):

    http://www.yourcompany.com/wsgwsoaphttp1

    However, if you allow external clients to connect direct to your application server (for example because it is a stand-alone server or in a development or test environment) then specify the application server host name and port number. For example (for SOAP over HTTP endpoint listener 1):

    http://your.server.name:9080/wsgwsoaphttp1

    WSDL serving HTTP URL root
    View the root of the web address for the WSDL files of the inbound services that are available at this endpoint listener. This address comprises the root of the HTTP address at which external clients access your endpoint listener application, followed by /sibws.
    If external clients access the endpoint listener through an HTTP server or server cluster, typically by using default port 80, then this URL root includes the HTTP server name and no port number. For example: 
    http://www.yourcompany.com/sibws
    However, if you allow external clients to connect direct to your application server (for example in a development or test environment) then this URL root includes the application server host name and port number. For example:
    http://your.server.name:9080/sibws
    Note: The WSDL serving HTTP URL root is only used internally by other components of WebSphere Application Server (notably the IBM UDDI registry). For all other uses, you access the WSDL file through the endpoint listener endpoint for the inbound service. To get the location details for a given inbound service WSDL file, publish the WSDL file to a compressed file, then look up the location within the exported WSDL file.
  5. Under the additional properties heading, click Connection properties.
    A list of all the service integration buses that are currently connected to this endpoint listener is displayed in a service integration bus connection properties collection form. Add, amend or delete buses in the list of currently-connected buses. To add a new bus, complete the following steps:
    1. Click New.
      The service integration bus connection properties settings form is displayed.
    2. Under the general properties heading, select an available service integration bus from the drop-down list.
      The bus is selected and the additional properties for the bus are displayed.
      Note: Under the connection properties for the bus there are Custom properties. These custom properties are name and value pairs that you can use to set internal system configuration properties. In each pair, the name is a property key and the value is a string value. You use custom properties to define the manner in which the endpoint listener connects to this bus. Included in this set is property name com.ibm.ws.sib.webservices.replyDestination, which defines the reply destination name used by the endpoint listener. Do not modify or remove this property, which is set automatically when the service integration bus is associated with the endpoint listener.
  6. Under the additional properties heading, click Associated application.
    Details for the application that handles the requests for this endpoint listener are displayed in an enterprise application settings form.
  7. Save your changes to the master configuration.

Results

If the processing completes successfully, the list of service integration buses that are connected to this endpoint listener is updated, and the list of endpoint listeners is redisplayed. Otherwise, an error message is displayed.

What to do next

You are now ready to select this endpoint listener for use with an inbound service as described in Making an internally-hosted service available as a web service.