---
sourceDocument: Xanadu Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/application-development

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Configure the App Engine Management Center

# Configure the App Engine Management Center {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Use the App Engine Management Center (AEMC) guided setup to step through the initial configuration of the Application Intake and Pipelines and Deployments applications. The Application Intake guided setup is optional, but if you want to use AEMC, the Pipelines and Deployments guided setup is required.

## Before you begin

Ensure that AEMC is installed on your production instance and all of your non-production instances (development, test, and the like).

Role required: admin

## About this task

Essentially, the AEMC guided setup contains the guided setup steps for both the Application Intake and Pipelines and Deployments applications. If you have already configured one or both of these applications, you can skip those steps of the guided setup.

## Procedure

1. In your production instance, navigate to AllApp EngineAdministrationGuided Setup.  
   The landing page provides information on the two applications that you must configure, Application Intake and Pipelines and Deployments.Figure 1. App Engine Management Center Guided Setup landing page
2. Initiate guided setup by selecting Get Started.  
   The App Engine Management Center guided setup category page provides a list of different categories of tasks that you must complete before you can use AEMC.Figure 2. App Engine Management Center Guided Setup category page  
   Note:  
   If you have previously started any of the guided setup tasks, and then exited without completing them, the Get Started button is labeled Continue.
3. Select the first Get Started button to initiate the Application Intake Guided Setup.  
   There are several [Application Intake configuration tasks](https://www.servicenow.com/docs/ed0v3Tp8PRAF8wN2n~zJjA "As you work through the App Engine Studio (AES) Application Intake guided setup, you must perform different configuration tasks.") you must complete.
   1. [Activate the Apply for Citizen Development catalog item](https://www.servicenow.com/docs/3rB7FhZBiwkkVQPJFOEAZQ "Enable citizen developers to submit their ideas for applications by activating the Apply for Citizen Development catalog item. This is the first step in configuring the App Engine Studio (AES) Application Intake app.").
   2. [Add users to the App Engine Admin group](https://www.servicenow.com/docs/zVFdt4J0pmTCV9Bqw_B1Aw "Add users to the App Engine Admin group in your production instance to give them administrative rights to App Engine Studio (AES). You must also identify a contact email address for the group. After you configure the email address of the App Engine Admin group, members can receive notifications for app development-related requests, including app intake requests.").
   3. [Create development environment records](https://www.servicenow.com/docs/KJGnd14h67iPi_VPE2mLDQ "Set up your App Engine Studio (AES) production and non-production (for example, development, test, and/or staging) environments by adding the URLs and credentials used to access each instance.").
   {#configure-aemc__ol_alg_2qb_yxb}When you've completed all of the tasks in this category, the Category screen reopens.
4. Select the next Get Started button to initiate the Pipelines and Deployments Guided Setup.  
   There are several [Pipelines and Deployments configuration tasks](https://www.servicenow.com/docs/CE8b_gVCp5pshadTDjqKdg "As you work through the Pipelines and Deployments guided setup, you must perform different configuration tasks on each of your instances.") you must complete.  
   On your production instance:
   1. [Configure environment credentials](https://www.servicenow.com/docs/ypK8EVpvKNqzG~lVc59teQ "Configure credentials in your production instance so that the flows used by the App Engine Management Center (AEMC) can access different instances.").
   2. [Configure your pipeline environments](https://www.servicenow.com/docs/KJGnd14h67iPi_VPE2mLDQ "Set up your App Engine Studio (AES) production and non-production (for example, development, test, and/or staging) environments by adding the URLs and credentials used to access each instance.").
   3. [Configure your pipeline](https://www.servicenow.com/docs/SyYBJ9Wsqd7qBn54Kh~Onw "Configure your App Engine Studio (AES) pipeline so that your administrator can quickly move an application from one environment to another.").
   4. [Add users to the App Engine Admin group](https://www.servicenow.com/docs/zVFdt4J0pmTCV9Bqw_B1Aw "Add users to the App Engine Admin group in your production instance to give them administrative rights to App Engine Studio (AES). You must also identify a contact email address for the group. After you configure the email address of the App Engine Admin group, members can receive notifications for app development-related requests, including app intake requests.").
   5. [Add ATF and instance scan suites for testing](https://www.servicenow.com/docs/bY7V6R2VPrwj1t_oYY30Zg "Add your customized test suites as part of an application deployment in addition to the instance scan and Automated Test Framework (ATF) testing suites that are standard in AEMC.").  
      Note:  
      You can add ATF and instance scan suites for testing only if you've already created them and set up your testing instance. If you have not done this yet, you must come back to this step.
   6. [Enable Change Management integration](https://www.servicenow.com/docs/5S_~Jx_A8HWaL2nYEWWDgA "Enable Change Management integration with AEMC so that deployments through the pipeline to the production environment are automatically scheduled based on the Change request state and planned change window.").
   7. [Configure properties to integrate Change Management](https://www.servicenow.com/docs/lBSCeDWfaVIAZaEn88oFZQ#configure-properties-integrate-cm "Configure predefined properties through the Pipelines and Deployments Guided Setup to tailor your Change Management and AEMC integration to your company's needs. Configuring these properties is optional.").
   {#configure-aemc__ol_wpg_vgc_yxb}  
   On your testing instance:
   1. [Configure environment credentials](https://www.servicenow.com/docs/ypK8EVpvKNqzG~lVc59teQ "Configure credentials in your production instance so that the flows used by the App Engine Management Center (AEMC) can access different instances.").
   2. [Configure your controller instance](https://www.servicenow.com/docs/cbza2jXjlsbcOOGrGhD_4w "You must identify one of the instances in your App Engine Studio (AES) pipeline as the controller instance. All communication between the instances in your pipeline, including the deployment order for applications in the pipeline, takes place in the controller instance.").
   3. [Enable Automated Test Framework (ATF) properties](https://www.servicenow.com/docs/P2Kw9DxmMCl_UTyd~Kw6uA "The App Engine Studio (AES) Pipelines and Deployments app includes an Application Test Framework (ATF) suite called the Application Deployment Test Suite. Two system properties control whether the test runs automatically whenever an app is deployed to a Test environment.").
   4. [Configure Automated Test Framework (ATF) suite](https://www.servicenow.com/docs/cP2Njdzlu6Zs5j5aasYMIg "The Automated Test Framework (ATF) enables you to create and run automated tests to confirm that your instance works after making a change. For example, after an upgrade, during application development, or when deploying instance configurations with update sets. Review failed test results to identify the changes that caused the failure and the changes that you should review.").
   5. [Configure Instance Scan suite](https://www.servicenow.com/docs/access?context=hs-landing-page&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US).
   {#configure-aemc__ol_a1m_phc_yxb}  
   On your other, non-production instances:
   1. [Configure environment credentials](https://www.servicenow.com/docs/ypK8EVpvKNqzG~lVc59teQ "Configure credentials in your production instance so that the flows used by the App Engine Management Center (AEMC) can access different instances.").
   2. [Configure your controller instance](https://www.servicenow.com/docs/cbza2jXjlsbcOOGrGhD_4w "You must identify one of the instances in your App Engine Studio (AES) pipeline as the controller instance. All communication between the instances in your pipeline, including the deployment order for applications in the pipeline, takes place in the controller instance.").
   {#configure-aemc__ol_trb_glc_yxb}  
   When you have completed the tasks in the second category, the Category page reappears. You have completed guided setup for App Engine Management Center.
5. **Optional:** Configure additional properties used to control system behavior in AEMC.
* **[Test App Engine Management Center functionality on a non-production instance](https://www.servicenow.com/docs/7XAUeI0dZ7GKamn193tSIw)**   
  Test App Engine Management Center (AEMC) on a non-production instance to confirm that everything is working as expected before moving to production.

*[\>]: and then