-
Notifications
You must be signed in to change notification settings - Fork 0
Home
[CoreMedia Content Cloud][contentcloud] comes in different flavours to integrate with different commerce systems like e.g. Salesforce Commerce Cloud. Additionally it is possible to use the CoreMedia connectors and APIs to integrate your custom commerce system.
This documentation and example code is meant to illustrate the way from the empty, stock systems on both sides to an integrated solution my means of a mock implementation.
In doing so we deal with four components:
- Your fictional Commerce System
- The CoreMedia Content Cloud System
- Fictional Adapter Module with e.g. Fragment Connector within the Commerce System
- Custom CoreMedia Content Cloud Extension for your Commerce System
As you can see, the bridge between the two systems rests on custom programmed parts in both systems. It is very unlikely that you will find sufficient parts and API in one of the both systems to leave out any of the components. Programming knowledge in CoreMedia Content Cloud and your Commerce System is essential.
The example codes does not deal with any specific commerce system and thus cannot show any details about the presentation layer there. What it does, is show the details of the Content Cloud catalog integration and a mock implementation of the APIs so that you have some parts running when dealing with the others.
To start building the mock or a bridge between the too systems you of course need those two systems as development instances installed and ready to use.
This means
-
A stock CoreMedia Content Cloud system with no customization
-
Your custom Commerce System
So the first essential step is to prepare such instances.
(The hardware requirements given in the CoreMedia manual apply here.)
This workspace with the mock extension only contains the CoreMedia Commerce Cloud side to demonstrate the integration.
The CoreMedia Content Cloud preparation for the development setup can be executed following the manual at
https://documentation.coremedia.com/
Since the commerce system will have to access the CoreMedia Content Cloud system and vice versa, the "remote setup" variant would be preferred for the Content Cloud integration or otherwise you will have to install all parts of the development stack on localhost, which is resource consuming.
Do a stock CoreMedia Content Cloud development installation before adding any custom codes to be sure everything is working and in place.
You may decide to switch off any of the modules you consider irrelevant for your use cases.
The CoreMedia Content Cloud workspace contains a deployment part where a simple development deployment can be achieved by using the deployment.zip artifact together with a modified single node JSON descriptor derived from the file.
The minimum modifications contain:
-
Location of the license files your received from the CoreMedia support team.
-
Hostname of the development system
...
"blueprint": {
"hostname": "my.content.cloud.host",
...
Be aware that this is not the fully qualified domain name for all CoreMedia
Content Cloud components but only the last part. So in this example e.g. the
studio will be accessible as studio.my.content.cloud.host.
Of course we cannot give any details here, but do a complete developer friendly setup and test all its parts before dealing with the integration.
Now that we have our development setup in place, we can go through the steps to build the integration.