With Intershop 7/Intershop Commerce Management, the relational database system is used to store data whenever a transactional access or search capability is required. As a rule of thumb, all business data and some of the system configuration data is stored in the relational database system. Access to the database system happens primarily via the object-relational mapping mechanism of the ORM engine, which internally uses the native client drivers to access the database server.

Currently, Intershop 7/Intershop Commerce Management support Oracle database systems only.

DBInit is a tool for initially creating the database schema objects and for preparing the database content of one or more Intershop 7/Intershop Commerce Management cartridges. It is not designed to migrate the database content and structure (see DBMigrate).

DBMigrate is a tool used to migrate the database content and the database structure of an Intershop 7/Intershop Commerce Management installation from a defined previous release to an installed current release. It defines one global migration process, which can be executed in different environments. DBMigrate reuses some recurring migration steps (e.g., table creation), supports different development teams to create their own migration processes, and can minimize the effort to upgrade the development environment.

to render something nonexistent, to eliminate an object, irrespective of its context

Note: sometimes "deletion" moves objects, e.g., products, to a recycle bin from where they can be recovered

In Intershop 7/Intershop Commerce Management, dependency injection is the preferred approach for accessing implementations of manager and provider interfaces. Intershop 7/Intershop Commerce Management support the dependency injection via the Guice framework. This enables type-safe binding of implementations to interfaces, simple injection of members, and makes it possible to remove static singleton access from the code.

As opposed to the component framework, which specifically supports Intershop's development artifacts, the dependency injection framework is easier to use and standard compliant.

Generally, dependency management (or dependency injection) is a software design pattern in which one or more dependencies (or services) are injected, or passed by reference, into a dependent object (or client) and are made part of the client's state. More specifically, it refers to the approach for accessing implementations of manager and provider interfaces.

• In Enfinity Suite 6, this mechanism relied on the naming manager.
• In Intershop 7/Intershop Commerce Management, the naming manager was replaced by the dependency injection framework and the component framework.

a container for all kinds of implementation artifacts that are to be "deployed" ("set up") upon installing the software, may be a cartridge (as a result of a build process) or any other software component required to run Enfinity Suite 6/Intershop 7

The specific type of deployment of Intershop Commerce Suite tailored to meet specific business needs. Intershop offers three basic deployment models:

• Intershop Commerce Suite Cloud
• Intershop Commerce Suite Managed
• Intershop Commerce Suite Enterprise

Development artifact refers to the source code files that make up Intershop 7/Intershop Commerce Management. Development artifacts include

• cartridges (containers for all other programming artifacts)
• Java code (persistent objects, business objects, providers, managers)
• pipelets and pipelines
• ISML templates
• pagelets
• queries
• webforms

as well as other individually "tangible" resources like, for example, extension points. Development artifacts are created, modified, debugged, built, and tested using Intershop Studio.

Intershop provides several development tools packaged in cartridges. Once integrated into the development environment, these development cartridges allow to:

• dev_organizationinfo: explore the organization structure of an Intershop 7/Intershop Commerce Management installation
• dev_basketinfo: view all available basket calculation data that is created by a checkout process of a single session
• dev_lilith: view log messages from different sources in a single UI and apply filters to search for log events that match certain criteria
• dev_apiinfo: view all available basket and order calculation data accessible via the new payment API; extendable for custom API implementations

The generic term "development tool" refers to software applications or helper programs that provide comprehensive or specific facilities to computer programmers for software development. In the context of Intershop software, the development tools include

• Intershop Studio
• development cartridges

As opposed to master data, dynamic data denotes information that is asynchronously changed as further updates to the information become available. In the business context, this may refer to orders, payments, stock information, etc.