Abstract: The disclosure generally describes methods, software, and systems, including a method for publishing messages through a messaging client of a database server. A message to be published to one or more message brokers is received at a server and from a database client. The message is in the form of a SQL statement. The received message is processed at the server. Message broker configurations associated with the received message are determined. The message is published to the one or more message brokers by invoking a messaging client at the server and using at least the message broker configurations.

Abstract: A messaging meta broker gateway for publish-subscribe messaging environments can provide connectivity, message routing, and subscription management between large numbers of clients and large numbers of brokers. The messaging meta broker gateway can provide access to large numbers of brokers to a client through a single connection. To a broker, the messaging meta broker gateway provides extremely wide fan-in and fan-out to gateway clients. To a service provider, the messaging meta broker gateway is a single system providing easy scaling with lightweight replication of instances, and shared, private, or virtual messaging environments supporting multiple customers and applications. The meta broker gateway can also connect gateway clients with other clients of the brokers, and also with archiving facilities. Protocol translation, security, and statistics logging are supported. The messaging meta broker gateway is suitable for cloud-based Internet-of-Things environments.

Abstract: The disclosure generally describes methods, software, and systems, including a method for publishing messages through a messaging client of a database server. A message to be published to one or more message brokers is received at a server and from a database client. The message is in the form of a SQL statement. The received message is processed at the server. Message broker configurations associated with the received message are determined. The message is published to the one or more message brokers by invoking a messaging client at the server and using at least the message broker configurations.

Abstract: Sending and/or receiving messages in a computer system having memory and a processor. The method includes configuring the memory to have one or more streams connecting a generic messaging client to send messages to and/or receive messages from one or more protocol-specific messaging clients. The streams are formed by providing configuration data comprising one or more destination definitions. Each of the destination definitions corresponds to one of the protocol-specific messaging clients. Each of the destination definitions has a specified messaging protocol and one or more stream definitions. Each of the stream definitions has parameters associated with the specified messaging protocol of a corresponding one of the destination definitions. In code for the generic messaging client, at least one stream object is provided specifying one of the destination definitions and one of the stream definitions.

Abstract: The disclosure generally describes methods, software, and systems, including a method for publishing messages through a messaging client of a database server. A message to be published to one or more message brokers is received at a server and from a database client. The message is in the form of a SQL statement. The received message is processed at the server. Message broker configurations associated with the received message are determined. The message is published to the one or more message brokers by invoking a messaging client at the server and using at least the message broker configurations.

Abstract: Methods and apparatus, including computer program products, are provided for handling database table changes. The method may include receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: Sending and/or receiving messages in a computer system having memory and a processor. The method includes configuring the memory to have one or more streams connecting a generic messaging client to send messages to and/or receive messages from one or more protocol-specific messaging clients. The streams are formed by providing configuration data comprising one or more destination definitions. Each of the destination definitions corresponds to one of the protocol-specific messaging clients. Each of the destination definitions has a specified messaging protocol and one or more stream definitions. Each of the stream definitions has parameters associated with the specified messaging protocol of a corresponding one of the destination definitions. In code for the generic messaging client, at least one stream object is provided specifying one of the destination definitions and one of the stream definitions.

Abstract: A client token is generated for a client process in response to a client token request. An authentication request including the client token is received from a client endpoint associated with the client process. The client endpoint is authenticated, including generating and providing an endpoint token to the client endpoint. A first mapping between the client token and transport channels used for messages received from the client process and a second mapping between the client endpoint and the client token are generated. A first message is received over a first transport channel from the client endpoint, the message including the client token and the endpoint token. A response to the first message is sent to the client endpoint over a second transport channel, without re-authenticating the client endpoint, the second transport channel being different than the first transport channel and being selected based on the first and second mappings.

Abstract: A messaging meta broker gateway for publish-subscribe messaging environments can provide connectivity, message routing, and subscription management between large numbers of clients and large numbers of brokers. The messaging meta broker gateway can provide access to large numbers of brokers to a client through a single connection. To a broker, the messaging meta broker gateway provides extremely wide fan-in and fan-out to gateway clients. To a service provider, the messaging meta broker gateway is a single system providing easy scaling with lightweight replication of instances, and shared, private, or virtual messaging environments supporting multiple customers and applications. The meta broker gateway can also connect gateway clients with other clients of the brokers, and also with archiving facilities. Protocol translation, security, and statistics logging are supported. The messaging meta broker gateway is suitable for cloud-based Internet-of-Things environments.

