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 ajo architectural 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 — covering both the profile store and the ajo relational store used for orchestrated campaigns what gets deployed profile track identity namespaces (customerid, planid, productid) standard xdm field groups, descriptors, and schemas enabled for profile catalog datasets enabled for profile merge policies and audiences profile data for three sample datasets depeche mode (traits + events), stranger things (traits), and decisioning (traits) relational track the customerid identity namespace 11 relational xdm schemas with primary key, foreign key, and version descriptors 11 datasets enabled for ajo orchestrated campaigns 11 dataflows loading data from the data landing zone note end to end deployment takes about 2 hours 23 minutes the profile and relational tracks run in parallel, and most of the time is unattended wait time that the cli enforces automatically prerequisites license entitlements administrative privileges for an ims org with real time cdp (w/streaming segmentation) and adobe journey optimizer (w/orchestrated campaigns) access rights an 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 both adobe experience platform api and adobe journey optimizer 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 120 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 both experience platform api and adobe journey optimizer api scopes (e g cjm suppression service client delete, cjm suppression service client all, 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 ajo architectural foundations menu from the main menu, select ajo arch foundations there are six steps split across two tracks profile track (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 depeche mode, stranger things, and decisioning profile data wait 60+ minutes after step 1 3 check profile health validates that all profile data loaded correctly wait 15+ minutes after step 2 step 1 takes about 2 minutes, step 2 about 6 minutes tip step 2 is safe to re run if something fails — it overwrites existing traits and skips duplicate events relational track warning the sandbox must have been in a "ready" state for at least 120 minutes before you run step 4 or step 6 step what it does before you run it 4 create relational base creates the customerid namespace and relational schemas/descriptors/datasets sandbox "ready" for 120+ minutes 5 load relational data uploads 11 csv files and creates the dataflows that load them runs right after step 4 — no manual wait needed 6 deploy relational base & data combines steps 4 and 5 into a single 5 minute run sandbox "ready" for 120+ minutes tip use step 6 instead of running steps 4 and 5 separately — it does the same thing in one pass with the propagation wait handled for you important all wait times above are checked automatically by the cli if you run a step too early, it will block and tell you how long to wait troubleshooting warning profile 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 warning relational data load fails partway through each api call retries up to 3 times if it still fails, cleanup removes the source connections, target connections, and dataflows it created so you can re run step 5 (or step 6) cleanly mapping sets can't be deleted through the api and may be left behind — this doesn't affect redeployment 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