Abstract: Messages may be provided to a source queue in serialized order, each message associated with a serialization context. The messages may be buffered in the source queue until a transmission time is reached, in turn, for each buffered message. Transmission-ready messages may be sent from the source queue according to the serialized order, using the serialization context, while continuing to store existing messages that are not yet transmission-ready. A queue assignment of the serialization context may be changed to a target queue. Subsequent messages may be provided with the serialization context to the target queue for buffering therein, while remaining transmission-ready messages may be continued to be sent from the source queue. The existing messages from the source queue associated with the serialization context may be determined to have been sent, and the subsequent messages may be sent from the target queue in serialized order, using the serialization context.

Abstract: Conditional deferred queuing may be provided. Upon receiving a message, one or more throttle conditions associated with the message may be identified. A lock associated with the throttle condition may be created on the message until the throttle condition is satisfied. Then, the lock on the message may be removed and the message may be delivered.

Abstract: A server node can monitor the status of servers in a server cluster. The node may receive an alert indicating that a server in the server cluster is unavailable. In response to the alert, the node can send instructions that cause pending remote procedure call requests to be canceled and then reissued to another server in the server cluster instead of to the first server.

Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for embedded application communication. In one aspect, a method includes providing a first Application Programming Interface (API) in the host application, where the first API is configured to interact with a virtual machine object model of the virtual machine to allow the host application to set and get properties of one or more first class instances residing in a virtual machine memory space, and to invoke methods on the first class instances, and providing a second API in the virtual machine configured to interact with a host application object model in the host application.

Abstract: Systems and methods for automating or at least partially automating the creation of connectors for a provisioning system are described. A provisioning system can include a connector creation module that analyzes an application programming interface (API) of a target system. Based on this analysis, the provisioning system can automatically create a connector module that can communicate with the target system. The connector creator may also provide a user interface that enables users to customize the functionality of the connector module. For example, a user can specify which routines of the target system API will be called by the connector module, which user identity parameters of the target system will be updated, and so forth. The connector creation module can automatically generate code for the connector module that implements the user-specified functionality. The finished connector module can be executed to provision the target system.

Abstract: A method of serialization in a data processing system includes serializing a mutable object utilizing a full serialization process, caching primitive data and metadata regarding the mutable object in binary format in cache and then checking whether primitive fields of the mutable object are modified. Thereafter, the mutable object is again serialized utilizing an abbreviated serialization process by reference to the cached primitive data and metadata if the primitive fields of the object are not modified. In the event that primitive fields of the object are modified, the full serialization process is utilized. Thereafter, the serialized mutable object is communicated to a distributed code element.

Abstract: A mobile computing device with a mobile operating system and desktop operating system running concurrently and independently on a shared kernel without virtualization. The mobile operating system provides a user experience for the mobile computing device that suits the mobile environment. The desktop operating system provides a full desktop user experience when the mobile computing device is docked to a secondary terminal environment. Applications of the desktop operating system communicate with applications and services of the mobile operating system through a cross-environment communication framework. The cross-environment communication framework may include interfaces to remotable objects allowing processes in the mobile operating system and processes in the desktop operating system to share memory in a thread-safe manner. The mobile computing device may be a smartphone running the Android mobile operating system and a full desktop Linux distribution on a modified Android kernel.

Abstract: A computer-implemented method for process integration may comprise providing a business logic layer that hosts business object(s), providing process broker(s), providing adapter(s) and providing a process broker handler. Each process broker may perform process integration tasks by dynamically determining whether, when and/or how routines of the business logic layer need to be integrated with routines of a second application. Each adapter may be part of a first application and implement methods to perform communication protocol specific logic. Each adapter may also be interoperable with at least one of the process brokers and one of the business objects to transform a message exchanged between the process broker and the second application from an internal format to an external format or vice versa. The process broker handler may be operable to instantiate the process broker and to instantiate an adapter stored in association with the instantiated process broker.

Abstract: A method for performing a remote procedure call between an application processor and a digital signal processor within a computing device. The computing device may compile interface description language data to generate stub software that executes on the application processor and skel software that executes on the digital signal processor. When an application executing on the application processor invokes a remote procedure call, the application processor may pack argument data within stack memory and transmit an interrupt to the digital signal processor, which may map the physical memory addresses of the argument data into local address space such that no copies of the argument data is made. The digital signal processor may execute skel software that unpacks the argument data and executes a service related to the remote procedure call.

Abstract: Through an asynchronous callback enhancement, a thread makes a non-blocking request (e.g., send, receive, I/O) to a message passing interface library, and a callback routine is associated with the request as an asynchronous callback to the thread. The callback is queued for execution in the requesting thread and so has a deterministic execution context. Callback queuing may occur in response to another thread detecting that the request is complete. Further control over callback execution is provided by state transitions which determine whether the thread is open to processing (e.g., executing) an asynchronous callback. Callback association is done by a broad or by narrow association routines. An application which has processes organized in ranks, each including a communication thread with associated callback(s), and multiple worker threads. Interruptible wait enhancements may also be present.