Abstract: Methods and apparatus, including computer program products, are provided for handling database table changes. The method may include receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: The present disclosure describes methods, systems, and computer program products for providing a lightweight deployment of mobile cloud applications. A computer-implemented method comprises: receiving, at a server and from a remote client device, a first request to create a frame for the application; storing, by the server, the frame of the application in a repository; generating, by the server, an identifier associated with the frame and the repository; initiating, by the server, a copying of the repository to a workspace; and receiving, by the repository or the workspace and from the remote client, a pushing command including the identifier to update the frame stored in the repository or the workspace with application data associated with a created, modified or deleted version of the application.

Abstract: A client token is generated for a client process in response to a client token request. An authentication request including the client token is received from a client endpoint associated with the client process. The client endpoint is authenticated, including generating and providing an endpoint token to the client endpoint. A first mapping between the client token and transport channels used for messages received from the client process and a second mapping between the client endpoint and the client token are generated. A first message is received over a first transport channel from the client endpoint, the message including the client token and the endpoint token. A response to the first message is sent to the client endpoint over a second transport channel, without re-authenticating the client endpoint, the second transport channel being different than the first transport channel and being selected based on the first and second mappings.

Abstract: The disclosure generally describes methods, software, and systems, including a method for publishing messages through a messaging client of a database server. A message to be published to one or more message brokers is received at a server and from a database client. The message is in the form of a SQL statement. The received message is processed at the server. Message broker configurations associated with the received message are determined. The message is published to the one or more message brokers by invoking a messaging client at the server and using at least the message broker configurations.

Abstract: The present disclosure describes methods, systems, and computer program products for providing a lightweight deployment of mobile cloud applications. A computer-implemented method comprises: receiving, at a server and from a remote client device, a first request to create a frame for the application; storing, by the server, the frame of the application in a repository; generating, by the server, an identifier associated with the frame and the repository; initiating, by the server, a copying of the repository to a workspace; and receiving, by the repository or the workspace and from the remote client, a pushing command including the identifier to update the frame stored in the repository or the workspace with application data associated with a created, modified or deleted version of the application.

Abstract: According to one general aspect, a method for a computing device may include establishing, via a first application executed by the computing device, a data session with a server. The server may maintain a set of session data associated with the data session. The method may also include processing a request to terminate the active functioning of the first application. The method may further include transmitting a session-inactivation message to the server, wherein the session-inactivation message instructs the server to maintain the set of session data.

Abstract: According to one general aspect, a method for a computing device may include establishing, via a first application executed by the computing device, a data session with a server. The server may maintain a set of session data associated with the data session. The method may also include processing a request to terminate the active functioning of the first application. The method may further include transmitting a session-inactivation message to the server, wherein the session-inactivation message instructs the server to maintain the set of session data.

Abstract: A data communication method that compensates for a disadvantageous characteristics of a first protocol. A client application and a server application employ a second protocol (i.e., a TCP/IP protocol) that is mapped onto the first protocol. A data communication request is received by a SOCKS client in accordance with the second protocol. The request, after being redirected client to a client interceptor by the SOCKS using a SOCKS protocol, is intercepted by the socks CLIENT. The client interceptor maps the request onto the first protocol, after which the client interceptor sends the mapped request to a server interceptor. The server interceptor compensates a disadvantageous characteristic of the first protocol to ascertain that a connection or transmission capacity condition exists and then to eliminate the condition. The server interceptor then maps the request onto the second protocol, after which the server interceptor transmits the mapped request to the server application.

Abstract: A data communication method that compensates for a disadvantageous characteristics of a first protocol. A client application and a server application employ a second protocol (i.e., a TCP/IP protocol) that is mapped onto the first protocol. A data communication request is received by a SOCKS client in accordance with the second protocol. The request, after being redirected client to a client interceptor by the SOCKS using a SOCKS protocol, is intercepted by the socks CLIENT. The client interceptor maps the request onto the first protocol, after which the client interceptor sends the mapped request to a server interceptor. The server interceptor compensates a disadvantageous characteristic of the first protocol to ascertain that a connection or transmission capacity condition exists and then to eliminate the condition. The server interceptor then maps the request onto the second protocol, after which the server interceptor transmits the mapped request to the server application.

Abstract: Means and method of data communication compensating disadvantageous characteristics of a first protocol for data communication between a client-application and a server-application. Communication requests of the client application and the server application adhering to a second protocol are intercepted by an client interceptor and a server interceptor. Besides mapping the second protocol onto the first protocol and back again the interceptors compensate disadvantageous characteristics inherent to the first protocol or arising from the combination of protocols transparently.

Abstract: Means and method of data communication compensating disadvantageous characteristics of a first protocol for data communication between a client-application and a server-application. Communication requests of the client application and the server application adhering to a second protocol are intercepted by an client interceptor and a server interceptor. Besides mapping the second protocol onto the first protocol and back again the interceptors compensate disadvantageous characteristics inherent to the first protocol or arising from the combination of protocols transparently.