An endpoint listener is the point (address) at which messages for
an inbound service are received. The endpoint listeners that are supplied
with WebSphere Application Server support SOAP over HTTP and SOAP over JMS
bindings.
Before you begin
Why and when to perform this task
A request arrives at an endpoint listener. It is passed to an
inbound port (at which point security and JAX-RPC handler lists can be applied)
then sent on to the service destination. Responses follow the same path in
reverse.
To use the administrative console to create a new endpoint listener
configuration, complete the following steps:
Steps for this task
- Start the administrative console.
- In the navigation pane, click one of the paths shown in the table Paths to this panel.
Paths to this panel |
server_name
cluster_name
|
The endpoint
listener collection form is displayed.
- Click New. The endpoint
listener settings form is displayed.
- Type 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
- Type the name by which the endpoint listener is known. 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). For example, for SOAP over HTTP endpoint listener 1
the listener application is soaphttpchannel1.ear and the
endpoint listener name is SOAPHTTPChannel1.
- Description
- Type the (optional) description of the endpoint listener.
- URL root
- Type 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, 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 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
- Type 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 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 IBM 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 zip file as described in Modifying an existing inbound service configuration, then look up the location within the exported WSDL file.
- Click Apply. The general
properties for this item are saved, and the additional properties options
are made available.
- Under the additional properties heading, click Connection
properties. A (currently empty) list of all the
service integration buses that are connected to this endpoint listener is
displayed in a service
integration bus connection properties collection form.
- Click New. The service
integration bus connection properties settings form is displayed.
- Under the general properties heading, choose an available service
integration bus from the selection list. The bus is selected
and the additional properties for the bus are displayed.
Note: Under the additional
properties heading there is a service properties option.
You use this option to configure the set of custom properties that define
the manner in which the endpoint listener connects to this bus. Included in
this set is property name com.ibm.websphere.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.
- Save your changes to the master configuration.
If the processing completes successfully, the list of service integration
buses that are connected to this endpoint listener is updated to include the
new bus, and the list of endpoint listeners is updated to include the new
endpoint listener. Otherwise, an error message is displayed.
You are now ready to configure this endpoint listener for use with
one or more secure buses as described in
Configuring the SIBus Web services to access a secure service integration bus, and to select this endpoint listener for use with an
inbound service as described in
Making an internally-hosted service available as a Web service.