Sap Ag

Sap Se

Stefan Rossmanith

Christoph Hofmann

Peter Surma

Andreas Dahl

Thomas Kunz

Hartwig Seifert

Jona Hassforther

Kathrin Nos

Thorsten Menke

Jens Baumgart

Omar-Alexander Al-Hujaj

Anne Jacobi

Volker Guzman

Duong-Han Tran

Otto Boehrer

Florian Kraemer

Thanh-Phong Lam

Joerg Kessler

Frank Gales

Peter Eberlein

Stefan A Baeuerle

Timm Falter

Marco Rodeck

Volker Wiechers

Wei-Guo Peng

Florian Chrosziel

Eugen Pritzkau

Jens Kisker

Dietmar Storz

Hans-Dieter Geyer

Christian Lienert

Joerg Kraemer

Bertram Vielsack

Roland Preussmann

Knut Thies

Otto Böhrer

Artur Godlinski

Rene Zink

Fritz Hoffmeister

A Content Service executing in a cloud-computing-based Cloud Platform receives enterprise threat detection (ETD) Content transmitted from an ETD Content Development System (CDS) as a publication of the ETD Content from the ETD CDS. The received ETD Content is stored into a Content Management System (CMS). A determination is made of a registered Client ETD System for which the ETD Content is relevant. The ETD Content is published to the registered Client ETD System.

Distributing cloud-computing platform content to enterprise threat detection systems

A log processing job executing on a log producing computing system is initiated for processing log data associated with the log producing computing system. Log entries are determined to be available for processing. At least one instance of a Log Extractor Factory, Reader, and Transformation component are instantiated for reading and transforming the log data. Read log data is transformed into a common semantic format as transformed log data and transmitted in real-time to a Streaming Component for storage in an Enterprise Threat Detection (ETD) System. A recovery point is stored with a recovery timestamp indicating a next log entry in the log data to process.

Providing semantic connectivity between a java application server and enterprise threat detection system using a J2EE data

Data characterizing a plurality of data accesses of objects at one or more log points is received by a data access framework. Thereafter, data accesses requiring logging are identified and one or more corresponding pre-specified attributes are then logged. Related apparatus, systems, techniques and articles are also described.

Data access logging

Techniques for mapping of messages includes receiving, from a first web service, a message comprising one or more operations in a first format; identifying a mapping interface that is based on the first web service, the mapping interface comprising one or more mappings for each of the operations of the message; identifying a second web service that is associated with the identified mapping interface; mapping the message to the second web service such that the one or more operations are in a second format associated with the second web service; and assigning a logical port connection to the second web service.

Mapping messages between web services

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for facilitating communication between enterprise software applications. Some enterprise software systems communicate using a message protocol designed for use with an exchange system. Those systems require the exchange system to communicate using that message protocol. To communicate with systems using that message protocol, a local system can build a message formatted in accordance with the message protocol, even without an exchange system. The local system stores configuration data and uses the configuration data to build the message.

Facilitating communication between enterprise software applications

A system and method for filtering messages in a messaging system is described. The system includes a user interface configured to receive user input for defining one or more message filters. Each message filter specifies predefined criteria by which a message is to be stopped. The system further includes a filter module comprising the one or more filters, and a queue connected with the filter module for queuing messages stopped according to one of the one or more filters. In a method, messages in the messaging system are stopped according to predefined criteria. Stopped messages are restarted according to a job executed by the messaging system.

Time and event controlled message processing

Systems and techniques are disclosed for transmitting a message through an application integration system without having to convert the message from a format that native to both a sending application and a receiving application. A computer-implemented method for transmitting a message from a sending application through an application integration system can include determining a receiving application of the message, and determining a file format used by the receiving application. If the file format used by the receiving application is substantially identical to a file format used by the sending application, the method can include wrapping the message in a markup language file envelope according to a markup language used by the application integration system. The message can then be routed in the markup language file envelope to the receiving application.

Native format tunneling

Methods and apparatus, including computer program products, are provided for messaging. In one aspect, there is provided a computer-implemented method. The method may include initiating a call from a first application to a second application. The method may determine whether the first application is local to the second application. A call may be made as a local call from the first application to the second application, when it is determined that the first and second applications are on the same computer. A call may be made as a remote call from the first application to the second application, when it is determined that the first and second applications are on separate computers. Related apparatus, systems, methods, and articles are also described.

Shortcut in reliable communication

Systems and techniques are disclosed for transmitting a message through an application integration system without having to converting the message from a format that native to both a sending application and a receiving application. A computer-implemented method for transmitting a message from a sending application through an application integration system includes determining a receiving application of the message, and determining a file format used by the receiving application. If the file format used by the receiving application is substantially identical to a file format used by the sending application, the method includes wrapping the message in a markup language file envelope according to a markup language used by the application integration system. The message is then routed in the markup language file envelope to the receiving application.

A system and method are disclosed for pseudo-synchronous communication in an asynchronous messaging network. The system includes a forward pipeline for transmitting asynchronous request messages from a sender system to the receiver system, and a backward pipeline for transmitting asynchronous acknowledgement messages from the receiver system to the sender system. Each acknowledgement message includes a reference to a request message and a result of an event associated with the request message.

Pseudo-synchronous messaging

A messaging system may include a sender backend system, a receiver backend system, and one or more intermediate hubs. The backend systems and message hubs may have messaging software with different protocol versions. The messaging system is downward compatible such that messages routed from the sender backend system through intermediate message hubs are received by the receiver backend system with a protocol version compatible with that of the receiver backend system.

Hub-based messaging system

A persistence layer for a message exchange system of an application integration system is disclosed. The message exchange system includes a message transport layer configured to transport messages from at least one sending application to one or more receiving applications, and a business process layer configured to execute business process logic on select ones of the messages processed by the message transport layer. The persistence layer is accessible by both the message transport layer and the business process layer, and is configured to store a reference associated with each messages processed by the message transport layer. A system further includes a database accessible from the persistence layer for storing a copy of each messages corresponding to the message references stored in the persistence layer.

Common persistence layer

Methods and systems for reliably exchanging a message among collaborating applications are disclosed. The methods and systems utilize a central exchange infrastructure (XI) for executing collaborative business processes among heterogeneous applications. Reliable message transmission is guaranteed by an Exactly Once Protocol (EOP), in which a database associated with the messaging and transport layer (MTL) of an HTTP-compliant server is used for storing a message identifier and comparing the message identifier to previously received message identifiers. If there is no match, the XI facilitates an exchange of message content of application data from a sending application to a receiving application.

Exactly once protocol for message-based collaboration

Growing community of inventors

Walldorf, Germany

Stefan Rossmanith