Abstract: A computer system including instructions recorded on a non-transitory computer-readable storage medium and readable by at least one processor, the system including a logging module, a receiving module, and a transmission module. The logging module is configured to log information associated with a scheduler. The receiving module is configured to receive a request for information associated with the scheduler. The transmission module is configured to transmit information associated with the scheduler.

Abstract: 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.

Abstract: A system and method for conducting a game between at least one live player and at least one computer-controlled player includes executing a training program between at least two agents to generate probability weights correlating actions or meta-actions representing a set or sequenced set of actions with a probability that the action or meta-action will produce a game outcome meeting a specified criterion or specified criteria. A game is conducted in which at least one live player plays against at least one computer-controlled player in which the computer-controlled player selects actions at one or more of the decision nodes in the game based, at least in part, on the probability weights.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: The present invention relates to a combustion engine, comprising an intake system having a throttle valve controlling an air flow to the combustion engine, a brake booster being in fluid communication with the intake system, downstream the throttle valve, via an evacuation duct for evacuation of air from the brake booster to the intake system, a crankcase being in fluid communication with the intake system, downstream the throttle valve, via a low load duct for conducting crankcase gases to the intake system, a venturi tube forming part of the low load duct, wherein the venturi tube comprises a narrow venturi tube portion forming a flow resistance within the low load duct through which the crankcase gases have to pass, wherein the evacuation duct is also fluidly connected to the venturi tube portion, via a connection duct, for further evacuation of air from the brake booster to the intake system.

Abstract: The present invention relates to a combustion engine, comprising an intake system having a throttle valve controlling an air flow to the combustion engine, a brake booster being in fluid communication with the intake system, downstream the throttle valve, via an evacuation duct for evacuation of air from the brake booster to the intake system, a crankcase being in fluid communication with the intake system, downstream the throttle valve, via a low load duct for conducting crankcase gases to the intake system, a venturi tube forming part of the low load duct, wherein the venturi tube comprises a narrow venturi tube portion forming a flow resistance within the low load duct through which the crankcase gases have to pass, wherein the evacuation duct is also fluidly connected to the venturi tube portion, via a connection duct, for further evacuation of air from the brake booster to the intake system.

Abstract: A method for processing a received message is provided. Such a method may associate the message with a default language that corresponds to a default codepage. Thereafter, portions of the message are identified as having language keys corresponding to unique language key codepages associated therewith. The language of each of the identified portions of the message is converted using the corresponding language key codepage and the language of portions of the message that do not have an associated language key with is converted with a default codepage. Also disclosed is a method for generating a message that associates the message with a default language and assigns each portion of the message that is not in the default language with a language key that corresponds to the language.

Abstract: 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.

Abstract: 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.

Abstract: 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.