Introduction
Administration of Brokers and Broker resources can be done by accessing through an HTTP client, which is an alternative to WebSphere Message Broker Explorer. Web User Interface is enabled by default for all the Brokers that are created in WebSphere Message Broker V 8.0.0.1. And the default port to access GUI is 44
-
Configuring Web User Interface Server
By using WebSphere
Message Broker Explorer or mqsichangeproperties commands enable Web User Interface to configure properties related to the HTTP or HTTPS port.
Using WebSphere Message Broker Explorer
-
Login to WebSphere Message Broker Explorer and navigate to IBM WebSphere MQ then click on Brokers, Right click on your broker name and select properties.
-
Select WebAdmin tab.
-
Enable Web User Interface and set the port.
If you are using HTTP, set Enabled to TRUE, set Enabled SSL to FALSE and enters a value for the HTTP port
If you are using HTTPS, set Enabled to TRUE, set Enabled SSL to TRUE and enter a value for the HTTP port.
-
Then click Apply and then click OK
Using mqsichangeproperties
-
If you using HTTP the command to be used is
mqsichangeproperties BrokerName -b webadmin -o HTTPConnector -n port -v portValue
BrokerName: Name of the Broker
portValue: HTTP port value by which we can access the WUI
-
If you using HTTPS the command to be used is
Mqsichangeproperties brokerName -b webadmin -o HTTPSConnector -n port, keystoreFile, keystorePass -v portValue, fileName, password
BrokerName: Name of the Broker
portValue: HTTP port value by which we can access the WUI
fileName: keystore file
password: password for the keystore file
-
To confirm that the properties are set correctly
If you are using HTTP, run the following command
mqsireportproperties brokerName -b webadmin -o HTTPConnector –a
If you are using HTTPS, run the following command:
mqsireportproperties brokerName -b webadmin -o HTTPSConnector -a
-
Enable the web user interface server for the broker:
To enable the web user interface, and to use HTTP as the communication protocol between the broker and the web user interface server, run the following command on a WebSphere Message Broker command line, where brokerName is the name of your broker:
mqsichangeproperties brokerName -b webadmin -o server -n enabled,enableSSL -v true,false
To enable the web user interface, and to use HTTPS as the protocol for communication between the broker and the web user interface server, run the following command:
mqsichangeproperties brokerName -b webadmin -o server -n enabled,enableSSL -v true,true
-
Confirm that the web user interface component is enabled by running the mqsireportproperties command
mqsireportproperties brokerName -b webadmin -o server -a
-
Restart the broker to make changes effect.
To start and stop a broker, you can use the mqsistart and mqsistop commands from the command line. Alternatively, on Windows and Linux, use the WebSphere Message Broker Toolkit or the WebSphere Message Broker Explorer to start and stop brokers
Accessing Web User Interface
-
By using the url http://localhost:4414 we can able to access the application Web user interface console.
Role based security
By using Role-based access we can control the broker and broker resources.
-
Each web user account associated with particular rule which contains a set of security permissions.
-
The permission is checked to determine a web user’s authorization to perform tasks in web user interface.
-
Broker administrator can control the access that web user have to broker resource by assigning each user to required role.
-
Administrator can grant same authorization to multiple users by assigning them to same role, but each user can be assigned to only one role.