Abstract: A system for processing electronic documents includes an existing business system (or systems) connected to a separate control system. The resulting composite system provides a framework that enables a flexible and customizable process definition for handling incoming documents. Within the process definition all the processing steps which are desired for handling an incoming electronic document can be predefined. Processing steps like checking the signature and authorizing an incoming legal document can be implemented in the control system and steps like posting a goods receipt or an invoice are implemented in one of the connected business systems. The content of the incoming document is evaluated to determine which business process may be used to carry out the necessary processing steps for the incoming electronic document. The assigned business process and a related process flow sequence define the processing steps to be implemented.

Abstract: A computer-implemented method includes: receiving metadata about a business network, the metadata gathered by computer-based entities performing automated discovery of the business network; generating a business network model based on the metadata, the business network model comprising objects and associations between them, the objects representing aspects of the business network found by the automated discovery, including at least: participants, systems, relationships, applications, interfaces, middleware, process steps, and documents; and modifying the business network model based on at least one input.

Abstract: To improve access to message content in a message exchange system, a context object is defined for the message as an abstraction of the message content. The context object can be assigned to many different message communication interfaces, thereby allowing context objects to be reused across various interfaces. The context object provides access both to a message payload, and parts of a message other than the payload, such as technical data. Accordingly, access to message content for various tasks and applicability to a number of different message interfaces is improved.

Abstract: Systems and methods for routing messages between applications in a network are disclosed. Messages are routed from a sending application to one or more receiving applications according to one or more routing rules. Each routing rule is used for determining the one or more receiving applications, and is associated with at least one routing object. The routing object is configured to associate the routing rule to the message based on content of the message. The routing objects are stored in a repository of design-time descriptions of the applications. The routing rules are stored in a directory of runtime descriptions of applications in the runtime landscape, and are accessed by a runtime engine for executing the routing.

Abstract: To improve access to message content in a message exchange system, a context object is defined for the message as an abstraction of the message content. The context object can be assigned to many different message communication interfaces, thereby allowing context objects to be reused across various interfaces. The context object provides access both to a message payload, and parts of a message other than the payload, such as technical data. Accordingly, access to message content for various tasks and applicability to a number of different message interfaces is improved.

Abstract: Systems and methods for routing messages between applications in a network are disclosed. Messages are routed from a sending application to one or more receiving applications according to one or more routing rules. Each routing rule is used for determining the one or more receiving applications, and is associated with at least one routing object. The routing object is configured to associate the routing rule to the message based on content of the message. The routing objects are stored in a repository of design-time descriptions of the applications. The routing rules are stored in a directory of runtime descriptions of applications in the runtime landscape, and are accessed by a runtime engine for executing the routing.