Abstract: In an example embodiment a mechanism for consumer group versioning is introduced. Here, each application runtime provides a version for any consumer group during its deployment and keeps increasing the version whenever there is an enhancement or bug fix. Thus, both the application and the consumer group will have a version. Once it is recognized that a consumer group assigned to partitions in a topic has an outdated consumer group version number (i.e., a consumer group with the same name/application but a later consumer group version number has been registered with the message broker), the old consumer group is disconnected immediately. This allows the message broker to immediately assign partitions to the consumers in the newer consumer group, thus avoiding the aforementioned delays and associated technical problems.

Abstract: Techniques and solutions are provided for improving the performance of scheduled, computer-implemented tasks. A scheduler client can include an embedded scheduler. The embedded scheduler can monitor resource use by the scheduler client during execution of instances of a scheduled job. The embedded scheduler can also monitor resource used by targets of the scheduler client. The embedded scheduler can improve parallelization of subtasks for an instance of a scheduled job. Multiple instances of the scheduler client can be created to provide additional resources to be used in executing schedule instances. The multiple instances of the scheduler client can share access to information regarding schedule instances, such as to assist in selection of schedule instances to be executed by a particular scheduler client.

Abstract: In order to address the technical problems encountered with tenant-specific connection pools and global connection pools, in an example embodiment, an efficient connection pool is provided, which restricts the total number of connections per application runtime instance (as with the global connection pool) but at the same time groups and maintains the connections at the tenant level, using tenant-specific sub-pools.

Abstract: In an example embodiment, a framework is provided to allow multiple actions related to a web page to be grouped together in a single bookmark, while still allowing a user to select a specific performed action on the web page associated with the bookmark. For example, a bookmark for an employee page may not just provide the user with the ability to navigate automatically to that employee page, but may also provide the user with the ability to edit or search that employee page, all from a single bookmark.

Abstract: In order to address the technical problems encountered with tenant-specific connection pools and global connection pools, in an example embodiment, an efficient connection pool is provided, which restricts the total number of connections per application runtime instance (as with the global connection pool) but at the same time groups and maintains the connections at the tenant level, using tenant-specific sub-pools.

Abstract: A specialized topic in a message broker that is devoted to infrastructure messages is used. This infrastructure topic is then subscribed to by various applications, such as application microservices, including instances of applications running on different versions of the same application. Subscribing message consumers can then write a message to the infrastructure topic, with the message including the application identification and version number. Other message consumers subscribed to the infrastructure topic will receive notifications of this posted message. When a message consumer receives such a message, it checks to see if the message comes from an application that has the same application identification as itself. Then it checks to see if the version number included in the message is greater than its own version number. If so, then the application version of the recipient message consumer has been superseded and the application disconnects itself from the message broker.

Abstract: In an example embodiment a mechanism for consumer group versioning is introduced. Here, each application runtime provides a version for any consumer group during its deployment and keeps increasing the version whenever there is an enhancement or bug fix. Thus, both the application and the consumer group will have a version. Once it is recognized that a consumer group assigned to partitions in a topic has an outdated consumer group version number (i.e., a consumer group with the same name/application but a later consumer group version number has been registered with the message broker), the old consumer group is disconnected immediately. This allows the message broker to immediately assign partitions to the consumers in the newer consumer group, thus avoiding the aforementioned delays and associated technical problems.

Abstract: In an example embodiment, a cross-tenant service broker with a router microservice is introduced. The router microservice writes information into the service broker. A data receiver then reads the information from the service broker and stores it in tenant specific storage. A distributer forwards data that belongs to other data centers. In each tenant, data center information is received as part of an application program interface (API). In order to address the fact that the tenancy model of a MAP and a MLAP may be different, a service registry (or service landscape registry, such as SLIS or LIS) kernel service is used to map the MLAP tenant(s) into the correct MAP tenant(s).

Abstract: In an example embodiment, rather than passing SQL statements directly from an application runtime to a relational database, the SQL statements are first passed to a wrapper functionality. The wrapper functionality takes the uncompelled SQL statements and arguments that need to be passed for the SQL statement as input parameters, executes the statement, and returns the results. This is accomplished by generating a hash identification out of the string SQL statement. The wrapper functionality then looks for a hash identification of an input SQL statement. If it exists, then a corresponding object in the database can be retrieved and executed. If the hash identification is not found, a database object is created that performs the same functionality as the SQL statement. At this time, the SQL statement is also precompiled, and an execution plan created either by the wrapper functionality or the relational database, or both).

