WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Modifying an existing endpoint listener configuration

Modify the configuration details for an endpoint listener that has been configured for use with inbound services.

Why and when to perform this task

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

Steps for this task

  1. Start the administrative console.
  2. In the navigation pane, click one of the paths shown in the table Paths to this panel.
    Paths to this panel

    Servers > Application servers > [Content Pane] server-name > Endpoint listeners
    Servers > Clusters > [Content Pane] 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. Modify the following general properties. If you are configuring an endpoint listener that is supplied with WebSphere Application Server, the required values are given in Endpoint listener configuration details.
    Name
    Modify the name by which the endpoint listener is known. This name must match the name of the endpoint listener application that you have installed. For example, for SOAP over HTTP endpoint listener 1 the listener application is soaphttpchannel1.ear and the endpoint listener name is SOAPHTTPChannel1.
    Note: When you change an endpoint listener name, the system looks up all objects that refer to it and updates the name.
    Description
    Modify the (optional) description of the endpoint listener.
    URL Root
    Modify the address at which external clients access the endpoint listener endpoint. The URL root is the context root of the endpoint enterprise 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. For example (for SOAP over HTTP endpoint listener 1):
    http://www.yourcompany.com/wsgwsoaphttp1
    WSDL serving HTTP URL root
    Each inbound service is described in a WSDL document. Modify the root of the Web address for the WSDL files of the inbound services that are available at this endpoint listener. The WSDL serving HTTP URL root is used by the HTTP and JMS endpoint listeners, and also by UDDI registries, to retrieve the WSDL for your inbound services. This URL comprises the HTTP address at which external clients access the machine on which your endpoint listener application is installed, followed by /sibws/wsdl. For example:
    http://www.yourcompany.com/sibws/wsdl
  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.
  6. Add, amend or delete buses in the list of currently-connected buses. For more information about connecting an endpoint listener to a service integration bus, see Creating a new endpoint listener configuration.
  7. Apply the changes.
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.
Related concepts
Endpoint listeners and inbound ports - entry points to the service integration bus
Related tasks
Configuring JMS resources for the synchronous SOAP over JMS endpoint listener
Creating a new endpoint listener configuration
Deleting endpoint listener configurations
Related reference
Endpoint listener configuration details

Task topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\tasks\tjw_epl_config.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)