WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

Other roles that affect permissions for users and groups are as follows:
► Sender
User/group can send (produce) messages to the destination.
► Receiver
User/group can read (consume) messages from the destination.
► Browser
User/group can read (non-destructive) messages from the destination.
Address the following questions:
► What users or groups, or both, do I need to define or have already been
defined?
► What are the minimum permissions I need to assign to each one?
Secure message transportation
A message engine uses a particular transport chain to connect to a bus and
communicate a message to another messaging engine. The transport chains
have attributes such as security encryption (using SSL or HTTPS, for example)
and the communication protocol used (TCP/IP, for example).
Encryption is obviously more secure, but can have performance impacts. This is
also true for the protocols, although your choice of protocol is usually decided for
you by what you are trying to communicate with. For each bus, you choose the
particular transport chains that have the attributes you need.
Relevant questions to ask when designing secure message transportation
solutions are as follows:
► What types of messages do I need secured?
► Where do I need to use encryption, and to what extent?
► What are the connection requirements (in terms of security) of the party I am
trying to communicate with?
10.5.3 Planning for high availability
An application server only has one messaging engine for each bus of which it is a
member. There is no option for failover. An application server that is clustered will
by default have one active messaging engine. If the server hosting the
messaging engine fails, the messaging engine activates on another server in the
cluster.
352 WebSphere Application Server V7.0: Concepts, Planning, and Design