| Term | Description |
|---|---|
| account | User"s identity represented by email address, which is the account identifier, and a password. |
| API proxy | A barrier that verifies access tokens, which are generated in the Builder, and communicates directly with a service. |
| authorization | YaaS uses the OAuth 2.0 Framework for authorization and authentication using access tokens, as described in the RFC 6749. |
| basepath | A unique part of YaaS URL, and first element in the URL path that distinguishes APIs provided by different organizations. For example, https://api.yaas.io/hybris/.../. |
| Builder | The key tool in YaaS used by both developers and businesses. Developers collaborate with it to build, manage, and publish packages, which are bundles containing services and Builder modules. Businesses use it to manage their projects, and the back end of the services to which they subscribe. The URL is http://builder.yaas.io. |
| Builder module | A user interface provided in the Builder to manage the back-office functionality. |
| Builder SDK | A command-line interface that you can use to create your own user interfaces to manage your services in the Builder. It enables you to run the Builder in develop mode so that you can implement Builder modules faster and more efficiently. |
| business service | A service that provides specific business functionality, such as products, loyalty, or orders. |
| client | An OAuth2 client application created within a project. After the tenant subscribes to a package that includes the client, it can access data from other tenants. |
| customer | A shopper that purchases products in the storefront. |
| Dev Portal | A centralized information hub with everything you need to know to build your own service or Builder module, including documentation, toolkits, and guidelines. The URL is http://devportal.yaas.io. |
| event | An event is YaaS is an instance of when something occurs, such as when an order is submitted. |
| index | A structured list of selected data from a collection that includes a low-level reference address, or the direct link to the set of data. Indices improve the speed and efficiency of retrieval operations on a collection. |
| Knowledge Hub | A centralized information hub for YaaS business users, with articles about new and updated features, training, cool uses of YaaS technology, and configuration guides. The URL is https://knowledge.yaas.io/. |
| mashup | A mashup service uses content from more than one source to create a single new service. |
| merchant | A person who runs a business and is responsible for selling goods for profit. |
| microservice | Small, isolated applications that are responsible for a single piece of functionality. |
| multi tenant | A software instance that serves multiple tenants. |
| YaaS organization | A YaaS organization either pays money, or receives money, through contracts. Each project that shares their packages, or subscribes to packages, is associated with one organization. |
| owner | The person who creates a project or registers a service or module within the Builder application. Owners have more rights than other members. It is also an authorization rule, which grants full access rights to a service, or Builder module. |
| package | A bundle of services and optional Builder modules. |
| profile | Data about a single consumer, collected and derived from events that are triggered by, or are logically associated with, that consumer. |
| project | An individual or collaborative project created and managed in the Builder, such as a storefront or video game. A project can use several packages or subscriptions found on the YaaS Market. |
| project ID | The identifier of your project in YaaS. In the Builder, retrieve it from the project"s Administration section. |
| RAML | RESTful API Modeling Language is a YAML-based language for describing RESTful APIs. |
| residence period | The timeframe after the end of the period when it is legally allowed to keep personal data, and before the actual data blocking or deletion of the data. |
| RESTful | A system that uses Representational State Transfer (REST). |
| retention period | The timeframe that personal data must be kept for any legal reason, after the initial data collection. For example, sales data that is retained for tax purposes. Access to personal data is restricted during the retention period. |
| SAP Partner | Partners are certified SAP professionals who can help you buy, build, implement, service, and support the SAP solution that best fits your unique needs. |
| scopes | The access rights to resources and operations in the service, such as product_manage which enables you to create and modify products. |
| service | A microservice running as a part of a hosted application on a server. |
| Service SDK | The Service Software Development Kit (SDK) provides helper modules so that you can work around any restrictions involved in running a service in the hybris cloud without having to make many modifications to the application itself. These helper modules are organized into libraries and plug-ins. |
| single tenant | A software instance that serves a single tenant. |
| storefront | The YaaS Storefront is a ready-to-use template that is integrated with the YaaS commerce service packages and other third-party services, such as search, payment, and tax services. It can be set up as a fully transactional storefront, or you can use the template as a starting point to customize your own features and functionality. |
| subscription | Subscriptions grant access to a specific package for a specific project in order to use the services bundled in that package. |
| techne | The design guideline and component library for YaaS. The URL for the techne website is http://techne.yaas.io. |
| tenant | A tenant is a group of users on a project sharing common access, with specific privileges to a service. |
| blocked data | Data that is no longer available for any type of processing, including the ability to read, write, or analyze. Blocked data is only available through restricted access for legal reasons. |
| token | YaaS uses the OAuth 2.0 access tokens, as defined in the OAuth 2.0 Framework: "a string denoting a specific scope, lifetime, and other access attributes". |
| user | Anyone with a YaaS account who therefore, can log into the Builder and the YaaS Market. A user can be invited to many projects, and have different user roles in each of those projects. |
| user roles | Each project or site can define user roles to perform different actions, such as an administrator role, versus a read-only role. |
| YaaS | YaaS stands for SAP Hybris [y] as a Service. |
| YaaS account | An individual account enabling access to the different areas of YaaS, such as the Builder, YaaS Market, or the Dev Portal. |
| YaaS Market | The site used to shop for and share new packages. The URL is http://market.yaas.io. |
| YRN | In YaaS, a global resource identifier is a Uniform Resource Name (URN) with a custom YaaS schema and is called a YaaS Resource Name, or YRN. |
No matching term found.
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.