Abstract: According to one general aspect, a method for managing a plurality of different tenants on a shared computing infrastructure including at least one application server apparatus may include associating a tenant with a plurality of services, wherein each service provides a set of actions that the service is configured to perform. In some embodiments, the method may include associating at least one tenant runlevel for each associated service with the tenant. In various embodiments, the method may include, when the application server apparatus executes a service for the tenant, determining the tenant runlevel associated with the tenant, and managing the set of actions configured to be performed by the service based at least in part upon the tenant runlevel associated with the tenant and the service.

Abstract: A kernel provides a mechanism allowing various applications (e.g. CRM, logistics, procurement, etc.) hosted on a plurality of different application servers, to share access to a common underlying system (e.g. database). An automated process for implementing a kernel change (e.g. for upgrade or replacement) may employ a “Stop-the-World” approach involving suspension of application server instances, coordinated by the start service of the last application server whose kernel is to be changed. As used herein, suspending refers to halting any processing prior to calling a central service (CS) as long as a CS instance is unavailable, and then to resuming processing once the CS instance becomes available. This suspension of relevant clients avoids errors from arising during the downtime of the CS instance. Once the application server instances are in a stopped state, the CS instance is restarted. Then, the application server instances are resumed, and their kernels are changed.

Abstract: One or more dynamic logon group parameters can be retrieved. The dynamic logon group parameters can be associated with an originator of requests for server processing by a computing system that includes a plurality of server instances, can be established prior to runtime, and can include an abstract definition of server instance characteristics required or preferred for handling the requests from the originator without designating specific server instances for handling the requests from the originator. One or more server instances can be selected from the plurality of server instances such that the one or more selected server instances satisfy the abstract definition of server instance characteristics. At runtime, the one or more selected server instances can be assigned to respond to the requests from the originator. Related articles of manufacture, systems, and methods are described.

Abstract: According to one general aspect, a method for managing a plurality of different tenants on a shared computing infrastructure including at least one application server apparatus may include associating a tenant with a plurality of services, wherein each service provides a set of actions that the service is configured to perform. In some embodiments, the method may include associating at least one tenant runlevel for each associated service with the tenant. In various embodiments, the method may include, when the application server apparatus executes a service for the tenant, determining the tenant runlevel associated with the tenant, and managing the set of actions configured to be performed by the service based at least in part upon the tenant runlevel associated with the tenant and the service.

Abstract: This disclosure provides various embodiments of software and systems for integrating static and dynamic content for an instance of a web page. In one aspect, the software identifies a content repository of structured dynamic content associated with information for a web page comprising unstructured static content. The software inserts a metadata data structure defining a set of the structured dynamic content into the unstructured static content of the web page to create a tag-enriched web page. The software can further perform a publish process for the tag-enriched web page comprising querying the content repository for the set of structured dynamic content information defined by the metadata data structure, populating the metadata-enriched web page with the results of the publish process query, and storing the updated web page at a web server.