New Changes WMB v 7.0  

Brokers maintain configuration data in the local file system

Brokers create and manage configuration data in an internal repository in the local file system, and have no requirement for a database. You can back up and restore the broker component and its internal repository by using the commands

                          mqsibackupbroker and mqsirestorebroker.

Database support for message flows and user data is unchanged; however, supported versions of Relational Database Management Systems (RDBMS) (supplied by IBM and other vendors) have been updated on some platforms.

Optimized deployment and interactions with the broker

Applications that manage brokers and their resources connect directly to the broker. These applications include:

* The WebSphere Message Broker Explorer, an administration toolkit delivered with Version 7.0, which is described later in this section.

* The WebSphere Message Broker Toolkit.

* Commands; for example, mqsideploy, mqsilist, and mqsistartmsgflow.

* All applications that are written to the Configuration Manager Proxy (CMP) API, including the     CMP Exerciser.

Administration security

Set up broker administration security to control the authority that is required by users to complete specific administrative tasks. You can enable security when you create a broker, or change it later on an existing broker. This option, which uses WebSphere MQ facilities, replaces Access Control Lists (ACLs) that were managed by the Configuration Manager in previous versions.

WebSphere Message Broker Explorer

The WebSphere Message Broker Explorer is an administration interface that is integrated as a plug-in into WebSphere MQ Explorer, so that you can administer both brokers and WebSphere MQ queue managers on local and remote computers.

Important status information is always on view, and you can access details about what each broker is doing, and has recently done. Configuration and other changes are monitored, and the user responsible for these changes is recorded.

The WebSphere Message Broker Explorer supports all the function that is provided by the Broker Administration perspective in the WebSphere Message Broker Toolkit in previous versions, and offers additional, more advanced features. Limited administration functionality is still available in the new Brokers view in the WebSphere Message Broker Toolkit to run a subset of operations.

The WebSphere Message Broker Explorer includes the following capabilities:

You can create, delete, start, and stop local brokers without using the command line.

You can see the relationships between your brokers and your queue managers.

You can deploy a broker archive file to multiple execution groups in one step.

You can see visualizations of your accounting and statistics data.

You can see visualizations of your resource statistics data.

You can configure broker properties, including creating and modifying configurable services.

You can view the broker administration queue, and remove pending tasks that have been submitted to the broker.

You can connect and configure settings for a DataPower® device.

Publish/subscribe support

All topic-based publish/subscribe operations are handled by WebSphere MQ. You can use WebSphere Message Broker facilities to extend publish/subscribe options to include content-based publishers and subscribers.

All applications use a single topic space that is managed by WebSphere MQ, and access control is handled by the queue manager. The concept of broker domains, which is valid in previous versions of WebSphere Message Broker, no longer exists; equivalent function for broker domains, broker topologies, and broker collectives is provided by WebSphere MQ clusters.

The Publication node uses WebSphere MQ publish/subscribe facilities. You can use the NoMatch terminal, new in Version 7.0, to identify scenarios in which no subscribers are registered to receive particular topics.

With these changes, your publish/subscribe network requires you to configure a broker only where you have content-based subscribers, not throughout the network. The content-based filters that you can specify can now include full ESQL expressions, including namespace support.

You can migrate JMS applications, and applications that use the MQRFH2 header, directly to WebSphere MQ.

WebSphere MQ Real-time Transport and WebSphere MQ Telemetry Transport nodes are no longer supported. Therefore, the following nodes have been removed:

Real-timeInput

Real-timeOptimizedFlow

SCADAInput

SCADAOutput

If you use the WebSphere MQ Real-time Transport, your applications can use equivalent qualities of service provided by WebSphere MQ. Migrate JMS real-time publishers and subscribers to the "read-ahead get" and "asynchronous-put" facilities of WebSphere MQ.

Message flows containing these nodes that you have migrated to WebSphere Message Broker Version 7.0 will not start until these nodes have been removed from the flow, and the flow has been redeployed.

Contact your account representative for more information about support for WebSphere MQ Real-time Transport and WebSphere MQ Telemetry Transport.

WebSphere Message Broker Toolkit

You can administer local and remote brokers in the Brokers view, which is new in Version 7.0. This view is integrated into the Broker Application Development perspective, so that you can access basic administration tasks while you are developing, deploying, debugging, and testing your applications.

