DE102004040010A1 - Information processing program runtimes controlling method, involves processing container contents by special commands of processing unit and forwarding contents logically by functional units in runtime environment - Google Patents

Abstract

The method involves packing incoming information in a container in a runtime environment. The container contents are processed by special commands of a processing unit and forwarded logically by functional units in the runtime environment that is configured from the functional units. The container is provided with meta-information about its content, and the functional units have direct access to the container including their content. An independent claim is also included for a device for controlling an information processing program runtimes in a computer system.

Description

The illustrated solution has a broad approach. Therefore it affects several areas the IT. The affected technology areas are listed here.

object technology

The Objective technology paradigms have largely evolved in the IT industry enforced. The object technology already offers one in the object language created organizational structure, structured with the software systems can be created. Key points in object technology include i.a. theories of inheritance and encapsulation. A good overview provides the homepage of the Object Management Group (OMG) to the current one State of the art in this area. http://www.omg.org/

Program architecture of Compiled languages

conventional Program architectures address their data elements directly the code segment out over a base address (beginning of the data segment) and fixed offset addresses, which are the physical location of the data element within the data segment reflect. On the data elements of the data segment can only be accessed by the program code of the code segment, as only this code knows the internal structure of the data segment. These Architecture for Compiler languages, such as Assembler, C ++, Java or Visual Basic has been known for decades and optimally supports the computer architectures.

application architectures

application architectures can usually divided according to a software layer model. These are in the individual presentation layer, test layer, Control layer, processing layer and access layer. ever after implementation can these layers merge and no clear structure can be seen.

today Applications often mix technical and technical content. A defined integer field for a calculated monthly salary already provides a mixed information with technical (depending on the computer model 2 or 4 bytes are occupied) and technical content. Passing of this data element with the monthly salary of the business layer to the presentation layer for output to a browser already has a technical content. The surrender Information from one shift to the next already contains one technical process, that of transferring.

component models

Component models developed in the 1990s and have developed, among other things, from object technology. The technology is widely established in the IT industry. Components are reusable software programs that contain a defined interface with a specific functionality. Characteristic of the technology is a standardized call technology with which a calling program (client) can control the functions of a component (server). The best-known representatives of component technology are: Corba see: www.omg.org COM / DCOM see: www.microsoft.com Java beans see: java.sun.com/products/ejb

application server

The technique has been known for many years. As a rule, the application server is deployed in a central location, so one of its tasks is the optimal sharing and management of resources (virtual memory, database connections, terminal connections, CPU performance) required by computer programs. As a rule, these resources are of a technical nature, in contrast to the resources (here, data of the application is meant) with which the application programs running on the application server have to do. The application servers stop at a memory request of the application pro This memory is available to you, but you can not interpret the content.

generation approach

One IT sector (see: www.omg.org) follows the generation approach through the "Model Driven Architecture "(MDA). Here are implementations based on an abstract model for different Target environments performed.

XML technology

The XML technology emerged from SGML technology in the late 1990s and has caused a great deal of attention through Internet technology. With the help of this technology, information data is not pure Accumulation of numbers and texts more, now for each piece of information Meta-data kept.

The Technology has found a wide range of applications in a short time.

The W3C web pages provide a good overview of the current state of XML technology: http://www.w3.org/
A multitude of developments in the XML area are visible on these pages, among others
DOM (Document Object Model)
SOAP / XMLP
XML Schema
XML Query
Web services

Disadvantages state of the art

Problems due to the architecture

• • Hohe Wartungsaufwände für bestehende Applikationen, u.a. bedingt durch Abhängigkeiten in den Schnittstellen und der Wiederverwendung von Klassen.
• • Hohe Komplexität in der Programmierung von Anwendungslösungen, bedingt durch die feste „Verdrahtung" von fachlichem und technischem Lösungscode. Dadurch muss ein Programmierer neben seinem fachlichen Wissen zur Lösung der fachlichen Aufgabe ein hohes technisches Wissen über das Umfeld haben.
• • Offenheit in der Architektur ist nur selten gegeben. Anwendungen verschiedener Software-Hersteller können oft nur mit grossen Aufwand, wenn überhaupt, integriert werden
• • Zunehmende Wartungsaufwände, je älter eine Anwendung wird. Dies hängt mit der starken Abhängigkeit der in einem Anwendungssystem miteinander kommunizierenden Programme zusammen.
• • Wenig offen für neue Entwicklungen, z.B. nachträgliche „Drag- and Drop" – Unterstützung in einem Anwendungssystem.
• • Die enthaltene Komplexität in der Anwendungsarchitektur erlaubt in der Regel keine Programmierung aus graphischen Bausteinen.
• • Unterschiedliche Kommunikationsformen in einer Transaktion (synchron und asynchron) nur aufwendig zu erreichen.
• • Verteilungsprobleme von Anwendungssoftware
• • Wiederverwendbare Infrastruktur-Services für die Anwendungen haben ihre Grenzen.
• • Dokumentation und tatsächlich implementierte Softwarefunktionen stimmen nicht überein.

The full scope of the problems of today's application / system architectures becomes clear when an analogy with a letter delivery, in this case with a very absurd, is used. Suppose a letter is carried by a postal company from Fürstenfeldbruck to Aligse near Hanover. In the first post office, in this case in Fürstenfeldbruck, the letter is opened and compared to a very specific style. If this letter is incorrectly structured, the letter will be returned to the sender. If the letter matches the template, it will be sent to the nearest post office, in this case to Munich. There, the same review process with the same style occurs. Also in Hanover and Lehrte until the letter arrives at the recipient in the mailbox in Aligse. A minor change in the letter content, such as changing the postal code from 4 to 5 digits, as happened in the 90s, means that all mail distribution points must be equipped with a new style before the first letter can be delivered. Since thousands of different letters are in circulation, a considerable administrative burden arises. In an application system, the mail distribution points are to be compared with the functional layers presentation, control, checking, processing and access layer, which passes through a message from a terminal such as a browser to storage in a database. As a rule, in addition to the content of a data element, the format description is also included in all functional layers. As a result, these layers have a strong dependence on the content of a message. These dependencies often do not make sense, for example, an access layer should provide data to a database; it does not need to know anything about the content. These dependencies give rise to a variety of problems known today, some of which are mentioned below:

• • High maintenance costs for existing applications, among others due to dependencies in the interfaces and the reuse of classes.
• • High complexity in the programming of application solutions, due to the fixed "wiring" of technical and technical solution code.This must be a programmer in addition to his technical knowledge to solve the technical task to have a high level of technical knowledge of the environment.
• • Openness in architecture is rarely given. Applications of different software manufacturers can often be integrated with great effort, if at all
• • Increasing maintenance, the older an application gets. This is related to the strong dependency of the programs that communicate with each other in an application system.
• • Little open to new developments, eg subsequent "drag and drop" support in one application system.
• • The included complexity in the application architecture usually does not allow programming from graphic blocks.
• • To achieve different forms of communication in a transaction (synchronous and asynchronous) only consuming.
• • Distribution problems of application software
• • Reusable infrastructure services for the applications have their limits.
• • Documentation and software features actually implemented do not match.

XML DOM

Direct addressing

The standardized Application Programming Interface (API) does not support any direct addressing to elements based on their schema definition several times in their expression (Array elements) can occur. So it is e.g. not possible, the eighth expression directly to a specific element. About one sequential read operation, the eighth element must be reached. ID attributes can for the requirement, Directly addressing elements not to be used. Corresponding The XML 1.0 Recommendation (REC-xml-19980210), must have ID attribute values within an XML document.

Please refer also: http://www.w3.org/DOM/

object technology

Problem of encapsulation

One The paradigm of object technology is encapsulation. Besides the advantages it also has disadvantages. Only the program code within the class can access the data structure of an instance of this class. External automation functions that control the content of the Need to recognize data, can thus not be developed.

Problem of the interfaces

High change effort in case of changes in interfaces of classes. through the direct interface dependence between the caller and the called function must have changes in the interface be made to all affected program parts.

Applikationssserver

The The task of an application server is to manage mainly technical resources for the applications under his control. He has one technically supportive Orientation. He contains little or no information about The object data model active in the application. This can be a Application server adopt little standardized service for applications.

Computer Languages

Dependence between code and data segment

By the direct addressing of the data elements from the code segment out over a base address (beginning of the data segment) and the fixed offset addresses, the physical location of the data element within the data segment reflects a strong dependence between program code and data structure. amendments in the data structure at least always have a new compiler run with the subsequent distribution of the newly created program. This intense dependence runs through a whole software system, even over computer limits time.

Description of processes in "texts"

The technical description of programs of the usual computer languages (Java, C ++, Visual Basic) are represented by formalized texts (sources). A compiler run captures these texts and transforms them into a form understandable by the machine. The content structures are only at the Compi ler run detected and thereby certain errors detected late. A direct content capture during the source creation does not take place, so that only limited support measures for programming are possible. The form of the textual representation of program sequences is in many cases confusing and does not correspond to the human ability to better perceive complex structures visually.

programming model

The usual today Programming models with object-oriented languages have one Focus on the reuse of classes or components and encapsulate a professional content, e.g. listing employees and calculating salaries. In doing so, subject matter and technical processes, e.g. List, Employees and Salaries' spend, closely with each other coupled, so that with regard to technical recurring processes no Reuse is given.

integration of application systems

existing Application systems have little integration possibilities among themselves, because they are at the level of individual software layers (e.g., access layer) only rarely interfaces for offer other programs to the outside.

Object of the invention

aim or object of the invention is the simple development of software solutions for professional Tasks in the field of e-business, commercial Computer, support of standard software and its integration. The existing today dependence Calling and calling programs is largely eliminated. In addition to the reuse of technical components is the re-use of infrastructure service allows resulting in a much faster development of new applications leads. Due to the simplicity, new use cases or procedures support e.g. Simultaneous synchronous and asynchronous communication in a transaction. This is the entire development and life cycle an application supported by graphical elements. The flowcharts The technical application is simultaneously documentation and process control.

Solution of the task

Basically Information circulating between terminals such as browser and resource manager are packed in containers, comparable to the contents of a letter. The functional layers involved have no direct dependence to the contents of a container. Furthermore, the technical data (Data elements) of a packet, as individually addressable units held in a memory management system. Concerning. Location and location exist no dependencies between adjacent data elements. Each data element can be individually and uniquely addressed throughout the system. The runtime environment becomes meta-data of the current data model an application available posed, thereby can intelligent control measures (e.g., loading related data when aggregated into the storage management system) is taken from the runtime environment become.

Around solve the task to be able to have to all not directly for the technical task necessary procedures and technical data of the processing layer are kept away, that of one Application developers to create programs. Only with professional Tasks, e.g. Calculate the quarterly results, read appropriate Methods of business layer technical data and then post the results returned to the centralized storage management system (SMS). From the business layer If no data is passed on to other layers, the information is passed on is only about References, which in turn point to objects in the SMS. By cleaning up the business layer of technical dependencies paves the way the program logic build up through graphic elements.

Advantages of the invention

architecture

• • Reduzierung von Komplexität in der Programmierung von Anwendungslösungen
• • Konzentration der Programmierung auf das fachlich Wesentliche
• • Eine kontextabhängige Steuerung ist in der Architektur integriert, dadurch vermindert sich die Komplexität im Anwendungsdesign.
• • Offenheit, auf Basis dieser Architektur können Anwendungen unterschiedlicher Software-Hersteller einfacher integriert werden
• • Reduzierung von Wartungsaufwänden
• • Offen für neue Entwicklungen, neue Infrastruktur-Services können bestehenden Anwendungen zur Verfügung gestellt werden, z.B. „Drag and Drop" Unterstützung, ohne diese anpassen zu müssen.
• • Ermöglicht Graphische Programmierung
• • Unterschiedliche Kommunikationsformen in einer Transaktion (synchron und asynchron)
• • Die Vorteile einer zentralistischen Architektur und die Vorteile der graphischen Computerleistung vor Ort wird in eine Gesamtarchitektur zusammengeführt.
• • Wiederverwendbare Infrastruktur-Services können aufgebaut werden.
• • Einheitliche Datengrundlage für das Ablaufverhalten des Anwendungssystems und der Dokumentation.