Abstract: In an example embodiment, a communication type registry is introduced that stores information about various versions of various communication types permitted within a system. A communication type owner defines a new communication type with a name, version number, and version details, and registers this information with the communication type registry. All source applications and target applications that have registered with the communication type registry then get notified when there is a new communication type or new version of an existing communication type available. Optionally a central repository can be used to store updates for all the source applications and target applications, where those applications can know to look for those updates.

Abstract: In an example embodiment, a specialized architecture is utilized in conjunction with a message broker to enable asynchronous communications. The specialized architecture provides central components within each data center to enable the communication, and also is able to segregate functionality across different microservice landscapes. A message broker alone may not be sharable across data centers for various technical reasons, such as security concerns, latency, or other technical constraints. Topic names may be utilized by the message broker to ensure delivery of the message to the correct microservice in the other data center.

Abstract: A method and system including at least one application, wherein a data storage is associated with each application; a de-duplication module; a de-duplication processor in communication with the de-duplication module and operative to execute processor-executable process steps to cause the system to: receive a data storage for each of the at least one application, wherein a first data storage and a second data storage include a same record or the one data storage includes two or more of the same record; separate the records into a key portion and a data portion; assign an internal key to each record, wherein the internal key is stored in both the key portion and the data portion for that record; calculate a golden record including golden record values; assign a golden record internal key to the golden record; replace each internal key in the key portion with the golden record internal key; and remove the data portion of each data record where the internal key in the data portion is different from the internal k

Abstract: A system, a method, and a computer program product for generation and consumption of global numbers. A range of global numbers for consumption by a plurality of processes of a software application in a plurality of software applications is generated. The range of global numbers is generated in accordance with one or more requirements of the software application and includes a plurality of blocks of global numbers. The generated range of global numbers is provided to the software application for consumption by the plurality of processes. Each process is assigned a block of global numbers in the plurality of blocks of global numbers and consumes the assigned block of global numbers. A count of global numbers in the global number range consumed by each process in the plurality of processes is determined. Another range of global numbers is generated upon determination of the count being below a predefined threshold.

Abstract: A method and system including a common dictionary module; a common dictionary processor in communication with the common dictionary module and operative to execute processor-executable process steps to cause the system to: define a common dictionary type; assign one or more characteristics to the common dictionary type; receive one or more data values; compress the dictionary type; and generate a common dictionary. Numerous other aspects are provided.

Abstract: A system, a method, and a computer program product for generation and consumption of global numbers. A range of global numbers for consumption by a plurality of processes of a software application in a plurality of software applications is generated. The range of global numbers is generated in accordance with one or more requirements of the software application and includes a plurality of blocks of global numbers. The generated range of global numbers is provided to the software application for consumption by the plurality of processes. Each process is assigned a block of global numbers in the plurality of blocks of global numbers and consumes the assigned block of global numbers. A count of global numbers in the global number range consumed by each process in the plurality of processes is determined. Another range of global numbers is generated upon determination of the count being below a predefined threshold.

Abstract: A method and system including a common dictionary module; a common dictionary processor in communication with the common dictionary module and operative to execute processor-executable process steps to cause the system to: define a common dictionary type; assign one or more characteristics to the common dictionary type; receive one or more data values; compress the dictionary type; and generate a common dictionary. Numerous other aspects are provided.

Abstract: A method includes defining a solution framework from a plurality of preconfigured components for developing a web service, defining a preliminary data model describing business objects associated with the web service, adding code that defines specific logic tasks associated with the web service, and deploying the web service utilizing the solution framework in a web server.

Abstract: A method and system including at least one application, wherein a data storage is associated with each application; a de-duplication module; a de-duplication processor in communication with the de-duplication module and operative to execute processor-executable process steps to cause the system to: receive a data storage for each of the at least one application, wherein a first data storage and a second data storage include a same record or the one data storage includes two or more of the same record; separate the records into a key portion and a data portion; assign an internal key to each record, wherein the internal key is stored in both the key portion and the data portion for that record; calculate a golden record including golden record values; assign a golden record internal key to the golden record; replace each internal key in the key portion with the golden record internal key; and remove the data portion of each data record where the internal key in the data portion is different from the internal k