4.0.x to 4.1.0.FR Migration
===========================

MySQL or Oracle migration: script has to be manually executed in DB prior to re-deployment of the new WAR version. Scripts are located in smp-setup.zip.

Oracle migration: First run oracle10g_4.0_to_4.1-createFunction.sql, and then the actual migration script oracle10g_4.0_to_4.1.sql.


===============================

4.1.0.RC  to 4.1.0.FR Migration
===============================

MySQL or Oracle migration patch script has to be manually executed in DB prior to re-deployment (mysql5innoDb_patch-4.1-RC1_to_4.1.sql and  oracle10g_patch-4.1-RC1_to_4.1.sql) of the new WAR version. 
Scripts are located in smp-setup.zip.


==================

SPECIAL REMARK
==================

In SMP 4.0, if only one domain is used, the application expects one key-pair in the keystore, and will use it for 2-way-SSL authentication in SML integration. 
This is automatic in 4.0 and no configuration of the certificate alias is required.
However, When migrating to SMP 4.1, the alias must be present in the SMP_DOMAIN table. 

The certificate alias must be added to the SMP_DOMAIN table in the database:
  e.g: update SMP_DOMAIN set SML_CLIENT_KEY_ALIAS='<certificate alias>';