The basis is the architecture. It leads to the following advantages in the development environment to be developed:

• • Reduce complexity in programming application solutions
• • Concentration of programming on the technical essentials
• • Contextual control is built into the architecture, which reduces the complexity of application design.
• • Openness, based on this architecture, applications from different software vendors can be integrated more easily
• • Reduction of maintenance costs
• • Open to new developments, new infrastructure services can be made available to existing applications, such as "drag and drop" support without having to adjust them.
• • Enables graphical programming
• • Different forms of communication in one transaction (synchronous and asynchronous)
• • The benefits of a centralized architecture and the benefits of on-site graphical computing performance are brought together in one overall architecture.
• • Reusable infrastructure services can be built.
• • Uniform data basis for the execution behavior of the application system and the documentation.

Comments on the benefits

programming model

• a) Anfordern einer bestimmten Liste durch einen Anwender
• b) (die Liste erstellen ist fachlicher Art)
• c) eine Benachrichtigung über erfolgreiche List-Erstellung an den Anwender schicken
• d) die Liste zustellen und anzeigen

sie sind unabhängig davon, ob diese Liste Mitarbeiter einer Abteilung oder Umsätze je Quartal enthält. Die Ausrichtung des Programmiermodells wird dahin gehen, dass zur Lösung eines fachlichen Problems technische Abläufe von den fachlichen Inhalten bzw. Funktionen getrennt werden. Die erstellten, ineinander greifenden Komponenten, die technische Abläufe unterstützen, stellen wiederverwendbare Infratruktur-Services dar.The implementation of the claims in a runtime environment enables a novel programming and reuse of infrastructure services. In this context, these services are software-based "bearer services" for subject-specific information.The services are independent of the technical content that accompanies them.The technical procedures for creating a list have the following individual steps

• a) Request a specific list by a user
• b) (the list is a technical one)
• c) Send a notification of successful list creation to the user
• d) deliver and display the list

they are independent of whether this list contains employees of a department or sales per quarter. The orientation of the programming model will be to separate technical processes from the technical contents or functions in order to solve a technical problem. The built-in, interlocking components that support engineering operations are reusable infrastructure-building services.

documentation

The to be created software procedures and dependencies are defined in the form of XML descriptions. These XML descriptions can at the same time for the documentation of the system is used. The documentation at the same time represents the process description.

Description of Implementation and execution details

The occurring in different programmed application systems show professional procedures in their patterns an often recurring flow behavior, such as. creating and outputting a list. The one among these procedures Existing program code includes execution behavior and technical information and is "wired" together in the one in today Application code of the presentation, control, testing, processing and access layer, both shares are also usually hardwired Program codes for the flow behavior and the professional behavior or the professional Information is necessary. The program code for the runtime performs doing a carrier service for professional Information. The following implementation and execution details are geared towards this goal.

construction

The task of the runtime environment is to record methods of functional classes to be programmed and to provide services that can be accessed from the methods by means of commands. For this purpose, the runtime environment is made up of various functional units that each assume specific tasks. The task of the methods to be programmed is the adoption, processing and forwarding of information of various kinds. For this purpose, incoming information from the presentation or access unit are packaged in indexed containers and stored in the memory unit. Each functional unit has access to the containers and their contents in the storage unit in order to be able to perform the service for which a functional unit is responsible. Containers and their contents are uniquely identified by corresponding identifiers. A container contains information, called an object instance here, of a particular class. There can be relationships between object instances of the same and different classes, which are held in an object instance of a specific class and also loaded into containers at the execution time of a functional class. The object instances of the subject classes contained in the containers contain meta information from the runtime environment, and this information too is kept in containers. The formatting instructions, also object instances of certain classes, for output to external devices such as browsers or mobile phones are also kept in containers. These formatting instructions generate an HTML data stream for output to a browser from the presentation unit. The functional units are controlled by context-related data, eg the role of a user, the type of output device, the active version of methods, so that different context-related execution behavior is supported.

To on the subsequently listed Processing unit need the individual functional units of a developer of a technical Application are not programmed, they are "defined".

The Functional units are in detail:

a) presentation unit

these Unit receives Messages from external devices, packs the message into a container and passes it to the storage unit. For expenses on external devices the presentation unit reads containers from the storage unit, builds an output message based on special formatting instructions contained in containers and passes this message to the end system.

b) test unit

these Unit checks received messages on formal and content correctness. The test regulations are present in containers of a certain class.

c) control unit

these Unit activates a specific one based on a received event Method of a class of the processing unit.

d) processing unit

in In this unit the information processing methods are more professional Classes. The special commands contained in the methods have over the Storage unit access to the contents of the container and control the container flow through the individual functional units. classes and methods need be defined or programmed by an application developer.

e) storage unit

these Unit temporarily saves Containers with their content in virtual memory. Every container will identified by a unique identifier. In addition will each data element within a container also by a unique identifier identified. Accesses to Resource Manager are always over the storage unit performed, this can decide if an object instance is loaded in a container is. If this is not the case, the access unit is activated, to load the corresponding object instance.

f) Command unit

these Unit gets from the processing unit the in a method one by one. Depending on the command, the command unit calls a specific command module to edit the command or delegate the execution other functional units.

g) access unit

this unit reads information from a resource manager or external system, transformed this into an internal format and stores them in a container of the storage unit. Likewise, it reads the contents of containers from the storage unit, transforms this read information into the data format of the resource manager or external system and transfers the transformed information to the resource manager or external system for storage on a persistent medium.

• 1, 2 Die von der Präsentationseinheit empfangene Nachricht eines externen Systems oder Browsers wird in einen Container verpackt, der Container und jedes darin enthaltene Datenelement wird über Identifier eindeutig gekennzeichnet und der Speichereinheit zum Zwischenspeichern übergeben.
• 3 In Abhängigkeit des mit der Nachricht verbundenen Ereignisses und einer kontextabhängigen Steuerinformation wird von der Steuereinheit die Verarbeitungseinheit aktiviert mit dem Auftrag, die Methode einer bestimmten Klasse zu starten.
• 4 In der Verarbeitungseinheit laufen folgende Schritte ab: a) Die Verarbeitungseinheit erkennt in einer internen Tabelle, dass die Methode noch nicht geladen worden ist und beauftragt die Speichereinheit, diese Methode und Meta Daten der Klasse in die Speichereinheit zu laden. b) Eine Instanz der internen Klasse „Methode" wird instanziiert und initialisiert. Diese Instanz nimmt interne Referenzen zwischen Operanden der Methoden-Befehle und die in der Speichereinheit liegenden Container auf. c) Die Verarbeitungseinheit übergibt der Befehlseinheit den ersten auszuführenden Befehl einschliesslich Operanden. Methoden der Verarbeitungseinheit können über einen entsprechenden Befehl den erstellten Container der Eingabenachricht einlesen und weiterverarbeiten. Für die Ausgabe einer Nachricht erstellt ein anderer Befehl einen Ausgabe-Container, der von der Präsentationseinheit für das Generieren einer Ausgabenachricht verwendet wird.
• 5. Die Befehlseinheit ruft die entsprechende Befehlsroutine auf. Je nach Befehl wird die Speichereinheit für den Zugriff auf Datenelemente aktiviert, die innerhalb eines Containers liegen.
• 6 Bei bestimmten Befehlen, z.B. Einlesen einer Objektinstanz einer fachlichen Klasse, aktiviert die Befehlseinheit die Speichereinheit. Über die Speichereinheit wird die Zugriffseinheit aktiviert. Diese liest von einem Resourcen-Manager die Objektinstanz.
• 7 Die Zugriffseinheit ruft direkt Funktionen der Speichereinheit auf für das Speichern der Objektinstanz in einen Container. Folgende Schritte laufen dabei ab: a) Anfordern eines Containers b) Einspeichern Datenelement in Container, dabei werden Container-ID, Identifier des Datenelementes und Inhalt des Datenelementes übergeben. c) Rückgabe der Kontrolle an die Befehlseinheit mit Übergabe der Container-ID.
• 8 Bei bestimmten Befehlen, z.B. Speichern einer Objektinstanz einer fachlichen Klasse, aktiviert die Befehlseinheit die Speichereinheit. Dabei übergibt sie der Speichereinheit die zu speichernde Container-ID. Die Speichereinheit ruft wiederum die Zugriffseinheit mit Übergabe der Container-ID auf. Über diese Container-ID wird die Objektinstanz aus dem Container über eine Funktion der Zugriffseinheit ausgelesen.
• 9 Die Zugriffseinheit transformiert die ausgelese Objektinstanz auf das Format des Resourcen-Managers und ruft diesen zur Speicherung der Objektinstanz auf. Anschliessend erhält die Befehlseinheit die Kontrolle zurück mit Angabe eines Response-Codes.
• 10 Vor Beendigung der Aktivitäten in der Verarbeitungseinheit (Programmende) muss von einer Methode der Verarbeitungseinheit ein Ausgabe-Container erstellt worden sein. Die Kontrolle wird an die Präsentationseinheit gegeben.
• 11, 12 Die Präsentationseinheit liest den Ausgabe-Container und generiert eine HTML-Ausgabe für die Ausgabe auf den Browser.

It shows 1 Execution behavior by the functional units

• 1, 2 The message received from the presentation unit of an external system or browser is packaged in a container, the container and each data element contained therein is uniquely identified by identifier and passed to the memory unit for caching.
• 3 Depending on the event associated with the message and context-dependent control information, the control unit activates the processing unit with the request to start the method of a specific class.
• 4 The processing unit executes the following steps: a) The processing unit recognizes in an internal table that the method has not yet been loaded and instructs the memory unit to load this method and meta data of the class into the memory unit. b) Instance of the internal class "Method" is instantiated and initialized This instance takes in internal references between operands of the method commands and the containers in the memory unit c) The processing unit gives the first instruction to be executed, including operands Methods The processing unit can use a corresponding command to read in and process the created container of the input message For issuing a message, another command creates an output container that is used by the presentation unit to generate an output message.
• 5. The instruction unit calls the corresponding instruction routine. Depending on the command, the storage device is enabled to access data items that reside within a container.
• 6 For certain commands, eg reading in an object instance of a domain-specific class, the command unit activates the memory unit. The access unit is activated via the storage unit. It reads the object instance from a resource manager.
• 7 The access unit directly calls functions of the storage unit for storing the object instance in a container. The following steps are carried out: a) Requesting a container b) Storing data element in container, container ID, identifier of the data element and content of the data element are transferred. c) return the control to the command unit with transfer of the container ID.
• 8 For certain commands, such as saving an object instance of a specialized class, the command unit activates the memory unit. In doing so, it transfers to the storage unit the container ID to be stored. The storage unit in turn calls the access unit with transfer of the container ID. This container ID is used to read the object instance from the container via a function of the access unit.
• 9 The access unit transforms the read object instance to the format of the resource manager and calls it to save the object instance. The command unit then receives the control back with specification of a response code.
• 10 Before the end of the activities in the processing unit (program end), an output container must have been created by a method of the processing unit. The control is given to the presentation unit.
• 11, 12 The presentation unit reads the output container and generates an HTML output for output to the browser.

Classes and organizational Structure of the runtime environment

