Name: Creating a Workspace in Eclipse in SAP Commerce Cloud
Uploaded: 2021-2-15
Duration: 322 s
Description: This demo shows how to create an Eclipse workspace in order to develop in Backoffice Framework.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div>This demo shows how to create an Eclipse workspace in order to   develop in Backoffice Framework.<br></div></div></div></div>

Creating a Workspace in Eclipse in SAP Commerce Cloud

Hi, my name is Lily. In this demo, I'll show you how to set up an eclipse workspace. Then import the minimal set of extension projects required for back office development. First I'll open eclipse. A pop up window asks me to specify which workspace to launch. I don't already have an eclipse workspace to point to, but I can set up a brand new empty one right now as I browse. Then launch that as my workspace. When doing SAP Commerce development, it is not necessary for the actual extension files to reside within subfolders of a workspace folder. A workspace folder can simply manage all the workspace metadata, and merely track the locations and statuses of the actual files. The first thing I normally see in a brand new workspace is a welcome screen. I'll just close it right out to get it out of the way. I'll use eclipse as built in import functionality to import projects. A brand new workspace may have a project Explorer with special options which can be used for importing. But I'll just use the standard approach via the file import pull down menu. I am prompted to specify the type of import or select general, then existing projects into workspace. If I have trouble remembering that existing projects resides under general, I could always find it by typing a project into the filter text area. Then I'll click next to continue. Now I'll select the root directory. For example, the root of the project search to be the Hybris directory just inside my commerce suite base installation folder. After a brief file scan, I see a list of existing projects. By default, all found projects are pre-selected. I click on Select All, then select only back office, config and platform. One way to avoid a lot of scrolling is if I click on any entry. Now let's check box and start typing the first few letters of the extension project I want to locate. Then eclipse will scroll it into view. I'll make sure that the checkbox for copy projects into workspace is unchecked, so that my workspace does not contain duplicates of the actual files, it's merely keeping track of. I'll now click Finish. The imported projects now appear in the Project Explorer. I'll wait for the eclipse build to finish because I have projects build automatically turned on and I'll look for missing dependency errors. The best way to see the causes of such errors is via eclipse as problems view windows show view other general problems or locate media filter text. Once the Eclipse Workspace build completes, this version of SAP Commerce will show me one error missing required project audit report services. Your results may vary. Thus I'll import them as an extension or extensions required by the back office extension to get my eclipse workspace to build cleanly. Note this time I'll import by right clicking on the background of the Project Explorer. Then click import. The rest of the import process is the same as before. I'll deselect all. Resize slightly to force Rerendering. Pick one or more projects and click finish. This time, after building completes I'll get zero errors in the problems view. The warnings are generally coding style issues so I can ignore them later. In addition to this minimal set of out-of-the-box extensions I just imported, I can import any custom back office extension. It might be part of a module based on the Y Commerce accelerator template, named my whatever module back office or one of generated via agent XY gen based on the Y back office template. Name my custom back office. Either way, the custom back office extension will have a dependency on the out-of-the-box back office extension, which has already been imported into my workspace. In this module, I've shown you the back office comes out-of-the-box as an extension in the ACP Commerce Suite product. I walked you through how to install and configure the SAP Commerce suite, and I showed you how to get back office up and running. I also showed you how to set up your own development environment so that you can add your own customizations to back office. A detailed guide to writing your own back office extensions is available in the documentation. Creating a custom back office extension tutorial. Now you should be able to use your own back office installation to follow along with the following demonstrations and try out the various user interface features we discussed in this training. Thanks for watching.