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 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: If
you are using different names or values for any parameter on this command,
you must replace the appropriate values with
your own.
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:
Created a broker called WBRK_BROKER.
Created and started a WebSphere
MQ queue
manager called WBRK_QM.
Created and set up the WebSphere
MQ resources
required by the broker, and defined these on the queue manager. This includes
the default dead letter queue (DLQ) which is automatically enabled by running
the mqsicreatebroker command.
Note: Note that this command does not start the listener
Ensured that all database tables required by the broker have been created
in the database WBRKBKDB.
Now that you have created a physical broker, you are ready to:
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