classes describe formally necessary resources and objects of a runtime environment and their applications running in it. For each class will be on one Resource Manager created a file. The contents of these files, also object instances, describe the actual resources and objects of a runtime environment and their running applications. The needed at runtime Object instances are loaded into containers of the runtime environment.

• • SYS-* => systemtechnische Resourcen, Objekte und Einstellungen der Ablaufumgebung.
• • NW A-* => Resourcen und Objekte einer fachlichen Anwendung
• • ON C-* => contextabhängige Verweise einer Anwendung

Files or classes of the runtime environment

• • SYS- * => system resources, objects and settings of the runtime environment.
• • NW A- * => resources and objects of a technical application
• • ON C- * => contextual references of an application

Object instances, whose class has been defined with the property "persistent", and the changed When command is "Commit" from the access unit to a resource manager saved.

Object instances, whose class has been defined with the property "temporary" and whose class in A method is declared when instantiating the corresponding Method automatically instantiated in the storage unit. When finished The method will use these at the next issue on a terminal from the Memory unit cleared.

Object instances, whose class has been defined with the service property and declared in a method is instantiating the corresponding method automatically instantiated in the storage unit. Upon termination of the professional Services are deleted from the storage unit. object instances stay with this property over received several dialog steps in the memory unit. Thereby can Information held between screen dialog steps in methods become.

Object instances, whose class has been defined with the property "global", will be opened when opening a Application instantiated by the storage unit and are per application only available with one object instance.

Object instances, whose class has been defined with the property "offset" internally have one another addressing mechanism between object code and container content. For performance reasons will the addressing is not over Indexes made but over fixed offset addresses. The element descriptor forms a fixed offset value. The actual physical location of the data element in the container is determined by this offset value.

Classes of the runtime environment

SYS-SYS

• • der Befehlssatz erweitert werden
• • Speicherbereiche vorallokiert werden
• • Anzahl Threads instantiiert werden

Object instances of this class define runtime environment initialization settings. They are an exception because they are not loaded into a container of the storage device. This can, inter alia

• • the instruction set can be extended
• • Memory areas are pre-allocated
• • Number of threads to be instantiated

SYS-UOW

object instances This class contains information from currently running "Unit of Work "operations and their status in the commit phase. For every active application is an object instance of this type is kept in the memory unit. Will the control statement "commit" from a method The processing unit is called, depending on a UOW service level the UOW process is logged and, in certain cases, controlled intervened, e.g. a backout is performed if there is an error in the Updating an object instance occurs. The intervention options be for each subsystem to which object instances to store or transfer are defined. Therefore be for each subsystem has the appropriate communication characteristics Are defined.

SYS-GPO

object instances This class contains information about current and completed information Business processes, where every business process has one unique GPO ID is marked. The status of a business process is determined by a Object instance identified with a unique GPO ID. A business process is a sequence of professional services, each one specific achieve professional results and in each case a subsequent professional Initiate service. A professional service that is a specific professional Result, e.g. A contract is concluded by the control statement "commit" and persisted. The changed one Status of this business process is also stored by the commit by the container contents, which the status of the business process holds, in the same transaction from the access unit to theirs Resource Manager is saved. Due to this status change a business process Another professional service can be started depending on the conditions or released.

SYS-LNK

Object instances of this class contain information regarding aggregation and association relationships between instances of freely definable, technically oriented ANW-CLS classes. For this purpose, for each object instance of a class that has an aggregation or association relationship to one or more object instances of other classes, an object instance of class SYS-LNK, including references by the object ID to the other object instances, is stored on a resource manager , When instantiating an object instance that has relationships with other object instances, the corresponding object instance (SYS-LNK) is also loaded into the memory unit. The object instance of class SYS-LNK has the same object ID, such as the object instance for which this referential relationship is being held. The command "setLink", with which a relationship between two object instances can be established, causes an entry to be made via command and memory unit in the corresponding object instance of SYS-LNK.

Example:

ANW-MAIN

Object instances of this class define a new application or a technical project. An object instance of this class has references to the objects contained in this application, which are object instances of the following classes: • ANW-MAIN Methods of super application can be inherited • ANW-CLS included classes • ANW-SRV included service • ANW-AKV Accumulate device / distributor object instances • ANW-MEN included menus

ANW-CLS classes

Instances of these classes describe things, concepts, constructs of the real or theoretical world in their behavior (methods) and status (attributes). The methods defined here have access to the attributes defined in the class. These object instances also describe the inheritance model with regard to specialization, aggregation and association with other classes (ANW-CLS). The object instance of these classes has references to object instances of the following classes • ANW-CLS inherited / aggregated / associated classes • ANW-MET included methods

It shows 2 class definition

When developing a method, this illustrated class definition is announced in the declaration part of the method. The operands of the instructions address the attribute names such as "p-nr" The compiler uses this addressing information to construct an object code that uses the element descriptors of the corresponding attributes as operands.

At the Read / save an object instance from / on a resource manager transformations are performed in the access unit. The Transformation routine uses the definitions Offset, Length, and Format from the class definition for the transformation.

• a) persistent
• b) temporär, context, service

besitzen.Object instances of these classes can have the properties

• a) persistent
• b) temporary, context, service

have.

object instances with property "persistent" form the actual Subjectively related classes, the real things or things of the conceptual world describe. You have methods that allow the object instances of this Classes can be manipulated or read. In a commit process become modified object instances on a resource manager saved (persistent).

instances with the property temporary, context or service form helper classes and usually exist only from data definitions at the time of calling a method of a class in the memory unit. they provide There are data items in a method where results are cached can be or from which initialization values (context) are read out can.

object instances This class represents meta-data and describes freely definable, professional classes in their individual elements, names and formats.

ANW-MET methods

Object instances of this class form the methods with the commands contained in them. The object instances of these classes have references to the object instances of the following classes: • ANW-CLS associated professional class • CON-CTL belongs to a specific context

ANW-MEN

Object instances of this class define menus for applications. They contain information and references to TXT and SVG object instances, which in turn contain text and graphics formatting instructions for output to the browser or output terminal. The object instance of this class has a reference to the object instance of the following class: • CON-CTL belongs to a specific context

ANW-SRV

object instances This class defines professional services. A service is one Sequence of individual dialog steps with a browser or terminal and leads to a professional result with a status change on a resource manager. The individual dialog steps are defined by unique events:

• a) einer Formatbeschreibung der Ausgabe (Objektinstanz von Klasse ANW-FRM)
• b) einer Aktion (z.B. Doppelklick) vom Benutzer
• c) Button-ID auf der die Aktion ausgelöst wurde

A unique event is made up of together

• a) a format description of the output (object instance of class ANW-FRM)
• b) an action (eg double-click) by the user
• c) Button ID on which the action was triggered

The presentation unit builds a unique Event ID based on these three event characteristics up and over this the control unit.

Event ID => Call a method a certain class

definition of a service takes place in an object instance of class ANW-SRV. Therefor is for any Dialog step of a service an entry about event ID and method of a Class made.

The object instance of this class has a reference to the object instance of the following class: • CON-CTL belongs to a specific context

IN-FRM

The instance of class IN-FRM is a global object instance. It is instantiated by the runtime environment when the application is opened and exists once per application. The data instance of this class contains the data elements received from a browser or terminal. The fixed system input destination SYSIN is assigned by default to the global instance of IN-FRM. This object instance is populated by the presentation unit upon arrival of a new browser message. Using the "getIn" command within a functional method of the processing unit, the method can selectively fetch data elements and assign them to other object instances of other classes. The input message transferred from the presentation unit may contain different data elements, to each data element within IN-FRM the values
Class ID
Element descriptor
data content
saved. In the assignment by the getIn command to an object instance of a particular class, the class ID and element descriptor assign only the data contents to the object instance that have the same class ID and element descriptor.

It shows 3 Assignment by "getIn" command

The Drawing shows the assignment of contents of the object instance of Class IN-FRM to other object instances of different classes with the "getIn" command, the "getIn" command will default to the object instance of IN-FRM, as an operand it contains a reference to a Object instance of a specific class. The command can be repeated several times be deposited on different object instances in a row, it only the data elements that have the same class ID are assigned in INF-FRM and target object instance.

OUT FRM

The Instance of class OUT-FRM is a global object instance. she will when opening The application is instantiated by the runtime environment and is per application once available. The command "putOut" writes information in this global object instance. The object instance of this class determines the output object instances of other classes, e.g. the classes ANW-FRM, ANW-TXT and ANW-SVG. The firmly defined System Output Destination SYSOUT is standard assigned the global object instance of class OUT-FRM. About SYSOUT receives the presentation unit when outputting to a terminal the necessary reference to the output object instances.

It shows 4 Assignment by command "putOut"

The Drawing shows the assignment of object instances of different Classes on OUT-FRM. In addition to the actual technical data, the formatting instructions, how to display the technical data on a browser over the Command "putOut" communicated Formatting instructions are over the object instance of ANW-FRM announced. OUT-FRM gets through putOut only references, there are no copy operations. The presentation unit accesses these references to the actual contents of the object instances and build the output message.

ANW AKV

Object instances of this class ANW-AKV define element-level accumulation and distribution operations between object instances of different classes and input and output classes. Special commands (getIn, putOut) specify in their operand a reference to an AKV object instance and object instances of classes to which accumulation and distribution operations are to be performed. In an object instance of an AKV class, the class and the element descriptors of the content to be transmitted are defined for a distribution process, and the class and the element descriptors of the content to be included for recording are defined. For an Ackumulationsvorgang the opposite way is defined. For an object instance of an AKV class to be created, a reference to another object instance of the ANW-VER class can be defined. This object instance contains context-related test specifications for received input messages. Context-sensitive information, such as the roles of users, can be used to perform a user-specific check of input messages. These test specifications are not programmed, they are defined.

It shows 5 Assignment by command "putOut"

Object instances of the AKV class can change the default assignment mechanism of the getIn and putOut commands. Without AKV object instance, an assignment is made if the following condition is met:

By AKV object instances can changed the assignments become. A data element within an object instance, determined by the format by class ID and element descriptor, can be another object instance with different class ID or element descriptor be assigned to.

ANW FRM

Object instances of this class, also called format description, contain information and references to TXT and SVG object instances, which in turn contain text and graphics formatting instructions for output to the browser or output terminal. Each format description is assigned a unique identifier. This is specified as an operand in the control statement "putOut" Furthermore, unique events can be defined using this identifier in conjunction with an action (press the "OK" button) appended to this format description. The presentation unit's main output routine receives the reference to the object instance of the ANW-FRM class on output. Via this reference, a corresponding formatting routine can be called, this gets all the information to generate a corresponding data stream, eg HTML, for the output device. The object instance of this class ANW-FRM has references to object instances of the following classes: • CON-CTL belongs to a specific context • ANW-TXT contains formatting instructions for text fields • ANW-SVG contains formatting instructions for Super Vector graphic objects

ANW TXT

object instances This class contains formatting instructions regarding display style and position textual content on a form that is for output on a terminal is determined. Text contents are the data elements from object instances. About the unique class ID and item descriptors become data items from object instances to the entries assigned in the formatting instructions.

ANW SVG

object instances This class contains formatting instructions regarding presentation and Positioning SVG Objects (Super Vector Graphic) on a Form that for output to a terminal is determined. SVG objects are in data elements of object instances containing a graphic objects-containing class. About the unique element descriptors Data items from object instances become the entries in the Associated with formatting instructions.

ANW VER

Object instances of this class contain test specifications for input from terminals (browser, mobile phone) or external callers. The object instance of this class has a reference to the object instances of the following class: • CON-CTL belongs to a specific context

CON-CTL

• a) device => vorgegeben
• b) Sprache => in seiner Anwender-Definition eingestellt
• c) Rolle => in seiner Anwender-Definition eingestellt

