RAFW in BF 7.1.2 changes the Application update behavior
Prior than 7.1.2. to update an EAR, you can simply use the action - "was_common_deploy_install_app" with "options.update.ignore.new=true" in the APPNAME.properties file.
Now, with 7.1.2, there is an action called "was_common_deploy_update_app" however, it expects a property file called "APPNAME_update.properties".
Question. What goes inside this "APPNAME_update.properties"? I do not see any template or sample file.
Thanks
Now, with 7.1.2, there is an action called "was_common_deploy_update_app" however, it expects a property file called "APPNAME_update.properties".
Question. What goes inside this "APPNAME_update.properties"? I do not see any template or sample file.
Thanks
One answer
Prior than 7.1.2. to update an EAR, you can simply use the action - "was_common_deploy_install_app" with "options.update.ignore.new=true" in the APPNAME.properties file.
Now, with 7.1.2, there is an action called "was_common_deploy_update_app" however, it expects a property file called "APPNAME_update.properties".
Question. What goes inside this "APPNAME_update.properties"? I do not see any template or sample file.
Thanks
I figured out why the option "options.update.ignore.new=true" is no longer working in 7.1.2.
I had to decipher the error code and came up with this format.
OPTIONS=-update.ignore.new
Now, I can update the existing application without overwriting the existing binding.
I wish RAFW development team be more informative about changing their command or property syntax.. Everything is like a puzzle or maze working with RAFW.