Apama Documentation : Release Notes : What's New in Apama 5.0 : Migrating from Apama 4.3
Migrating from Apama 4.3
 
Platform changes between 4.3 and 5.0
Changes to Apama client APIs between 4.3 and 5.0
Migrating 4.3 projects that use Web Services Client adapters
If you are upgrading from Apama 4.3 the following topics provide migration notes, information about backwards incompatible changes, and additional helpful information for migrating applications from Apama 4.3.
*Changes to EPL features in Apama 5.0
*Deprecated serialize and deserialize operations have been removed
*Deprecated high availability components removed
*Event Modeler standard block changes
*Changes related to dashboards
*New correlator-integrated messaging for JMS features
*Changes to engine_send
*New ADBC adapter features
Before migrating your application, read the information in the above topics as well as the information provided in this topic and in the following topics:
Platform changes between 4.3 and 5.0
Changes to Apama client APIs between 4.3 and 5.0
Migrating 4.3 projects that use Web Services Client adapters
In Apama 5.0, the OEM installer has been removed. The silent installation mode has been retained. Information for creating a properties file and for running an installation in silent mode can be found in the Software AG Knowledge Center in Empower: http://empower.softwareag.com.
The Apama correlator needs a license file in order to run for more than 30 minutes. Previously the Apama product used a British spelling ("licence" - with a 'c'). For consistency with other products, this has been changed to the American spelling "license" (with an 's'). This change is visible in a number of places such as the correlator command line, sentinel agent command line, EMM. If your scripts use the old spelling, you should modify them to use the new spelling. Note that the this affects the --license option for starting the correlator and the sentinel agent. (Scripts that use the short-hand command-line parameter to the correlator "-l" do not need to change.) This also affects the Ant properties and task attributes in apama-macros.xml, so Ant scripts and properties files may no longer run until the spelling is updated.
The environment variables APAMA_AGENT_CWD and APAMA_AGENT_ARGS no longer have any relevance on UNIX. Users should either use the default settings, run sentinel_agent by hand, or edit the init script.
Apama no longer supports Progress Control Tower.
For further migration assistance, contact Apama technical support.
Copyright © 2013-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback