SAP Commerce Cloud
FormerlySAP Hybris Commerceuntil 2018
SAP's commerce platform, once Hybris: a Java platform extended with extensions, ImpEx and its type system, run by SAP as SAP Commerce Cloud, with the composable storefront in front of it. The product behind the SAP Commerce door: what is entered there is the tooling that reaches into or builds on an instance, and the product itself is not an option.
Where it sits
Connected from
data, HTTP, outbound. Its tools read the type system, Spring beans, configuration properties, cronjob status, the local console log and FlexibleSearch results out of a running instance through the Hybris Administration Console.
Functional boundary
Not for production: the README states local and development instances only, and the server refuses a HAC URL whose host is not private unless `HAC_ALLOW_REMOTE=true` overrides that guard. Masking applies to `config_get` only, so `logs_tail` and `monitoring_info` output, thread dumps included, is unmasked and may carry sensitive data, and whatever a tool returns goes to the MCP client and its model. Certificate checks are disabled whenever `HAC_INSECURE_TLS=true` is set, which the README names as typical for local HAC.
data, outbound. One of its three utility scripts, query-items.sh, runs a FlexibleSearch query against a running instance through the Hybris Administration Console; the reference guides and templates reach nothing themselves.
Functional boundary
Not for a project below the 2211-jdk21.1 baseline: older releases and the JSP Accelerator are covered only as explicitly marked legacy material, so a JSP storefront or a pre-JDK-21 platform is outside what the guides are written against. Knowledge with reach only through one script — it can tell an agent what to write and, apart from `query-items.sh`, cannot let it read what a given system contains.
Details
Graph
For your agent
- Ref
external:sap-commerce-cloud- JSON
- /externals/sap-commerce-cloud.json
- MCP
- Connecting an agent