Inbound transport options
There are number of options, such as network and security settings, that apply when configuring messaging engines that receive messages.
The configuration of network transport for service integration is managed through the transport channel service. You can use this service to add, remove, or modify protocols that can be used to establish connections to an application server over a network.
- TCP
- Secure Sockets Layer (SSL) over a TCP network.
- Tunneling through Hyper Text Transfer Protocol (HTTP) connections.
- Tunneling through HTTPS (secure HTTP) connections.
You can also configure one of two different types of transport chain to be used by IBM MQ links and IBM MQ client links. These transport chains support:
- TCP
- Secure Sockets Layer (SSL) over a TCP network.
IBM MQ queue manager sender channels and WebSphere® Application Server applications that use the IBM MQ messaging provider can communicate with a messaging engine by using either of these transport chain types.
- InboundBasicMessaging
- Allows communication by using the TCP protocol. The default port used by this chain for the first server on the node is 7276. Check the selected port is not already used, for example if you are creating a second server on a particular node. 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
- 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. Check the selected port is not already used, for example if you are creating a second server on a particular node. 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
- Supports IBM MQ queue manager sender channels and applications by using the IBM MQ messaging provider connecting over a TCP network. The default port used by this chain is 5558, this can be automatically adjusted to avoid conflicts.
- InboundSecureMQLink
- Enables IBM MQ queue manager sender channels and applications by using the IBM MQ messaging provider to establish SSL based encrypted connections over a TCP network. The default port used by this chain is 5578, this is automatically adjusted to avoid conflicts.
- soReuseAddr
- Allows the WebSphere Application Server administrator to control bind behavior. When the WebSphere Application Server is restarted, if the inbound TCP channels have problems trying to bind the listening socket, errors are printed into the SystemOut file until either the bind is successful or the number of allowed bind attempts has been passed. This custom property helps to avoid repeated error messages during the bind process.
By default all of these transport chains are configured to use the SIBFAPInboundThreadPool thread pool to handle the data they receive. No reason has been identified for it being necessary to change the minimum or maximum size of this thread pool.
Inbound channel chains that are used for communicating with messaging engines are usually started when the application server that hosts them is started. This can occur even if the application server does not host any active messaging engines. When an inbound chain starts, it binds to the TCP port that it has been assigned and accepts network connections. The following table describes the circumstances under which the inbound chains relating to messaging function are started:
Messaging chains | IBM MQ interoperation chains | |
---|---|---|
SIB service disabled for server | Not started | Not started |
SIB service enabled for server and no IBM MQ links or IBM MQ client links resources defined | Started | Not started |
SIB service enabled and IBM MQ links or IBM MQ client links resources defined | Started | Started |
For more information about enabling or disabling the SIB service, see SIB Service Detail Form.
For more information about defining IBM MQ related resources, see, for example, IBM MQ 鏈結傳送端通道 [設定].
Note that there is no affinity between a particular inbound channel chain and a messaging engine. Any messaging engine active on a server can be contacted by any inbound channel chain that is running. This has important implications when attempting to secure network communications: communication with the messaging engines that are active in an application server is only as secure as the least secure messaging chain active on the server within the same category, that is, a messaging chain or MQ interop chain.
- The 跨引擎傳輸鏈 field in the 匯流排 [設定]. This specifies the chain used when establishing connections between nodes in the same cell.
- The 目標入埠傳輸鏈 field in the Default messaging provider unified connection factory [設定]. This specifies the transport chain name to use when establishing a network connection for use by a JMS application when connecting to a remote messaging engine.