正式なコメント
Hi Tom
Thanks for contacting Accelerite support
I shall cross check internally and revert back to you soon
We are developing a connector for CPBM 2.6. Our current connector version is 1.1.1. Our version under development is 1.2.0. When version 1.1.1 is installed and configured etc, I can upgrade to version 1.2.0 by simply stopping cpbm, installing the 1.2.0 connector jar, updating the version in the map file and restarting cpbm. However, if I then need to make another code change, I can't simply rewrite the 1.2.0 jar file with a new one and restart. Doing so, it seems that the old connector code is still used (ie - even though the jar is different, older code seems to be used). I don't want to keep incrementing the version numbers as we are still testing and making changes. What are the correct steps to follow to replace a connector jar file with a new version of itself. My goal is to replace the 1.2.0 jar multiple times while testing various changes without having to re-install or use different version numbers. Thanks!
Hi Tom
Thanks for contacting Accelerite support
I shall cross check internally and revert back to you soon
Hi Tom
Greetings
Please find the response from the engineering team
Replacing the jar should work for most of the cases except application resource file changes.
If there is any change in resource properties then without version change the new messages will not be applied.
The workaround for this is to reduce the “application_resource_version” number in “applicationresourceschangelog” table.
If there is any other issue then please clean up the work directory.
rm -rf /usr/share/vts3/work/*
If still issue persists then provide the details of the issue.
Also please let us know if you interested in Accelerite support contract
Regards
Kiran Manohar
Product Engineer – Cloud Platforms
Email: kiran.chavala@accelerite.com |Contact No 91 8067721402
https://support.accelerite.com/hc/en-us
Ask, Discuss, Answer