Main features of cmemc include:
- List, edit and check configurations.
- List, create, delete, inspect datasets as well as dataset resources.
- List, import, export, delete or open graphs.
- List, import, export, create or delete Build projects.
- List, execute, replay or open local and remote SPARQL queries.
- List, install, uninstall, import and open vocabularies.
- List, execute, open or inspect workflows and workflow schedulers.
- Import or export whole Build workspaces and graph stores.
- List, get or inspect server metrics.
In order to start working with cmemc, follow one of the installation options.
The following pages provide documentation for specific cmemc related topics:
Installation and Configuration — cmemc can be installed using the python package from pypi.org / the release package or by pulling the docker image.
Certificate handling and SSL verification — In a reasonable production deployment, all client-accessible Corporate Memory APIs will be securely available as HTTPS endpoints. This document clarifies how to deal with certificates.
Environment based Configuration — In addition to configuration files, cmemc can be widely configured and parameterised with environment variables.
File based Configuration — This page documents how to configure cmemc via configuration files.
Getting Credentials from external Processes — This page discusses how to avoid passwords in configuration files by using configured credential processes or environment variables.
Command Reference — This document lists the help texts of all commands as a reference and to search for it.
Troubleshooting and Caveats — This page lists and documents possible issues and warnings when working with cmemc.
Using the docker image — In addition to the stand-alone cmemc binaries from the distribution package, the pypi or the brew based installation, you can use the eccenca cmemc docker image which is based on the official debian slim image. This is especially needed when you want to use cmemc in orchestrations.
Workflow execution and orchestration — In some cases, you need to automate a complete graph of integration workflows which depend on each other and can sometimes run in parallel or after each other.