older files it changes to an old-config-bkp. folder within the instance directory. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 15.15. 2.26.0 Full release Paging can now be configured by message count. 15.21.2. Upgrading from 2.20.0 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: a. etc/bootstrap.xml b.

older files it changes to an old-config-bkp. folder within the instance directory. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 15.14. 2.26.0 Full release Paging can now be configured by message count. 15.20.2. Upgrading from 2.20.0 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: a. etc/bootstrap.xml b.

older files it changes to an old-config-bkp. folder within the instance directory. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 15.13. 2.26.0 Full release Paging can now be configured by message count. 15.19.2. Upgrading from 2.20.0 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: a. etc/bootstrap.xml b.

older files it changes to an old-config-bkp. folder within the instance directory. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 15.12. 2.26.0 Full release Paging can now be configured by message count. 15.18.2. Upgrading from 2.20.0 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: a. etc/bootstrap.xml b.

older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2 deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 2.26.0 Full release notes Paging can now be configured by message count. Upgrading from older versions 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii

older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2 deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 2.26.0 Full release notes Paging can now be configured by message count. Upgrading from older versions 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii

older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2 deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 2.26.0 Full release notes Paging can now be configured by message count. Upgrading from older versions 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii

older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2 deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 2.26.0 Full release notes Paging can now be configured by message count. Upgrading from older versions 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: i. etc/bootstrap.xml ii

older files it changes to an old-config-bkp. folder within the instance directory. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 15.10. 2.26.0 Full release Paging can now be configured by message count. 15.16.2. Upgrading from 2.20.0 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: a. etc/bootstrap.xml b.

older files it changes to an old-config-bkp. folder within the instance directory. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new deleted. 3. Related startup script or profile cleanups are needed: a diff file demonstrating the changes needed since 2.26.0 is available here for *nix or here for Windows. 15.8. 2.26.0 Full release Paging can now be configured by message count. 15.14.2. Upgrading from 2.20.0 1. Due to XML schema changes to correct an inaccurate domain name 2 files will need to be updated: a. etc/bootstrap.xml b.