Migrating From Broker To Universal Messaging - Webinar - Dec 2015
Migrating From Broker To Universal Messaging - Webinar - Dec 2015
Migrating From Broker To Universal Messaging - Webinar - Dec 2015
WEBMETHODS BROKER TO
UNIVERSAL MESSAGING
Jonathan Heywood
Senior Director Product Management,
Product Marketing and Communities
Software AG
Java C# JMS
C++
AMQP
Python
JavaScript Enterprise Web
MQTT
Flex
Silverlight HTTP
LDAP
Objective C
Mobile IoT
• High availability
– True active-active clustering
– Fast fail-over
– No need for special HA infrastructure
• Performance
– Heavily optimized for modern multi-core processors
– Streamlined storage files
– Faster than Broker
Broker 9.6
5
• Broker 9.6 is the last version of
Broker
• Shipped and supported with all
webM releases thru 2017Oct
Public announcement
years •
•
FAQ on Empower (Oct 2015)
TECHniques article (Oct 2015)
• Presentation at IW (Oct 2015)
End-of-maintenance End-of-support • Public webinar (Dec 2015)
October 2019 October 2020 • Email to customers (Dec 2015)
Apr Oct Apr Oct Apr Oct Apr Oct Apr Oct Apr Oct Apr Oct Apr
2014 2014 2015 2015 2016 2016 2017 2017 2018 2018 2019 2019 2020 2020 2021
• Non-webMethods applications
– No code changes required (if using standard JMS)
– Simply switch client libraries and update connection URL
Broker Broker UM
JMS with
Native JNDI CFs and JNDI CFs and
webMethods API destinations
brokerjndimigration.bat
destinations
• Integration Server
– No Flow code changes required
– Simply switch wM Messaging alias
to point to Universal Messaging
– Run migration utility to optimize IS
Doc Types and Triggers for use
with UM
Additionally:
• Active-active clustering
• FAQ on Empower
– https://empower.softwareag.com/brokerendoflife/
• Documentation
– webMethods > Products > Universal Messaging >
Migrating from Broker to Universal Messaging
• TECHcommunity
– http://techcommunity.softwareag.com
– webMethods > Messaging