|mail server||A mail server is a software that serves as an electronic post office for e-mail. Mails are exchanged between mail servers across networks. The mail server is built around agreed-upon, standardized protocols for handling mail messages and the content they might contain.|
|major release||A release of a software product with significant and incompatible changes to a previous version. The incompatible changes may include changed or removed APIs and fundamental changes in underlying technologies or programming concepts.|
|managed service framework||The managed service framework is a collection of standardized programming features provided by Intershop 7/Intershop Commerce Management to integrate third-party applications or external services easily via "adapter" cartridges. The framework also includes some standard back-office functionality for controlling integrated services.||Overview - Managed Service Framework|
|management context||Management context refers to the level in the organizational structure as set up in Intershop 7/Intershop Commerce Management, including organization, channel and application. Each management context has its own data repository and its own, individually assigned users who are allowed to access it.|
|management tool||In Intershop 7/Intershop Commerce Management, a generic name for all applications that provide functionality for business-relevant tasks, like product management, content management, order management, etc., or system-relevant tasks like monitoring, controlling, etc.|
Depending on the context, "manager" may refer to different concepts:
Generally, marketing refers to all means for communicating the values of a product, service or brand to customers, for the purpose of promoting or selling that product, service, or brand. In the context of e-commerce software, marketing refers to means that help to promote the web shop itself and to increase the shop's sales volume. In Intershop 7/Intershop Commerce Management, this includes
as well as technical means like SEO support or product data feeds to price comparison web sites and online marketplaces.
|Overview - Marketing|
|mass data cleanup|
In the context of Intershop 7/Intershop Commerce Management, mass data cleanup refers to operations for removing large amounts of web shop data from the database. To this end, Intershop 7/Intershop Commerce Management provide specific jobs that comply with the following important aspects:
|Overview - Mass Data Cleanup|
|master catalog||catalog defined from a master product repository, can be shared across individual channels|
|master component||In content sharing scenarios, content components that are created and maintained in the master content repository of the sales organization, to be distributed across channels|
|master content||content stored in the master content repository|
|master content repository||set of all content assets of a sales organization that can be derived into any available channel repository|
From a business point of view, master data is persistent, non-transactional data that defines business entities (or business objects).
For products, for example, the master data usually include ID/SKU, short description, long description, classification/categorization etc. For customers, master data include, among others, name, address, birthday, etc.
In addition to master data there are dynamic data.
|master page||In content sharing scenarios, pages that are created and maintained in the master content repository of the sales organization, to be distributed across channels|
|master product||product stored in the master product repository, can be shared across individual channels|
|master product repository||set of all products of a sales organization that can be derived into any available channel repository|
|master role||pre-defined role that must exist in all departments of the sales organization or partner|
|master slot||In content sharing scenarios, slots that are created and maintained in the master content repository of the sales organization, to be distributed across channels|
|master workflow||in Enfinity Suite 6 B2B and procurement models, an approval defined for the entire system, available for all departments and cost centers|
|media asset management||In the context of e-commerce software, media asset management refers to the centralized control of images, videos, and other digital content.||Overview - Media Asset Management|
|media object||in Enfinity Suite 6's CMC, file-based content items stored in the file system, of any format other than simple text (i.e., graphic or video files)|
Generally, a merchant is a business actor who trades in goods or services produced or delivered by others, in order to earn a profit.
From Intershop's perspective, a merchant is the sales organization that uses Intershop's software to drive its e-commerce initiative. With respect to the system operation, a merchant can either run the software on its own premises, or contract a hosted environment as a tenant.
Messaging refers to mechanisms for interprocess communication. In Intershop 7/Intershop Commerce Management, the messaging cartridge implements multicast messaging, used to send event messages inside an Intershop 7/Intershop Commerce Management cluster, as well as a framework for integrating external messaging systems, like JMS or JGroups.
There are four types of events that are distributed:
|Overview - Messaging|
|microprocessor||A microprocessor incorporates the functions of a computer's central processing unit (CPU) on a single integrated circuit (IC). Some computers can have more than one microprocessors; this is called multiprocessing. Some microprocessors have multiple CPU cores, this is called multi-core.|
|microservice||Microservices are an architectural pattern in computer software design, in which complex software is composed of small, independent processes that act together in order to fulfill a common goal. Microservices are self-contained units of functionality, which are largely decoupled, do a specific (small) task and communicate with each other using technology-agnostic protocols. This allows for a modular software design, leveraging continuous refactoring and releasing.|
Migration describes the process of changing systems, in order to change technology, data formats, replace software or move to other hardware.
At Intershop, a migration project with Enfinity Suite 6/Intershop 7/Intershop Commerce Management software, typically involves the following tasks:
|minimum order value|
Generally, it is advisable to define a minimum order value to avoid that the 3rd party expenses for the order fulfillment (acceptance and delivery) are higher than the turnover. It has to be considered if the minimum order value should apply on gross or net prices, inclusive or exclusive service charges.
In Enfinity Suite 6, Intershop 7 and Intershop Commerce Management, this value defines the minimum value that an order must reach for a promotion, additional payment costs etc. to become effective.
|minor release||A release of a software product that is still compatible with a previous version, but may include new or enhanced APIs, programming concepts or features.|
|mobile shop||Generally, a mobile shop is a type of online shop whose storefront application is specifically designed to be used with mobile devices.|
|module||A module is a functional part of Intershop Commerce Suite that is promoted individually. Modules can be inclusive functional units that may be activated and deactivated separately. Some modules are delivered as a part of the standard platform (e.g., Search and Navigation, PIM, Shopping Cart, Checkout, Promotions, WCM, etc.); other modules are positioned as extensions to the platform that must be purchased separately (e.g., Product Configurator, payment connectors, etc.) In addition, there are additional modules that may operate independently, like Intershop Commerce Advisor or Intershop Commerce Insight.|
|mounted catalog||in Enfinity Suite 6's catalog sharing, a shared catalog included into the current channel|
|multi-channel sales||Multi-channel sales is a concept to sell products directly to the public via more than one distribution channel/sales channel. |
Companies selling via different sales channels are called multi-channel retailer.
|multi-core processor||A multi-core processor is a CPU with two or more CPU-cores on the same chip.|
|multi-data center support||Multi-data center support refers to the possibility to distribute Intershop 7/Intershop Commerce Management clusters over multiple data centers in an active-active scenario. Each data center hosts one or more Intershop cluster(s) consisting of multiple Intershop Web Servers, multiple Intershop Application Servers, at least one Intershop Shared Files instance and a database instance. The Intershop clusters are synchronized with each other to support session failover between the data centers. Each cluster hosts several sites, whereby a site is only active in one data center. Oracle Streams is set up and used to synchronize transactional data between the databases in the data centers.||Overview - Multi Data Center Support|
|multi-tenancy||Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants). Multitenancy is contrasted with a multi-instance architecture where separate software instances (or hardware systems) are set up for different client organizations. With a multitenant architecture, a software application is designed to virtually partition its data and configuration, and each client organization works with a customized virtual application instance.|
|multi-vendor catalog||in (Enfinity Suite 6's) procurement models, a buyer catalog that consists of products from multiple suppliers|
|naming manager||In Enfinity Suite 6, the naming manager is a singleton that is responsible for the dependency management, i.e., for handling manager and provider classes. In addition, the naming manager provides a convenience method to look up PO factories from the ORM engine.||Overview - Naming Manager|
|navigation bar||navigation element in front end applications of Enfinity Suite 6, Intershop 7 and Intershop Commerce Management|
|never out of stock|
Never out of stock (NOOS) products belong to a basic assortment of the merchant that will be sold for a longer period. These products should never be out of stock for selling, that means never out of stock at the fulfillment center.
Other kind of products are seasonal products that are sold only within a certain time / season.
These terms are very common within the fashion industry.
Depending on this division in NOOS and seasonal products
|new customer||A new customer is a customer who placed the first order with a merchant. Usually the merchant defines a period of time during which a new customer is handled specifically (for example, gets special offers). After this time the customer will be treated as an.|
A newsletter is a publication that is sent out regularly by e-mail. It usually refers to a key topic, refers to upcoming events and/or current offers and is sent to customers or selected customer groups that have given their permission.
The handling of newsletters includes:
|NFR||see non-functional requirement|
In the context of continuous integration, a nightly build refers to a build process that compiles all system components that belong to an assembly. The produced output is supposed to be promoted through various integration and test stages in the artifact repository.
The nightly build is started usually at night when no code modification commits are expected and, consequently, no snapshot builds are triggered.
|Node Manager||The Node Manager is a standalone Java program that is used to control all application server processes in an Intershop 7/Intershop Commerce Management instance. The Node Manager starts, stops and (in case of abnormal process termination) restarts application server processes. In addition, it provides the communication interface for Cluster Management that is used for remote control purposes.|
Is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors or features.
Non-functional requirements are often called qualities of a system. Other terms for non-functional requirements are "constraints", "quality attributes", "quality goals", "quality of service requirements" and "non-behavioral requirements". Informally these are sometimes called the "ilities", from attributes like stability and portability.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.