Implement testing and validation processes to ensure only authorised changes are promoted to Higher Environments

[AEM_Forum]

Hi,

In an Adobe Campaign implementation, how to ensure only authorized changes are promoted to production (Development, Test, and Production Environments)?

Like someone designated for this task will look at all changes and approve some and disapprove others and only approved changes move forward.

My understanding is that if we integrate SVN (source code system), only bug free code could be checked in and only checked in code could be moved up in the higher environments.

Before checking in, we perform correct amount of testing.

Is this view correct, or any other option is available, either out of box or through any tool?

The other point is that typically out of all AMC products, only AEM has Java code along with JS, CSS, etc, but all other AMC products have just JS or just configurations.

If it is JS, it could be stored in a source code control system, like SVN, how to version configurations?

Also, how to move configurations to higher environments automatically, given that they are not stored in SVN?

In the absence of automatic deployments options, do we have to manually configure?

Appreciate your support.

Thanks,

Rama.

[Vipul_Raghav]

Hi Rama,

Such functionality is not available OOB.

Certain external vendors have developed a custom solution for integrating with SVN and Visual Source Safe.

Movement of entities are done via packages and you will have to employ practices to ensure such packages are validated and approved through internal processes before migrating to the higher environment.

Regards,
Vipul

[AEM_Forum]

Appreciate your very informative reply Vipul.

1. Typically what does a package contain?

a. Code

Java/JS/CSS/RDBMS Stuff like Stored Procedures/Triggers?

This is all code.

b. configurations: If we do any configurations in the product, how to package and deploy them in other instances?

2. How to create and deploy packages? Using AC UI?

Thanks,

Rama.

[RamaRajesh]

Data packages let entities of the Adobe Campaign database be displayed via files in XML format.

Each entity contained in a package is represented with all of its data.

The principle of data packages is to export a data configuration and integrate it into another Adobe Campaign system.

Below is the diagram for packaging:

You can also find the documentation at Data packages

[AEM_Forum]

Hi,

1. So, when we say a package, it consists of Core Package, Security Package and Application Package?

2. A combination of all these three packages is called a "Data Package"?

3. So, this contains not just data from RDBMS, but also the configurations done in AC?

4. We use Package export wizard UI to create packages and Package import wizard UI to import packages?

Please confirm.

Appreciate your support.

Thanks,

Rama.

[RamaRajesh · Accepted solution]

Hi,

The package export wizard is accessible via the Tools > Advanced > Export package/Import Packagae... menu of the Adobe Campaign client console. There are three types of exportable packages:

• User package: it enables you to select the list of entities to be exported. For example: Export all recipients with average purchase amount>$50
• Platform package: it includes all added technical resources (not standard): schemas, JavaScript code, etc. Example: Exports the forms and schemas in your namespace.
• Admin package: it includes all added templates and business objects (not standard): templates, libraries, etc. Example: Campaign templates, Delivery templates, libraries etc.

I hope all your questions are answered and the other information about data packages can be found at the link provided in my previous comment.

Thanks,

Rajesh