Top Stories

Managed Methods Inc., a provider of SOA (Service Oriented Architecture) visibility and SOA runtime governance today announced the availability of their SOA management and runtime governance support for deeper visibility for applications running on IBM WebSphere ESB, MQ, WSRR and environments secured by IBM DataPower. End-to-end management and monitoring is crucial to the performance of a business transaction. This additional capability expands the SOA environments that JaxView supports, including a wide range of support for applications exposed by ESBs , protocols and messaging and back end-databases including IBM DB2. "We are exceptionally pleased with this release for the support of these integration and mediation products. Our customers are using JaxView in varying ways, from agentless visibility to security and brokering, with varying environments. " states Al ... (more)

New Performance Testing Solution Speeds Development of IBM WebSphere MQ-Based Business and Web Services Applications

(August 20, 2002) - Rational Software has collaborated with CommerceQuest to develop the MQTester for Rational, a new automated performance-testing solution that speeds the development of higher-quality IBM WebSphere MQ-based business and Web services applications. The MQTester for Rational is an advanced-capability plug-in for Rational Suite® TestStudio® that expands the capabilities of Rational's open, extensible software development platform. It records the actual message traffic of the product application and then replays it in the IBM WebSphere MQ environment in a way that accurately reflects production conditions. This enables greater reliability in testing IBM WebSphere MQ-based applications MQTester for Rational enables IBM WebSphere MQ testers and developers to: Record both the IBM WebSphere MQ client and WebSphere MQ server message queuing interface (MQI) c... (more)

DataPower Enhances Security and Performance for WebSphere MQ

(September 16, 2003) - The latest firmware release for the DataPower XS40 XML Security Gateway and XA35 XML Accelerator network devices include support for IBM's WebSphere MQ (formerly MQ Series) protocol. This integration, achieved in part by establishing a technology licensing relationship with IBM Corporation, enables direct access to the XML acceleration and Web services security benefits of DataPower's XAN products from MQ Series applications. Support for MQ also makes it possible to use the XS40 XML Security Gateway as a wirespeed trusted gateway between internal MQ-based Web services and external HTTP Web services. The integration is available immediately as an optional part of firmware Release 2.3. The integration allows the XS40 and XA35 to accept messages that come across HTTP as well as MQ, extract the XML message, and process it based on its source and c... (more)

Q Pasa! Now Provides Robust Monitoring for WebSphere MQ for TPF

MQSoftware, Inc.'s Q Pasa! middleware management system is the first solution to provide monitoring support for WebSphere MQ for TPF (Transaction Processing Facility) used by airlines, hotels, and financial institutions worldwide. Q Pasa! will provide first-ever out-of-the-box monitoring of MQ for TPF, providing dashboard visibility of MQ metrics, queues, events and associated technologies. MQSoftware also announced today that KLM, one of the world's largest airlines based in the Netherlands has licensed Q Pasa! to monitor their WebSphere MQ environment. KLM will co-present with MQSoftware at the TPF User Group meeting next week. Q Pasa! provides for the first time, complete visualization of WebSphere MQ metrics for the TPF operating system, as well as other associated applications and technologies. TPF is a high-volume transaction processing system demanding fast r... (more)

Looking Beyond MQ

It's likely you've been working with WebSphere MQ (WMQ) for years developing, deploying, monitoring, or all of the above. It's also likely that by now you have assembled a tool bag full of items to support your implementations and ongoing operations. And you've no doubt become accustomed to dealing with problems within the MQ domain. But what if you could see more of the transactional journey on either side of MQ? Organizations doing this are finding new ways to improve levels of service and avoid costly upgrades. Initially, just seeing the touch points, you know - the "puts" and the "gets" ­ along with MQ administration probably seemed entirely sufficient in order to manage WMQ. A common assumption was that as long as we saw messages coming and going, things were okay. Analogous to Archimedes' principle of water displacement, the health of MQ or any other middleware... (more)

Nastel's Smart Plug-in for WebSphere MQ Available to HP Software Customers

