The JECIS API is the foundation of the JECIS commerce platform. It is an API that is JSR 283 compliant and follows the same principles and standards as any JCR Content Repository API.
JECIS can run its own JCR Content Repository or can be added to any existing, JSR 283 compliant content repository. Typically JECIS will use its own workspace "jecis". But it's of course also possible to create commerce content in an existing workspace, like e.g. the default workspace "default".
The JECIS API also has a REST communication feature. This allows interesting system configuration concepts that run JECIS repository outside of an existing CMS module. Using JECIS REST it's possible to run JIM as a CMS module accessing JECIS content remotely.
JECIS relies on its own name space and custom taylored node types. These node types ensure high performance results when searching for distinct commerce content. It is also in preparation of the new Oak pre-indexing concept to improve performances.
Developers will not need to study and incorporate these node types. The JECIS API encapsulates reading and writing commerce content behind easy-to-use Java classes. Nevertheless it's of course also possible to use JCR API functionality to search and retrieve commerce nodes and properties the traditional way.
The content structure of JECIS takes full advantage of the benefits of a hierarchical content model. Below the root node /jecis are the Store nodes and below the Store nodes are all the content nodes relevant to that specific store.
In addition the commerce content is structured into content sections, e.g. products, clients, shipping, taxes, etc. Most of these content structures are identified by their own node types.
The benefits of this concept:
► Scalability — Authors can define "unlimited" amount of stores, products and more without needing any engineers to model the content structure.
► Expandable — Developers can extend the content structure with custom nodes and properties whenever needed. There are no limitations to the content structure, like e.g. with RDBMS driven systems.
► Performance — The nature of the node-types allows not only granular indexing, but also very fast retrieving of specific content. In addition, developers can create their own content functionality using either the JECIS or the JCR API.
► Independent — You are not locked into a proprietary system. Although JECIS and JIM are proprietary API solutions, the content itself is based on the JCR 283 content repository standard.