Sneak Peek: New and Improved DXP ADEs

As an Optimizely MVP, we are sometimes given the first look at new features! In this case, we were told about a re-released DXP feature (which used to be the bane of my existence), called an ADE (Additional Development Environment)

Before I go into what this is and why this is amazing, feel free to nominate someone or apply to become an MVP here: https://world.optimizely.com/community/omvp/become-a-member/

What is an ADE? Why is it useful?

An ADE (Additional Development Environment) allows customers to add more integration environments to the standard sets of environments.

Sizable development teams and those who have a need to develop features in parallel before merging them into production can find themselves being constrained by the standard set of environments.

ADEs allows them more flexibility in their deployment pipeline by offering an indefinite amount of deployment environments. These environments can be re-used for other purposes as well, as they’re essentially a separate playground.

What is new?

In .NET Framework (CMS 11 and lower), an ADE was a separate DXP environment that was basically put somewhere in the ether, and did not connect to any other environment. There was no PAAS Portal or Development API integration. You would use Publish Profiles to deploy into the environment, and that is about it.

Since the launch of CMS 12, which is now a Linux-based Azure App Service, ADEs have not been available.

Based on the sneak peek from the product team, the new features are slated to include:

  • Support for the Deployment API
  • Support for content sync to and from other environments
  • Support for all quality of life features in the paasportal (database exports, application logs, purging CDN cache etc.)

ADE and the Deployment API

I have already updated my OptiCloud scripts to allow for deployment To and From the ADEs when they are re-released.

The naming scheme in the Target and Source Environment is as following for the ADE environments:

  • ADE#
    • ADE1, ADE2, ADE3…….ADE100

So the complete list of Target and Source Environments are:

  • Integration
  • Preproduction
  • Production
  • ADE#

Conclusion

This seems to be a HUGE win for those who need an ADE.

In a previous job, we had two (2) ADEs (in the old .NET Framework style), and it was a nightmare to manage.

As I said earlier, this is simply a sneak peek to these new-style ADEs. Keep an eye on the blogs from the product team for when these are ready!

Make sure to nominate someone or apply to become an MVP here to get insider information and a TON of other benefits: https://world.optimizely.com/community/omvp/become-a-member/

Default image
Eric Markson

Technical Architect @ Verndale | Optimizely MVP - Platinum | Optimizely Content Cloud SME - Platinum

Articles: 16

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.