Abstract: A method, apparatus, and computer program product for virtualizing baseboard management controller (‘BMC’) operation in a host computer comprising a base BMC is provided. Example embodiments include executing, by the host computer, a virtual BMC; registering, by the virtual BMC, with the base BMC of the host computer; and processing BMC requests sent to the base BMC by the virtual BMC. In some example embodiments, prior to registration of the virtual BMC, BMC requests are processed by the base BMC. Some other example embodiments include determining, by the base BMC, periodically at a predefined period of time, whether the virtual BMC is active; and upon the base BMC determining that the virtual BMC is not active: deregistering, by the base BMC, the virtual BMC; and processing subsequently received BMC requests by the base BMC.

Abstract: A framework can provide function execution services. The framework can comprise a controller layer, a wrapper layer, and a function layer. The controller layer can be configured to process function definition requests and function execution requests, and return results. The wrapper layer can be configured to query the function layer to determine function definitions and pass function execution requests and results with the function layer. The function layer can comprise functions and/or features. A function execution request can be performed by determining a step execution sequence, executing the step execution sequence, and returning results of the execution of the step execution sequence. The step execution sequence can comprise setup steps, execute steps, and/or finalize steps.

Abstract: A computing platform may include heterogeneous processors (e.g., CPU and a GPU) to support sharing of virtual functions between such processors. In one embodiment, a CPU side vtable pointer used to access a shared object from the CPU 110 may be used to determine a GPU vtable if a GPU-side table exists. In other embodiment, a shared non-coherent region, which may not maintain data consistency, may be created within the shared virtual memory. The CPU and the GPU side data stored within the shared non-coherent region may have a same address as seen from the CPU and the GPU side. However, the contents of the CPU-side data may be different from that of GPU-side data as shared virtual memory may not maintain coherency during the run-time. In one embodiment, the vptr may be modified to point to the CPU vtable and GPU vtable stored in the shared virtual memory.

Abstract: Administering incident pools including assigning an incident received from one or more components of the distributed processing system to a pool of incidents; assigning to each incident a particular combined minimum time for inclusion of the incident in the pool; in response to the pool closing, determining for each incident in the pool whether the incident has met its combined minimum time for inclusion in the pool; if the incident has been in the pool for its combined minimum time, including the incident in the closed pool; if the incident has not been in the pool for its combined minimum time, moving the incident from the closed pool to a next pool; applying incident suppression rules using the incidents assigned to the next pool; and applying incident creation rules to the incidents that were assigned to the next pool, while omitting any duplicate incidents caused by the assignment.

Abstract: Methods, systems, and computer-readable media are disclosed for monitoring a distributed application. A particular method identifies a plurality of components of a distributed application. The method also identifies a specific technology associated with a particular component and attaches a technology specific interceptor to the particular component based on the identified specific technology. The method includes intercepting messages that are sent by or received by the particular component using the technology specific interceptor. At least one potential work item is generated based on the intercepted messages. The method includes determining whether to schedule the at least one potential work item for execution based on a predicted impact of the at least one work potential item on performance of the distributed application.

Abstract: Administering incident pools including assigning an incident received from one or more components of the distributed processing system to a pool of incidents; assigning to each incident a particular combined minimum time for inclusion of the incident in the pool; in response to the pool closing, determining for each incident in the pool whether the incident has met its combined minimum time for inclusion in the pool; if the incident has been in the pool for its combined minimum time, including the incident in the closed pool; if the incident has not been in the pool for its combined minimum time, moving the incident from the closed pool to a next pool; applying incident suppression rules using the incidents assigned to the next pool; and applying incident creation rules to the incidents that were assigned to the next pool, while omitting any duplicate incidents caused by the assignment.

Abstract: Embodiments of the present invention may provide a local process integration component to facilitate process integration. The local process integration component may include an adapter, a process broker and a process broker handler. The process broker may collaborate with the business logic and adapter to perform business-centric integration logic. The architecture is based on is a toolkit and generator approach. For inbound communication, the adapter is responsible for control flow while the process broker handler provides generic services. For outbound communication, the process broker is responsible for control flow while the process broker handler provides generic services. The control flow orchestration is uniformed by code generation.

Abstract: A message processing apparatus which communicates with a plurality of software components, and transfers a message received from a software component to another software component holds a message received from a software component, manages the received message, the number of transmissions, and the holding period in correspondence with each other, and transmits the held received message to another software component in response to a delivery request from the other software component. When no new delivery request is received for the managed holding period after transmitting the received message by the managed number of transmissions, the message processing apparatus deletes the received message from the management targets.

Abstract: Management of transaction message flow utilizing a transaction message queue. The system and method are for use in financial transaction messaging systems. The system is designed to enable an administrator to monitor, distribute, control and receive alerts on the use and status of limited network and exchange resources. Users are grouped in a hierarchical manner, preferably including user level and group level, as well as possible additional levels such as account, tradable object, membership, and gateway levels. The message thresholds may be specified for each level to ensure that transmission of a given transaction does not exceed the number of messages permitted for the user, group, account, etc.

Abstract: Described are techniques for communicating between one or more producers and one or more consumers. A first consumer of an event queue registers for notification regarding occurrences of one or more events. A producer of the event queue posts one or more notifications to one or more consumers of the event queue regarding one or more occurrences of one or more events. Each of the consumers receive notification regarding occurrences of events for which said each consumer is registered. The first consumer retrieves posted event notifications regarding events for which said first consumer is registered. If the first consumer is executing in user space and an event notification list to which said event notifications for said first consumer are posted is located in shared memory, said first consumer retrieves said posted event notifications without proxying into kernel space.