Show Menu
TOPICS×

Before starting migration

In this document, commands linked to the database are given as an example. These may vary depending on their configuration. Contact your database administrator.

Warnings

Installed version

Before migrating, you should install the latest build of the current version that you are using.
Check the version on your server by going to the Help> About menu on the client console using the nlserver pdump command.

Data backup

Before starting a migration process, you must back up your data.

Environment

  • It is not possible to change your database engine type (DBMS). For instance, you cannot switch from a PostgreSQL engine to an Oracle engine. However, you can switch from an Oracle 8 engine to an Oracle 10 engine.
  • It is not possible to go from a non-Unicode database to a Unicode database.

Recommendation

As the migration procedure is particularly sensitive, we strongly recommend reading this document thoroughly before starting the procedure.

Migration steps

The migration procedure must be carried out on all servers and in a particular order.
  • In the case of a standalone platform (single machine mode), the application is migrated in its entirety.
  • In the case of a standard platform (enterprise), the migration steps are as follows:
    1. Migrate the marketing server.
    2. Migrate the mail server (mta).
    3. Migrate the redirection and tracking servers (Apache / IIS).
  • In the case of a Cloud Messaging platform , the execution servers are hosted at Adobe Campaign. Please contact Adobe Campaign to coordinate migration between different servers.
  • In the case of a Power Booster or Power Cluster platform , the migration steps are as follows:
    1. Migrate the redirection and tracking servers (Apache / IIS).
    2. Migrate the Power Booster/Cluster servers.
    3. Migrate the marketing server.
Communication between a v6.02 marketing server and a v7 Cloud Messaging or Power Booster/Cluster server is possible. Nevertheless, if you decide to keep your v6.02 marketing server, this must be updated with the most recent v6.02 build before migrating to the Cloud Messaging or Power Booster/Cluster.

User passwords

In v7, internal and admin operator connection must be secured by a password. We strongly recommend assigning passwords to these accounts and all operator accounts, before migration . If you have not specified a password for internal , you will not be able to connect. To assign a password to internal , enter the following command:
nlserver config -internalpassword

The internal password must be identical for all the tracking servers. For more information, refer to the Internal identifier and About permissions sections.