Abstract: Certain example embodiments relate to techniques for managing the interprocess communication between at least one database client process and at least one database server process in a database system. The at least one database client process sends at least one request to the at least one database server process, with the at least one request comprising one or more buffers. The one or more buffers are transferred, in a single step, from the at least one database client process to a buffer area. The one or more buffers are transferred, in a single step, from the buffer area to the at least one database client process. The buffer area is directly accessible by the at least one database server process.

Abstract: Certain example embodiments relate to importing assets into a service-oriented architecture (SOA) registry. An SOA system includes a repository for storing a plurality of files relating to real assets, and a registry containing metadata and/or other information about these real assets, including at least one registry asset per real asset. Each registry asset has a registry asset type. A generic import module is configured to (a) receive as input one or more import specifications, with each import specification defining how information from an external specification file of an asset type is to be extracted to create one or more registry assets of one or more corresponding target registry asset types, (b) generate one or more registry assets of one or more target registry asset types based on a corresponding import specification, and (c) register the generated one or more registry assets of the one or more target registry asset types.

Abstract: A method for authenticating an entity at a first data resource, the method comprising the steps of: sending a first request token from the entity (100) to a token distribution unit (20) to request a first one-way authentication token, the first request token being a function of authentication information provided by the entity (100); sending the first one-way authentication token from the token distribution unit (20) to the entity (100); sending the first one-way authentication token from the entity (100) to the first data resource (200) to authenticate the entity (100) at the first data resource (200); sending the first one-way authentication token from the first data resource (200) to the token distribution unit (20) to validate the first one-way token; and invalidating the first one-way token.

Abstract: Systems, methods, and computer program products are provided for instant recovery of a virtual machine (VM) from a compressed image level backup without fully extracting the image level backup file's contents to production storage. The method receives restore parameters, initializes a virtual storage, and attaches the virtual storage to a hypervisor configured to launch a recovered VM. The method stores virtual disk data changes inflicted by a running operating system (OS), applications, and users in a changes storage. The method provides the ability to migrate the actual VM disk state (taking into account changed disk data blocks accumulated in changes storage) so as to prevent data loss resulting from the VM running during the recovery and accessing virtual storage, to production storage without downtime. In embodiments, the method displays received restore parameters in an interactive interface and delivers the recovery results via an automated message.

Abstract: The example embodiments disclosed herein relate to networks and, more particularly, to systems and/or methods that enable processes to be routed and/or executed in a distributed, location transparent manner. A process engine for use across instances of a service-oriented integration server is provided to a network having a messaging layer. The process engine executes a process in accordance with a process model defined at design time. Each instance of the process engine comprises runtime artifacts such as deployable units of executable logic; a publishing service for publishing a process transition document (PTD) that includes routing data as a part of the message itself; a subscription service for subscribing to the PTDs to be routed to the corresponding instance of the process engine; and a filtering service for filtering other PTDs published to the messaging layer.

Abstract: Memory allocation in a Broker system for managing the communication between a plurality of clients and a plurality of servers. The method may include allocating memory for a plurality of memory pools; and dividing each memory pool into memory blocks of a size which is specific to the type of a resource. The resource may be related to the communication managed by the Broker.

Abstract: The example embodiments disclosed herein relate to application integration techniques built around the publish-and-subscribe model (or one of its variants). In certain example embodiments, a first standards-based messaging protocol (e.g., the JMS messaging protocol) may be used to create a trigger so that a message envelope according to a second standards-based messaging protocol (e.g., SOAP) may be communicated over the first standards-based messaging transport layer. In other words, in certain example embodiments, a trigger according to a first protocol (e.g., JMS) may have a message according to a second protocol (e.g., SOAP) associated therewith so as to enable the message to be communicated over the first protocol's transport layer. The trigger may be configured to receive a message from a web service consumer via the JMS messaging protocol and pass it to the web service stack for dispatch to the web service provider.

Abstract: A system for testing at least one software product comprising a requirement loader and a test specification loader. The requirement loader is adapted for loading a plurality of requirements on the software product into a database. The test specification loader is adapted for loading a plurality of test specifications for the software product into the database, each test specification being related to one or more of the requirements. The test specification loader is further adapted for generating during loading of a test specification a virtual test specification in the database for each of the one or more related requirements, the virtual test specification comprising all test specifications for the respective requirement on the software product stored in the database.

Abstract: Method of authenticating a user in a heterogeneous computer environment. The method may include defining a set of unique prefixes, each prefix identifying a type of user repository; defining a set of abstract repository names, each abstract repository name identifying an address of a user repository; and authenticating the user in the heterogeneous computer environment by assigning a sequence comprising a unique prefix, a reference to an abstract repository name and a unique identifier for the user within the user repository indicated by the reference to the abstract repository name.

Abstract: The present invention relates to a communications system having at least one communications means by means of which the communications system can be connected to at least one further processing unit and/or to a further communications system, having at least one first memory means, having at least one second memory means and having at least one security apparatus, wherein identical information is stored on the first and second memory means and wherein damage to the communications system can be determined with reference to a comparison of this information by means of the security apparatus. The present invention furthermore relates to a security apparatus and to a method of determining damage to a communications system.

