Follow the steps detailed in this task for
creating a broker on Linux platforms.
To create a broker:
- Log on using your service user ID. If you use the su command
to switch user you must ensure that you invoke that user's profile.
- Enter su - <user ID> to run a different
user's profile.
- Run '. <install_dir>/bin/mqsiprofile' to
source the mqsiprofile script and set up the environment
for a single targeted runtime. You must do this before you can
run any of the WebSphere Event Broker commands.
- Ensure that the broker database instance profile has been run.
Invoke the SQL profile that was created when the broker database was created.
- Enter the following command to create the broker:
mqsicreatebroker WBRK_BROKER -i wbrkuid -a wbrkpw
-q WBRK_QM -n WBRKBKDB -u dbuid -p dbpw
Note: The service user ID you use on the mqsicreatebroker command
line must be the user ID that you use to invoke the mqsicreatebroker command,
or root.
If you are using different names or values for any parameter
on this command, replace the appropriate values with your own.In the command
above:
- WBRK_BROKER
- Is the broker name.
- wbrkuid
- Is the service user ID that is used to run the broker.
- wbrkpw
- Is the password for the service user ID.
- WBRK_QM
- Is the name of the WebSphere
MQ queue manager
that the broker will use. This queue manager is created if it does not exist.
- WBRKBKDB
- Is the name of the existing broker database, the broker tables will be
created within this database.
- dbuid
- Is the user ID that has read, write and create access permissions for
the database. This is the user ID that will be used to read and update the
broker's persistent store.
- dbpw
- Is the password that is associated with the database user ID, dbuid.
On completion of this task, you have:
Now that you have created a physical broker, you are ready to
complete the next actions:
- Create and start the WebSphere
MQ queue manager
channels that are required to connect WebSphere Event Broker components
(brokers, User Name Servers, and Configuration
Manager).
This allows components in your broker domain that are supported by different
queue managers to exchange messages and communicate effectively. Refer to Connecting components
- Add the broker to the broker domain.