cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading from 2205 to 2211 how to upgrade web services extension

djboyd4715
Participant

background

A SI did an upgrade of our 6.4 to 2205.  With that many things were carried forward because they worked.  ie. our current webservices extension ( which looks to have been generated from ycommercewebservices )

We are now in the process of moving to 2211 and I want to redo a few things as we will be moving away from the accelerator to a headless cms solution ( not spartacus ).  One area is the webservices.

Is there an "upgrade" path for this older webservice extension to use yocc - or do I just need to create a new extension based on yocc and then "move" over items that were customized in the old extension?

My understanding is that in 2211 there is

ywebservice - a simple template that allows one to create their own webservices 

yocc - used to extend the OOTB webservices which are build on the MVC pattern

 

View Entire Topic
adamreisberg
Active Participant

Hi @djboyd4715 

In order to move away from ycommercewebservices, you have three (3) key areas:

  1. commercewebservices - this is the OCC V2 API layer for SAP Commerce Cloud (and recommended solution for replacing non-customized components of ycommercewebservices) It is a default set of commerce APIs, of which you can view the available APIs offered here - Commerce Webservices API docs. Do note that the OCC V2 APIs are authenticated by OAuth2 and have a defined URL path of "/occ/v2". 
  2. yocc - this is the template extensibility layer for Commerce Web Services (commercwebservices). This method can typically add additional APIs to the "/occ/v2" endpoint (and in some cases replace). Use this if you want to have new endpoints on OCC V2 APIs or replace (in some specific cases) the commerce web services. This leverages the OAuth2 authentication layer of commercewebservices.
  3. ywebservices - this template extensibility is used when you need a distinct endpoint from the "occ/v2" (e.g. defining a different endpoint in CCV2 for IP Filter Sets), need a different authentication layer (not OAuth), and have custom needs. Different authentication can be applied to extensions generated by these endpoints. I do not recommend replicating "commercewebservices" endpoints via a custom ywebservices generated extension.

In summary:

  1. Leverage OOTB OCC V2 endpoints from "commercewebservices"
  2. Customize (add - and sometimes replace) endpoints using "yocc"
  3. Roll your own with "ywebservices" if you have specific use cases where you cannot use "OCC V2" or "OAuth2"