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: 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: 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: Techniques for providing an error log include establishing, by a hub computing system, a connection with a back-end computing system, the back-end computing system executing a first computer-implemented programming language; receiving, at the hub computing system, a request for an error log from an Open Data Protocol (OData) application that resides on a mobile communications device, the mobile communications device executing a second computer-implemented programming language different than the first computer-implemented programming language, and the error log including error log entries associated with a runtime processing of a data model; registering, on the hub computing system, the error log as an OData service configured to be provided over an OData channel between the hub computing system and the mobile communications device; and providing, by the hub computing system, the error log to the OData application as the OData service over the OData channel.

Abstract: Techniques for providing an error log include establishing, by a hub computing system, a connection with a back-end computing system, the back-end computing system executing a first computer-implemented programming language; receiving, at the hub computing system, a request for an error log from an Open Data Protocol (OData) application that resides on a mobile communications device, the mobile communications device executing a second computer-implemented programming language different than the first computer-implemented programming language, and the error log including error log entries associated with a runtime processing of a data model; registering, on the hub computing system, the error log as an OData service configured to be provided over an OData channel between the hub computing system and the mobile communications device; and providing, by the hub computing system, the error log to the OData application as the OData service over the OData channel.

Abstract: Among other disclosed subject matter, a computer-implemented method of remotely generating a purchase order is to be initiated. The method includes receiving a communication in an enterprise resource planning (ERP) system. The ERP system has a purchasing transaction configured for communicating with each of multiple vendor systems for performing the acquisitions. The received communication is sent wirelessly from a mobile device operated by a user. The mobile device is configured for obtaining information from the user in a process compatible with the purchasing transaction for generating a purchase order in the ERP system. The method includes generating the purchase order in the ERP system. The purchase order includes an instruction to a vendor operating a first vendor system to deliver a quantity of a product type. The method includes forwarding the purchase order from the ERP system to the first vendor system.

Abstract: Among other disclosed subject matter, a computer-implemented method of remotely generating a purchase order is to be initiated. The method includes receiving a communication in an enterprise resource planning (ERP) system. The ERP system has a purchasing transaction configured for communicating with each of multiple vendor systems for performing the acquisitions. The received communication is sent wirelessly from a mobile device operated by a user. The mobile device is configured for obtaining information from the user in a process compatible with the purchasing transaction for generating a purchase order in the ERP system. The method includes generating the purchase order in the ERP system. The purchase order includes an instruction to a vendor operating a first vendor system to deliver a quantity of a product type. The method includes forwarding the purchase order from the ERP system to the first vendor system.