MQ 2.1 CONSOLE

Contents

• Introduction
• Features
• Getting Started

Introduction

The jBroker MQ Console is a tool which enables users to administer a live remote jBroker MQ server. The jBroker MQ Console specifically enables administrators to manage the destinations (queues and topics) hosted by any accessible jBroker MQ server. Also, the administrators can manage security for these destinations by setting permissions for users and groups.

The jBroker MQ Console is a J2EE Web Archive application with an html front-end. The application takes advantage of the Apache Struts model-view-controller framework, and uses custom tag libraries. As a consequence, the jBroker MQ Console can be deployed and run on any J2EE application server. This enables users to remotely administer a running jBroker MQ server via a browser.

Features

The functionality provided enables users to:

• Connect to a remote jBroker MQ server
• Create, delete and edit queues
• Create, delete and edit topics
• Create, delete and set passwords for users
• Create and delete groups, and add users to groups
• Create and delete Access Control Lists (ACL). Also, associate principals (users & groups) with an ACL with specific permissions)

Getting Started

The jBroker MQ Console is packaged as a Web Application Archive (WAR) file, which can be deployed into any J2EE Application Server. Below is a brief installation guide for common application servers. Please consult your Application Server documentation for more information about deploying WAR files. The WAR file for the console application is located in the console directory.

Novell eXtend AppServer Install

Perform the following steps to install the WAR file on Novell eXtend Application Server:

1. Start the application server.
2. Add a new webbase (database) to the local application server.
3. From a DOS prompt, change directory to the directory containing the Console WAR file. Then, run SilverCmd to deploy the application WAR file (jbmq_console.war) to the Application Server webbase using the provided eXtend AppServer specific deployment plan (jbmq_console_war_silver_plan.xml). For example:

      SilverCmd DeployWAR localhost:80 mywebbase jbmq_console.war -f jbmq_console_war_silver_plan.xml -o -v 1

4. Run a browser against the URL of the Console WAR application. For example: http://localhost:80/mywebbase/console

Please note that the supplied deployment plans are for Novell eXtend Application Server 4.0. You may need to modify the deployment plans for other version of the server.

Tomcat Install

Perform the following steps to install the WAR file on Tomcat:

1. Copy the Console WAR file (jbmq_console.war) to the Tomcat webapps directory.
2. Start or re-start Tomcat (e.g. using the startup.bat or startup.sh script provided in the Tomcat bin directory).
3. Run a browser against the URL of the Console WAR application. For example: http://localhost:8080/jbmq_console

Note: On Tomcat 3.2.x you need to place the jbroker-mq.jar file in the CLASSPATH available to Tomcat. You also need to place jbroker-rt.jar into the CLASSPATH, unless jBroker ORB is installed as a Java Extension. These steps are not necessary when running Tomcat 4.0+.

Orion^TM Install

Perform the following steps to install the WAR file on Orion:

1. Create an EAR file from the WAR file by packaging application.xml and jbmq_console.war. You can use the build_ear.{sh,bat} file.
2. Copy the Console EAR file (jbmq_console.ear) to the Orion applications directory.
3. Instruct Orion to load the Console application by adding the following line to the server.xml file in the Orion config directory:

      application name="jbmq_console" path="../applications/jbmq_console.ear"/>
     

4. Bind the Console application to the default web site by adding the following line to the default-web-site.xml file in the Orion config directory:

      <web-app application="jbmq_console" name="jbmq_console" root="/console"/>
     

5. Start or re-start Orion using the command line:

      java -jar orion.jar

6. Run a browser against the URL of the Console WAR application. For example: http://localhost/console

Back to top.