WebSphere messager Broker Installation configuration

Preparatory work

MB run depends on MQ, so install the MQ,MQ installation process slightly, and later assume that you already have the basics about MQ, such as queue managers, queues, channels, and so on.

After installing MQ , create a Queue Manager (QM) named TESTQM (MQ objects are case-sensitive, in order to avoid unnecessary trouble, here the uniform uppercase, underlined), this queue manager is the basis of the MB run, When you create a Configuration Manager, agent, and execution group with a MB script, you specify the QM name

then create the runtime database, named TestDB, with the MB with Derby, you can also choose DB2, note that the database here refers to the MB itself to run the required database, currently 6.1 version can only use Derby or DB2. The method can be created using the MB script command: Mqsicreatedb, or it can be created using the script command or graphical interface of the corresponding database itself.

about the MB database:

Configuration Manager can only be used in Derby, and the proxy may use a variety of databases, but different database creation commands are different (including the differences on different platforms, specific reference to the Red book); The proxy database can be shared, and Configuration Manager can share a derby database with an agent When you create a database using Mqsicreatedb, if you have installed DB2, a DB2 database is created by default, or Derby

The above is to create a run time environment for the MB run, and then start creating the MB instance

first of all, of course, to install the MB , the process is very simple, omit the table. When the installation is complete, there is a command console in the Start menu, such as:

Click on it, into the MB of a command console environment, in fact, and the normal Windows command console is no different, mainly because it helps you set up the relevant environment variables, you can directly enter the MB command script.

As mentioned earlier, the MB Configuration Manager is used to uniformly manage the individual runtime components of the MB, so first create a configuration Manager

Mqsicreateconfigmgr –i user–a PASSWORD–QTESTQM

Specify user name, password and queue Manager, user name password is entered when you log on to the local machine, must have sufficient permissions (specific permissions are not clear, I directly with the administrator account, in-depth discussion please refer to MB of Red Book)

you will find that the name of the database is not specified, because Configuration Manager automatically creates a new derby database when it is created, and can only be used with the Derby database, the user cannot change

The name of Configuration Manager is not specified, and a default name is created under Windows: CONFIGMGR

Then create the agent, named Testbroker

Mqsicreatebrokertestbroker –iuser–a password–q testqm–n TESTDB

most are the same as creating Configuration Manager, just one more option for specifying the database, again reminding, must be Derby or DB2, two options.

Finally, use "Mqsistart component Name" To start Configuration Manager and Proxy

Configure MB Toolkit

WMBT There is no special requirement for the installation itself, it is not verbose here.

the next key is to connect to the Configuration Manager that you just created in WMBT, which acts as if you were to configure an instance of the application server in eclipse to deploy your Java EE project directly as a graphical interface without having to knock commands yourself.

, new, file, domain connection

In the popup window, fill in the relevant parameters

Just fill in the Queue Manager name, domain name, port, note that the queue Manager is not the Configuration Manager (you did not specify a port when you created Configuration Manager, because it uses the port of the queue manager)

also for Svrconn channel name, SYSTEM. BKR. Config is generated automatically when you create the Configuration Manager, and can be viewed in the MQ Explorer through the display system objects, you can also build a server connection channel, and then enter the name of the channel here

All normal, you can see the lower left corner of the "Domain" window, a new domain connection, with a tree structure to show the proxy you just created (if your agent is based on the Derby database, if based on DB2, you need to explicitly add "proxy reference" in the domain connection), now you can right-click Testbroker, and then create an execution group. After you've developed the MB project, you can deploy it by hitting a package and dragging it into the execution group.

WebSphere messager Broker installation configuration