Creating a new endpoint listener configuration

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

For every server or cluster that is to host an endpoint listener, you must install and configure a Service Data Objects (SDO) repository on the stand-alone server, or (for a server or cluster that is part of a managed cell) on the network deployment cell.

If you want to change the default HTTP endpoint listener security role, do so before you configure the SOAP over HTTP endpoint listener.

Before you configure a SOAP over JMS endpoint listener, configure the associated JMS resources.

You can set up separate endpoint listeners for inbound and outbound requests. For more information, see Endpoint listeners and inbound ports: Entry points to the service integration bus.

決定要用哪個方法來配置這些資源。 You can create a new endpoint listener configuration by using the administrative console as described in this task, or by using the createSIBWSEndpointListener command.
Note: 如果您想要建立自己的端點接聽器應用程式的端點接聽器配置,而不用 WebSphere Application Server 隨附的其中一個接聽器的配置,您必須使用 wsadmin 工具。

About this task

Endpoint listeners are a physical endpoint for receiving inbound service requests. An inbound service describes a bus destination as a logical web service. An inbound port associates a (logical) inbound service with an endpoint listener to provide a (physical) endpoint where the service can be invoked. Therefore you must have defined an endpoint listener before you can create an inbound port.

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 configure a new endpoint listener for use with an inbound service is a two-stage process:
  1. Configure the listener for a specific application server or cluster (as described in this task).
  2. Configure an inbound service on the same bus to use the listener (as described in the task Making an internally-hosted service available as a web service).

To use the administrative console to configure an endpoint listener, complete the following steps:

Procedure

  1. Start the administrative console.
  2. In the navigation pane, click one of the following paths:
    • 伺服器 -> 伺服器類型 -> WebSphere Application Server -> server_name -> 端點接聽器
    • 伺服器 -> 叢集 -> WebSphere 應用程式伺服器叢集 -> cluster_name -> 端點接聽器
    The endpoint listeners collection form is displayed.
  3. Click New. The New endpoint listener wizard is displayed.
  4. Use the wizard to create the new endpoint listener configuration by completing the following steps. For more information about the properties that you set with the wizard, see 端點接聽器 [設定]. You might want to use the values given in Example values for endpoint listener configuration.
    1. Select listener name and binding type.
      Endpoint listener name
      Type the name of your choice by which the endpoint listener is known. For example: wsgwsoaphttp; wsgwsoaphttp2; SOAPJMSChannel1; SOAPJMSChannel2.
      Binding type
      Select the type of binding that this endpoint listener supports. For a SOAP over HTTP or SOAP over HTTPS endpoint listener, select SOAP/HTTP or SOAP/HTTPS. For a SOAP over JMS endpoint listener select SOAP/JMS.
    2. Optional: Configure JMS settings.

      This panel is only displayed if you selected SOAP/JMS in the previous panel.

      You can choose to deploy your endpoint listener application to use an activation specification or a listener port. Listener ports are stabilized. For more information, read the article on stabilized features. Wherever possible, you should deploy your endpoint listener application to use an activation specification. You can use only activation specifications with the default messaging provider; you can use either activation specifications or listener ports with the WebSphere MQ messaging provider.

      Select from the drop-down lists the listener port, or the activation specification and queue connection factory that you have previously configured as described in Configuring JMS resources for the synchronous SOAP over JMS endpoint listener.

    3. Configure required URLs. Configure web addresses for the application root and the WSDL serving root. You can either select pre-configured addresses based on the known virtual hosts, or create new values.
      URL 根目錄
      選取或輸入外部用戶端用來存取端點接聽器端點的位址。 URL 根目錄是端點接聽器應用程式的環境定義根目錄,它提供網址根目錄,用來建置 WSDL 檔案內的端點位址,以將要求者引導到這個端點接聽器。
      An HTTP server can be used with a stand-alone application sever. Alternatively, if your endpoint listener is used by external clients to access a cluster providing high availability or workload management, your cluster usually employs a suitably configured HTTP server (or WebSphere proxy server) operating as an IP-sprayer. In either case, 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. 比方說,如果是 SOAP over HTTP 端點接聽器 1:

      http://www.yourcompany.com/wsgwsoaphttp1

      For a stand-alone application server, your endpoint listener is typically configured for clients to connect directly to an individual application server. If your endpoint listener is used by external clients to access a cluster, you can configure the listener so that clients connect directly to an individual application server within the cluster as shown in the following example, but this might restrict the high availability or workload management capabilities of your cluster. 不過,如果您容許外部用戶端直接連接您的應用程式伺服器(例如,因為它是一部獨立式伺服器,或它是在開發或測試環境中),請指定應用程式伺服器名稱和埠號。 比方說,如果是 SOAP over HTTP 端點接聽器 1:

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

      where the port number (specified as 9080 in this example) matches the WC_defaultHost port value for the application server concerned.
      提供 HTTP URL 根目錄的 WSDL
      Type the root of the web address for the WSDL files of the inbound services that are available at this endpoint listener. 這個位址包含外部用戶端用來存取端點接聽器應用程式的 HTTP 位址起始位置,後面跟著 /sibws This represents the URL that is used when publishing the WSDL URL to a UDDI registry. The host and port name you specify for the WSDL serving HTTP URL root typically match those you specify for the URL root.
      如果外部用戶端是透過 HTTP 伺服器或伺服器叢集來存取端點接聽器(通常是藉由使用預設埠 80),這個 URL 根目錄就包括 HTTP 伺服器名稱,但沒有埠號。例如:
      http://www.yourcompany.com/sibws
      不過,如果您容許外部用戶端直接連接您的應用程式伺服器(例如,在開發或測試環境中),這個 URL 起始位置就包括應用程式伺服器主機名稱和埠號。 例如:
      http://your.server.name:9080/sibws
      Note: 服務 HTTP URL 起始位置的 WSDL 只供 WebSphere Application Server 的其他元件在內部使用(尤其是 IBM UDDI 登錄)。 至於所有其他用法,您是透過入埠服務的端點接聽器端點來存取 WSDL 檔。 如果要取得給定的入埠服務 WSDL 檔的位置詳細資料,請依照Modifying an existing inbound service configuration的說明,將 WSDL 檔發佈為壓縮檔,然後在匯出的 WSDL 檔內查閱這個位置。
    4. Select the service integration buses to which the new endpoint listener should be connected. Only buses of which the application server or cluster is a member are available for selection.
  5. Click Finish.

Results

If the processing completes successfully, the list of endpoint listeners is updated to include the new endpoint listener. 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.

指出主題類型的圖示 作業主題



時間戳記圖示 前次更新: July 9, 2016 11:16
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=tjw_epl_new_61x
檔名:tjw_epl_new_61x.html