fest zugeordnet.Object instances of this class contain information about the contextual concept of an application. For each defined application in ANW-MAIN context support can be set. The context is determined by the context groups Device, Language and Role. A user who logs on to an application becomes the context under which he works

• a) device => specified
• b) Language => set in its user definition
• c) Role => set in its user definition

permanently assigned.

Calls to object instances of certain classes of the application system are logical calls for the runtime environment, this applies to a) ANW-MET Method of a class b) ANW-SRV professional service c) ANW-FRM Format description of an output d) ANW-MEN Menu of an application e) ANW-CLS of type context Initialization data in data object f) ANW-VER Verify for input from the browser or external callers

During the Development of the objects of the application system become the individual Objects of this listed Classes assigned to a specific context or the "main-common" if this object is used for all context settings valid is.

internally is the logical environment of the runtime environment in a real Call implemented. The runtime environment knows the context under which a user is running. It also knows the context definition of this application. The Context definitions provide a search path for finding the real one Object dar. Is in a level no entry of a real object found, will be in the next higher level checked.

It shows 6 Context-definiton

Example:

Context setting of a user Device: browser Language: German Role: guest

Search Path: 1. Scanners / German / Bed Second Scanners / German / Common Third Browser / Common / Bed 4th Browser / common / common 5th Common / German / Bed 6th Common / German / Common 7th Common / Common / Bed 8th. Common / Common / Common 9th Main Common

In order to The search paths can not be too long, for each logical object and each class of an application, e.g. for methods to be specified whether context support is required. If not, you can branch directly to Main-Common become.

presentation unit

input

• a) Ereignis-Daten
• b) Fachliche Daten aus Eingabe-Form

Program routines of the presentation unit are waiting to receive new messages from a browser or terminal. A message from a browser or device contains the following information:

• a) event data
• b) Technical data from input form

• a) Aufbau einer Ereignis-ID

After receiving a message, the following steps will be performed:

• a) Structure of an event ID

• • Focus der Ausgabe-Form (ANW-FRM), über welche die Aktion ausgelöst wurde
• • Element, auf die eine Action ausgelöst wurde, z.B. Submit-Button
• • Aktion die ausgelöst wurde, z.B. Doppelklick

Each message received by the presentation unit is associated with a unique event determined by:

• • Focus of the output form (ANW-FRM) over which the action was triggered
• • Element to which an action was triggered, eg Submit button
• • Action that was triggered, eg double-click

• • eindeutige Objekt-ID der Objektinstanz der Klasse ANW-FRM,
• • einer Objekt-ID auf die eine Action vollzogen worden ist (z.B. SVG-Objekt Submit-Button)
• • und der Action-ID auf Grund eines bestimmten Mouse-Click Verhaltens am Browser.

Objekt-ID (ANW-FRM) + Objekt-ID (SVG-Objekt) + Action-ID => Ereignis – ID

• b) Transferieren der fachlichen Daten von System-Destination SYSIN zu der standardmässig zugeordneten globalen Objektinstanz IN-FRM. Die vom Browser oder Endgerät empfangenen fachlichen Daten enthalten je Informationseinheit einen Bezeichner und den eigentlichen Wert. Der Bezeichner setzt sich zusammen aus:

Class-ID + Element-Descriptor All together allow to build a unique event ID:

• • unique object ID of the object instance of class ANW-FRM,
• • an object ID to which an action has been executed (eg SVG object submit button)
• • and the Action ID due to a specific mouse-click behavior on the browser.

Object ID (ANW-FRM) + Object ID (SVG Object) + Action ID => Event ID

• b) Transfer of the technical data from system destination SYSIN to the globally assigned global object instance IN-FRM. The technical data received by the browser or terminal contain an identifier and the actual value for each information unit. The identifier consists of:

Class ID + element descriptor

The received data can of object instances of different classes, the Class ID's in IN-FRM carried become.

It shows 7 Definitions in IN-FRM

output

The presentation unit build a message for a browser or a terminal on. about the fixed system destination SYSOUT, which is the global object instance from OUT-FRM by default can be assigned over the object instance of ANW-FRM the two output types ANW-TXT or ANW-SVG determines and calls the assigned output routine become. This generates a message for the browser or terminal.

It shows 8th Outputs on SYSOUT

About the fixed destination SYSOUT, outputs are executed on browser. The Object instance OUT-FRM is assigned by default to SYSOUT. The one to call Formatting routine is dependent object instance assigned by the OUT-FRM, whether TXT output or SVG edition.

It shows 9 Implementation of formatting / object instance / in HTML

The identification of each input field originating in a particular class is accomplished through the Class ID (Example: 123) and the Element Descriptor (Example: 456) of the Data Element. Correspondingly, the HTML field name (example: C 123.E456) must be constructed from the class ID and element descriptor when a data element is output to the screen, with subsequent input by the user. This built-up field name becomes output to a browser in the HTML data stream with built-in. Upon subsequent entry in such a field, the built-up field name is given in an input message, thereby the reference to an object instance of the corresponding class and the data element can be established via element descriptor when reading the message by the command "getIn".

test unit

• a) Vor Ort direkt am Browser, hierfür werden die Prüfvorschriften von der Präsentationseinheit bei der Ausgabe direkt mit übertragen. Integrierte Script-Prozeduren in der HTML-Ausgabe, die auf Eingabefelder eingestellt sind, verwenden diese Prüfvorschriften
• b) Beim Einlesen des ANW-IN Container durch den Befehl „getIn". Hier kann die Prüfvorschrift in Form einer Objektinstanz der Klasse ANW-VER bei einer Objektinstanz der Klasse ANW-AKV bzw. direkt beim Befehl „getIn" angegeben werden.

The test unit becomes effective at two different locations.

• a) On site directly at the browser, for this purpose the test instructions are transmitted directly from the presentation unit during the output. Integrated Script procedures in the HTML output that are set to input fields use these test specifications
• b) When the ANW-IN container is read in by the "getIn" command Here, the test specification can be specified in the form of an object instance of class ANW-VER for an object instance of class ANW-AKV or directly for the command "getIn".

control unit

There several applications can be active, must have an association before calling the control unit from the presentation unit which input is made at the browser of which active application is to be assigned. This happens over An internal application ID for an open application of the runtime environment is awarded.

It shows picture 10 conversion of event into method call

In Figure 10 shows the process which steps in the control unit be done. After selecting a service displayed in the menu screen all dialog steps under this service. The control unit will after receiving a new message called by the presentation unit. She is given the event ID by the presentation unit. Under the expiring context of this application, defined by An object instance of class CON-CTL is called for the logical, called Service in the file CON-CTL an object instance of a real service entry searched. A real service found here becomes an object instance loaded from the file ANW-SRV. From this found object instance will then be over the event ID identifies the method to invoke.

access unit

The Access unit controls the activities regarding read / save container content from / to resource manager and external systems. She is waiting for an impulse from the storage unit.

• • Lesen der Containerinhalte
• • Transformation der Container-Inhalte auf das Zielsystem. Hierfür werden Mapping-Informationen für die zu speichernde Klasse aus der sie beschreibenden Objektinstanz der ANW-CLS Klasse gelesen. Hierüber wird auch eine Zuordnung der Element-Descriptoren auf das transformierte Zielformat getroffen.
• • Aufbau des Zugriffsbefehls für das Zielsystem
• • Ansteuerung des Zielsystems über den Transport-Controller
• • Warten auf Response des Zielsystems
• • Rückgabe Response an Speichereinheit

During a save process, she is given a list of container IDs to be submitted to the external system. The main access routine takes over the independent control of all activities, which are:

• • Reading the container contents
• • Transformation of container contents to the target system. For this purpose, mapping information for the class to be saved is read from the object instance of the ANW-CLS class that describes it. This also makes an assignment of the element descriptors to the transformed target format.
• • Structure of the access command for the target system
• • Control of the target system via the transport controller
• • Waiting for response of the target system
• • Return response to storage unit

• • Ansteuern des Zielsystems über den Transport-Controller
• • Warten auf das Ergebnis der Lese-Operation
• • Transformation der gelesenen Daten. Hierfür werden Mapping-Informationen von der gelesenen Objektinstanz aus der sie beschreibenden Objektinstanz der ANW-CLS Klasse gelesen. Hierüber wird auch eine Zuordnung der gelesenen Satzstruktur auf die Element-Descriptoren getroffen.
• • Einspeichern transformierter Daten in den Container
• • Rückgabe Response an Speichereinheit

During a read operation, the access unit is notified of the access command which is to be transferred to the external system in addition to the container to be recorded. The main access routine takes over the independent control of all activities, which are:

• • Activation of the target system via the transport controller
• • Wait for the result of the read operation
• • Transformation of the read data. For this purpose, mapping information from the read object instance is read from the object instance of the ANW-CLS class describing it. This is also an assignment of the read sentence structure to the element descriptors made.
• • Storing transformed data into the container
• • Return response to storage unit

It Figure 11 shows the structure of the access unit

• a) Transformationsroutine
• b) eine Routine für den Befehlsaufbau an den Resourcen-Manager
• c) Transport-Controller, der die einzelnen Zugriffsschritte durchführt

When the access unit is called, the main access routine receives control, which, based on initialization parameters, overrides the activities for accessing a resource manager

• a) Transformation routine
• b) a command build routine to the resource manager
• c) transport controller, which performs the individual access steps

The The transformation routine to be called is to be read or class to be stored. The main access routine receives the information which transformation routine to load is from initialization data the SYS-SYS file. The respective transformation routine can be used for the subsystem, that supports her the structure of the data structures to be read or written determine from an object instance of the ANW-CLS class and corresponding Perform transformations. The routine for The command setup can make special adjustments to a resource manager carry out. The transport controller takes over the control of the external system

storage unit

The Storage unit stores all object instances of different classes in containers. The containers are in a virtual memory. Each object instance present in a container is stored in the storage unit held only once, even if different tasks have the same object instance address. Within the storage unit is every container addressed by a container ID. The contents of in containers lying object instances, so the data elements are through addressed the element descriptor. For array data elements, the index information is still available added. Containers have a fixed base length or a multiple of it. Internally manages the storage unit an address table for Container. The container ID used in the methods as an object handle occurs, corresponds to the index in the address table.

It Figure 12 shows concurrent, read access to an object instance

• • Erstellen Container
• • Löschen Container
• • Kopieren Container
• • Auslesen Objektinstanz des Container
• • Einspielen Objektinstanz in Container
• • Lesen Datenelement
• • Modifizieren Datenelement
• • Löschen Datenelement
• • Insert Datenelement
• • Einlesen Objekt-Liste
• • Commit
• • Update einer einzelnen Objektinstanz auf einem Resourcen-Manager

The storage unit is called by other functional units for particular services. These services are implemented as system routines. The following services are provided:

• • Create container
• • Delete container
• • Copy containers
• • Read object instance of the container
• • Import object instance into container
• • Read data element
• • Modify data element
• • Delete data element
• • Insert data element
• • Read object list
• • Commit
• • Update a single object instance on a resource manager

Container

One Container contains belong together Information of all kinds, here object instance of a class called. Containers can Object instances of professional classes, e.g. Personal data and object instances system technical classes (the runtime environment). In the Container object instances contain a number of individual ones Information, here called data elements. The semantic and formal Description of a data element of a corresponding class Called an element, and in turn becomes an object instance of a container stored. Each of these elements of a class contains a unique one Identifier, called element descriptor. About the element descriptor can uniquely address a data element of a particular container become. A container gets a unique from the storage unit In container methods, this reference is object handle called. about The container ID can be the container throughout the runtime environment be clearly addressed.

