Adapt your configuration configuring-your-platform

Certain major changes in Adobe Campaign v7 require specific configuration. These configurations may be necessary before or after migrating.

During the migration, the NmsRecipient table is rebuilt from the schemas definition. Any change made to the SQL structure of this table outside of Adobe Campaign will be lost.

Example of elements to check:

  • If you have added a column (or an index) into the NmsRecipient table but you have not detailed it in the schema, this will not be saved.
  • The tablespace attribute takes back its values by default, in other words those defined in the deployment wizard.
  • If you have added a reference view to the NmsRecipient table, you must delete it before migrating.

Before the migration before-the-migration

When migrating to Adobe Campaign v7, the following elements must be configured. These elements must be addressed before starting the postupgrade.

  • Passwords

    You must configure the Admin and Internal passwords. Learn more

After the migration after-the-migration

After running postupgrade, check and configure the following elements:

  • Mirror pages

    Mirror page personalization block has changed with v6.x. This new version improves security when accessing these pages.

    If you used the v5 personalization block in your messages, the mirror page display will fail. Adobe highly recommends to use the new personalization block when inserting mirror page in your messages.

    However, as a temporary workaround (and as the mirror pages are still live), you can turn back to the old personalization block to avoid this problem by changing the option XtkAcceptOldPasswords and set it to 1. This will not affect the usage of the new v6.x personalization block.

  • Syntax

    If you encounter any errors related to the syntax, during the postupgrade, you must temporarily activate the allowSQLInjection option in the serverConf.xml file, as this gives you time to rewrite the code. Once the code is adapted, make sure to reactivate the security.

  • Conflicts

    The migration is performed through a postupgrade and conflicts may appear in reports, forms or web applications. These conflicts can be resolved from the console.

  • Tomcat

    If you customized the installation folder, make sure to check it is correctly updated after the migration.

  • Reports

    All out-of-the-box reports currently use the v6.x rendering engine. If you had added JavaScript code into the reports, some elements may be impacted.

  • Web Applications

    After the postupgrade, if you have any problems connecting to your identified Web applications, you must activate the allowUserPassword and sessionTokenOnly options in the serverConf.xml file. To avoid any security issue, these two options must be reactivated after the problem is solved.

    Depending on the type of Web applications and their configuration, you must perform additional manipulations to ensure they work correctly.

  • Interaction

    If you use Interaction, you must adjust any parameters after the migration.