Manual Setup

this is only required if you are looking to do this on at your own pace if you are in a training course or event this will have been already done for you ) lab assets deployed listed below are all the assets that are deployed as part of the deploy json package identity namespaces (4) schema registry classes (1) field groups (13) schemas (10) identity descriptors (12) relationship/reference descriptors (6) friendly name descriptors (3) catalog datasets (10) flow service source > http api (1) dataflows (10) > all using mapping sets profile store ( mailto\ depeche mode\@dep com ) 3 contributing trait based datasets (3 records) 7 contributing event based datasets (43 events) 4 lookup datasets | 22 records profile merge policies (2) default merge policy > system generated dep no stitch audiences (1) any event streaming (within the hour) event data spans up to 6 months in arrears based on the date of the deployment the date is dynamically generated as part of the deployment scripts the aep enviornment you deploy in must be part of a commercial license as non commerical environments have strict data retention requirements that are not supported with this deployment files to download you will need to download the following files to your local machine to install the lab assets to your individual sandbox installing via newman cli pre requisite software https //nodejs org/en/download/package manager/ installed https //learning postman com/docs/collections/using newman cli/installing running newman/ installed downloaded deployment files installation instructions install newman download the following files from the repository env manual deploy json > postman environment file deploy json > postman deployment collection health manual json > postman health collection configure you env manual deploy json file with the appropriate developer console project credentials and save it execute the deployment collection in newman using the following command newman run deploy json e env manual deploy json delay request 750 bail failure timeout script 4800000 when it completes wait 15mins and then execute the health json collection newman run health json e env manual deploy json delay request 750 bail failure there is a 1hr delay in the deployment execution to ensure that the control plane has had time to fully populate before data is introduced if you see failures with data missing you will need to try to manually resend it in or can brute force a sandbox reset and retry deployment a successful health check run will result in a totalfound count matching the totalexpected count this should be 137