IP Library › Granted Patent US 7,743,029
Granted Patent B2
US 7,743,029 · App. 10/836,851 · Granted Jun 22, 2010

Log configuration and online deployment services

Assignee: SAP AG
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,743,029
App. No.
10/836,851
Granted
Jun 22, 2010
Kind
B2
Abstract

Methods and apparatuses for configuring logging of a deployment of an enterprise component are described herein. In one embodiment, in response to a request for deploying an enterprise component, a logging configuration process extracts logging configuration information from a logging configuration file associated with the enterprise component and configures the logging for the respective enterprise component being deployed. The logging configuration file is designed exclusively for configuring logging of the enterprise component. Thereafter, the deployment information of the enterprise component is logged based on the extracted logging configuration information when the enterprise component is deployed. Other methods and apparatuses are also described.

Claims (44)

1. A method for deploying an enterprise component in an enterprise computing environment, the method comprising:

in response to a granted request for deploying an enterprise component, extracting logging configuration information from a logging configuration file packed with the enterprise component prior to deployment, wherein the logging configuration file specifies how the deployment information should be logged during the deployment;

logging deployment information of the enterprise component based on the extracted logging configuration information during deployment of the enterprise component; and

storing the logged deployment information in a storage.

2. The method of claim 1 , further comprising retrieving the configuration file from a deployable file containing the enterprise component, in response to the granted request.

3. The method of claim 1 , wherein the enterprise component is one of an interface component, a resource component, a service component, and a library component.

4. The method of claim 1 , further comprising storing the logging configuration file in a database for later use after the enterprise component is deployed.

5. The method of claim 4 , further comprising:

updating the logging configuration information via an administration API;

and storing the updated logging configuration information in the logging configuration file stored in the database.

6. The method of claim 5 , further comprising logging deployment information of the enterprise component according to one or more policies of the updated logging configuration file during the redeployment of the enterprise component in response to a granted request for redeployment.

7. The method of claim 1 , wherein the logging configuration file is written as a metadata file.

8. The method of claim 1 , wherein the enterprise component is a J2EE compatible component.

9. A apparatus for deploying an enterprise component in an enterprise computing environment, the apparatus comprising:

a log manager for managing logging deployment information of an enterprise component during the deployment of the enterprise component in response to a granted request for deployment; and

a log configuration service, when executed by the log manager, causes the log manager to

in response to a granted request for deploying an enterprise component, extract logging configuration information from a logging configuration file packed with the enterprise component prior to deployment, wherein the logging configuration file specifies how the deployment information should be logged during the deployment;

log deployment information of the enterprise component based on the extracted logging configuration information during deployment of the enterprise component in response of a granted request for deployment; and

store the logged deployment information in a storage.

10. The apparatus of claim 9 , wherein the log manager retrieves the configuration file from a deployable file containing the enterprise component.

11. The apparatus of claim 9 , wherein the enterprise component is one of an interface component, a resource component, a service component, and a library component.

12. The apparatus of claim 9 , wherein the log manager stores the logging configuration file in a database for later use after the enterprise component is deployed.

13. The apparatus of claim 12 , further comprising an administration API to allow an administrator to:

update the logging configuration information; and

store the updated logging configuration information in the logging configuration file stored in the database.

14. The apparatus of claim 13 , wherein the log manager logs deployment information of the enterprise component according to one or more policies of the updated logging configuration file during the redeployment of the enterprise component in response to a granted request for redeployment.

15. The apparatus of claim 9 , wherein the logging configuration file is written as a metadata file.

16. The apparatus of claim 9 , wherein the enterprise component is a J2EE compatible component.

17. A machine-readable storage medium having executable code to cause a machine to perform a method, the method comprising:

in response to a granted request for deploying an enterprise component, extracting logging configuration information from a logging configuration file packed with the enterprise component prior to deployment, wherein the logging configuration file specifies how the deployment information should be logged during the deployment;

logging deployment information of the enterprise component based on the extracted logging configuration information during deployment of the enterprise component; and

storing the logged deployment information in a storage.

18. An enterprise computing system, comprising:

a processor;

a memory coupled to the processor; and

a logging process executed from the memory, in response to a granted request for deploying an enterprise component causes the processor to

extract logging configuration information from a logging configuration file packed with the enterprise component prior to deployment, wherein the logging configuration file specifies how the deployment information should be logged during the deployment;

log deployment information of the enterprise component based on the extracted logging configuration information during deployment of the enterprise component; and

store the logged deployment information in a storage.

19. A method for deploying enterprise components in an enterprise computing environment, the method comprising:

in response to a granted request for deploying a plurality of enterprise components, for each of the plurality of the enterprise components being deployed, extracting configuration information from a configuration file packed with the respective enterprise component prior to deployment;

deploying each of the plurality of enterprise components using the configuration information extracted from the respective configuration file;

logging deployment information for the respective enterprise component according to one or more logging policies specified in the respective configuration file, wherein the logging policies in the configuration file specify how the deployment information should be logged during the deployment of the respective enterprise component; and

storing the logged deployment information in a storage.

Assignments (2)
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0334 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 29, 2004
From: FREY, GREGOR K.; PETROV, MIROSLAV R.; MANEFF, GEORGI G.
To: SAP AKTIENGESELLSCHAFT
Reel/Frame 015934/0337 →
Continuity (3)
Continuation In Part 1074900500 · Dec 30, 2003
Continuation In Part 1074961500 · Dec 30, 2003
Related Publication 20050149535A1 · Jul 7, 2005