Sap Ag

Sap Se

Vladimir Pavlov

Peter K Matov

Hristo S Iliev

Petar Zhechev

Verzhiniya Noeva

Hristo Kostov

Hristo K Sabev

Krasimir I Topchiyski

Vesselin Mitrov

Viktoriya T Ivanova

Viktoriya Ts Ivanova

Radoslav Ivanov

Bistra Yakimova

Krasimir Topchiyski

An archive file including an extension server runtime of the arbitrary server and one or more auxiliary computer modules is received. Input values of one or more configuration parameters including a number of extension server nodes to be installed are received. The archive file is extracted at a file system of the at least one server instance. The extracted extension server runtime is read by an extension server bootstrap from the one or more auxiliary modules. The number of extension server nodes as specified by the input values are installed based on the extracted extension server runtime on the at least one server instance by the extension server bootstrap.

Installation of an arbitrary server as an extension of a computing platform

Applications and their application components run on a cloud platform and an underlying cloud runtime infrastructure. The cloud platform provides a service that exposes an interface to remotely change log levels of logger objects defined in application components. The application logs are generated and stored for the application components on the cloud runtime infrastructure of the cloud platform. Log levels affect the content stored in the application logs. The exposed interface is instantiated to process remote requests for managing application logs and log levels for a specified application component. The application component is deployed on the cloud platform. The requested change in the log levels is performed based on the implementation of the interface. The change in the log levels is performed in the configuration data on the cloud runtime infrastructure provided by the cloud platform.

Managing application log levels in cloud environment

Applications and their application components are deployed on a cloud platform. The application components generate application logs on the underlying cloud runtime infrastructure of the cloud platform. In one aspect, the application logs may be stored on a network storage on the cloud platform. In another aspect, the application logs may be stored on the cloud runtime infrastructure. The cloud platform provides a service that exposes an interface to remotely provide the stored application logs. The exposed interface is instantiated to process remote requests for application logs for a specified application component. The remote requests are sent from a client. The requested application logs are retrieved based on the implementation of the interface. The application logs are provided to the client.

Providing remote application logs for cloud applications

The present disclosure involves systems, software, and computer implemented methods for retrying business methods at an application server after thrown exceptions. One process includes operations for invoking a business method of an enterprise bean hosted in an enterprise bean container. The operations further include determining whether retry conditions are satisfied after an exception is thrown during execution of the business method. The business method is invoked again based on a predefined retry policy when the retry conditions are satisfied.

Business methods retry optimization

A method to start enterprise applications on demand using naming references is described. The method matches Enterprise JavaBeans applications to respective naming references, checks if the matched application is running and starts it if it is not.

Starting enterprise applications on demand

A runtime environment injects an instance of an external resource into an application component to be executed in the runtime environment by first determining an external resource associated with the application component, then selecting from a library of injectors an injector to inject an instance of the application component with an instance of an external resource referenced by the external resource annotation. The selected injector determines the instance of the application component to inject with the instance of the external resource and injects the instance of the application component with the instance of the external resource.

Injection library

One embodiment of the invention employs 'transparent object persistence' techniques in which persistent data objects (i.e., the objects that represent persistent data from a database) are separated from business processing objects (i.e., the objects that handle the requests, process specific business operations, manipulate the persistent data and respond to clients). Within a Java 2 Enterprise Edition ('J2EE') environment, the business processing objects are entity beans managed by an Enterprise Java Bean (&#x201c;EJB&#x201d;) container. A persistence manager manages the persistent data objects, which provide an in-memory representation of a set of database data. The entity beans manipulate the persistent data by invoking get/set accessor methods on the persistent data objects. In one embodiment, the persistence manager associates a state with each of the persistent data objects which indicates an operation to be performed within tables of a relational database when the modifications to the persistent data objects are committed to the relational database.

System and method for transparent persistence management

A system and method are described for ordering a database flush sequence prior to committing transaction changes to a database. In one embodiment, a plurality of data operations modifying persistent data objects are performed in a sequential order within an object-oriented environment. Relational dependencies between the persistent data objects are evaluated and the changes to the data objects are reordered based on the relational dependencies. Once reordered, the changes are committed to the database. In one embodiment, a depth first search algorithm is employed to determine the appropriate order to commit the data to the database.

Growing community of inventors

Sofia, Bulgaria

Vladimir Pavlov