Abstract: A method of exchanging application messages generated by an applications with a format specified by a predetermined protocol and then encapsulating the message with a railroad edge messaging protocol (EMP) header and a railroad Class D messaging transport header to form a packet for transmission across a railroad communications system.

Abstract: A method of exchanging application messages generated by an applications with a format specified by a predetermined protocol and then encapsulating the message with a railroad edge messaging protocol (EMP) header and a railroad Class D messaging transport header to form a packet for transmission across a railroad communications system.

Abstract: A method of exchanging centralized train control (CTC) messages in a railroad communication system includes generating a message having a format defined by a protocol with an application running on a sending one of a railroad wayside system and a railroad dispatch system. A railroad edge messaging protocol (EMP) header and a railroad Class D messaging transport header are appended to the message to generate a packet. The packet is transmitted to a receiving one of the railroad dispatch system and the railroad wayside system across the railroad communications system.

Abstract: A social analytic system may identify the social signals associated with a brand, campaign, or any other topic. The social analytic system may generate a vocabulary associated with the brand, campaign, or topic based terms used in the associated social signals. The vocabulary may be used for generating social media analytics and identifying social media events, such as marketing campaigns. In one example, a vocabulary may be compared with vocabularies associated with different constituents to identify the positive and negative terms in the vocabulary.

Abstract: A social analytic system may identify the social signals associated with a brand, campaign, or any other topic. The social analytic system may generate a vocabulary associated with the brand, campaign, or topic based terms used in the associated social signals. The vocabulary may be used for generating social media analytics and identifying social media events, such as marketing campaigns. In one example, a vocabulary may be compared with vocabularies associated with different constituents to identify the positive and negative terms in the vocabulary.

Abstract: A social analytic system may identify the social signals associated with a brand, campaign, or any other topic. The social analytic system may generate a vocabulary associated with the brand, campaign, or topic based terms used in the associated social signals. The vocabulary may be used for generating social media analytics and identifying social media events, such as marketing campaigns. In one example, a vocabulary may be compared with vocabularies associated with different constituents to identify the positive and negative terms in the vocabulary.

Abstract: A social analytic system may identify the social signals associated with a brand, campaign, or any other topic. The social analytic system may generate a vocabulary associated with the brand, campaign, or topic based terms used in the associated social signals. The vocabulary may be used for generating social media analytics and identifying social media events, such as marketing campaigns. In one example, a vocabulary may be compared with vocabularies associated with different constituents to identify the positive and negative terms in the vocabulary.

Abstract: Highly-available processing of an asynchronous request can be accomplished in a single transaction. A distributed request queue receives a service request from a client application or application view client. A service processor is deployed on each node of a cluster containing the distributed request queue. A service processor pulls the service request from the request queue and invokes the service for the request, such as to an enterprise information system. If that service processor fails, another service processor in the cluster can service the request. The service processor receives a service response from the invoked service and forwards the service response to a distributed response queue. The distributed response queue holds the service response until the response is retrieved for the client application.

Abstract: High availability is obtained for the deployment and undeployment of application views by placing a redundant JMX server on each server in a cluster of servers for an application integration system. Each redundant JMX server can manage deployment work for the cluster, and is capable of sending a JMX notification to every other server in the cluster relating to the deployment work, such as a deploy, undeploy, or processing notification. While an administration server can manage the other servers in the cluster, the redundant JMX servers are capable of managing deployment work for the cluster in the event of a failure of the administration server. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Abstract: High availability event forwarding can be obtained utilizing distributed queues in a server cluster. Each server can receive an event from a data system, such as a database or SAP™ system. Event queues exist on servers in the cluster can store an event until, for example, the event is delivered to a user or retrieved for processing. An event processor examines the load of each event queue and selects the event queue with the lightest load. The event processor generates an alias for the selected queue, such that a user, integration system, or client application does not need to know the identity of the physical queue storing the event, but only needs to refer to the ‘distributed queue’ or alias. After a physical queue is selected and an alias assigned, the event is forwarded to the selected queue.

