MQdev Blog - moving to Messaging on Developerworks!

TODAS AS PUBLICAÇÕES

Welcome to the IBMers' Blog on Messaging

neekrish Visits (3392)

The first post of a Blog - irrespective of the subject in question, is as intriguing and challenging as publishing your first Best-seller. Audience a warm welcome to 'The IBMers' Blog on Messaging ' 'The IBMers' Blog on Messaging ' , is our next entity, post to 'The developerWorks Space on Messaging' . This portmanteau of weblog is dedicated to IBM Messaging products, viz. WebSphere MQ , WebSphere Message Broker , WebSphere MQ Everyplace , & Lotus Expeditor micro broker . Moving further we would have write-ups, work-arounds, discussions,... [More]

Marcações: firstpost

Lotus Expeditor micro broker

neekrish Visits (3807)

If you are wondering how to extend your ESB to the small devices like PDAs, Smartphones, sensors etc.... you have reached the right place. This is where you enter the pervasive world and pervasive messaging enables flow of information between your device world and enterprise world. Louis V. Gerstner described pervasive computing as "a billion people interacting with a million e-businesses with a trillion intelligent devices, all interconnected…". Now we live in a world where there are lots of messaging media, such as cell phones, voice mail,... [More]

Marcações: pervasive

New Enhanced Version of Message Broker V6 : Release 1

neekrish Visits (4990)

In the realm of Messaging Products, a new version of Message Broker is released. Have a look at the announcement letter here . I was always curious to watch something new in Message Broker, not only that I work on it, but, the fact of the NEW Message Broker supporting a new variety of Nodes. The new set of nodes supports the ERP applications, the High Performance XML Parser, the enhanced support to WebService, are something to watch for. What’s new in Version 6.1? Extended platform and operating system support for runtime environments New... [More]

Marcações: wmb

Singling out CLNTCONN channels

neekrish Visits (4936)

Client channel definition tables, or CCDTs for short, are convenient ways for the client to read channel definitions. A CCDT file contains all CLNTCONN channel definitions of a particular queue manager. So, how does a client using a CCDT know which channel to use ? The answer lies in the way the CCDT itself is written by the queue manager. The queue manager writes channel definitions on to the CCDT file in alphabetical order. So, the client picks up the first channel whose QMNAME parameter matches with the queue manager name parameter of the... [More]

Marcações: singleout svrconn wildcard

Using the Expeditor's JNDi feature in micro broker bridge to MQ

neekrish Visits (3163)

Here's is a simple tip to help you bind the MQ objects to the JNDI repository of Lotus Expeditor. Here we use the programmatic JNDI feature. The Lotus Expeditor's initial context is com.ibm.pvc.jndi.provider.java.InitialContextFactory. Let's start with creating the initial context Hashtable env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.pvc.jndi.provider.java.InitialContextFactory"); InitialContext context = new InitialContext(env); Follow the instruction in this documentation link so that we can use the MQ JMS objects... [More]

Micro broker bundles

neekrish Visits (3604)

If you see Lotus Expeditor installation, you'll see many bundles, Here your guide to identifying the micro broker related bundles. com.ibm.micro.bridge.mq.jms_XXX.jar or package com.ibm.micro.bridge.mq.jms contains the classes that you need for connecting to WebSphere MQ using MQJMSConnectionDefinition from the micro broker bridge com.ibm.micro.bridge.jndi.jms_XXX.jar or package com.ibm.micro.bridge.jndi.jms contains the classes required for the miro broker bridge to connect to a JNDI enabled JMS provider using JNDIConnectionDefinition.... [More]

Micro broker logs

neekrish Visits (3258)

If you are working on Lotus Expeditor, you would have probably figured out how to see INFO level logs for particular bundle. For micro broker also you can increase the logging levels the same wayHere are 6 simple commands that can be used in the XPD console for you to see all the micro broker logs at INFO level. setlogrlev com.ibm.micro INFO setlogrlev com.ibm.micro.bridge.jndi.jms INFO setlogrlev com.ibm.micro.bridge.mq.jms INFO setlogrlev com.ibm.mqttclient INFO setlogrlev com.ibm.micro.utils INFO setlogrlev com.ibm.mqttclient.jms INFO There... [More]

Simplest micro broker JMS client

neekrish Visits (3708)

If you want to quickly get started with writing a micro broker JMS client and connecting to a micro broker, here's how you do it. JmsFactoryFactory is your entry point into the JMS implementation classes. You need to add com.ibm.msg.client.jms and com.ibm.msg.client.mqtt as imports along with javax.jms in the manifest. Get started with creating a connection factory like this JmsFactoryFactory jmsFactory = JmsFactoryFactory .getInstance(MQTTConstants.PROVIDER_NAME); JMS 1.1 simplifies messaging with unified domains and hence you just need to... [More]

Links to developer works resources on IBM messaging products

neekrish Visits (3159)

Here are the links for forums, community spaces and feature pages: For links to new releases, articles, and many interesting things in the IBM messaging space visit: Messaging community space WebSphere MQ WebSphere MQ forum Developer works page on WebSphere MQ WebSphere Message Broker WebSphere Message Broker forum Developer works page on WebSphere Message Broker Lotus Expeditor Micro broker Lotus Expeditor forum (micro broker forum also) Developer works page on Lotus Expeditor WebSphere MQ everyplace WebSphere MQ Everyplace forum

Micro broker Information center

neekrish Visits (3031)

Here's the micro broker information center (documentation) . It has only micro broker information and excludes Lotus expeditor info. It gives you the javadoc for MQTT, micro broker administration and transformation. The complete Lotus Expeditor information center can be accessed over the web here . From: Neeraj Krishna & Vijay

Blogs