adobe campaign source code repository tools

Basically there are two delivery channels available: The Mobile App Channel lets you use the Adobe Campaign platform to send personalized notifications to iOS and Android terminals via apps.

Adobe Analytics & Campaign Combined Together can delver following capabilities. Below given mobile app procedures.Īdobe Campaign lets you design and orchestrate targeted and personalized campaigns on multiple channels, such as e-mail, direct mail, SMS, Wap Push, search, social etc.Īnalytics service provide various levels of views like visitor geo-location, what days they come the most frequently, and how long they’re staying as well as several metrics based on e-commerce data, CRM attributes, engagement, etcĪdobe Analytics data can be used to create effective Adobe campaign across channels.

Run the same test suite which you ran before upgrade and ensure things are normal.īasically Analytics integration for AEM website and mobile app procedure remains same.

Verify the upgrade.log and error.log for any issues.

Archive then delete the log files - Delete all old log files.Ĭontent Repository Migration : Migrate the repository to Apache Oak Using crx2oak tool.ĪEM Upgrade: Start the AEM 6.2 quickstart jar with the appropriate run modes (author, publish).

upgrade customization - Upgrade your customs codes to reflect new APIs, removing deprecated ones.

Disable custom authentication mechanisms - Disable any hooks related to authentications.

Run a test suite - Ensure you have a test suite with all functionality checking.

Consistency and Traversal Checks - Validate system checks using Adobe tools.

Cleanup any content - remove unwanted content, packages, workflows.

Create a full backup - Take a backup of content and any custom codes.

Preparing the source instance: Here we are ensuring our environment is ready for upgrade.

Another success factor is you testing the upgrade activities minimum 3 times in development machines, to ensure all integration, third party APIS work perfectly. Ensure the infrastructure team is fully understood the architectural changes. If your code is well maintained, and components are granular, you are safe. Note: For AEM 6.1 to 6.2 upgrade, we don't have to do step (1) since we already have OAK(CRX3).ĪEM versions 5.4 to AEM 6.1 can be directly upgraded to 6.2.ĪEM 5.3 and below versions needs to upgrade first to version 5.4 or above, then to AEM 6.2.ĪEM 6.1 to 6.2 upgrade can be carried out by just upgrading AEM(Not repository), In all other versions we need to upgrade the repository.

Adobe campaign source code repository tools