Abstract: High availability event forwarding can be obtained utilizing distributed queues in a server cluster. Each server can receive an event from a data system, such as a database or SAP™ system. Event queues exist on servers in the cluster can store an event until, for example, the event is delivered to a user or retrieved for processing. An event processor examines the load of each event queue and selects the event queue with the lightest load. The event processor generates an alias for the selected queue, such that a user, integration system, or client application does not need to know the identity of the physical queue storing the event, but only needs to refer to the ‘distributed queue’ or alias. After a physical queue is selected and an alias assigned, the event is forwarded to the selected queue.

Abstract: Highly-available processing of an asynchronous request can be accomplished in a single transaction. A distributed request queue receives a service request from a client application or application view client. A service processor is deployed on each node of a cluster containing the distributed request queue. A service processor pulls the service request from the request queue and invokes the service for the request, such as to an enterprise information system. If that service processor fails, another service processor in the cluster can service the request. The service processor receives a service response from the invoked service and forwards the service response to a distributed response queue. The distributed response queue holds the service response until the response is retrieved for the client application.

Abstract: High availability event forwarding can be obtained utilizing distributed queues in a server cluster. Each server can receive an event from a data system, such as a database or SAP™ system. Event queues exist oil servers in the cluster can store an event until, for example, the event is delivered to a user or retrieved for processing. An event processor examines the load of each event queue and selects tie event queue with the lightest load The event processor generates an alias for the selected queue, such that a user, integration system, or client application does not need to know the identity of the physical queue storing the event, but only needs to refer to the ‘distributed queue’ or alias. After a physical queue is selected and an alias assigned, the event is forwarded to the selected queue. This description is not intended to be a complete description of, or limit the scope of, the invention.

Abstract: High availability event forwarding can be obtained utilizing distributed queues in a server cluster. Each server can receive an event from a data system, such as a database or SAP™ system. Event queues exist on servers in the cluster can store an event until, for example, the event is delivered to a user or retrieved for processing. An event processor examines the load of each event queue and selects the event queue with the lightest load. The event processor generates an alias for the selected queue, such that a user, integration system, or client application does not need to know the identity of the physical queue storing the event, but only needs to refer to the ‘distributed queue’ or alias. After a physical queue is selected and an alias assigned, the event is forwarded to the selected queue. This description is not intended to be a complete description of, or limit the scope of, the invention.

Abstract: Events are delivered to multiple topic subscribers using a single distributed event topic. An event generator can receive data for the event from an EIS and can generate an event object. An event queue stores the event object until the event is retrieved by an event processor, which publishes the event to each destination. One of these destinations, the distributed event topic, receives the published event from the event processor and handles the delivery of the event to any user subscribing to the event topic. Each subscriber can utilize a remote application view to invoke system functions in the EIS and receive messages from the information system on behalf of the subscriber. A user event queue can be used for each topic subscriber to store an event until the subscriber is capable of receiving the event.

Abstract: Highly-available processing of an asynchronous request can be accomplished in a single transaction. A distributed request queue receives a service request from a client application or application view client. A service processor is deployed on each node of a cluster containing the distributed request queue. A service processor pulls the service request from the request queue and invokes the service for the request, such as to an enterprise information system. If that service processor fails, another service processor in the cluster can service the request. The service processor receives a service response from the invoked service and forwards the service response to a distributed response queue. The distributed response queue holds the service response until the response is retrieved for the client application.

Abstract: High availability is obtained for the deployment and undeployment of application views by placing a redundant JMX server on each server in a cluster of servers for an application integration system. Each redundant JMX server can manage deployment work for the cluster, and is capable of sending a JMX notification to every other server in the cluster relating to the deployment work, such as a deploy, undeploy, or processing notification. While an administration server can manage the other servers in the cluster, the redundant JMX servers are capable of managing deployment work for the cluster in the event of a failure of the administration server.

Abstract: High availability event forwarding can be obtained utilizing distributed queues in a server cluster. Each server can receive an event from a data system, such as a database or SAP system. Event queues exist on servers in the cluster can store an event until, for example, the event is delivered to a user or retrieved for processing. An event processor examines the load of each event queue and selects the event queue with the lightest load. The event processor generates an alias for the selected queue, such that a user, integration system, or client application does not need to know the identity of the physical queue storing the event, but only needs to refer to the ‘distributed queue’ or alias. After a physical queue is selected and an alias assigned, the event is forwarded to the selected queue.