New users: use the links in this topic to find out how to plan and configure
a broker domain. You can create a simple broker domain for testing purposes
on your Message Brokers Toolkit machine using the Default
Configuration wizard. When you are ready to create a broker domain
for testing on platforms other than Windows or Linux (x86 platform), or for
production purposes, you must plan your broker domain carefully using the
information provided in the WebSphere Message Broker information
center.
What do I need to know about broker domains?
A broker
domain is one or more brokers that share a common configuration, together
with the single Configuration Manager that controls them. Use the links in
this section to find information that you might find useful before planning
and designing your broker domain.
- What is a broker?
A broker is
a set of execution processes that hosts one or more message flows to route,
transform, and enrich inflight messages. Follow this link to get information
about brokers, and the resources that you need to create and configure your
brokers.
- What is a Configuration Manager?
The Configuration Manager is the interface between the workbench
and an executing set of brokers. It provides brokers with their initial configuration,
and updates them with any subsequent changes. It maintains the broker domain
configuration. The Configuration Manager is supported on
all the broker platforms. Follow this link to get information about the main
functions of the Configuration Manager, and the resources
that you need to create and configure your Configuration Manager.
- What is a User Name Server?
The
User Name Server is an optional runtime component that provides authentication
of users and groups performing publish/subscribe operations. Follow this link
to get information about the User Name Server.
- What is a publish/subscribe topology?
A
publish/subscribe topology consists of the brokers, the Collectives,
and the connections between them, that support publish/subscribe applications
in the broker domain. Follow this link to get an introduction to broker networks
and publish/subscribe topologies.
- What do I need to know about databases?
WebSphere Message Broker uses databases to store internal data
about the broker. You must create and configure the broker database before
you can create any brokers. Follow this link to find out more about broker
databases and how to create connections to them.
What do I need to know about authorization and security?
Each
broker domain must contain one Configuration Manager, which manages the configuration
of the domain, and at least one broker. The number of brokers that you include
in the broker domain depends on several factors, including your performance
requirements and the type of applications in your broker domain. If the broker
domain is for use with publish/subscribe applications, you can include a User
Name Server to manage access to topics. Follow the links in this section to
get information about authorization, access control and security for your
broker domain.
How do I plan a broker domain and configure prerequisites?
Use
the following links to find out how to plan your broker domain. You can also
find out about tasks you must complete before you can configure your broker
domain.
- How do I plan a broker domain?
Follow
this link to find out what you need to consider when you plan your broker
domain.
- How do I set up broker domain security?
Follow
this link for information on how to set up security for your broker domain.
Each link comprises a list of reminders or questions about the security tasks
to consider for your broker configuration. The answers to the questions provide
the security information that you need to configure your WebSphere Message
Broker components, and also give you information about other security controls
that you might want to deploy.
- How do I configure my databases?
WebSphere Message Broker uses databases for two purposes:
- Component databases, which the broker uses to store its internal data.
Each broker must have its own set of tables in the database but multiple brokers
can share the same database.
- User databases, which you use to store your business data that can be
processed by your message flow applications.
You must manually create and configure the broker database or databases
using a supported database manager before you can create your brokers. When
you create your brokers, the tables for each broker are automatically created
in the database. Follow this link to get instructions on how to create and
configure databases for use as broker database, or a user database.
How do I create and configure broker domain components?
A
broker domain must contain at least one broker and the Configuration Manager.
If the broker and Configuration Manager share the same
queue manager, you do not need to create any WebSphere MQ infrastructure to
connect them together. In more complex broker domains, you might create several
brokers (each on their own queue manager), a Configuration Manager,
and WebSphere MQ channels (or a WebSphere MQ cluster) to connect the components
together. You might also create several execution groups on each broker to
manage the message flow applications that you deploy to the broker. If you
are creating a broker domain for publish/subscribe applications, you can optionally
create a User Name Server to manage publisher and subscriber authorities.
To create a broker domain, complete the following tasks in order:
- How do I create a broker?
On Windows
and Linux (x86 platform), you can create brokers in
the Message Broker Toolkit using the Command Assistant
wizard. Alternatively, or on UNIX and z/OS platforms, create the components
from the command line. Create as many brokers as you require.
- How do I create the Configuration Manager?
On
Windows and Linux (x86 platform), you can create the Configuration Manager in the Message Broker Toolkit using
the Command Assistant wizard. Alternatively, or on UNIX and z/OS platforms,
create the components from the command line. Create only one Configuration Manager for
each broker domain.
- Optional: How do I create the User Name Server?
On
Windows and Linux (x86 platform), you can create the
User Name Server in the Message Broker Toolkit using
the Command Assistant wizard. Alternatively, or on UNIX and z/OS platforms,
create the components from the command line. Create only one User Name Server
per broker domain, and only if you want to manage access to publish/subscribe
applications.
- How do I verify that all the components have
been created successfully?
You can use the mqsilist command
to check that your components were created successfully
- How do I connect the components together?.
If
you have created a single broker that shares a queue manager with the Configuration Manager, the broker and Configuration Manager can
communicate without any additional configuration. For components that are
on different queue managers to communicate, however, you must create WebSphere
MQ channels between the queue managers. You can do this by manually creating
all the channels or by defining the queue managers in a cluster. For more
information about queue manager clusters, see the WebSphere MQ documentation.
- How do I start the Configuration Manager?
Follow
this link to get instructions on how to start the Configuration Manager.
- How do I start a broker?
Follow
this link to get instructions on how to start a broker.
- How do I start the User Name Server?
Follow
this link to get instructions on how to start the User Name Server.
- How do I create a domain connection?
You
can configure your broker domain using the Message Broker Toolkit on
Windows and Linux (x86 platform). You can configure and administer
your broker domain components using the Broker Administration perspective in
the Message Broker Toolkit.
- How do I add a broker to my broker domain?
Adding
a broker to the broker topology creates a reference to the broker in the configuration
repository. The physical broker must have been created before you can add
the broker using the Message Broker Toolkit. Follow
this link to find out how to add a broker to your broker domain. When you
add a broker to the broker domain, the default execution group is added to
the broker, ready for message flows and related resources to be deployed to
it.