Download Latest Version mqweb-0.0.7.tar.gz (247.1 kB)
Email in envelope

Get an email when there's a new version of MQweb

Home / 0.0.7
Name Modified Size InfoDownloads / Week
Parent folder
readme.txt 2012-11-13 2.1 kB
0
mqweb-0.0.7.tar.gz 2012-11-13 247.1 kB
0
Totals: 2 Items   249.1 kB 0 
Building MQWeb
--------------

1. Get Poco 1.5 from http://pocoproject.com.
   Build and install it
2. Get premake4 from http://industriousone.com/premake and install it
3. Unzip the mqweb archive and go to the root directory of mqweb
4. Run premake4
5. Build mqweb with the target you specified in step 4.
6. Create mqweb.properties in the directory that contains the mqweb executable
   and change the following properties:
   
    mq.web.static=<full path to folder where the mqweb static files are stored>
    mq.web.templates=<full path to folder where the mqweb templates are stored>
    mq.web.port=<port number>

    When mq.web.port is omitted, 8081 will be used.

Running MQWeb
-------------

1. By default mqweb connects in bindings mode. This can be changed by 
   setting the mq.web.mode property to 'client' and to configure Websphere MQ 
   client or mqweb. 
   
   a) Configure Websphere MQ Client: 
   To connect to a queuemanager use a client channel definition table and 
   set the environment variables MQCHLLIB and MQCHLTAB, or use mqclient.ini 
   and set ChannelDefinitionFile and ChannelDefinitionDirectory (Note: on 
   Windows the environment variable MQCLNTCF must point to mqclient.ini). 
   When only one queuemanager is used MQSERVER can be used.
   
   b) Configure mqweb:
   Add mq.web.qmgr properties as follows:
    mq.web.qmgr.<qmgrName>.connection=<host>(<port>)
    mq.web.qmgr.<qmgrName>.channel=<channelName>
   Where <qmgrName> is the name of the queuemanager, <host> the server where
   the queuemanager is running. <port> is the port of the listener and
   <channelName> is the name of the server connection channel.
   
2. When no name is passed in the URL, mqweb will try to connect to the default
   queuemanager. In bindings mode this is done by connecting with a blank
   queuemanager name. In client mode this can be configured by setting
   mq.web.defaultQmgr property. When this property doesn't exist, mqweb will 
   try to connect with "*" and hopes that a client channel definition table 
   is configured.
Source: readme.txt, updated 2012-11-13