Overview
When a new session starts, this enricher extracts the referring URL from the request's HTTP header and persists this information as a node associated with the Session node.
Events
The front-end entered event, stored in the Context service, triggers the Referer Enricher. This enricher extracts the value of the referer attribute in the event's HTTP headers.
| Triggered by Schema | Payload schema | Payload example |
|---|---|---|
context/commerce/SessionStarted | Schema | Example |
The Referer Enricher draws an edge between a Session node and the RefererURL node in the graph database as shown, indicating the URL from which the user arrived at the current resource location. For more information, see the Secure Graph service documentation.
| Node or Relation | properties |
|---|---|
nodes/commerce/RefererURL | referer |
commerce/Session/commerce/RefererURL/marketing/HAS |
Metamodel
Enrichers react to one or more schema events. A schema event references a context, a node, an edge, or a property; for example, a keyword search context, the creation of a new product node, the update of an edge between product and cart nodes, or the update of an edge property. In response to a triggering schema, the enricher retrieves the complete event data from the context service, enriches this data, and updates the graph accordingly. Enrichers can only affect their declared schemas in the graph.
The following interactive graphic displays the schemas that invoke this enricher and the schemas the enricher can affect in the graph.
To zoom in and out of the image, use the scroll wheel on your mouse. To pan the image, click on the background and drag.
Glossary
| Term | Description |
|---|---|
| authorization | The process of determining whether a given microservice has permission to gain consent. |
| consent | Permission to access (read, write) specific profile data, for example, permission to read/write age estimation or physical address. Some consents can be toggled by the consumer, other consents can be toggled by the tenant. |
| consent class | A string alias, defined by developers, that references a set of profile data (also called "schemas") for which consent can be granted and revoked. This string is exposed to users (consumers and tenants) as a reference through which they control consent. For example, the consent class "Purchases" might reference a set of data that includes items purchased, purchase dates, and purchase prices. Toggling consent for "Purchase" would enable and disable consent for that entire set of data. |
| consent reference | A unique, randomized string that serves as a passcode to decrypt data associated with one or more schemas. Various service calls require a consent reference. |
| consumer | The end user whose actions yield profile data in the graph. A profile describes a single consumer. |
| context | Data that affects the state of the graph. This data can be collected from consumer-triggered events or from third-party sources such as weather stations. |
| context repository | A temporary cache for adapted context data, before it is further processed by enrichers and persisted in the graph. |
| context service | An internal microservice that manages the insertion of, and the retrieval of, context data in the context repository. |
| encryption key | A unique, randomized string used to encrypt and decrypt specific data in the graph. Each data element is encrypted with a different encryption key. Decryption, using this key, is required to access, view, and alter the data. |
| enricher | A microservice that retrieves data from the Context Repository and/or Graph, possibly alters or extends it, and then persists data in the graph. An enricher can interpret data points, or sets of data points, to yield new data to persist. For example, an enricher can interpret purchasing data and contemporaneous weather station data to yield new data indicating that the consumer is a rainy-day shopper. |
| graph | The database that stores profile data as nodes, edges, and properties, and allows semantic queries. |
| package | A developer-defined bundle of microservices. A partner, team, tenant, or another package can subscribe to a particular package to access the functionality of those bundled microservices. |
| profile | Data about a single consumer, collected and derived from events that are triggered by, or are logically associated, with that consumer. |
| schema | A string representation of a path in the graph that represents an abstraction, rather than a concrete instance, of a particular data structure. |
| subscription | A relationship between an actor (a tenant or a team) and a package, wherein the actor gains access to the functionality of that package. |
| tenant | A registered entity with a shared commercial goal that subscribes to SAP Hybris Profile services and packages to reach that goal. A tenant can also develop and contribute enrichers and context adapters to the SAP Hybris Profile suite. Within YaaS, a tenant is a project. |
If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.
Use our private help channel. Receive updates over email and contact our specialists directly.
If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.