Example values for endpoint listener configuration

We can configure any number of endpoint listeners with values of our own choosing, including the example values given in this topic.

When we create an endpoint listener configuration, we provide the following configuration details:

Endpoint listener name

The name by which the endpoint listener is known.

URL root

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 used to build the endpoint addresses within WSDL files to direct requesters to this endpoint listener.

WSDL serving HTTP URL root

The root of the web address for the WSDL files of the inbound services 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.

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, we 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 as described in Modifying an existing inbound service configuration, then look up the location within the exported WSDL file.

The rest of this topic gives example configuration details (endpoint listener name, endpoint listener URL root and WSDL serving URL root) for four endpoint listeners that we might want to create:

• SOAP over HTTP endpoint listener 1
• SOAP over HTTP endpoint listener 2
• Synchronous SOAP over Java Message Service (JMS) endpoint listener 1
• Synchronous SOAP over JMS endpoint listener 2

SOAP over HTTP endpoint listener 1

Endpoint listener name

SOAPHTTPChannel1.

URL root

The address at which external clients access the endpoint listener endpoint. 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 this endpoint listener):

http://www.yourcompany.com/wsgwsoaphttp1

However, if we allow external clients to connect direct to the 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 this endpoint listener):

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

WSDL serving HTTP URL root

The root of the HTTP address at which external clients access your endpoint listener application, followed by /sibws. For example:

http://www.yourcompany.com/sibws

or

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

The WSDL serving HTTP URL root is only used internally by other components of WAS (notably the IBM UDDI registry). For all other uses, we access the WSDL file through the endpoint listener endpoint for the inbound service.

SOAP over HTTP endpoint listener 2

Endpoint listener name

SOAPHTTPChannel2.

URL root

The address at which external clients access the endpoint listener endpoint. 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 this endpoint listener):

http://www.yourcompany.com/wsgwsoaphttp2

However, if we allow external clients to connect direct to the 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 this endpoint listener):

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

WSDL serving HTTP URL root

The root of the HTTP address at which external clients access your endpoint listener application, followed by /sibws. For example:

http://www.yourcompany.com/sibws

or

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

The WSDL serving HTTP URL root is only used internally by other components of WAS (notably the IBM UDDI registry). For all other uses, we access the WSDL file through the endpoint listener endpoint for the inbound service.

Synchronous SOAP over Java Message Service (JMS) endpoint listener 1

Endpoint listener name

SOAPJMSChannel1.

URL root

You specify the properties of the synchronous SOAP over JMS endpoint listener 1 endpoint using the following syntax:

jms:/queue_or_topic_indicator?property_name=property_value and so on, separating each property using the "&" character.

For example, if we use the default values for queue destination and queue connection factory when you install the synchronous SOAP over JMS endpoint listeners, then the first part of the end point address is:

jms:/queue?destination=jms/SOAPJMSQueue1&connectionFactory=jms/SOAPJMSFactory1

For each of the synchronous SOAP over JMS endpoint listeners, here is the full list of properties that we can specify in the endpoint address:

WSDL serving HTTP URL root

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 we allow external clients to connect direct to the 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

The WSDL serving HTTP URL root is only used internally by other components of WAS (notably the IBM UDDI registry). For all other uses, we access the WSDL file through the endpoint listener endpoint for the inbound service.

Synchronous SOAP over JMS endpoint listener 2

Endpoint listener name

SOAPJMSChannel2.

URL root

You specify the properties of the synchronous SOAP over JMS endpoint listener 2 endpoint using the following syntax:

jms:/queue_or_topic_indicator?property_name=property_value and so on, separating each property using the "&" character.

For example, if we use the default values for queue destination and queue connection factory when you install the synchronous SOAP over JMS endpoint listeners, then the first part of the end point address is:

jms:/queue?destination=jms/SOAPJMSQueue2&connectionFactory=jms/SOAPJMSFactory2

For the full list of properties that can be specified in the endpoint address for synchronous SOAP over JMS endpoint listener 2, see the list of properties previously detailed for Synchronous SOAP over JMS endpoint listener 1.

WSDL serving HTTP URL root

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 we allow external clients to connect direct to the 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

The WSDL serving HTTP URL root is only used internally by other components of WAS (notably the IBM UDDI registry). For all other uses, we access the WSDL file through the endpoint listener endpoint for the inbound service.