--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development Release : - australia ft:locale : - pt-BR ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Configure # Configuring App Engine Studio and related apps {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura App Engine Studio (AES) guided setup walks you through the implementation process, one step at a time. As you finish each setup procedure, you're prompted to begin the next one. When you have finished configuring AES, you have the option of configuring other products related to AES: * App Engine Management Center (AEMC) * Application Intake * Pipelines and Deployments {#aes-setup__ul_nqq_swk_nsb} Each of these products has its own guided setup. If you have already configured one or more of the products and you are prompted to configure it again, you can simply ignore that instruction. The following diagram illustrates the preferred method for implementing AES and associated applications:Figura 1. AES implementation AES implementation usually follows these steps. 1. On a development instance, install AES and the Pipelines and Deployments plugin. For more information, see [Installing App Engine Studio](https://servicenow-prod.fluidtopics.net/gn35Xb5HaTn~fhsn1xHTEg "You can install the App Engine Studio (AES) application (com.snc.app-engine-studio) if you have the admin role. The application installs related ServiceNow Store applications and plugins if they are not already installed."). 2. Complete the AES guided setup. For more information, see [Configure App Engine Studio](https://servicenow-prod.fluidtopics.net/SnfLL0O0LtImuZVYBJbVCg "App Engine Studio (AES) guided setup provides a sequence of tasks that help you configure AES on your ServiceNow instance."). 3. On your production instance: 1. Complete the Application Intake guided setup. For more information, see [Configure Application Intake](https://servicenow-prod.fluidtopics.net/1erz2wJla0W8e6tmOP0~GA "Use the App Engine Studio (AES) Application Intake guided setup to step through the initial configuration of the Application Intake application. Detailed instructions for each step are provided in subsequent sections of the product documentation."). 2. Complete the Pipelines and Deployments guided setup. For more information, see [Configure Pipelines and Deployments](https://servicenow-prod.fluidtopics.net/cyoyYrjdGhH7FmbtbLgXWg "Use the Pipelines and Deployments guided setup to complete the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation."). {#aes-setup__ol_ez4_4gg_jvb} 4. On a development instance, complete the first non-production task of the Pipelines and Deployments guided setup. 5. On your test instance, install Pipelines and Deployments. 6. Complete both non-production tasks of the Pipelines and Deployments guided setup on the test instance. 7. In all the other non-production instances in your pipeline: 1. Install Pipelines and Deployments. 2. Complete the first non-prod tasks of the Pipelines and Deployments guided setup. {#aes-setup__ol_wrl_nhg_jvb} 8. Repeat step 7 across all non-production instances, as needed. 9. Install the AEMC plugin on each instance in your pipeline. For more information, see [Configure the App Engine Management Center](https://servicenow-prod.fluidtopics.net/o49h~ssIbBT2yAq8CU~MIA "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."). AEMC allows admins to manage app development from intake through production on your production instance. {#aes-setup__ol_jpd_3rf_jvb} Nota: If you plan on cloning your production instance to one or more non-production instances, you should also install the AES product on your production instance prior to cloning. For more information, see [Create a clone preserver](https://www.servicenow.com/docs/access?context=create-new-clone-preserver&version=australia&pubname=australia-platform-administration&ft:locale=en-US) and [Cloning instances with AES](https://servicenow-prod.fluidtopics.net/xw1WfLAjMFPT0cQhJfkRqQ "Learn how to protect the data, tables, and templates you've created in App Engine Studio when using System Clone to copy instances from production to non-production."). * **[AES and domain separation](https://servicenow-prod.fluidtopics.net/tiBDtj4HUfCyNbYeMNt79A)** Domain separation is unsupported for App Engine Studio (AES). Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data. * **[Installing App Engine Studio](https://servicenow-prod.fluidtopics.net/gn35Xb5HaTn~fhsn1xHTEg)** You can install the App Engine Studio (AES) application (com.snc.app-engine-studio) if you have the admin role. The application installs related ServiceNow® Store applications and plugins if they are not already installed. * **[Configure App Engine Studio](https://servicenow-prod.fluidtopics.net/SnfLL0O0LtImuZVYBJbVCg)** App Engine Studio (AES) guided setup provides a sequence of tasks that help you configure AES on your ServiceNow instance. * **[Cloning instances with AES](https://servicenow-prod.fluidtopics.net/xw1WfLAjMFPT0cQhJfkRqQ)** Learn how to protect the data, tables, and templates you've created in App Engine Studio when using System Clone to copy instances from production to non-production.