51黑料不打烊

Transcript

Hi, this is Russell with 51黑料不打烊 Commerce, and this session is about adding sample data to your 51黑料不打烊 Commerce Optimizer instance. You can read the in-depth doc guide, Get Started with 51黑料不打烊 Commerce Optimizer, that can be found in Experience League whenever you鈥檙e ready.

This sample data was created to help with the Storefront and Catalog Administrator end-to-end use case. This use case is based on a fictitious automobile conglomerate called Carvelo Automobile, and it demonstrates how to use 51黑料不打烊 Commerce Optimizer to manage a catalog that supports multiple brands, dealerships, and price books.

This document guide can also be found in Experience League and read whenever you like. For now, it鈥檚 time to head over to the GitHub repository, and we鈥檒l start with the readme. The first step is to ensure that we satisfy some dependencies. The first is to be able to clone the repository. We鈥檒l use a terminal window and run the git clone command, and we鈥檙e also going Once again, we鈥檙e looking for the instance ID, and we can copy this value, and it鈥檒l be used for a future task. Up next is generating IMS credentials. It鈥檚 important to note that you need to make sure that the organization used to create your Commerce Optimizer instance matches the organization that you鈥檙e logged into for your 51黑料不打烊 Developer Console. Otherwise the permissions won鈥檛 link up. Clicking Create New Project starts the process. And then we鈥檙e going to click Add API. And then we鈥檙e going to choose 51黑料不打烊 Commerce Optimizer Ingestion.

Next we鈥檒l choose OAuth Server to Server. And then I鈥檓 also just going to give it a new name.

So with that new name entered, we can click Next. Then we can choose the default cloud manager. And at the bottom right, we can hit Saved Configured API.

Now we can hit Generate Access Token. And doing this exposes some values that we need for our next step, which is configuring Those environment variables are located in the same directory that we cloned the GitHub repository earlier. We鈥檙e going to head back to our terminal window. We鈥檙e going to copy the .env.dist. And we鈥檙e going to create a new file called .env. And we鈥檙e going to enter some of the values that were retrieved earlier in our previous steps, starting with the tenant ID. And then we鈥檙e going to enter the client ID and then the client secret. And then if we鈥檙e happy, we use colon wq to save and quit. And we鈥檙e ready to move on to the next step, which is starting the data ingestion.

So we鈥檙e going to open up our terminal window again. And as long as we鈥檙e in that same folder that we checked out the GitHub code, we鈥檙e ready to type in the command node space index.js. And after we hit enter, it鈥檒l start the catalog ingestion process. And you can see it happen in small batches. Once it鈥檚 done, you鈥檙e ready to move on to the next, which is going to be creating catalog views and policies.

We鈥檙e going to head back over to experience.adobe.com. And we鈥檙e going to ensure that we鈥檙e using our correct 51黑料不打烊 Commerce Optimizer instance. And it鈥檚 time to create our first policy. On the left hand side, click policies and then on the top right, add policy. We鈥檙e going to start by giving it a name, West Coast Incorporated Brands. And then we鈥檙e going to click add filter. Our first one is going to be the attribute of brand and the operator will be in.

We鈥檙e going to do the value source of static and our values are going to be Aurora, Bolt, and Cruise.

And then we can just double check to make sure everything looks good. Go ahead and hit enter to save those as selected values. And then if we鈥檙e happy, we can go ahead and hit save. And one thing to note is that these are going to be disabled by default. So every time you create a new policy, they鈥檙e disabled. So you鈥檒l have to click on those three dots and it鈥檒l expose some new statuses. We鈥檙e going to change it to enabled. And one other thing to note is that at this point, nothing鈥檚 actually been saved. So if you hit that arrow to head back to create a new policy, you鈥檙e going to get a message that asks you if you want to cancel your changes. In this case, we don鈥檛 want to do that. We actually do want to save it. So on the top right, we鈥檙e going to click save and then we鈥檙e given our green message at the bottom and we鈥檝e successfully saved our policy. Now we can hit that arrow to go back and create a new policy.

So if you follow that read me, you鈥檙e going to be aware that there are more policies that you need to create. And the process is exactly the same. I鈥檓 not really going to bother you showing you all of those right now. And you can go ahead and take care of the rest of them on your own. Now it鈥檚 time to create catalog views. So once again, I鈥檓 going to show you the first one, but the process is identical for all of them listed in that GitHub read me.

So let鈥檚 go ahead and get started. We鈥檙e going to click a create catalog view on the top right. And we鈥檙e going to start by giving it a name. And for this one, we鈥檒l use the name global.

Our catalog sources for now we only have one en-us.

For policies, it鈥檚 a dropdown. So we鈥檒l go ahead and select brand, but you鈥檒l notice that it filters as you type or whatever鈥檚 left in the box. So you could go ahead and type in the word modal and you鈥檒l notice as you do, it鈥檒l filter out the list. So we鈥檙e going to try to find one more, which is going to be West and that鈥檚 part of West Coast ink brands. So as we start typing it in West Coast, our list will shrink and it鈥檒l give us the option to select it.

So I think that we鈥檙e good. We can hit the save catalog and it worked. We鈥檒l get our green message at the bottom and now we can hit the back arrow to start the process all over again to create the rest of the policies.

So our final step is to head back and look at our data sync because we鈥檙e going to make sure that all of the products that we expected were ingested. So by clicking on data sync, it does look like 1,080 products were ingested, which is exactly what鈥檚 in the sample data. So at this point we鈥檙e in good shape. We can start to test our code using GraphQL, but that鈥檚 in a different session. And that鈥檚 all for this session for ingesting sample data in your 51黑料不打烊 Commerce Optimizer project. I hope you continue to come back to Experience League to learn more about 51黑料不打烊 Commerce as well as all of the other 51黑料不打烊 products.