Abstract: In an airbag module arrangement, an airbag module is arranged on a vehicle component, in particular a seatback, the airbag module including an airbag carrier, an airbag and a gas generator, which are jointly attached to a support structure in an installation space of the vehicle component, from which the airbag exits in the event of a triggering and subsequently opens at least one material layer situated over the airbag module and inflates in a passenger compartment, etc. There is a provision for the installation space of the airbag module to be surrounded by a foam part that is closed at least in the direction of inflation, and a fleece-like layer to be situated on the inner side of foam part at least in the desired exit region of the airbag module from the foam part, which has a specifiable perforation in the desired exit region of the airbag module.

Abstract: Techniques are provided to integrate applications having different data structures. Data from the application having a less restrictive data structure is provided to the application with a more restrictive data structure as the application is capable of storing the data. Data from the application having a less restrictive data structure may be stored.

Abstract: Techniques are provided to integrate application systems by using an isolated mapping point that is a computer system, a server, or other computing device that includes a mapping data store and performs mapping functions. An isolated mapping point receives data from the sending system, transforms the data as necessary, and sends the transformed data to the receiving system. The isolated mapping point performs the data transformation without accessing data or processes on the sending system or the receiving system. The isolated mapping point is separate (or isolated) from both the sending system and the receiving system. The isolated mapping point uses only data included in the mapping database. The isolated mapping point receives data included in the mapping database received through a well-defined interface.

Abstract: In an airbag module arrangement, an airbag module is arranged on a vehicle component, in particular a seatback, the airbag module including an airbag carrier, an airbag and a gas generator, which are jointly attached to a support structure in an installation space of the vehicle component, from which the airbag exits in the event of a triggering and subsequently opens at least one material layer situated over the airbag module and inflates in a passenger compartment, etc. There is a provision for the installation space of the airbag module to be surrounded by a foam part that is closed at least in the direction of inflation, and a fleece-like layer to be situated on the inner side of foam part at least in the desired exit region of the airbag module from the foam part, which has a specifiable perforation in the desired exit region of the airbag module.

Abstract: Methods and systems for data maintenance in an offline-distributed database network system, which comprises a central system having a central database, and node systems having local databases capable of containing different subsets of data from the central database. First, change information relating to data stored in at least one of the central and local databases is recorded in at least one of the node systems. Then, a replication object including the change information is transmitted, if an online connection is available, from the recording node systems to the central system or from the central system to the recording node systems. The recipients of the replication object are determined based on at least one lookup table in the central system. The lookup table is updated in accordance with the change information of the replication object.

Abstract: Techniques are provided to integrate applications having different data structures. Data from the application having a less restrictive data structure is provided to the application with a more restrictive data structure as the application is capable of storing the data. Data from the application having a less restrictive data structure may be stored.

Abstract: Techniques are provided to integrate application systems by using an isolated mapping point that is a computer system, a server, or other computing device that includes a mapping data store and performs mapping functions. An isolated mapping point receives data from the sending system, transforms the data as necessary, and sends the transformed data to the receiving system. The isolated mapping point performs the data transformation without accessing data or processes on the sending system or the receiving system. The isolated mapping point is separate (or isolated) from both the sending system and the receiving system. The isolated mapping point uses only data included in the mapping database. The isolated mapping point receives data included in the mapping database received through a well-defined interface.

Abstract: Techniques are provided to integrate applications having different data structures. Data from the application having a less restrictive data structure is provided to the application with a more restrictive data structure as the application is capable of storing the data. Data from the application having a less restrictive data structure may be stored.

Abstract: Techniques are provided to integrate application systems by using an isolated mapping point that is a computer system, a server, or other computing device that includes a mapping data store and performs mapping functions. An isolated mapping point receives data from the sending system, transforms the data as necessary, and sends the transformed data to the receiving system. The isolated mapping point performs the data transformation without accessing data or processes on the sending system or the receiving system. The isolated mapping point is separate (or isolated) from both the sending system and the receiving system. The isolated mapping point uses only data included in the mapping database. The isolated mapping point receives data included in the mapping database received through a well-defined interface.

