--- sourceDocument: Yokohama Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Configure Pipelines and Deployments # Configure Pipelines and Deployments {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Use the App Engine Studio (AES) Pipelines and Deployments guided setup to step through the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation. ## Before you begin Role required: admin ## About this task The Pipelines and Deployments guided setup provides a sequence of tasks that help you configure Pipelines and Deployments on the ServiceNow AI Platform. For more information on each task, see [Pipelines and Deployments configuration tasks](https://servicenow-prod.fluidtopics.net/gJNQeEQR7akNKSuuPulu6A "As you work through the Pipelines and Deployments guided setup, you must perform different configuration tasks on each of your instances."). For general information about guided setup, see [Using guided setup](https://www.servicenow.com/docs/access?context=guided-setup&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). ## Procedure 1. Navigate to AllApp EnginePipelines and DeploymentsGuided Setup. The landing page provides information on the different categories, tools, and user access. Figure 1. Pipelines and Deployments guided setup landing page 2. To initiate guided setup, select Get Started. The Pipelines and Deployments Guided Setup category page provides a list of different categories of tasks you must complete before you can use Pipelines and Deployments. Note: If you have previously started any of the guided setup tasks, and then exited without completed them, the Get Started button will be labeled Continue. Figure 2. Pipelines and Deployments guided setup category page Important: Please be aware that each of the categories of tasks shown here are to be performed on different environments in your pipeline. 3. Select the first Get Started button to begin performing configuration tasks on your production environment. 1. [Configure environment credentials](https://servicenow-prod.fluidtopics.net/CCPrlOlA6ZBzrRybt87iWg "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://servicenow-prod.fluidtopics.net/hJxuurdVY0ikEtekdvTA3Q "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://servicenow-prod.fluidtopics.net/pf60saxjyuGV0COpGEa7jA "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://servicenow-prod.fluidtopics.net/dtM3thE6B5fF7VJQ~5o70w "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://servicenow-prod.fluidtopics.net/BAC_keCgP82NJNDV1YEdxg "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://servicenow-prod.fluidtopics.net/nt7Iq251aDI3b0cM3alwgw "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://servicenow-prod.fluidtopics.net/P_PZM80pYJRLXAgaGt4NKA#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."). {#config-p-and-d__ol_cc1_vjr_yxb} When you have completed all of the tasks in this category, the Guided Setup screen reappears. 4. Select the next Get Started button to begin performing configuration tasks on your testing environment. 1. [Configure environment credentials](https://servicenow-prod.fluidtopics.net/CCPrlOlA6ZBzrRybt87iWg "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://servicenow-prod.fluidtopics.net/GyaTyaBJjFilz0QcAFAv0g "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://servicenow-prod.fluidtopics.net/sqZc6ltzwTFENVTJ83gPMg "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://servicenow-prod.fluidtopics.net/cKDbfiKQi3wb2j3g4WmMOg "The Automated Test Framework helps you ensure the integrity of your instance by enabling the creation and execution of automated tests following any changes."). 5. [Configure Instance Scan suite](https://www.servicenow.com/docs/access?context=hs-landing-page&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US). {#config-p-and-d__ol_lt1_14r_yxb} When you have completed all of the tasks in this category, the Guided Setup screen reappears. 5. Select the last Get Started button to begin performing tasks for all of the other non-production (that is, test, development, staging, and so forth) instances in your pipeline. 1. [Configure environment credentials](https://servicenow-prod.fluidtopics.net/CCPrlOlA6ZBzrRybt87iWg "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://servicenow-prod.fluidtopics.net/GyaTyaBJjFilz0QcAFAv0g "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."). {#config-p-and-d__ol_umj_k4r_yxb} Congratulations! You have completed guided setup for the Pipelines and Deployments application. * **[Pipelines and Deployments configuration tasks](https://servicenow-prod.fluidtopics.net/gJNQeEQR7akNKSuuPulu6A)** As you work through the Pipelines and Deployments guided setup, you must perform different configuration tasks on each of your instances. *[\>]: and then