Follow the steps detailed in this task for
creating a broker on either Linux (zSeries
platform) or Linux (x86 platform).
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 the profile to set up the environment with
the required locale variables:
Check the contents of the sample profile, supplied
in the broker samples directory /opt/mqsi/sample/profiles/profile.lnx,
to ensure it is appropriate for your environment. More details about the variables
that are in the profile are provided in Are the UNIX environment variables set correctly?. If you are running on RedHat Enterprise Linux AS3.0 or later, or
SuSE Linux Enterprise Server (SLES) Version 9 or later, on either Linux for
Intel or Linux for zSeries, you must add the environment variable LD_ASSUME_KERNEL
to the profile before you run it. If you do not do this on affected systems,
any attempt to start a broker will fail with abend BIP7064S. Insert this line
into profile.lnx:
export LD_ASSUME_KERNEL=2.4.19

- Enter the following command to run the profile:
. /opt/mqsi/sample/profiles/profile.lnx
- 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
Business Integration 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 using the workbench (Adding a broker to a broker domain).