Follow the steps detailed in this task for
creating a Configuration
Manager onLinux platforms.
To create a Configuration
Manager.
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 Message Broker commands.
Log on using your user ID. If you use the su command
to switch user from root, enter su
- <user ID> to run your user profile.
Enter the following command to create the Configuration
Manager:
mqsicreateconfigmgrCMGR01 -i wbrkuid -a wbrkpw -q WBRK_QM
If you are
using different names or values for any parameter on this command, you must replace the appropriate values with your
own.
In the command above:
CMGR01
Is the name of the Configuration
Manager that you are
creating.
wbrkuid
Is the service user ID that is used to run the Configuration
Manager.
wbrkpw
Is the password for the service user ID.
WBRK_QM
Is the name of the WebSphere
MQ queue manager
that will host the Configuration
Manager. This is created
if it does not exist.
On completion of this task, you have:
Created a Configuration
Manager.
Created and started a WebSphere
MQ queue
manager called WBRK_QM.
Created and set up the WebSphere
MQ resources
required by the Configuration
Manager, and defined these
on the queue manager. This includes the default dead-letter queue (DLQ), which
is automatically enabled by running the mqsicreateconfigmgr command.
Set up the authorizations that the Configuration
Manager requires
to access WebSphere
MQ resources.
Now that you have created the Configuration
Manager,
you are ready to:
Create and start the WebSphere
MQ queue manager
channels that are required to connect WebSphere Message 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.