This section of the web-site explains the functionality of '1C:Enterprise 8.2
Managed Application' framework version.
For the first time 1C:Enterprise framework version 8.0 was introduced in
Spring 2004. Being an evolutionary development of version 7.7, the new version
implemented all technological and methodical practices
and experience accumulated by 1C Company through 13 years of business software
development.
The framework released had brought into reality the 'platform-based' approach
to development, customization, support and use of business applications.
As technologies kept on developing, as well as expectations and demands of
customers, later in 2006 1C Company released a new milestone version of the
framework – 1C:Enterprise 8.1.
This version implemented significantly improved scalability (server cluster
support, the capability to run on Windows or Linux systems, new database support
added – PostgreSQL® and IBM DB2®, etc), brand new
capabilities for information analysis and search, enhanced system administration
tools and more. At that, the new version did not have major differences in user
operation with the application, and therefore did not require additional
trainings for them.
And in 2009 a still newer version of the framework released –
'1C:Enterprise 8.2 Managed Application'.
'Managed Application' represents a fundamental change of 1C:Enterprise 8
architecture, the most significant one since its first release in 2004.
Inheriting all thewell-proven approaches from previous
versions to creation and execution of business applications, it introduces new
significant advantages, such as new user operation interface, new level of
scalability, reliability and performance.
There is a possibility to synchronize all these configurations to each other.
The final result should be present in the base configuration, which is used for
updating the database configuration for users to work with.
General Description of 1C:Enterprise 8 Framework
Architecture
1C:Enterprise 8 framework has a number of means, tools and mechanisms
defining a concept of quick creation of applied solutions – data structure
creation, form designing, programming business logic, creation of interactive
reports, etc. Presence of these mechanisms allows to correlate technologic
capabilities with a business scheme of development and introduction of applied
solutions. Certainly, on the one hand, they limit (and quite deliberately) a
developer’s freedom in the way he creates a solution, on the other – protects
him from designing and development mistakes and helps to get an operable
solution within quite short period of time, that can be later developed and
maintained by this or other developer, if necessary.
The key points of the framework to be emphasized here are that it provides
rapid application development (RAD) through isolation of a developer from
technologic details. At that, RAD ideology of the framework is used for creation
of business application, including the application business logic. For example,
when a developer creates a business application using universal means (such as
Delphi, or C++), he must take into account the database type it’s supposed to
interact with, take care of what tables should be created, with what fields in
them, of which types, how they should be linked with each other, which fields
should be indexed, how often, etc., etc. In case of creation of a business
application on 1C:Enterprise 8 framework, he just needs to understand what
business entity he wants (a document, such as invoice, or a catalogue, such as a
list of customers, etc.) and add the entity into the applied solution. The
framework automatically creates all relevant tables, types, references, dialog
forms, etc. Algorithmic programming is used for business logic only.
From point of view of technology, 1C:Enterprise 8 framework consists of the
following basic items (see picture):
The framework core including an execution environment and a set of basic
functions and business objects.
Embedded libraries of problem-oriented objects.
Application development tools.
The capability for on-going development and updating of
applied solutions.
General 1C:Enterprise 8 architecture
Such architecture provides the following unique characteristics:
The capability for RAD and their quick subsequent modification.
Maximum standardization of the design model and the business logic
of applied solutions.
Isolation of application developers from technological details.
Openness – final applied solutions are not like a black box, but
they can be understood by end-users or other developers.
The capability for on-site adaptation of applied solutions.
Algorithmic programming of business logic only.
Scalability of applied solutions.
The capability for on-going development and updating of
applied solutions.
Used terms
1C:Enterprise 8 – 'Framework' or 'Platform'?
1C:Enterprise – is a system of programs including a platform and a set of
applied solutions built on the platform for various areas of activity and
enterprise scales.
There are two main terms that 1C Company uses for 1C:Enterprise 8: 'platform'
and 'framework'. At that, both are applicable and yet, there is a difference.
1C treats 'framework' as a more general term, meaning both 1C:Enterprise
runtime and development ('Designer')
mode, also including some external libraries.
'Platform' is used for 1C:Enterprise working namely in 'Enterprise' mode. It
is also used if one needs to demonstrate what the platform includes also a
business-platform for business process automation, duplication of ready
solutions, maintenance and support, etc. While 'framework' means only
technological issues, not business process automation, for example.
This split of terms is not strict. In general, reading documentation on
1C:Enterprise 8 one can meet both terms used side by side.
The Platform and Business Applications
There is a strict division in 1C:Enterprise 8 between the platform and
business applications.
The platform is primarily the framework where a business application
functions. In addition, the platform contains some
development tools for the whole development, distribution, administration
and support of business applications.
A business application is an independent entity but it is entirely based on
the technologies of the platform.
'Applied Solutions', 'Business Applications' and 'Configurations'
'Configuration' – is what that is created during development stage on
1C:Enterprise 8 framework.
You cannot call it module – since a configuration may consist of different
modules and subsystems.
You cannot call it executable code – since it is more than code, it contains
metadata objects' description. In fact, all metadata objects are metadata
objects' templates that are configured in a special way by a developer to
describe specific business-object types. And all the set of configured objects,
including some business logic code, is called 'configuration'.
The development process is also called 'designing', and the tool that is used
for that – 'Designer'.
As a rule, these terms are used in terms of the framework as a development
environment.
When a configuration becomes a final product, it becomes an 'applied
solution'. That is a product that can be considered separately from the
framework: it can be marketed, sold, supported, etc. (but not used)
independently from the framework. (We should keep in mind that an applied
solution cannot 'live' on its own – it can operate only being executed on the
framework. Just like a CD-player is needed to playback a CD.)
Both 'configuration' and 'applied solution' terms mean one the same part of
1C:Enterprise 8 system that operates under control of the framework and is
visible to users. Use of a particular term depends on the context.
If it says about developer's actions then 'configuration' term is used, since
it's an exact 1C:Enterprise 8 term.
While 'applied solution' term is more generally accepted and therefore
understandable by users.
An 'applied solution' and the framework together make a 'business
application'. For example, there is 1C:Accounting 8 business application that
includes 'Enterprise Accounting' configuration (or 'applied solution', since it
is a final, ready to use product).
'Database', 'Information Base' and Configurations
'Database' term is too limited for 1C:Enterprise 8 concept. Therefore
1C:Enterprise 8 operates with 'information base' term.
Information base contains a database (which contains, it its turn, user
data). In addition to it, an information base contains:
A database configuration – the configuration that users work with.
A base configuration – editable configuration that developers work with.
One or more vendor configurations. This configuration contains previous
state of a distributed configuration. If there are several vendors for a
configuration (for example, if each of them supports only his part) then
there will be several such configurations in an information base.
Administrative information
There also can be an external configuration repository, used for team
development.
Next