MELVILLE, N.Y., Feb. 5 /PRNewswire/ -- Nastel Technologies, a leading provider of performance monitoring and management software for integrated applications and an HP Platinum Partner, today announced that its Nastel AutoPilot WebSphere MQ (APWMQ) Smart Plug-in (SPI) for HP Software is available through HP, effective immediately. The Nastel SPI for WMQ has been certified by HP for its functionality and integration with HP Operations Management Software. The Nastel APWMQ SPI for HP extends the span of control of HP Software by enabling users to monitor and manage IBM WebSphere MQ (MQSeries) environments directly from their HP Operations console. The APWMQ SPI makes the HP Operations console a single point of control over the entire enterprise IT infrastructure with complete access to all WebSphere MQ nodes from application servers to mainframes, including those not ... (more)

Implementing J2EE/.NET Interoperability Using WebSphere MQ Part 2 - Putting theory into practice

In Part 1 of this series, we discussed how the use of messaging software can alleviate some of the problems with integration of J2EE and .NET environments using Web services. In this article we will discuss implementation of the proposed architecture on both J2EE and .NET platforms, along with possible enhancements of the proposed solution. All of the code referenced in this article is available for download from Implementing the .NET Client Although support pack MA07 supports all the basic functionality of WebSphere MQ and is implemented based on the WebSphere MQ Java object model, implementation of interoperability with a JMS-based J2EE implementation poses the following challenges: 1.  Implementation of JMS for WebSphere MQ introduces the RFH2 header, which is used by this implementation to support JMS-required features (e.g.,... (more)

Monitoring WebSphere MQ-Connected Applications

Enterprises need to think about a performance management solution that will give them real-time end-to-end visibility into the entire Web application environment from browser to back-end systems, including messaging middleware such as WebSphere MQ. By providing an application-centric view of MQ-connected environments, such a tool allows application administrators to work collaboratively with MQ administrators without displacing existing MQ monitoring tools. The result is an effective, seamless process for detecting, triaging, and diagnosing application performance issues in complex interconnected environments. Intended for Web application administrators, this article will discuss the core requirements for monitoring and managing the performance of WebSphere MQ-connected Web application environments and illustrate the advantages in having a single tool that can prov... (more)

IBM WebSphere WAS for z/OS and MQ

As a J2EE application server, WAS for z/OS supports the Java Messaging Service (JMS). There are three choices for JMS providers in WAS for z/OS V5.x: WebSphere MQ (WMQ), Embedded Messaging (EM) JMS provider, or a third-party product. The EM JMS provider is a simplified WMQ. It provides an isolated messaging environment in WAS for z/OS that can't be used to interoperate with any other messaging systems. Obviously the JMS support in WAS for z/OS was a temporary solution. Now it's been deprecated in WAS for z/OS V6. Instead a new JMS provider named Service Integration Bus (SIB) has been introduced. SIB is part of IBM's Enterprise Services Bus (ESB) infrastructure solution, which isn't just a simple JMS provider. I'll discuss WAS for z/OS and SIB in a separate article. There are few third-party messaging products that run on z/OS. So this article will focus on discuss... (more)

Message-Driven Beans in WebSphere

With WebSphere Application server 5.0+ you can now add Message-Driven Beans (MDBs) to your WebSphere arsenal. These beans are handy for many processes. I recently had to write a MDB using MQ Series. WebSphere Application Server (WAS) 5.0 had the same functionality built-in, but I had a hard time learning how to use it. I also encountered some issues while configuring it to run in a load-balanced environment. First of all, there's no real way of balancing the load in a clustered environment for MDBs. All nodes in the cluster will fight for the messages as they enter the queue. This is a limitation that can't be worked around. There's another pitfall that will affect you even if you don't plan to use load balancing. If for any reason the queue manager connection fails, your MDB will be rendered useless until someone restarts the message listener service on the applica... (more)

Implementing J2EE-.NET Interoperability Using WebSphere MQ

It is today's reality that most companies are using both J2EE and .NET environments for their software implementation. Until recently, the prevalent solution for integration of these two environments has been HTTP-based Web services. Although this solution works well in many cases, it suffers from the following drawbacks: 1.  Most implementations today are synchronous and based on the synchronous nature of the underlying HTTP protocol. 2.  Reliable messaging is difficult to implement using HTTP. 3.  Load balancing in an HTTP-based environment requires a client-side load-balancing implementation, which is usually quite difficult when compared to server-side load balancing. 4.  Client and server application life cycles have to be synchronized in order for Web services-based communications to work. Some of these problems can be easily alleviated by using messaging software... (more)