Abstract: Techniques are provided to permit a gradual or phased migration of a computing environment including groups of mobile clients to a new version of an application program such that the unavailability or downtime of any mobile client is minimized. In one general aspect, the techniques permit a mobile client to connect with an application server of the corresponding version for synchronization whether the mobile client is operating on the starting-version or the new or target-version of the application program and migrates the data between the two versions of the application program. A migration bridge between the starting-version and the target-version of the application program synchronizes the data in the two versions of the application program.

Abstract: Techniques are provided to integrate two or more application systems by using an declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities. Integration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software.

Abstract: Embodiments of the present invention relate to automating the creation of user interfaces for integration. Integration is a process that involves accounting for the differences between two different types of software to enable the exchange of information between the two types of software. Typically, the initial work of the integration process produces a useful storehouse of information about message formats, mappings, data manipulations and other information related to integration. Further on, the deployment of a concrete integration solution adds data about a specific integration landscape to this storehouse. Embodiments of the present invention relate to processing information in this storehouse to automatically generate user interfaces for use in performing integration control operations.

Abstract: Techniques are provided to integrate two or more application systems by using a declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities. Integration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software.

Abstract: Techniques are provided to integrate two or more application systems by using an declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities. Integration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software.

Abstract: Techniques are provided to integrate two or more application systems by using an declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities. Integration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software.

Abstract: Techniques are provided to permit a gradual or phased migration of a computing environment including groups of mobile clients to a new version of an application program such that the unavailability or downtime of any mobile client is minimized. In one general aspect, the techniques permit a mobile client to connect with an application server of the corresponding version for synchronization whether the mobile client is operating on the starting-version or the new or target-version of the application program and migrates the data between the two versions of the application program. A migration bridge between the starting-version and the target-version of the application program synchronizes the data in the two versions of the application program.

Abstract: Companies and other organizations store extensive datasets having overlapping data contents in different data base systems whose data base structures are incompatible with one another. The invention is concerned with the integration of such structurally incompatible data base systems, in particular with the data interchange between such systems. Various procedures are proposed which serve the purpose of combining such data base systems together such that problem-free data interchange is possible in both directions. In particular, the invention allows data shared across the system to be entered and changed in the different systems.

Abstract: Layering techniques are applied to business software integration, in order to provide an integration package that is usable “out of the box,” i.e., substantially upon installation thereof and after a brief configuration process. Accordingly, embodiments may comprise a technical support layer and a business content layer, where the technical support layer and the business content layer are substantially separate and distinct from each other. The technical support layer may comprise a plurality of predefined connectivity and integration patterns that can be configured to support precoded business logic in the business content layer. The layering helps to avoid “monolithic” structures that can prolong integration and be difficult to maintain.

Abstract: Methods and systems for data maintenance in an offline-distributed database network system, which comprises a central system having a central database, and node systems having local databases capable of containing different subsets of data from the central database. First, change information relating to data stored in at least one of the central and local databases is recorded in at least one of the node systems. Then, a replication object including the change information is transmitted, if an online connection is available, from the recording node systems to the central system or from the central system to the recording node systems. The recipients of the replication object are determined based on at least one lookup table in the central system. The lookup table is updated in accordance with the change information of the replication object.

Abstract: Methods and systems for data maintenance in an offline-distributed database network system, which comprises a central system having a central database, and node systems having local databases capable of containing different subsets of data from the central database. First, change information relating to data stored in at least one of the central and local databases is recorded in at least one of the node systems. Then, a replication object including the change information is transmitted, if an online connection is available, from the recording node systems to the central system or from the central system to the recording node systems. The recipients of the replication object are determined based on at least one lookup table in the central system. The lookup table is updated in accordance with the change information of the replication object.