If you are using messaging security, there are a number of considerations that apply to messaging engines.
When bus security is enabled, you must set the Inter-engine authentication alias property to be used for authentication of messaging engines joining the bus and for secure communication between messaging engines.
You can use secure transport connections (SSL or HTTPS) to ensure confidentiality and integrity of messages in transit between messaging engines. This is achieved by defining an appropriate secure transport chain and then referencing the transport chain name from the Inter-engine transport chain property of the bus. For more information, see Secure transport considerations.
Incoming connections to a messaging engine can be controlled by setting the Inter-engine authentication alias property to prevent unauthorized clients or messaging engines from establishing a connection. Refer to Adding a bus for further information.
Access to the data store for a messaging engine can be secured using a user ID and password. Higher levels of security can be applied to the data store using the features of the underlying database, for example, Cloudscape allows the whole database to be encrypted, DB2 allows specific tables to be encrypted. These features must be managed directly by the appropriate database administrator. Refer also to Securing database access.