Description of problem:
As JON was being rebased from EAP 6.3.3 onto EAP 6.4.3, it was discovered that if we did not use the same configuration base(EAP 6.3.x) that it would cause non-trivial update scenarios at patch application time.  

If customers had made any changes to the configuration files during JON 3.3.0 -> 3.3.3, it would require manual intervention to merge said changes from JON 3.3.4 and onward. 

Version-Release number of selected component (if applicable):
N/A.