Add a transport to the list of permitted transports [設定]

如果要在主控台中檢視這個頁面,請按下列路徑:

服務整合 -> 匯流排 -> security_value -> [其他內容] 允許的傳輸 -> member_name.

「配置」標籤

「配置」標籤顯示這個物件的配置內容。 這些內容會保留下來,即使停止並重新啟動執行時期環境也一樣。請參閱資訊中心作業說明,以取得如何將配置變更套用於執行時期環境的相關資訊。

一般內容

傳輸鏈名稱

You can manage inbound chains through the administrative console by selecting either 伺服器 -> 伺服器類型 -> WebSphere Application Server -> server_name -> [伺服器傳訊] 傳訊引擎入埠傳輸 or 伺服器 -> 伺服器類型 -> WebSphere Application Server -> server_name -> [伺服器傳訊] IBM MQ 鏈結入埠傳輸. You can also use these administrative console panels to define new transport chains from a set of templates.

The outbound chains that an application server uses for bootstrap operations are defined when the server is defined. They can be altered, or new bootstrap chains can be defined, by using the wsadmin tool.

Information Value
必要
資料類型 下拉清單
範圍
InboundBasicMessaging
This transport chain allows communication through the TCP protocol. The default port used by this chain for the first server on the node is 7276. You should verify that the selected port is not already used, for example if you are configuring a second server with the same name as the first server. Messaging engines hosted in other application servers and JMS applications running in a client container can communicate with the messaging engines of the server by using this transport chain.
InboundSecureMessaging
This transport chain provides secure communication by using the secure sockets layer (SSL) based encryption protocol over a TCP network. The default port used by this chain for the first server on the node is 7286. You should verify that the selected port is not already used, for example if you are configuring a second server with the same name as the first server. The SSL configuration information for this chain is based on the default SSL repertoire for the application server. Messaging engines hosted in other application servers and JMS applications running in the client container can communicate using this transport chain.
InboundBasicMQLink
This transport chain supports IBM MQ queue manager sender channels and applications by using the IBM MQ JMS provider connecting over a TCP network. The default port used by this chain is 5558, although this can be automatically adjusted to avoid conflicts.
InboundSecureMQLink
This transport chain enables IBM MQ queue manager sender channels and applications by using the IBM MQ JMS provider to establish SSL based encrypted connections over a TCP network. The default port used by this chain is 5578, although this is automatically adjusted to avoid conflicts.
範圍 (continued)
BootstrapBasicMessaging
This transport chain is used to establish bootstrap connections to inbound chains configured for TCP-only connections to an application server, such as the InboundBasicMessaging chain.
BootstrapSecureMessaging
This transport chain is used to establish secure connections by using secure sockets layer (SSL) based encryption. The SSL configuration used is taken from the default SSL repertoire when used in an application server environment or from a configuration file when used by the client container. This chain can be used for establishing bootstrap connections to inbound chains that are configured to use SSL, for example, the InboundSecureMessaging chain. Success in establishing such a connection depends on a compatible set of SSL credentials being associated with both this bootstrap outbound chain and also with the inbound chain to which the connection is being made.
BootstrapTunneledMessaging
This transport chain is used to establish bootstrapping connections that are tunneled through HTTP. This transport chain tunnels JFAP and uses HTTP wrappers. Before you can use this bootstrap transport chain, you must define a corresponding server transport chain on the bootstrap server. (See 伺服器 -> 伺服器類型 -> WebSphere Application Server -> server_name -> [伺服器傳訊] 傳訊引擎入埠傳輸.)
BootstrapTunneledSecureMessaging
This transport chain tunnels JFAP and uses HTTP wrappers. Used to establish bootstrapping connections that are tunneled through secure HTTP (HTTPS). Like the BootstrapSecureMessaging outbound chain, this chain also derives its SSL configuration from the default SSL repertoire when used in an application server or from a configuration file when used in the client container.
範圍 (continued)
OutboundBasicMQLink
This transport chain is used to establish connections with IBM MQ queue manager receiver channels. It is used when communicating with IBM MQ through a WebSphere® MQ link.
OutboundSecureMQLink
This transport chain is used to establish connections with IBM MQ queue manager receiver channels that have been secured by using SSL. It is used when communicating with IBM MQ through a WebSphere MQ link. The SSL configuration used is taken from the default SSL repertoire for the application server being used to contact the queue manager.
OutboundBasicWMQClient
This transport chain is used when communicating with IBM MQ receiver channels. It is used when communicating with IBM MQ through a WebSphere MQ server.
OutboundSecureWMQClient
This transport chain is used when communicating with IBM MQ receiver channels that have been secured by using SSL. It is used when communicating with IBM MQ through a WebSphere MQ server.

指出主題類型的圖示 參照主題



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