Does WebSphere Message Broker V7 promise anything new?
vivekgrover 120000FG70 Visits (10792)
While working with the older versions of WebSphere Message Broker (WMB) V6.x, did you ever feel “Gosh! “Why does it have so many components in a single product”. If so, you have reached the right place. We will discuss some of the key features introduced in WebSphere Message Broker V7 and familiarize you with the simplified architecture of the product in addition to giving you the agility to extend your SOA environment.
WebSphere Message Broker V7 was announced in October 2009. It promises to simplify your overall messaging infrastructure and introduces new capabilities. As most of you know, WebSphere Message Broker is a plat
The WebSphere Message Broker V7 environment is mainly divided into two parts:
However, if you use the WebSphere MQ Real-time Transport, your applications can use equivalent qualities of service provided by WebSphere MQ.
New features for WebSphere Message Broker Development
Pattern instances: Patterns are reusable solutions that encapsulate a tested approach in solving common architectural, deployment, and design tasks in a particular context. Patterns can be used to generate customized solutions to a recurring problem in a more effective way. Patterns in WebSphere Message Broker V7 can be referenced to providing guidance in implementing solutions. Pattern specifications typically include the description of identified solutions. Patterns greatly reduce the development cycles as the resources can be generated from a set of predefined templates thus increasing the efficiency. WebSphere Message Broker Toolkit V7 displays Pattern instances -> Patterns Explorer, which provides a list of patterns and provide details on each of them.
WebSphere Message Broker Explorer: The WebSphere Message Broker Explorer is a tool for administrators, and provides the capability for enhanced WebSphere Message Broker monitoring and management. WebSphere Message Broker Explorer is installed as a plug-in for WebSphere MQ Explorer, the Brokers view is added to the MQ Explorer-Navigator pane. The WebSphere Message Broker Explorer also provides functionalities such as Create, delete, start and stop brokers, deploy, create and modify configurable services, as well as a number of QuickViews that can be used to view the properties of brokers and their resources. These are automatically displayed in the Brokers folder in the MQ Explorer, Navigator view.
Ease of deployment: It is no longer required to create BAR files for deployment. With WebSphere Message Broker V7 Toolkit; you can deploy message flows directly into execution groups without having to build BAR files. Dragging the message flow to the execution group will deploy the message flow and the associated artifacts directly. However, BAR files can still be created to perform deployment to the broker.
Enhanced support for the PHPCompute node: Support for the PHP scripting language is available on all supported operating systems, except Solaris on x86-64. The PHPCompute node supports general purpose transformation logic in the PHP language, and complements the Compute, JavaCompute, XSLTransform, and Mapping nodes. In addition, the set of supported PHP extensions has been increased.
Additional new nodes: Here are the new message flow nodes introduced in WebSphere Message Broker V7:
New features for WebSphere Message Broker Runtime
Clustering and Multi-instance brokers: Support of basic failover has been introduced in WMB V7 with the help of multiple-instance (MI) queue manager feature in MQ V7.0.1. MuIti-instance feature helps making MQ and Broker highly available, without other HA solutions. Multi-instance brokers and queue managers store their configurations on shared network storage so that if a failure occurs in an active component, the passive component assumes the configuration and operation of the active component.
Audit and monitoring: You can configure your message flows to emit event messages that can be used to support transaction monitoring and comprehensive auditing, and business process monitoring. These events may be consumed by a diverse range of applications, including WebSphere Business Monitor, WebSphere MQ and JMS applications, and vendor applications for business intelligence, and audit scenarios.
Resource statistics: You can collect statistics to monitor the performance of certain resources used by execution groups in the broker to help with problem diagnosis and broker optimization. For example, you can monitor the sockets that are used by SOAP nodes in your message flows. This can be done using WebSphere Message Broker Explorer or mqsi
Service Federation Management (SFM) enablement: Service Federation Management console is provided in WebSphere Service Registry and Repository V7.0, which allows you to establish bridges between separate ESBs in your enterprise, allowing services and applications to be shared between domains. You can use a broker as a connectivity server that can be administered by a Service Federation Management (SFM) console provided with WebSphere Service Registry and Repository V7.0.
For more information and details on the new features in WebSphere Message Broker V7, you can refer to the following sources:
I hope this information is helpful in planning your upgrade to WebSphere Message Broker V7. Let me know if you have any questions.