Transport security in service integration bus

By enforcing transport encryption in bus configuration settings, you do not need to configure individual chains on the bus to meet requirements.

Note: The use of permitted transports requires all members of the bus to be at the WebSphere® Application Server Version 6.1 or later version. Configuring using administrative console helps to prevent any errors. However if a bus is configured to use permitted transport and has a previous level bus member, the runtime operations ignore the setting and issue a warning.
The transport security functionality addresses the following issues:
You can enforce transport encryption with a bus configuration setting on a bus with Version 6.1 or later bus members. This setting is independent of the bus security setting, so chains can be locked down without enabling bus security. The use of permitted chains has three settings: When the use of permitted chains is enabled, the bus only allows access to the permitted chains. When the bus is set to be secure, by default you can only have chains that use the SSL channel. If the bus is not set to be secure, the default setting allows access for all chains.

When the use of permitted chains is enforced and a protocol is not specified for inter-bus communications then InboundSecureMessaging is assumed instead of InboundBasicMessaging. This assumption can be avoided by setting the protocol attribute in the bus configuration. If InboundSecureMessaging is not a permitted chain then an error occurs.

To configure transport security for your bus refer to Administering transport chains.




Related concepts
Learning about service integration security
Related tasks
Administering transport chains
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=cjr0490_
File name: cjr0490_.html