Deployment Instructions

deployment instructions note this is only required if you're working through the labs at your own pace if you're in a live training course or event, your sandbox has already been deployed for you the aep foundations lab pack is deployed to your sandbox using the dep cli, a command line tool that creates the schemas, datasets, dataflows, and sample data you'll use throughout the labs what gets deployed 4 identity namespaces 1 schema class, 13 field groups, 10 schemas 12 identity descriptors, 6 relationship/reference descriptors, 3 friendly name descriptors 10 catalog datasets 1 http api source connection and 10 dataflows profile data a single depeche mode profile (3 trait datasets, 7 event datasets) plus 3 lookup datasets 2 profile merge policies and 1 audience (any event streaming, within the hour) note end to end deployment takes about 2 hours 24 minutes, most of which is unattended wait time between steps the cli enforces these waits automatically, so you don't need to time anything yourself prerequisites license entitlements administrative privileges for an ims org with real time cdp (w/streaming segmentation) access rights an adobe experience platform role with all permissions on the target sandbox including the api credential you created from the developer console setup steps developer console credentials a project that includes adobe experience platform api's if you don't have these yet, follow developer console setup first a sandbox empty, of type dev and in a "ready" state for at least 60 minutes before you start deployment node js any recent lts version, on windows or mac 1\ install the cli clone or download the dep cli repository https //github com/adobe/dep cli from the dep cli directory, run npm install start the cli with npm start note node js is required before you run the commands above if you don't have node js installed yet, see the wiki's node js setup https //github com/adobe/dep cli/wiki/nodejs setup page first for full install details, including screenshots and how to update an existing install, see the installation https //github com/adobe/dep cli/wiki/installation wiki page 2\ configure your environment file the cli deploys to whichever sandbox your environment file points at, so this has to be set up correctly before you run anything copy envfiles/sample env json and give it a new name, e g my env json open the file and fill in the following fields using the values from developer console setup field value api key client id client secret client secret ims org organization id scopes must include experience platform api scopes (openid, session, adobeid, read organizations, additional info projectedproductcontext) sandbox name the sandbox you're targeting — must be empty and of type dev save and close the file tip you'll be prompted for this file's name each time you run a cli command, so you can reuse it across every step below 3\ run the aep foundations menu from the main menu, select aep foundations there are three steps, and they have to run in order warning the sandbox must have been in a "ready" state for at least 60 minutes before you run step 1 step what it does before you run it 1 create profile base deploys identity namespaces, schemas, datasets, merge policies, and audiences sandbox "ready" for 60+ minutes 2 load profile data creates dataflows and streams profile and lookup data wait 60+ minutes after step 1 3 check profile health validates that all data loaded correctly wait 15+ minutes after step 2 step 1 takes about 2 minutes to run, step 2 about 6 minutes, and step 3 is a quick validation with no wait of its own the 60 and 15 minute gaps between steps are for aep to finish propagating data behind the scenes — that's most of your 2 hour timeline important the cli checks these wait times automatically if you run a step too early, it will block and tell you how many minutes remain — you don't need to track the clock yourself tip step 2 is safe to re run if something goes wrong it overwrites existing trait records and skips duplicate events troubleshooting warning health check fails with missing events some profile data hasn't finished propagating yet wait another 15 minutes and re run check profile health if it still fails, re run load profile data, wait 15 minutes, and check again something else looks wrong as a last resort, you can reset the sandbox from the cli's sandbox management menu and redeploy from step 1 warning resetting a sandbox is destructive the cli will ask you to type the sandbox name to confirm before proceeding