The data elements within a container are addressed by the element descriptors. Each data element has an associated, unique element descriptor. The value of this element descriptor is used as an index to the address table in the container. This can be done in the Address table, which addresses the actual data element within the container. The direct addressing of each data element in a container, without sequential searching or putting on a parent element, is supported by this technique. For arrays that exist x times, the indexes of the dimensions are also used for the addressing.

Container have a fixed base length or a multiple of it. The data elements within containers also have a fixed base length or a multiple of these Base length. Internally, a length byte is carried in a data element. By This addressing mechanism has the size and location of a data element does not affect the processing unit method code.

It Figure 13 shows the addressing mechanism in containers

Object ID and Container ID

A an object instance of a class present on a resource manager is provided with a unique object id that is valid for the entire Lifetime of an object instance is preserved. About this can the object instance is uniquely addressed. Be about this object ID referential relationships between object instances (available in SYS-LNK) recorded. Is an object instance in a container of the storage unit loaded, this object instance becomes more specialized within methods Classes over an object handle referenced. This object handle is the same the container ID in which the object instance is loaded.

It Figure 14 shows object ID and container ID

command unit

The Command unit interprets the object code of a compiled one Command of a professional method.

Object code of a method

During the Compilation process are the compiler's commands (source code) the method or the stored XML command elements of the "source code" interpreted and using the element name (same element name in Source of Method and the element description of class ANW-CLS) the element descriptor (El-DE) determined. The element descriptor can then be written in the object code to be created by the compiler.

It Figure 15 shows class description and object code

ever after operation code (voc), the command unit calls a specific one Command module for editing the command. Become data elements needed from the storage unit, routines of the memory unit are called. Get these routines the participating operands (see example above => 11 003) and can then directly access the affected container and the data item. The number 11 refers to an entry, which in turn refers to a Entry within a container table references and the number 003 identifies the element descriptor that is on the data element inside the container.

It Figure 16 shows command operands and container addressing

CreateObject command

• • Laden der Meta-Daten (Objektinstanz der Klasse ANW-CLS) einschliesslich abhängiger Meta-Informationen bei aggregierten bzw. spezialisierten Klassen
• • Bereitstellen Speicher für Container in der Speichereinheit
• • Rückgabe einer Container-ID an die verarbeitende Instanz

The createObject command causes a particular command module to invoke an object instance of a particular class in the command unit, which in turn activates the memory unit. <br/><br/> Via memory unit routines, a container is built into the memory unit :

• • Loading the metadata (object instance of class ANW-CLS) including dependent meta-information in aggregated or specialized classes
• • Provide storage for containers in the storage unit
• • Returning a container ID to the processing entity

Command "move"

The "move" command causes a specific command module to be called in the command unit, which in turn activates the memory unit. Via routines of the memory unit, the move operation is carried out, wherein the data element is transferred from a container into a data element of the same or another container. If the object instance of the target container is an instance with the property "persistent", a first move operation to this target container copies it from the storage unit and performs the operation on the newly created container.

Command "call method"

• • Aufbau einer Instanz einer internen Klasse Methode
• • Sichern Rücksprunginformation der aufrufenden Methode
• • Laden von Meta-Informationen (ANW-MET)
• • Laden Objekt-Code der Methode in einen Container der Speichereinheit
• • Laden Objektinstanzen) falls "temporäre" Klassen im Deklarationsbereich der Methode definiert sind
• • Initialisieren der neuen Methoden-Instanz
• • Laden des ersten Befehls in die Befehlseinheit und ausführen

For the call-method command, the command unit invokes a particular command module to load and execute a method, as follows:

• • Building an instance of an internal class method
• • Save return information of the calling method
• • Loading Meta Information (ANW-MET)
• • Load object code of the method into a container of the storage unit
• • Load object instances) if "temporary" classes are defined in the declaration area of the method
• • Initialize the new method instance
• • Load the first command into the command unit and execute

The calls calling method the method called a container ID, via which the called method Access to needed Receives data items in this container.

It Figure 17 shows method call and transfer of data elements

Command "setLink"

Of the Command "setLink" with which a relationship can be established between two object instances, controls corresponding command module in the command unit, which in turn drives the memory unit. Through routines of the storage unit become two specific containers with object instances of type SYS-LNK addressed. Each of these two object instances becomes a new one Added entry of the object ID, which reflects the new relationship between both object instances. In the subsequent control statement "commit", the contents of these containers of the access unit is stored on a resource manager.

It Figure 18 shows method call and transfer of data elements

Commit command

• • Aufruf der Speichereinheit: Vorgang commit durchführen.
• • Die Speichereinheit ermittelt, welche Container in der Transaktion verändert worden sind und deren Zustandsänderung an beteiligte Subsysteme weitergegeben werden muss.
• • Aufruf der Zugriffseinheit: Übergabe einer Container-Liste, welche Container von der Statusänderung betroffen sind und auf Resourcen-Manager zu speichern sind.
• • Warten auf Beendigung des Commit-Vorganges

For the commit command, the command unit invokes a specific commit command module, following these steps in the module:

• • Calling the memory unit: perform the commit procedure.
• • The storage unit determines which containers in the transaction have been changed and whose status change must be passed on to participating subsystems.
• • Access unit access: transfer of a container list, which containers are affected by the status change and are to be stored on resource manager.
• • Wait for the commit to complete

• • Lesen des ersten Containers aus der Speichereinheit einschliesslich Art der Statusänderung (update, delete, insert)
• • Ermitteln der Kommunikationseigenschaften des beteiligten Subsystems (für diesen Container) mit der damit verbundenen Statusänderung aus der Objektinstanz vom Typ SYS-SYS
• • Durchführen der Transformation
• • Aufbau eines Zugriffsbefehls
• • Aufruf des Subsystems
• • Überwachen des Zugriffs mit Protokollierung
• • Lesen des nächsten Containers mit den bereits dargestellten Verarbeitungsschritten
• • Rückgabe der Kontrolle an die Methode der Verarbeitungseinheit.

The access unit automatically assumes the further processing steps in order to pass on the status changes to the subsystems. These steps are:

• • Read the first container from the storage unit including the type of status change (update, delete, insert)
• • Determine the communication properties of the participating subsystem (for this container) with the associated status change from the object instance of type SYS-SYS
• • Perform the transformation
• • Structure of an access command
• • call the subsystem
• • Monitor access with logging
• • Read the next container with the processing steps already described
• • Return control to the processing unit method.

The entire control for the update process is kept away from the technical method. For A logical transaction is a collection of all changed, deleted, or newly created object instances, all located in containers, into a unit of work.

Command "getIn" with operand one Instance of ANW-AKV

• • Aufruf Speichereinheit: Laden Objektinstanz der Klasse ANW-AKV
• • Aufruf Speichereinheit: Ermitteln der zu übertragenden Datenelemente aus Objektinstanz von ANW-AKV
• • Aufruf der Speichereinheit: Auslesen der Datenelemente aus IN-FRM
• • Abgleich der ausgelesenen Definitionen aus ANW-AKV und IN-FRM
• • Aufruf der Speichereinheit: Schreiben Datenelemente in fachliche Objektinstanz der entsprechenden Klasse

For the getIn command, the command unit invokes a specific command module.The global object instance of class IN-FRM is addressed in this command.

• • Call memory unit: Load object instance of class ANW-AKV
• • Call memory unit: Determine the data elements to be transferred from the object instance of ANW-AKV
• • Calling the memory unit: Reading the data elements from IN-FRM
• • Comparison of the read definitions from ANW-AKV and IN-FRM
• • Calling the memory unit: Write data elements into the functional object instance of the corresponding class

Command "putOut" with operand one Instance of ANW-AKV

For the command "putOut" calls the command unit a specific command module. The global object instance of the class OUT-FRM is addressed in this command.

The Control statement "PutOut" contains operands for one Reference to an ANW-FRM, an ANW-AKV and an object instance whose Content is to spend. The presentation unit can over these allocations for the appropriate output device generate the output message.

• • Aufruf der Speichereinheit: Adressierung OUT-FRM für Übergabe der Objektinstanz deren Inhalt ausgegeben werden soll
• • Aufruf der Speichereinheit: Adressierung OUT-FRM für Übergabe der Objektinstanz von ANW-AKV
• • Aufbau der Speichereinheit: Adressierung OUT-FRM für Übergabe der Objektinstanz von Klasse ANW-FRM.

The following steps are performed in the module:

• • Calling the memory unit: Addressing OUT-FRM for transferring the object instance whose contents are to be output
• • Calling the memory unit: Addressing OUT-FRM for transferring the object instance of ANW-AKV
• • Structure of the memory unit: Addressing OUT-FRM for transferring the object instance of class ANW-FRM.

Command "return

• • Restoren Rücksprung-Informationen
• • Freigeben der zu beendenden Methode
• • Freigeben der in der beendenden Methode enthaltenen Objektinstanzen der Klasse ANW-CLS (Eigenschaft temporär)
• • Aufbau des nächsten Befehls (Befehl nach Method-Call der beendenden Methode).

The "return" command terminates an actively running method, and control returns to the calling method, and if the terminating method belongs to an application-class class, the dialog step is ended and a message is output to a browser or terminal the command "return" calls the command unit a specific command module. The following steps are performed in the module:

• • Restore return information
• • Release the method to be stopped
• • Releasing the object instances of class ANW-CLS contained in the terminating method (property temporary)
• • Structure of the next command (command after method call of the terminating method).

Command "logon"

• • Aufruf Speichereinheit: laden ANW-MAIN Objektinstanzen der Anwendung
• • Aufruf Speichereinheit: laden ANW-MEN Objektinstanzen der Anwendung
• • Aufruf Speichereinheit: laden ANW-MET Objektinstanzen der Anwendung
• • Ermitteln Startup-Methode
• • Aufruf Befehleinheit: aufruf Startup-Methode.

For the "logon" command, the command unit invokes a particular command module, which activates a specialized application, loading the metadata needed for the application into the storage device.

• • Call storage unit: load ANW-MAIN object instances of the application
• • Call memory unit: load ANW-MEN object instances of the application
• • Call memory unit: load ANW-MET object instances of the application
• • Determine startup method
• • Call instruction unit: call startup method.

Command "sendEvent"

Of the SendEvent command sends a specific one Event in an event queue. Other tasks can register for events These get over afterwards Notify the "waitEvent" command about the Occurrence of the corresponding event.

• • Schreiben bestimmten Event in eine bestimmte Event-Queue

For the sendEvent command, the command unit invokes a specific command module, following the steps in the module:

• • Write a specific event to a specific event queue

Command "waitEvent"

• • Warten auf bestimmten Event einer bestimmten Event-Queue

The waitEvent command waits for a specific event written to the event queue by the sendEvent command. For the waitEvent command, the command unit invokes a specific command module, following the steps in the module:

• • Wait for specific event of a specific event queue

embodiment

• (1) Das Ablaufsystem empfängt ein Ereignis und eine Eingabenachricht. Diese Eingabennachricht wird durch die Präsentationseinheit in einen Container gepackt und der Speichereinheit zum Zwischenspeichern (Container IN-FRM) übergeben.
• (2) Die Methode_1 wird von der Steuereinheit aufgerufen.
• (3) Die Methode erstellt über einen entsprechenden Befehl (CreateObject) den Container C1 vom Typ „persistent" in der Speichereinheit.
• (4) Über den Befehl GetIn wird der Inhalt des zwischengespeicherten Containers dem Container C1 zugewiesen. Über den Befehl „GetIn" können weitere Inhalte des Containers IN-FRM auf Objektinstanzen anderer Klassen zugewiesen werden.
• (5) Über den Befehl „Commit" werden die Objektinstanzen, deren Klasse mit „persistent" definiert worden sind, auf die Datenbanken bzw. Resourcen-Manager festgeschrieben. In diesem Fall nur die Objektinstanz des Containers C1.
• (6) Über den Befehl „PutOut" wird eine fest vorgegebene Ausgabe-Message (OK-Msg) dem Ausgabe-Container OUT-FRM zugewiesen.
• (7) Bei Beendigung der Methode wird von der Präsentationseinheit der Container OUT-FRM gelesen und eine Ausgabenachricht entsprechend dem Ausgabegerät erstellt.

