配置傳輸鏈
傳輸鏈是由一或多種類型的通道所組成,每一種都支援不同類型的 I/O 通訊協定,如:TCP 或 HTTP。網路埠可供傳輸鏈內的所有通道共用。通道組織架構功能會將到達該埠的要求,自動分送到適當的 I/O 通訊協定通道準備處理。
開始之前
確定可供新的傳輸鏈使用的埠。如果您需要設定共用埠,您必須執行下列動作:
- 利用 wsadmin 指令來建立您的傳輸鏈。
- 確定所有共用這個埠的通道都指派了相同的識別加權。
關於這項作業
您需要配置傳輸鏈,以提供網路服務給下列功能:IBM® 服務整合技術的服務整合匯流排元件、Caching Proxy,以及高可用性管理程式的核心群組橋接器服務。
您可以使用管理主控台或 wsadmin 指令,來建立傳輸鏈。如果您使用管理主控台,請完成下列步驟:
程序
- 在管理主控台中,按一下伺服器 > 伺服器類型 > WebSphere 應用程式伺服器 > server_name或伺服器 > 伺服器類型 > WebSphere Proxy 伺服器 > server_name,然後依照所建立的鏈結類型,選取下列選項之一:
若為應用程式伺服器,請在「儲存器設定」區段中,選取下列其中一個選項:
- 按一下 SIP 儲存器設定 > SIP 儲存器傳輸鏈。
- 按一下 Web 儲存器設定 > Web 儲存器傳輸鏈。
按一下儲存器服務 > ORB 服務 > ORB 服務傳輸鏈。
- 在「伺服器傳訊」區段中,按一下傳訊引擎入埠傳輸或 IBM MQ 鏈結入埠傳輸。
對於 Proxy 伺服器,在「HTTP Proxy 伺服器設定」之下,按一下 Proxy 伺服器傳輸,選取 HTTPS_PROXY_CHAIN 或 HTTP_PROXY_CHAIN。之後,再按一下 HTTP Proxy 入埠通道。
- 按一下新建。
這時「建立新的傳輸鏈」精靈會起始設定。在建立傳輸鏈的過程中,會要求您:
- 指定新傳輸鏈的名稱。
- 選取一個傳輸鏈範本。
- 如果有埠可供新的傳輸鏈連結,請選取一埠。如果埠無法使用,或者您想定義新埠,請為該埠指定一個埠名、主機名稱或 IP 位址,以及有效的埠號。
避免困難: 如果您正在配置的傳輸鏈包含 TCP 通道,精靈會顯示已配置的 TCP 通道清單,以及所列出之 TCP 通道未使用的埠清單。您必須選取一個其他 TCP 通道都沒有在使用中的埠。
同樣地,如果您在配置的傳輸鏈包含 UDP 通道,精靈會顯示已配置的 UDP 通道清單,以及這些 UDP 通道未使用的埠清單。您必須選取一個其他 UDP 通道都沒有在使用中的埠。
gotcha
當您按一下完成時,新的傳輸鏈就會加到傳輸鏈畫面上、已定義之傳輸鏈的清單中。
- 按一下傳輸鏈的名稱,以檢視該傳輸鏈包含之傳輸通道所能使用的配置設定。
如果要變更任何這些設定,請完成下列動作:
- 按一下需要變更設定的通道名稱。
- 變更配置設定。
有些設定(例如:埠號)取決於建立傳輸鏈時所指定的內容,且這些設定無法變更。
- 按一下自訂內容來設定系統已定義的任何自訂內容。
- 配置變更之後,請按一下確定。
- 停止再重新啟動應用程式伺服器。
您必須停止再重新啟動應用程式伺服器,變更才會生效。
下一步
更新在伺服器啟動期間會發出呼叫以啟動傳輸之您的任何常式。在伺服器啟動期間,當常式發出呼叫來啟動傳輸時,產品會將呼叫轉換成傳輸通道呼叫。
更新在伺服器啟動期間會發出呼叫以啟動傳輸之您的任何常式。在伺服器啟動期間,當常式發出呼叫來啟動傳輸時,該產品會發出錯誤訊息。

