Steps:

1) Create new ESB runtime, select the SOA Platform dir path
2) Accept default version, specify a name for the new run-time
3) Then - before saving the new ESB runtime change the version number - the results are:

With an SOA-P 5.2 server (ESB 4.10):

• The default ESB version displayed is 4.10
• If this is changed to 4.11, this warning is displayed:
  No exact match found for ESB runtime version 4.10. Assuming compatible with latest version: 4.7.
• If the version is changed back to 4.10, the error is still displayed in the wizard

With an SOA-P 5.3 server (ESB 4.11):

• The default ESB version displayed is 4.11
• If this is changed to 4.12, this warning is displayed:
  No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
• If the version is changed back to 4.11, the error is still displayed in the wizard

With an SOA-P 5.3.1.ER3 server (ESB 4.11.1):

• The default ESB version displayed is 4.11
• If this is changed to 4.12, this warning is displayed:
  No exact match found for ESB runtime version 4.11. Assuming compatible with latest version: 4.12.
• If the version is changed back to 4.11, the error is still displayed in the wizard

With an SOA-P 5.3.1.ER4 server (edited VERSION file in rosetta.jar to be ESB 4.12):

• The default ESB version displayed is 4.12
• If this is changed to 4.11, this warning is displayed:
  No exact match found for ESB runtime version 4.12. Assuming compatible with latest version: 4.11.
• If the version is changed back to 4.12, the error is still displayed in the wizard