It shows Figure 19 Example of an input / output to a browser

• (1) The execution system receives an event and an input message. This input message is packed by the presentation unit into a container and transferred to the storage unit for caching (container IN-FRM).
• (2) Method_1 is called by the control unit.
• (3) The method uses a corresponding command (CreateObject) to create container C1 of type "persistent" in the storage unit.
• (4) The GetIn command assigns the contents of the cached container to container C1. The "GetIn" command can be used to assign further contents of the container IN-FRM to object instances of other classes.
• (5) The "Commit" command commits the object instances whose class has been defined as "persistent" to the databases or resource managers. In this case, only the object instance of the container C1.
• (6) The command "PutOut" assigns a fixed output message (OK-Msg) to the output container OUT-FRM.
• (7) Upon completion of the method, the presentation unit reads the container OUT-FRM and creates an output message corresponding to the output device.

Note about infrastructure services

The Contains method_1 in this example, in their commands no references to technical Data elements, only subject-dependent Information about the operands C1. The "data stream" on the way from presentation unit to a resource manager is running the method "over." By this circumstance technical data does not physically pass through the scope of a Method. If the operand C1 is initialized application-specific, the processing entity can be used in many ways.

programming model

Features of the programming model:

• • Each technical project is in an object instance of class ANW-MAIN described.
• • For this Application can One to many professional classes of ANW-CLS are defined.
• • One certain professional class is defined with the attribute "application".
• • One Application is instantiated with the command "logon".
• • at Activation of an application becomes the object instance of the professional Pre-instantiated class with the attribute "Application".
• • The Apply methods of class with attribute "Application" the activation of further professional classes and the calling of Methods of these activated classes.
• • Applications can inherit other applications, this application can be the methods of call inherited application.

Features of the supported object model

The runtime environment supports an object model at the class and data level. Conventional object-oriented languages encapsulate the object instances of instantiated classes. The object instances of classes described here are also encapsulated, only methods of their own class or inherited methods can access the object instances. The object instances reside in containers of the memory unit which However, individual functional units of the runtime environment have access to the object instances via the memory unit.

A technical class, defined by an object instance of ANW-CLS, always has a unique class ID. The class ID is the same the object ID whose value in the object ID attribute of the object instance of ANW-CLS.

specialization

classes can from other classes their behavior (methods) and the status (elements) inherit. In object instances of class ANW-CLS becomes specialization Are defined.

It shows picture 20 specialization

Sub-Klasse_1 and Sub_class_2 inherit the methods and attributes of their superclass. The specialization relationships are in the class description the super class that defines sub_class_1 and 2.

aggregation

classes can be composed of other classes. They inherit in this case the behavior (methods) of the aggregated classes. Professional classes, which aggregate other classes can cause instantiation that their aggregated classes are instantiated by the runtime environment become. Object instances of class ANW-CLS become the aggregation Are defined

It shows picture 21 aggregation

Klassen_A aggregates classes class_1 and class_2. The aggregation relationships be in the class ANW-CLS for Class_A, Class_1 and Class_2 defined. The public expression of a certain relationship, i. the aggregation relationship of very specific Instances of one or more classes are stored in SYS-LNK.

association

classes can Own relationships with other classes. In object instances of the Class ANW-CLS defines the association

It shows picture 22 association

A Object instance of class_1 can have a relation to an object instance have class_2. The association relationships become object instances defined by class_1 and class_2 of class ANW-CLS. The real one shaping a particular relationship, i. the association relationship of whole certain functional object instances are stored in SYS-LNK.

Initialisierungskonzept for methods

• 1) Eingestellte Kontexdefinition einer Anwendung
  
• 2) Definition einer Klasse in ANW-CLS von Typ „context".
  
• 3) Deklaration der Klasse ANW-CLS vom Typ „context" im Deklarationsbereich einer Methode. Die Deklaration entspricht einer logischen Deklaration, zur Ausführungszeit wird eine reale Objektinstanz des jeweiligen Kontext zugeordnet.
  
• 4) Pflege der Initialisierungswerte für reale Objektinstanzen der Klasse ANW-CLS (context) im jeweiligen Kontext. Objektinstanzen der Klasse ANW-CLS des Typ „context" definieren Initialisierungsparameter für Methoden. Die in einer Methode enthaltenen Befehle können diese Initialisierungs-Parameter direkt lesen.
  
• 5) Aufruf und Initialisierung einer Methode. Für die logische Deklaration einer ANW-CLS Klasse vom Typ „context" wird unter dem laufenden Kontext, z.B. der Rolle „Kunde", eine reale Objektinstanz der Klasse „Konto-Init-Werte" gesucht und in diesem Beispiel geladen. Eine Methode kann hierdurch ihr Ablaufverhalten bestimmen. Je nach Kontext, in dem die Methode läuft, kann über das Kontextkonzept eine andere Objektinstanz mit anderen Initialisierungsparametern angezogen werden.

The context-dependent initialization concept of methods depends on different definitions, these are in detail:

• 1) Set context definition of an application
  
• 2) Definition of a class in ANW-CLS of type "context".
  
• 3) Declaration of class ANW-CLS of type "context" in the declaration area of a method The declaration corresponds to a logical declaration, at execution time a real object instance of the jewei assigned to a valid context.
  
• 4) Maintenance of the initialization values for real object instances of class ANW-CLS (context) in the respective context. Object instances of class ANW-CLS of type context define initialization parameters for methods The commands contained in a method can directly read these initialization parameters.
  
• 5) call and initialize a method. For the logical declaration of an ANW-CLS class of type "context", a real object instance of the class "Account Init Values" is searched under the current context, eg the role "customer" and loaded in this example Depending on the context in which the method is running, the context concept can be used to attract another object instance with different initialization parameters.

The Administration environment of the runtime environment supports directly this concept of initialization of methods. Each in one application defined class of ANW-CLS type "context" is through the administrator environment for the respective application automatically integrated. In this administrator environment will for every defined application defines the defined object instances of the class ANW-CLS (context) considering the defined context with their respective input parameters. The parameters can be set in This administrator branch can be set directly.

Extensible instruction sets

The Extendable Command Set architecture allows new commands define and expose the runtime environment. The following coordinated individual components work together:

It Figure 23 shows Extensible Instruction Sets

development environment

In The development environment of the runtime environment must have a new command control to be activated. This will cause a graphical command control in the command bar, in which all active command controls one Application are visible.

Structure of the command

One Command is composed of an operation code and operands. The operands are interpreted by the command module, which is based on the operands must be matched. The operands are entered by Command control set in the development environment, in the Usually they consist of constants or element descriptors including References to a container ID.

Command Control

In A graphically based flowchart of a method becomes a command control placed in the appropriate place where its activity required is. The control leads the developer of an application to the necessary inputs of the operands. The defined command and the necessary operands are stored in an XML structure. For the filing and correct placement in this XML structure provides the development environment has an interface that provides the control must drive.

compiler

Of the Compiler generates from the XML structure that describes the method an object code. The individual commands appear with their set operation code and the operands in this object code.

command unit

The Command unit interprets the object code of a command. Based of the operation code is jumped to the command table, where the addresses of the Command modules are to be found.

command module

The Command module receives from the instruction unit, the operand list of a command. Operand list and command module are matched. The command module uses the well-defined interface of the memory management system, to access data elements of containers.

Interface of the memory management system

• • Erstellen Container
• • Löschen Container
• • Kopieren Container
• • Auslesen Objektinstanz des Container
• • Einspielen Objektinstanz in Container
• • Lesen Datenelement
• • Modifizieren Datenelement
• • Löschen Datenelement
• • Insert Datenelement
• • Einlesen Objektinstanz
• • Einlesen Objekt-Liste
• • Commit
• • Update Objektinstanz

The hard-defined interface of the memory management system provides a set of functions that can be called by a command module. These are, for example

• • Create container
• • Delete container
• • Copy containers
• • Read object instance of the container
• • Import object instance into container
• • Read data element
• • Modify data element
• • Delete data element
• • Insert data element
• • Read object instance
• • Read object list
• • Commit
• • Update object instance

SYS-SYS

In the runtime environment initialization data becomes the supported commands and associated command modules. When starting the runtime environment If this initialization data is read, the command table is initialized and the associated command modules loaded.

development environment

• • Anwendung und geerbte Anwendungen
• • Klassen, geerbte Klassen und aggregierte Klassen
• • Methoden
• • Service
• • Menüs
• • Geschäftsprozesse (GPO)
• • Kontext-Elemente wie Rollen, Device, Sprache
• • Befehle innerhalb einer Methode

The graphically based development environment captures all information and relationships of all objects involved in an application in XML structures. Relationships between objects are not textually captured by source code, they are described by graphical connectors. Objects of an application are:

• • Application and inherited applications
• • Classes, inherited classes, and aggregated classes
• • Methods
• • Service
• • Menus
• • Business Processes (GPO)
• • Contextual elements such as roles, device, language
• • Commands within a method

The individual objects such as application, classes, methods, service and their relationships are stored in XML structures as object instances of the classes ANW-MAIN, ANW-CLS, ANW-MET, ANW-SRV, ANW-MEN and so on. These definitions simultaneously form process instructions and documentation. The individual graphical objects can be created by double-clicking, eg on element travel system, ge be specified.

It Figure 24 shows objects of an application to be developed

Of the Flowchart of a method of a class is represented by graphic elements, here command controls called, described. Command controls are in the flowchart of a Attached method to connection points mentioned here, this can be the position of each command control dependent on to other command controls. Double click on a command control can the operands for be specified this command. Command controls have access to the metadata of an application, ie the object instances of ANW-CLS, ANW-MET, ANW-SRV and so on the possible and necessary inputs to a particular command-control exactly guided become.

It Figure 25 shows the graphical programming of a method

Command Controls

It Figure 26 shows some command controls

Everyone Command represented by a command control is internally in own XML command element filed and is identified by a unique element ID. The XML Command elements are linked by references through this Element ID, this can be done for a single command the previous and subsequent command, at Branching commands also have several choices of successor commands be recognized. The connection points In the graphical flowchart, these references identify between Command elements.

Each XML command element has the following structure:
position information
describes previous and subsequent commands

declaration information

describes depending on the type of command, the definitions entered, for IF command, e.g. the query conditions and references to element descriptors and Object handle (container identifier)

Object code

Object code based on the command type and entered declaration information. This is used by the compiler to create the object code of the method installed at the appropriate place.

glossary

class

description from object technology, where classes are next to a behavior (Methods) also define a status (attributes). A lot of similar records, which have a uniform structure, become a class summarized.

method

description from object technology, in which the behavior of classes through Methods is defined. Methods usually lead to modifications and read requests on attributes of an object instance.

object

designation from the object technology. Object is a single expression, also called instance of a class.

object instance

Name for an object loaded in a container of a certain class within the Ab running environment. This object instance is addressed by a container ID. The object instance contains a unique object ID that identifies this object instance on a resource manager and in the runtime environment.

element

least Information unit in a class. An element describes one Information unit semantic, e.g. with name, format and length. unique Identifier for an element within a class is the element descriptor.

Element descriptor

description for one Identifier that uniquely identifies each element of a class becomes.

data element

Designated an information value within an object instance. It puts represents the value of an element within an object instance Data element belongs to a particular element. Each data element can be unique and directly above Object ID and the value of the element descriptor are identified. When array structures come for the unique identification of a data element nor the position indexes added.

Object ID

