WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Planning a broker environment

When you start to plan your broker environment, you must first consider your resource naming conventions and the design of the WebSphere® MQ infrastructure.

You might also want to consider how your configuration might affect performance of your brokers and message flows. See Performance planning for information about these aspects.

You must also consider how to configure your brokers:
  1. Performance: What is the required message throughput? See Optimizing message flow throughput.

    What is the size of the messages that are being processed? Larger messages take longer to process. A few brokers handling many messages might degrade overall performance. See Performance planning.

  2. Operation mode: The mode in which your broker is working can affect the number of execution groups and message flows that you can deploy, and the types of node that you can use. See Restrictions that apply in each operation mode. (This option does not apply to brokers that you create on z/OS® systems.)
  3. Application independence: Do you need to isolate applications from each other? You might want to separate applications that serve different functions; for example, personnel and finance.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:57


Task topicTask topic | Version 8.0.0.7 | ae03250_