Depending on your configuration, there are several ways of carrying out migration tests.
You should have a test/development environment to carry out migration tests. Adobe Campaign environments are subject to license: check your license contract or contact your Adobe representative.
Stop all developments in progress and carry them over to the production environment.
Make a backup of the development environment database.
Stop all Adobe Campaign processes on the development instance.
Make a backup of the production environment database and restore it as a development environment.
Before starting the Adobe Campaign services, run the freezeInstance.js cauterization script which lets you clear the database of any objects that were running when the backup was started.
The command launches by default in dry mode, and lists all the requests that were executed by that command, without launching them. To execute cauterization requests, use run in the command.
Make sure your backups are correct by trying to restore them. Make sure you can access your database, your tables, your data, etc.
Test the migration procedure in the development environment.
If the migration of the development environment is successful, you can migrate the production environment.
Due to changes made to the data structure, importing and exporting data packages is not possible between a v5 platform and a v7 platform.
Various options let you measure the impact from a migration and identify the potential problems. These options are to be executed:
in the config command:
nlserver.exe config <option> -instance:<instance-name>
or at the postupgrade:
nlserver.exe config -postupgrade <option> -instance:<instance-name>
<instanceame>option. We do not recommend using the -allinstances option.
The -showCustomEntities option displays the list of all non-standard objects:
nlserver.exe config -showCustomEntities -instance:<instance-name>
Example of a sent message:
The -showDeletedEntities option displays the list of all the standard objects that are missing in the database or the file system. For each missing object, the path is specified.
nlserver.exe config -showDeletedEntities -instance:<instance-name>
Example of a sent message:
Out of the box object 'nms:deliveryCustomizationMdl' belonging to the 'xtk:srcSchema' schema has not been found in the file system.
Integrated as standard in the postupgrade command, this process lets you display warnings and errors that could make the migration fail. If errors are displayed, the migration has not been executed. If this happens, correct all the errors then re-start the postupgrade.
You can start the verification process on its own (without migration) using the command:
nlserver.exe config -postupgrade -check -instance:<instance-name>
You can ignore all warnings and errors with the JST-310040 code.
The following expressions are searched for (case sensitive):
|| Error code
|| Log type
|| This type of syntax is no longer supported in delivery personalization.
|| This library must not be used.
|| This connection method must be no longer be used.
| new SoapMethodCall(
|| This type of error leads to a migration failure.
|| This type of deployment is no longer supported. Office 365 and On-premise Microsoft CRM connector deployment type have now been deprecated.
If you are using one of these deprecated deployment types in an external account, this external account should be deleted and you should then run the postupgrade command.
To change to Web API deployment, refer to Web applications.
| CRM v1(mscrmWorkflow/sfdcWorkflow)
|| Microsoft CRM, Salesforce, Oracle CRM On Demand action activities are no longer available. To configure the data synchronization between Adobe Campaign and a CRM system, you need to use the CRM connector targeting activity.
A database and schema coherence check is also carried out.
This option lets you restore out-of-the-box objects if they had been modified. For each restored object, a backup of your changes is stored in the selected folder:
nlserver.exe config -postupgrade -restoreFactory:<backupfolder> -instance:<instance-name>
We strongly recommend using absolute folder paths and keeping the folder tree structure. For example: backupFolder\nms\srcSchema\billing.xml.
If you restart the postupgrade after a migration failure, it resumes from the same place it was stopped.