- Product documentation
- Latest updates
- Release Notes
- Getting Started
- Sending Messages
- Get started with messages
- Delivery best practices
- Key steps when creating a delivery
- Sending emails
- Sending messages on mobiles
- Sending push notifications
- Sending direct mail
- Using delivery templates
- Personalizing deliveries
- Using seed addresses
- Subscriptions and referrals
- Monitoring deliveries
- Tracking messages
- Deliverability management
- Content management module
- Orchestrating Campaigns
- Reporting
- Designing web content
- Integrating with Adobe Experience Cloud
- Automating with Workflows
- Introduction
- General operation
- Executing a workflow
- Targeting activities
- Flow control activities
- Action activities
- About action activities
- Delivery
- Delivery control
- Continuous delivery
- Recurring delivery
- Cross-channel deliveries
- Local approval
- Data loading (RDBMS)
- Loading (SOAP)
- Data loading (file)
- Content Management
- Data extraction (file)
- SQL code and JavaScript code
- SQL Data Management
- Nlserver module
- Update aggregate
- Event activities
- Use cases
- Monitoring workflows
- Advanced management
- Technical workflows
- About technical workflows
- Deliveries
- Campaign
- Web Analytics
- Distributed Marketing
- Deliverability monitoring
- Inbox rendering
- Interaction
- Control of offer engine
- Message Center (Control)
- Message Center (Execution)
- Mobile App Channel
- LINE Channel
- Marketing Resources (MRM)
- Social Marketing
- Integrations with Adobe Experience Cloud solutions
- Privacy Data Protection Regulation
- Transfer to Mid-sourcing
- Mid-sourcing platform
- Managing Offers
- Transactional Messaging
- Integrating with Social media
- Installation and configuration guide
- Architecture principles
- Deployment guidelines
- Deployment types
- Campaign on Windows
- Campaign on Linux
- Initial configuration
- Additional configurations
- Accessing an external database
- Appendices
- Monitoring guide
- Introduction
- Production procedures
- Data processing
- Updating Adobe Campaign
- Database maintenance
- Troubleshooting
- Performance and throughput issues
- Images missing
- Image display issues
- Temporary files
- Database performances
- Modules and frequent issues
- Log precision
- Tracking logs issues
- Workflow execution
- Failure to connect
- Connection thresholds
- Stack trace in Linux
- Encoding of the Oracle database
- Console update
- Lost password
- JSP behavior
- Developers guide
- Migration guide
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
- The migration process must be performed only by expert users. You must be assisted by at least a database expert, a system administrator and an application developer from Adobe Campaign.
- Before starting migration, check that the systems and system components that you use are in fact compatible with v7. Consult the compatibility matrix.
- If you use Adobe Campaign Cloud Messaging (mid-sourcing), contact Adobe before beginning the entire migration procedure.
- Before starting a migration process, you must back up your data.
- The migration process may take several days to be completed.
- Adobe Campaign v7 is stricter than the 5.11 and 6.02 versions in terms of in configuration. This is principally to avoid problems such as data corruption and to preserve data integrity in the database. Consequently, certain functions offered in v5.11 and v6.02 may no longer work in v7 and may therefore need to be adapted after migration. Before putting into production anything, we suggest you systematically test all configurations, particularly workflows which are necessary to using Adobe Campaign.
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 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:
- Migrate the marketing server.
- Migrate the mail server (mta).
- 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:
- Migrate the redirection and tracking servers (Apache / IIS).
- Migrate the Power Booster/Cluster servers.
- Migrate the marketing server.
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.