One Data element that uniquely identifies an object instance.

Container

Under Container is one in the storage unit in this patent application related Information called composed of individual data elements and over the container ID is addressed.

program

description for a Computer program, which converts from a compiler into a machine-readable format is converted. The machine-readable program consists of this the two parts "program segment" and "data segment". The program code of the program segment addresses the individual data elements within of the data segment via fixed offset addresses, in which the position of a data element within the data segment. The addressable Data is physically in the data segments (exception stack segment).

• a) direkt die Hardware, also CPU
• b) eine virtual machine, z.B. JVM gemeint.

Note: in this context is machine-readable

• a) directly the hardware, so CPU
• b) a virtual machine, eg JVM meant.

application server

Operating environment for computer programs, solve a technical problem. Important in this context is that for the application server no restriction on a specific subject area. The technical implementation An application server can take various forms. Are important the available functions and their tasks of the application server, so are u.a. Manages resources. These are virtual memory, Database connections, connections to terminals (session handling). Of Furthermore, the unit of work (UOW) handling is taken over by the application server.

Operating environment

• a) direkt in einem Applikationsserver integriert sein, in der Regel ist sie dann vom selben Software-Hersteller
• b) sie kann als Zusatzkomponenten (Java-Beans, COM-Komponenten, C++ Klassen) auf einem Applikationsserver aufsetzen. In der Regel ist die Ablaufumgebung dann von einem anderen Software-Hersteller als dem des Applikationsservers.

Entscheidend ist die erreichte Gesamtfunktionalität, weiter das angestrebte Ziel, und mit welchen Mitteln dieses Ziel erreicht wird.A runtime environment in this patent application refers to the part of an application system that contains the classical components of an application, these are presentation layer, control layer, test layer and access layer. The programs of the processing layer (programs of business and infrastructure layer) run within the runtime environment. The technical implementation of the runtime environment can be designed differently, it can

• a) be integrated directly into an application server, usually it is then from the same software manufacturer
• b) it can be set up as additional components (Java beans, COM components, C ++ classes) on an application server. In general, the runtime environment is then from a different software manufacturer than the application server.

The decisive factor is the overall functionality achieved, the desired goal, and the means by which this goal is achieved.

Application layer, application logic, application system

designated in this context the sum of all to be programmed, to be generated or defining components of a software system to a to solve certain technical task.

access layer

part of the part to be programmed, generated or defined an application system that provides access to persistent data or remote access.

application layer

designated in this context the summary of business layer and infrastructure layer.

Businesschicht

designated in this context, the part of the programs that are purely technical Perform processing, without access layer, test layer, Control layer and presentation layer. The programs of this layer must usually be programmed.

infrastructure layer

designated in this context, the part of the programs or methods that are reusable, provide non-technical functions. Methods of this Layer are characterized by the fact that they have no technical data or data elements, but only references to objects different professional classes. The programs of this layer have to usually be programmed.

Check Layer

of the Part of the application layer that goes into the application server technical data checked for accuracy.

control layer

of the Part of the application layer, the inputs from the presentation layer or a remote client and performs control of the calling processing to be called.

presentation layer

of the Part of the application layer that handles the rendering of a screen or remote output takes over or receive a screen or remote input. Also the software part, physically on the terminal is, counts to.

object model

designated in this context all necessary for a technically circumscribed task Objects of different classes and their dependencies among each other.

Active data model

within a functional transaction, all actively involved object instances.

UOW data model

all amended persistent object instances that are jointly named as "Unit of Work "edited and have to be stored.

Virtual Machine (VM)

description for one software-based implementation based on a function call or a defined operation code a specific software-based control initiates, e.g. "About wearing Content of data element A to data element B ".

subsystem

description for a Resource Manager or external system with the defined communication properties. These communication properties are taken from the access layer for the Control of the subsystem used.

Claims (12)

