Creating a broker
==================
You can create brokers on every platform that is supported by WebSphere® Message Broker. The broker runs as a 64-bit application on all platforms except Linux® on x86 Start of change and Windows® on x86End of change.
Before you start:
Complete the following tasks:
* Ensure that your user ID has the correct authorizations to perform the task. Refer to Security requirements for administrative tasks.
* On distributed systems, you must set up your command-line environment before creating a broker, by running the product profile or console; refer to Setting up a command environment.
* On z/OS, you must create and start the queue manager for this broker before you create the component.
Create a broker by using the command line on the computer on which you have installed the broker component. On Windows and Linux on x86, you can alternatively use the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer to complete this task.
* You must give the broker a name that is unique on the local computer.
* Broker names are case sensitive on all supported platforms, except Windows.
* You must associate each broker with its own dedicated WebSphere MQ queue manager.
* Brokers can access only local queue managers, so you cannot create a broker on a queue manager that is on a remote system.
The mode in which your broker is working, can affect the number of execution groups and message flows that you can deploy, and the types of node that you can use. See Restrictions that apply in each operation mode.
To create a broker, follow the link for the appropriate platform. Alternatively, follow the link to create a broker using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer.
* Linux and UNIX
* Windows
* z/OS
* Creating a broker using the WebSphere Message Broker Explorer
=======================================================================
Creating a broker on Linux and UNIX systems
=============================================
On Linux® and UNIX systems, create brokers on the command line; on Linux on x86, you can also create brokers in the WebSphere Message Broker Toolkit.
Before you start:
* If you want to configure the broker as a WebSphere MQ trusted application, see Using WebSphere MQ trusted applications.
* Read Considering security for a broker.
* Check which operation mode you are licensed to use. If you do not set a mode, the automatic default is enterprise mode; see Operation modes.
When you create a broker, the command creates the specified queue manager if it does not exist.
To create a broker:
1. Ensure that you are logged in using a user ID that has authority to run the mqsicreatebroker command.
2. Run the mqsiprofile script to set up the command environment for the broker:
. install_dir/bin/mqsiprofile
You must run this script before you can run the WebSphere Message Broker commands.
For more information, see Setting up a command environment.
3. Use the mqsicreatebroker command to create the broker.
For example, if you want to create a broker called MB7BROKER on a queue manager called MB7QMGR, enter the following command:
mqsicreatebroker
MB7BROKER -q
MB7QMGR
4. To enable function that becomes available in WebSphere Message Broker fix packs, use the -f parameter on the mqsichangebroker command. For more information, see mqsichangebroker command.
You have created a broker.
Next: Complete the following tasks:
1. Start the broker by using the mqsistart command.
2. Connect to the broker from the WebSphere Message Broker Toolkit, the WebSphere Message Broker Explorer, or a CMP API application.
When you have completed these tasks, you can create the resources that you want to associate with the broker; for example message flows. You can create and work with resources by using either the WebSphere Message Broker Toolkit or the CMP API.
==================
You can create brokers on every platform that is supported by WebSphere® Message Broker. The broker runs as a 64-bit application on all platforms except Linux® on x86 Start of change and Windows® on x86End of change.
Before you start:
Complete the following tasks:
* Ensure that your user ID has the correct authorizations to perform the task. Refer to Security requirements for administrative tasks.
* On distributed systems, you must set up your command-line environment before creating a broker, by running the product profile or console; refer to Setting up a command environment.
* On z/OS, you must create and start the queue manager for this broker before you create the component.
Create a broker by using the command line on the computer on which you have installed the broker component. On Windows and Linux on x86, you can alternatively use the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer to complete this task.
* You must give the broker a name that is unique on the local computer.
* Broker names are case sensitive on all supported platforms, except Windows.
* You must associate each broker with its own dedicated WebSphere MQ queue manager.
* Brokers can access only local queue managers, so you cannot create a broker on a queue manager that is on a remote system.
The mode in which your broker is working, can affect the number of execution groups and message flows that you can deploy, and the types of node that you can use. See Restrictions that apply in each operation mode.
To create a broker, follow the link for the appropriate platform. Alternatively, follow the link to create a broker using the WebSphere Message Broker Toolkit or WebSphere Message Broker Explorer.
* Linux and UNIX
* Windows
* z/OS
* Creating a broker using the WebSphere Message Broker Explorer
=======================================================================
Creating a broker on Linux and UNIX systems
=============================================
On Linux® and UNIX systems, create brokers on the command line; on Linux on x86, you can also create brokers in the WebSphere Message Broker Toolkit.
Before you start:
* If you want to configure the broker as a WebSphere MQ trusted application, see Using WebSphere MQ trusted applications.
* Read Considering security for a broker.
* Check which operation mode you are licensed to use. If you do not set a mode, the automatic default is enterprise mode; see Operation modes.
When you create a broker, the command creates the specified queue manager if it does not exist.
To create a broker:
1. Ensure that you are logged in using a user ID that has authority to run the mqsicreatebroker command.
2. Run the mqsiprofile script to set up the command environment for the broker:
. install_dir/bin/mqsiprofile
You must run this script before you can run the WebSphere Message Broker commands.
For more information, see Setting up a command environment.
3. Use the mqsicreatebroker command to create the broker.
For example, if you want to create a broker called MB7BROKER on a queue manager called MB7QMGR, enter the following command:
mqsicreatebroker
MB7BROKER -q
MB7QMGR
4. To enable function that becomes available in WebSphere Message Broker fix packs, use the -f parameter on the mqsichangebroker command. For more information, see mqsichangebroker command.
You have created a broker.
Next: Complete the following tasks:
1. Start the broker by using the mqsistart command.
2. Connect to the broker from the WebSphere Message Broker Toolkit, the WebSphere Message Broker Explorer, or a CMP API application.
When you have completed these tasks, you can create the resources that you want to associate with the broker; for example message flows. You can create and work with resources by using either the WebSphere Message Broker Toolkit or the CMP API.
Comments
Post a Comment