migration from Baltimore toolkit to Openssl toolkit

The major difference is indeed the upgrade from the Baltimore toolkit to the OpenSSL toolkit. Note that in Orbix 6.3.8 which is due to be released next month we are also adding support for SHA-256 certs. I would advise if you are doing this upgrade that you move to 6.3.8 since it is coming out so soon. Note you will need to be supported to do this upgrade. If you do have an active support contract I suggest you raise a support case with us if you have any questions.

The other thing to be aware of is the fact that we will drop some platforms and compilers when we add support for newer platforms and compilers.

Hi Martin

Thanks for your replies so much.

So...that's to say...it's not just a simple configuration changes to migrate from Baltimore toolkit to Openssl toolkit? Um...I need to have some code changes (C apps) in client? Reference to the migration part of the release_notes...I thought that I just needed to change the configuration file of the domain...

Hi Arica,

Sorry it's been so long since you heard from us on this. I noticed your reply while replying to another post here. You shouldn't need to do any code changes in your application and this will just come down to configuration changes to tell it to pick up the new OpenSSL toolkit now instead of the Baltimore one. Everything remains binary compatible in the upgrade.