In case you have commerce extensions based on legacy LiveContext APIs, you should upgrade them and make sure everything fits into the Commerce Hub architecture.

The CoreMedia Commerce Hub controls the communication of CoreMedia apps with commerce systems by defining a vendor agnostic API covering the most common eCommerce features and providing a default client-server implementation of this API.

The client part of the CoreMedia Commerce Hub is named generic client. The server part is named adapter service. Adapter services are vendor-specific extensions of the base adapter which itself defines the Commerce Hub API and serves as a runtime environment controlling the communication between generic client and commerce system.

There is no general How-to Guide or manual about how to migrate your extension code, because it depends a lot on your customization itself.

For example, if you are running a blueprint extension which adds commerce-specific links to your CAE, you should consider to move the commerce-related code to the commerce adapter. The CAE extension itself should never communicate with the commerce system directly. Instead, the generic client library runs in the CAE and reads all commerce link templates from the commerce adapter again and provides them to the CAE linkschemes.

To learn more about the Commerce Hub architecture in general, have a look at the reference manual Custom Commerce Adapter Developer Manual