WMB Migration From V6.1 to 7.0

Following is the migration done on V7.0 from V6.1 :


Message Broker Version 7 will not contain a Configuration Manager

• Brokers become responsible for deployment, management and enforcement of administrative security.
• Existing tools administer each broker directly.

Significant simplification of the broker operational model

• Fewer installed and configured components.
• Single view of the broker environment - No synchronization required.

The Configuration Manager really has gone -  It has not “moved inside the broker”.


Long-standing niggles have been eliminated

• One-step broker creation (no Configuration Manager association step)
•  No service user ID requirement on non-Windows platforms.
• No “Deployment already in progress” messages.
• No Configuration Manager / Broker synchronization problems
• Cancel deployment.
• Performance.

ConfigManagerProxy (CMP) API changes

• Administration API simplified
• Removal of Configuration Manager.
• Removal of publish / subscribe component (now in WebSphere MQ)
• Package names, class names and method signatures unaffected
• Support for version 6.0 / 6.1 applications.
• Applications will compile without change
• Applications that do operations that are relevant in version 7 should continue to work.

Summary

• The Configuration Manager has been removed in Message Broker version 7.
• This significantly simplifies operational management
•  No domains.
• Single deployment type.
• The Message Broker Toolkit, Message Broker Explorer, command line interface, and user application connect directly to brokers.
• The broker environment is easier to manage.
• One view of all broker components.
• More information returned to tools.
• Improved connect and deployment times.

Additional information can be read from http://webspheremb.blogspot.in/2011/07/message-broker-faq-25.html