Abstract: Collaboration by a plurality of users in an application. The application may include processing logic and a user interface. The user interface may include at least one control element adapted to receive collaborative input, where the at least one control element may be linked to a collaboration utility. The collaboration utility may be adapted to generate the collaborative input for the control element based on the individual inputs of at least some of the plurality of users.

Abstract: The present invention concerns a method for the rule-based monitoring of a component (C1) added to a service-oriented architecture (SOA), the SOA comprising a plurality of components (C2, . . . , Cn) being monitored by a plurality of monitoring components (M2, . . . , Mn), the method comprising the following steps: a. selecting a component (C2) from the plurality of components (C2, . . . , Cn) of the SOA which is similar to the added component (C1) based on a similarity-metric; b. selecting at least one rule (R2) from the monitoring component (M2) of the selected component (C2), wherein the at least one rule (R2) has already been validated during the operation of the SOA; and c. adding the at least one rule (R2) to a new monitoring component (M1) of the added component (C1).

Abstract: Certain example embodiments relate to a system for secure complex event processing (CEP). The system includes an input adaptor configured to receive at least one input event from at least one external source system. The at least one input event comprises at least one event-specific disclosure permission concerning data of the input event. A CEP engine is configured to process the at least one input event and to produce at least one corresponding complex output event. A security enforcer is configured to remove data from the at least one output event that is not in accordance with the at least one event-specific disclosure permission defined in the corresponding at least one input event. An output adaptor is configured to send the at least one output event to at least one external target system.

Abstract: Certain example embodiments described herein relate to interactive model merging systems and/or methods and, more particularly, to using basic information obtained during merging to help a user resolve high-level merge conflicts. In certain example embodiments, instead of leaving it to the user to resolve the merge conflicts on the level of the atomic elements (e.g., objects and connections with a non-empty merge state), the recognition of high-level merge conflicts may help capture the semantics of the differences between the models being merged on a larger scale (e.g., covering a possibly very large number of model elements in one conflict) and/or also may generally help allow the user to resolve them easily and quickly within a reduced number of operation. The high-level merge conflicts may be resolvable at their high levels or decomposed and resolved at a lower level depending, in part, on the type of conflict involved.

Abstract: Managing the lifecycle of a service oriented architecture (SOA). The method may include selecting a subset of a plurality of objects of the SOA for lifecycle management in accordance with the requirements of an organization implementing the SOA, and assigning a lifecycle property to each member of the subset of the plurality of objects of the SOA.

Abstract: The system may provide for the collection of data in a heterogeneous network, long term secure storage of the data, and secure transfer of the data to an environment that may be secure and controlled for the purpose of controlled and secure selected viewing of all or parts of the data. The data stored may include core data of interest as well as any data that is associated with the core data. The core data and associated data may be stored. To do so, the system may identify and collect associated data at the point of release of all or part of the data. Further, the system may provide secure and controlled transfer of the data to a permanent and secure media. Lastly, the system may provide secure transfer of all or parts of the data from the media to a controlled and secure environment suitably constructed to provide for secure viewing of all or parts of the data under the control of the owner of the data.

Abstract: Monitoring a software system based on a service oriented architecture (SOA). The method may involve system components communicating with each other via sending messages. The method may include receiving a monitoring message by a monitoring component where the monitoring message may be sent from a system component of the software system. The method may further include providing an ontology including at least one interpretation rule for the message by the monitoring component. The method may also include reacting of the monitoring component in accordance with the at least one interpretation rule.

Abstract: The present invention concerns a computer-implemented method for debugging a job running on a legacy system, wherein the method comprises the following steps: a. identifying (01) the job to be debugged, wherein the identifying (01) comprises programmatically reading (101) a screen provided by the legacy system that displays a list of active jobs of the legacy system by means of screen scraping; b. programmatically retrieving (04) the source code that corresponds to the job identified in step a. by means of screen scraping; and c. programmatically creating (05) at least one breakpoint in the source code retrieved in step b.

Abstract: The example embodiments disclosed herein relate to application integration techniques built around the publish-and-subscribe model (or one of its variants). In certain example embodiments, application integration techniques for managing and/or monitoring a business process comprising a plurality of activities, events, and/or objects located in at least one resource external to the application integration system and a process engine thereof are provided. During design time, by introspecting the business object types involved in the activities, events, and/or objects of the at least one resource, potential state changes may be identified, and an integrative linkage may be established, with the integrative linkage being managed and maintained by a process monitoring agent (PMA). During runtime, the PMA may “listen” to the business object state changes in the at least one external resource and notify the local process engine accordingly.

Abstract: Certain example embodiments described herein relate to techniques for matching business requirements with available services in service-oriented business process systems. An n-to-m relationship between process steps and services may be established. In certain example embodiments, both future design and dynamic runtime changes become possible by elaborating on possible resolution techniques before process execution and by identifying/resolving configurational dependencies. The addition of a service-oriented process configuration layer is made possible in certain example embodiments by enhancing the way that business processes are modeled visually or notationally, and through the implementation of a metamodel. The model linking process steps and services may be extended so as to support logical operators, rules or constraints for matching process steps and services, dependencies and relationships, etc.