The WebSphere Message Broker Toolkit includes an impact analysis tool that you can use to discover interdependencies between resources, and assess the effects of planned changes to those resources. See Impact analysis: analyzing the effects of planned changes to your applications.

Patterns

A pattern is a reusable solution that encapsulates a top-down tested approach to solving a common architecture, design, or deployment task in a particular context. This approach complements bottom-up development of creating message flows and nodes.

A number of patterns are supplied in the WebSphere Message Broker Toolkit, and you can use the Patterns Explorer, which includes comprehensive help, to simplify creation of common scenarios.

You can configure these patterns with values for use in your own environment to solve specific business problems. The supplied patterns use preferred techniques in message flow design, to produce efficient and reliable flows.

SCA nodes for WebSphere Process Server

Five new built-in message flow nodes are provided to improve the interaction between WebSphere Message Broker and WebSphere Process Server Version 6.2 by using Web Services (SOAP over HTTP) or WebSphere MQ bindings.

The nodes are the SCAInput, SCAReply, SCARequest, SCAAsyncRequest, and SCAAsyncResponse nodes.

Enhanced support for the PHPCompute node

Support for the PHP scripting language is available on all operating systems on which WebSphere Message Broker is supported, 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.

SAP Enhancements:

Use the SAPReply node to send a reply to an SAP synchronous callout. Use this node with an SAPInput node to implement a message flow application that acts as a remote function call (RFC) destination.

Generic IDoc routing

By using the SAPInput node in passthrough mode, WebSphere Message Broker can receive any IDoc, and route it according to IDoc type. By using this method, you can also use a single RFC program ID to receive all IDoc types, while still allowing individual IDoc processing.

SAP high availability

You can deploy an SAP adapter and a message flow that contains an SAPInput node to two brokers on your network; these brokers can accept IDocs concurrently from the same SAP system so that you can build a highly available environment.

On distributed systems, two brokers share state by using queues on a third queue manager, which is running in multi-instance mode. Each broker has client connections to that queue manager.

On z/OS®, the shared state is stored on a shared queue. Each broker connects to the queue sharing group.

Iterative discovery

You can take an adapter component that was created by using the Adapter Connection wizard in WebSphere Message Broker Version 7.0, and update it with newly discovered objects from the Enterprise Information System (EIS) by running the Adapter Connection - Iterative Discovery wizard. This facility is known as iterative discovery. You can either add the new objects without modifying existing objects, or replace existing objects.

Iterative deployment

If your message flow acts as a gateway to an EIS, you can use it to call new services that did not exist when you developed the flow. You can also create an event handler to an EIS to handle new event types that did not exist when you first developed your message flow. In both cases, if a new service or event is provided by the EIS, you do not have to modify and retest the message flow. This facility is called iterative deployment.

Sequence and Resequence nodes:

WebSphere Message Broker provides support for adding sequence numbers to messages, and for reordering messages in the message flow based on their sequence number. You can use the new Sequence node to add sequence numbers to the messages, and the new Resequence node to reorder the messages into their original sequential order.

New configurable services for EDA nodes:

You can use the following configurable services to define the WebSphere MQ queues on which EDA nodes store event state:

Aggregation

Collector

Resequence

Timer

Resource statistics:

You can collect statistics for some of the resources that are used by execution groups in the broker to help with problem diagnosis and broker optimization. Supported resources are the Java™ Virtual Machine (JVM), and the outbound sockets. For example, you can monitor the sockets that are used by SOAP nodes in your message flows.

You can start and stop statistics collection at broker or execution group level by using the WebSphere Message Broker Explorer, the CMP API, or the mqsichangeresourcestats command.

The resource statistics framework is based on the existing accounting and statistics for message flows, and generates periodic messages as publications that your programs can subscribe to. You can also view these statistics in the WebSphere Message Broker Explorer, which provides both numeric and graphical representations.

Multi-instance brokers

WebSphere Message Broker builds on the multi-instance queue manager support introduced in WebSphere MQ Version 7.0.1 to provide a highly available configuration with active and passive brokers.

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. The use of queue managers in this way avoids the requirement for a high availability solution, such as HACMP™, supplied by a vendor software company.

----

Java

Java 1.6 (Version 6) is supported in all environments. On IBM platforms, the IBM J9 engine is supplied, which benefits from reduced startup time and memory footprint.

For More Information Technical changes check below Links:

https://www.ibm.com/support/knowledgecenter/SSKM8N_7.0.0/com.ibm.etools.mft.doc/bh44620_.htm