- 按一下伺服器,然後展開伺服器類型。
- 按一下 WebSphere 應用程式伺服器 > server_name。
- 展開 Web 儲存器設定,然後按一下 Web 儲存器傳輸設定 > transport_chain_name。
- 按一下 Web 儲存器入埠通道。
- 在寫入緩衝區大小欄位中,指定 32768,然後按一下確定。
- 按一下儲存。
如果要利用 wsadmin Scripting 來變更值,請參閱使用 Web 儲存器入埠通道內容檔的相關說明文件。
gotcha次主題
傳輸鏈
傳輸鏈代表在應用程式伺服器環境中,供 I/O 作業使用的網路通訊協定堆疊。HTTP transport collection
Use this page to view or manage HTTP transports. Transports provide request queues between web server plug-ins and web containers in which the web modules of applications reside. When you request an application in a web browser, the request is passed to the web server, then along the transport to the web container.HTTP transport settings
Use this page to view and configure an HTTP transport. The name of the page might be that of an SSL setting such as DefaultSSLSettings. This page is not available if you do not have an HTTP transport defined for your system.傳輸鏈集合
請利用這個頁面來檢視或管理傳輸鏈。傳輸鏈可透過傳輸通道或通訊協定堆疊(通常以 Socket 為基礎)來通訊。Transport chain settings
Use this page to view a list of the types of transport channels configured for the selected transport chain. A transport chain consists of one or more types of channels, each of which supports a different type of I/O protocol, such as TCP, HTTP, or DCS.HTTP tunnel transport channel settings
HTTP transport channel settings
Use this page to view and configure an HTTP transport channel. This type of transport channel handles HTTP requests from a remote client.TCP transport channel settings
Use this page to view and configure a TCP transport channels. This type of transport channel handles inbound TCP/IP requests from a remote client.DCS transport channel settings
Use this page to view and configure an DCS transport channels. This type of transport channel handles inbound Distribution and Consistency Services (DCS) messages.ORB service transport channel settings
Use this page to view and configure an Object Request Broker (ORB) Service transport channels. This type of transport channel handles CORBA and RMI/IIOP inbound messages for the ORB Service. It enables clients to make requests and receive responses from servers in a network-distributed environment.SSL inbound channel
Use this page to determine which SSL inbound channel options to specify for the application server.Session Initiation Protocol (SIP) inbound channel settings
Use this page to configure the SIP inbound channel settings.Session Initiation Protocol (SIP) container inbound channel settings
Use this page to configure the SIP container inbound channel settings.User Datagram Protocol (UDP) Inbound channel settings
Use this page to configure the UDP Inbound channel settings.Web container inbound transport channel settings
Use this page to view and configure a web container inbound channel transport. This type of channel transport handles inbound web container requests from a remote client.DataPower appliance manager transport channel settings
Use this page to view and configure a DataPower® appliance manager transport channel. This type of transport channel handles events from managed DataPower appliances.HTTP transport channel custom properties
If you are using an HTTP transport channel, you can add any of the following custom properties to the configuration settings for that channel.HTTP Tunnel transport channel custom properties
If you are using an HTTP Tunnel transport channel, you can add the following custom properties to the configuration settings for that channel.TCP transport channel custom properties
If you are using a TCP transport channel, you can use TCP transport channel custom properties to configure internal TCP transport channel properties.Web container transport chain custom properties
Use this page to set custom properties for a web container transport channel.Configuring inbound HTTP request chunking
Inbound HTTP request chunking is used to eliminate the restriction on messages greater than 10MB. The 10MB restriction is set because the entire message is buffered in the controller before the HTTP request is dispatched to the servant, therefore, the controller may fail with an out of memory condition when multiple large HTTP messages are processed simultaneously. With chunking enabled, the message is broken up into smaller pieces before it is processed by the web container and application. As a result, only one small chunk is buffered in memory at a time in the controller thus greatly reducing the amount of memory consumed by large HTTP messages. Applications do not require changes to enable inbound HTTP chunking.Transport chain problems
Review the following topics if you encounter a transport chain problem.Deleting a transport chain
Transport chains cannot be deleted the same way that HTTP transports can be deleted. Because you cannot have multiple HTTP transports associated with the same port, when you delete an HTTP transport, you effectively delete the associated port and stop all traffic on that port. However, the process is more complicated for a transport chain because multiple transport chains might be associated with the same port and you do not want to disrupt traffic on transport chains that you are not deleting.Disabling ports and their associated transport chains
Transport chains cannot be disabled the same way that HTTP transports can be disabled. Because you cannot have multiple HTTP transports associated with the same port, when you disable an HTTP transport, you effectively disable the associated port and stop all traffic on that port. However, the process is more complicated for a port that has associated transport chains because multiple transport chains might be associated with the same port, and you might not want to disrupt traffic on all of the transport chains at the same time.SIP UDP 傳輸通道自訂內容
您可以將下列自訂內容新增到「階段作業起始通訊協定 (SIP)」UDP 傳輸通道的配置設定中。


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=trun_chain_transport
檔名:trun_chain_transport.html