Method and device for receiving and controlling information-processing, program-controlled processes in computer systems, characterized in that incoming information is packed into containers in the device referred to here as a runtime environment. In the runtime environment constructed from functional units, the container contents are processed by means of special commands of the processing unit and forwarded logically by the functional units. The containers are provided with meta-information about their content and relationships with other containers. All functional units have direct access to the containers, including their contents. The functional units are in detail: a) presentation unit this unit receives / sends messages from / to external terminals or end systems such as browsers. b) Checking unit This unit checks received messages for correctness of form and content c) Control unit This unit activates a method of the processing unit on the basis of a received event d) Processing unit This unit contains information processing methods. The special commands contained in the methods have direct access to the contents of the containers via the command / memory unit and control the containers through the individual functional units. e) Storage Unit This unit stores containers in virtual memory with the data items contained in object instances. Each container is identified by a unique container identifier. In addition, each data element within a container is also identified by a unique identifier. f) Command unit This unit processes the commands contained in the information-processing methods or delegates the execution to other functional units. g) Access unit This unit reads information from a resource manager or external system and stores this information in containers of the storage unit. Likewise, it transfers information, taken over as a container from the storage unit, to resource managers and external systems for storage on a persistent medium. The message of an external system received by the presentation unit is packed into a container, containers and each data element contained therein are uniquely identified by identifiers and transferred to the memory unit for buffering. Depending on the event associated with the message and context-dependent control information, the control unit determines a specific method to be activated. The processing unit is called and the method determined by the control unit is loaded. The processing unit gives the instruction unit the first instruction to be executed, which activates a particular module of the instruction unit, depending on the type of execution the command. The method contains commands for further, specifically executed processing steps. The commands contained in the method are classified according to the following functional characteristics, whereby mixed forms occur: a) Container-creating commands create a container in the memory unit. In addition, you can load object instances or object lists from a resource manager or external system into the container. b) Container-saving commands cause the transfer of containers to an external system or the transfer to a resource manager for storage on a persistent storage medium. c) Container deleting commands delete a container from the storage management system. d) Object instructions receive, at run time, a reference to an object instance of a particular class in which instruction execution instructions are communicated. e) Container contents read / modify commands read / modify the content of containers f) flow control commands cause control of the flow behavior of methods The processing unit reads the first instruction to be executed, including operands, contained in the method. This is transferred to the command unit and, depending on the command, a specific sequence in the command unit is triggered or delegated to other functional units. After the execution of the command, the next command to be executed is read and another sequence is initiated. Container creating commands cause the creation of a container in the storage unit. In addition, they can import object instances or object lists into the container. In this case, a specific command module is activated in the command unit. Starting from this command module, various functional units are activated: • Command unit: activate Memory unit => load Meta data • Storage unit: create a container in the storage unit • Storage unit: activate Access unit => read Meta data • Access unit: read meta data from a resource Manager and save meta-data in container • Command unit: activate storage unit => load subject-specific object instance • storage unit: create container for functional object instance • storage unit: activate access unit => read object instance • access unit: read functional object instance from a resource manager and save object instance in container • Storage unit: check referential relationships with other object instances • Storage unit: Depending on the previous check, additional object instances must be loaded. The activation for this is initiated by the module of the memory unit. Container-saving commands cause a container content to be stored on a resource manager or on an external system. In this case, a specific command module is activated in the command unit. Starting from this command module, various functional units are activated: • Command unit: activate Storage unit => save container contents • Storage unit: identify all containers that have been changed in the transaction. The memory unit keeps a log of all containers changed in a transaction. • Memory unit: activate Access unit => transfer List of containers to be stored • Access unit: per container the class of the contained object instance and the subsystem involved is determined. • Access unit: per subsystem the communication properties (communication protocol , Communication driver, ...) and transformation rules determined • Access unit: The object instance is read from the container and the transformation to the destination format of the resource manager or external system is performed. • The access unit knows the communication characteristics of the resource managers and external systems and performs them one after the other accesses via the communication drivers by • storage unit => delete containers from storage management system (the containers with outdated content that have been copied for an update process). Container deleting commands cause containers to be deleted in the storage management system. There is no deletion on the assigned resource manager. To do this, a container-saving command must be issued. A delete command activates a specific command module in the command unit. Starting from this command module, various functional units are activated: Memory unit: checking the referential integrity rules of the deletion process (metadata already loaded, object instance already active) for the functional object instance • memory unit => load object instance from SYS-LNK in which referential relationships are stored • memory unit: check whether there are relationships to object instances to be deleted • memory unit: if no => copy the container to be deleted • Storage unit: copy container • Storage unit: set status change (delete) on copied container. Container content-dependent commands cause a content to be changed or read from a container. There they lead via the given operands, which consist of the unique identifiers of container and data element, to modify or read a data element of a container. In addition to a single data element, a data element group, which is also identified via a unique identifier, can be read or manipulated. For a content-dependent command, the command unit activates a specific command module. Starting from this command module, various functional units are activated: • command unit: activate memory unit => read or modify data element • memory unit: copy container • memory unit: read or modify data element • memory unit: if modified => set change of state (modify) Sequential commands cause a Control the flow behavior of methods. Each command within a method is uniquely addressable. Via the references contained in the flow control commands, which refer to corresponding other commands, the next command to be executed is transferred to the command unit and executed. Sequential commands calling other processing unit methods are executed by the instruction unit step by step or delegated to other functional units. In the case of a run-controlling command, a specific command module is called in the command unit. Starting from this command module, various functional units are activated: • Command unit: activate Storage unit => load object code of the method • Storage unit: create a container in the storage unit • Storage unit: activate access unit => read meta data of the method • Access unit: read meta data from a resource manager • storage unit: store meta data in container • storage unit: create container in the storage unit • storage unit: enable access unit => read object code of the method • access unit: read the object code from a resource manager • storage unit: store object code in container • Command unit: determine the object instances contained in the declaration area of the method (the classes with property temporary, context, service) • Command unit: activate Memory unit => load the object instances if object instances are defined in the declaration area si nd. The method is loaded via storage and access unit, whereby the object code of the method is stored in a container of the storage unit. After loading, the method is initialized and the first executable command is passed to the instruction unit and executed. Sequential commands that cause an active method to terminate are executed or delegated step by step by the command unit. The storage unit is called and temporary containers of the terminating method are released. After completing this method, the instruction unit will re-activate the original calling method and continue through the sequence of instructions. Sequencing instructions that cause termination of active processing are also executed or delegated by the instruction unit step by step. • Command unit: Restore return information • Command unit: activate Storage unit => release temporary containers • Storage unit: delete Set container or delete status • Command unit: activate Storage unit => release Method • Storage unit: set Use-Count of the method to be stopped • Storage unit : Call Next Command (Method Call Command) The presentation unit is called and an output message is created for the corresponding output device from a previously assigned output container. Subsequently, the message is sent to the output device and the active processing is terminated. Object commands receive operands at execution time, one of which is a reference to an object instance of a particular class to be specifically defined. Through this instance, the command receives input information to which the instruction's processing refers, eg, transferring contents of one or more containers to another container or containers. Object commands are executed or delegated step by step by the command unit. • Command unit: call memory unit => load object instance • memory unit: create container • memory unit: call access unit => read object instance • access unit: read data record and store in container • command unit: call memory unit => read instructions • memory unit: return the instructions • command unit: Processing (with call possibly further functional units) characterized in that presentation unit, test unit, control unit and access unit are implemented in system routines of the runtime environment. The control of the outsourced functional units are not programmed in a technical application to be created, but defined. The functional units paged out in the runtime environment and the associated system routines are independent of the containers involved and their contents, ie they do not need to be reprogrammed or extended to support a new class. The system routines of the functional units are controlled by objects of the application system that are stored in the ANW- * files and loaded into containers when a specialized application is opened. characterized in that from external systems (resource manager) coming data of certain information structure are converted into an internal format and stored as an object instance in a container, which allows direct addressing to individual data elements. The internal format is formally described using metadata of class ANW-CLS. This meta-data, which also resides as an object instance in a container, is referenced by the object instances of the internal format via class ID and element descriptor. characterized in that contiguous information can be summarized in containers. Containers can contain various contents of different classes. In them, data is read from or stored on a persistent medium. Internal, coherent information of the runtime environment is also summarized in containers. Each element with the contained value can be directly addressed in the container, without sequential searching of similar elements. characterized in that containers are formed in the memory unit by a structure in which each individual data element can be stored and read by itself and independently of the location of other data elements. Each container can be uniquely addressed by an identifier, the container ID. Each container contains an index-based addressing mechanism that can be used to directly and uniquely address the data elements contained in the containers. For this purpose, the unique identifier of a data element called element descriptor is used. This element descriptor is used as an index in a table in the container that points to the actual data elements. The object instance contained in a container can be read coherently, so that the correct order of the individual data elements of the object instance is maintained. A container can be moved or copied in its entirety, the internal information is retained. characterized in that information-processing methods to be programmed are classified into two types, whereby mixed forms can occur: a) Infrastructure methods These methods contain commands which are independent of a particular technical processing and perform their processing on a multiplicity of object instances of different classes, eg Copy a container. Characteristic of these methods is that the methods do not contain any functional data elements of a particular class. The data stream or container is routed past the method, but the method retains control of the container. This crucial feature enables infrastructure services to be set up that are independent of the "content" of the containers to be "transported." These infrastructure services are controlled by initialization data of the methods that are defined based on a specialist service concept for each technical service These infrastructure services can be compared to the motorways, for example, they connect Hamburg with Munich via certain sub-highways.The option of getting from Hamburg to Munich via these motorway sections corresponds to an infrastructure service.Which vehicle (container) travels with which content these freeways sections , is usually irrelevant b) Business methods These methods contain a technical processing and are formed by container-reading and container-modifying commands The methods contain in their declaration area technically dependent data definitions. that the storage unit is realized by a central storage management system (SMS) in which all object instances are loaded in containers only once and shared by different processes. Containers to be changed are copied by the storage management system and the new container is made available to the relevant process (task) on its own. All functional units have direct access to the containers and data elements within the storage unit; there is no encapsulation of the containers in relation to the functional units. In the memory management system, each data element of a container is directly and uniquely addressable via the identifier of the container and the identifier of the data element (element descriptor), without iterative sequential passes. For array data elements, the position indices are added to uniquely identify a data element. In addition to the object instances whose class is defined by the type "persistent", ie which are to be stored on a resource manager, there are also object instances in the SMS whose classes are defined as "temporary". The same addressing procedures with identifiers for containers and identifiers of the data element also apply to these. An important feature of the memory management system is that the memory unit for each current transaction carries a log in which status changes (rebuilding a container, changing the contents of a container, deleting a container) of containers are noted. With commit processing, these containers, whose status has been changed, are to be processed as a coherent unit of work and to be communicated to the access unit. A commit command saves all changed containers. characterized in that methods of the processing unit directly address the data elements lying in the containers via an identifier of the container and an identifier of the data element. Methods of the processing unit define in their declaration area the class to which the object instance loaded in the container is accessed. The declaration contains the reference to the unique identifier of the container and the unique identifiers of the contained elements. The compiler uses this definition in the data definition area to construct the opcode and to address a container and the data elements. characterized in that methods of the processing unit exercise direct control over the flow of container contents through the layers involved. By means of a corresponding command, a method can read in the cached container content of a terminal (eg browser) into one or more containers located in the storage unit or, for example, cause the transfer of the containers located in the storage unit to a resource manager for storage. The controlling-type methods have no knowledge of the contents of containers, but are driven by contextual data. As a result, these methods can be used for a large number of different containers. Reusable infrastructure services are hereby established. characterized in that methods of the processing unit can call directly other methods of the processing layer, wherein an information transfer via the following two options: a) the calling method passes for each parameter for each of these parameters a container identifier and the element descriptor to the called method. b) the calling method only transfers container identifiers, in which case the called method has access to all data elements of these containers. After completing the called method, the next command in the calling method continues after the call. characterized in that a continuous and uniform addressing of a data element within a container in the memory unit by container identifier and element descriptor over all functional units of the software system. These units are access unit, processing unit methods, test unit, control unit, presentation unit. Depending on the software implementation of the runtime environment, these units can be clearly delimited from one another, or can merge smoothly. characterized in that a unique identifier of each element of a class is ensured by an element descriptor. The value of this element descriptor is preserved for the entire "lifetime" of an element in a class, uniquely addressing the content of an element within a container, that is, the data element Index used for addressing a table element, characterized in that methods of the processing unit can call the access unit via sending and receiving commands, for example, to cause the loading of an object instance into a container.After that, with the following command, which after the sending or receiving receiving command follows, proceeded. characterized in that for the lying in container object instances of different classes, the support of a continuous object model by command, memory unit, processing and presentation unit consists. Consistent support for an object model in this documentation means: a) for command and memory units, the administration of referential integrity of object instances with respect to generalization / specialization, aggregation, and association. b) processing unit program-technical linking of object instances of different classes with regard to inheritance, aggregation and instantiation of classes. c) Presentation unit The components of an output on a terminal device (eg browser) consist of object instances of the class SVG objects, text objects and technical object instances. SVG and text objects determine formatting and positions of text and input fields on the output device. All output object instances are stored in containers of the central storage unit and can be used from there. Metadata of the object model describing each technical application is loaded by the access unit into containers of the memory unit when a specialized application is opened and is used by internal routines of the presentation, processing and access unit for the purpose of automating processes. Automated processes include managing and checking the referential integrity of object instances or automatically loading dependent object instances. characterized in that update operations are initiated on resource manager of the command "commit" and for a logical transaction all changed, deleted or newly created containers in the storage unit are combined in a "unit of work". The object instances in the containers can contain technical data as well as system-technical information, eg object instances of the class SYS-LNK. The status changes of these containers combined in a "unit of work" are passed to one or more resource managers for storage.The access unit controls all subsystems involved, via which resource managers or external systems can be reached, according to their communication characteristics In the SYS-SYS class, the access unit receives information about the properties of the subsystems.The access unit takes over the control of the entire update process, that is, changing information on a resource manager, deleting information and adding information Specialized classes with their contained methods, inheritance relationships to other classes with regard to specialization, aggregation and association in XML documents are stored When opening a functional application, these definitions are triggered by the instruction unit via the access unit loaded into a container of the storage unit. characterized in that the technical classes do not encapsulate the object instances in the containers for presentation, testing, control and access unit. The "content-dependent" commands of processing unit methods can read and write to the data elements of the containers, characterized in that context-dependent support (device type, language, role, client) is integrated in the functional units of the runtime environment, becoming a logical call Depending on the context, an object of the runtime environment is resolved into a real call of a real object instance, characterized in that an organizational structure for the inclusion of all necessary objects of particular classes of an application (application, classes, methods, services, business processes, users, groups, roles) is integrated is characterized in that the performance support classes of the property "offset" can be defined, which allow a direct offset addressing from a method to the lying in container data elements. In this case, an operand for the addressing of a data element does not represent an element descriptor, but an offset value via which a data element in a container is addressed. characterized in that the key features of the runtime environment are determined in its compilation of points described below: • Outsourcing of the presentation, test, control and access layer of an application system in the functional units presentation, testing, control and access unit of the runtime environment • Unique Identification of data elements via container ID and element descriptor across all functional units • Direct access via the storage unit to containers and data elements from the technical methods • The controlling control remains with the technical methods, which include A) the reading / saving of object instances from / to a resource manager B) the direct call of another method and return to the calling method C) Read in egg news and output output messages. under claims Apparatus and method according to claim 1 characterized characterized in that based on the mentioned in the claim 1 Features a development system is designed, which the creation of technical methods through the assembly of graphical elements allows. The commands (for example IF or FOR command) are not stored as source text, but in XML documents. For each Command is directed to the previous and following command. About connection points the sequence of commands is defined graphically. For each Command becomes the type of command (e.g., FOR loop) and its necessary operands recorded. From the sum and the order of commands one Method will compile the appropriate object code created, with which the command unit is controlled. Apparatus and method according to claim 1 characterized characterized in that the functional units in the runtime environment "NATURAL" Software AG to get integrated. This will be container content that is in the Storage unit as a new data area type in the declaration area a Natwal application program Are defined. The natwal compiler recognizes this during compilation new data area type and builds for accessing the container contents internally a natwal object code up, over the Natwal Nucleus the storage unit for accessing a container can drive. In a Natural program, the data elements can be used simultaneously of containers and the data elements addressed in conventional data structures become. Apparatus and method according to claim 1, characterized characterized in that information-processing methods of professional Classes from programs, subroutines, functions, interpreter languages, scripting languages can be formed. Device and method according to claim 1, thereby in the instruction set of the instruction unit is designed to be expandable is and allows new object commands. The dispatching mechanism the processing unit reads the object code of a method that recognizes a defined command and invokes the command unit. These calls the appropriate command module for processing the command on. The following components are used: a) command control graphic Control element within the development environment, which command and operands for specifies the command module. b) Command module program code in the instruction unit which executes the translated instruction. This Command module uses fixedly defined interfaces of others Functional units. c) Command object instance object instance a specific class in the instructions for the command module. About here special processing steps of the command module are controlled. d) Command code in SYS-SYS Definition in the command table with corresponding command code and associated command module. About this is the command module is loaded into the runtime environment. Through this Object commands can novel, very powerful Commands that run in a particular context are implemented. Apparatus and method according to claim 5, characterized that defines a command based on the object commands will, the data element transfers container contents of different classes. About this command will be in the processing unit defines accumulation and distribution operations, that of the presentation or access unit accomplished become. A corresponding instruction of the processing unit specifies a command object instance in which instructions are to be accumulated or distributed Elements of classes are specified. Apparatus and method according to claim 5, characterized that defines a command based on the object commands which reads a command object instance from a container, contains the conditions which evaluates the object command for further processing steps head for. Apparatus and method according to claim 5 characterized that defines a command based on the object commands which reads a command object instance from a container, which contains technical procedures, which the object command evaluates and controls certain processes. Apparatus and method according to claim 1, characterized marked identifier of container and element descriptor be realized by values that are the direct, unambiguous entry to allow in a table to address a table element directly. Device and method according to claim 1, thereby in that in the command unit following commands are defined: commit save object instances to Resource Manager update to save certain object instances on Resource Manager createObject create Container and load meta-data deleteObject delete object in the storage unit link object referential relationship Remove between object instances unlinkObject referential Break down the relationship between object instances list objects referential Display relationships of an object instance getObject a Load specific object instance from a resource manager Move Datenlemente from one object instance to another or the same Copy overall Copy containers with content to a new container return back to calling method logon activate application with loading the meta-data and calling the startup method if Comparison at least two data elements loop Loop processing (FOR, WHILE, ...) Device and method according to claim 1, thereby in that the calling technique for accessing the in containers contained data elements can be realized differently: a) The call is directly integrated in the corresponding programming language. In this case, the compiler creates an opcode for the corresponding one Command, a reference to the container identifier and a reference to the identifier of the data element b) he can by a Function call to be realized with transfer of the two identifiers for containers and data element c) he can by a method call with transfer the two identifiers to the instance of a class be realized. In all three cases is accessed by the access a command module of the command unit. This module then controls further functions of the Storage unit access to the data elements of the container. Apparatus and method according to claim 1, characterized in that the objects to be created an application • object application • object class • object method • Object menu • Object Service • Object Business process and their relationship to each other can be created from graphical elements within the development environment. The definitions of these created objects are stored in XML files. The functional units of the runtime environment Load these object descriptions into containers of the memory unit. These descriptions control the flow behavior of an application. The descriptions in the XML files also represent the documentation for an application.