Component offline deploy

• US 20050278341A1
• Filed: 05/28/2004
• Published: 12/15/2005
• Est. Priority Date: 05/28/2004
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Semerdzhiev, Krasimir P., Petev, Petio G., Quang, Pham D., Kostadinov, Dimitar P.
• Application Number:
  US10/856,554
• Publication Number:
  US 20050278341A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Embodiments include a system for updating software components in a computing system. The update system may deploy software components into a centralized database. The update system may provide an interface for deploying software components into the database. The update system may map the software components into a relational database or similar database system. In an additional embodiment, the deployed software components may be downloaded from the centralized database during a start up process for a computing system.

Claims

1. A apparatus comprising:

an interface to select a software component for one of deployment and removal;

a database to store software components for use by a server to provide services to a client; and

a deployment module in communication with the interface and a database to provide a standardized interface to initiate one of a deployment and a removal of a software component from the database.

2. The apparatus of claim 1, wherein the deployment module generates a mapping of a file structure of a component to be one of deployed and removed.

3. The apparatus of claim 1, further comprising:

a configuration manager to generate a set of database commands to implement the removal or deployment of the software component.

4. The apparatus of claim 1, further comprising:

a software deployment archive containing the software component.

5. The apparatus of claim 1, further comprising:

a server in communication with the database to update its configuration based on the deployment in the database.

6. A method comprising:

receiving a deployment request;

accessing a software deployment archive; and

initiating a transfer of a software components in the software deployment archive into a database, the database to supply a set of servers with the software component.

7. The method of claim 6, wherein accessing comprises:

opening the software deployment archive (SDA) which is one of a bootstrap SDA, a kernal SDA, service SDA, library SDA, interface SDA, single module SDA, and java application SDA.

8. The method of claim 6, further comprising:

analyzing a software deployment archive to validate files in the software deployment archive.

9. The method of claim 6, further comprising:

mapping the software component into the database which is a relational database.

10. The method of claim 6, further comprising:

opening a java archive file containing the software deployment archive.

11. The method of claim 6, further comprising:

replacing the software component in the database with an updated software component.

12. A method comprising:

receiving an indicator of a software component;

receiving a remove request; and

initiating the removal of the software component from a database, the database to supply a set of servers with software components.

13. The method of claim 12, further comprising:

tracking references to a software component and removing the software component if no references exist.

14. The method of claim 12, further comprising:

sending a query to the database which is a relational database that contains software components for applications.

15. The method of claim 12, further comprising:

determining a location of the software component in the database.

16. A system comprising:

a client;

a plurality of servers to provide a service to the client;

a central database to provide a software component of the service to each of the plurality of servers; and

a deployment module to deploy or remove the software component from the central database.

17. The system of claim 16, further comprising:

a user interface to allow a selection of the software component to be deployed or removed.

18. The system of claim 16, further comprising:

a configuration manager to map a software component into a relational database location.

20. The apparatus of claim 18, further comprising:

means for opening the software deployment archive (SDA) which is one of a bootstrap SDA, a kernal SDA, a service SDA, a library SDA, an interface SDA, a single module SDA, and a java application SDA.

21. The apparatus of claim 18, further comprising:

means for replacing a set of files in the database with files from the software deployment archive.

23. The apparatus of claim 21, further comprising:

means for tracking references to a resource and initiating a removal of the resource if no references to the resource exist.

19. An apparatus comprising:

means for receiving a command to deploy a software deployment archive; and

means for transferring the software deployment archive to a database, the database to supply a software component to a server to provide a service.

22. An apparatus comprising:

means for receiving a command to remove a software component from a database, the database providing the software component to a set of servers to provide a service; and

means for removing the software component from the database.

24. The apparatus of claim 22, further comprising:

means for locating the software component in the database.

25. A machine readable medium, having instructions stored therein which when executed cause a machine to perform a set of operation comprising:

receiving a command to deploy a software deployment archive; and

transferring the software deployment archive to a database, the database to supply a software component to a server to provide a service.

26. The machine readable medium of claim 25, having further instructions stored therein which when executed cause a machine to perform a set of operations further comprising:

opening the software deployment archive (SDA) which is one of a bootstrap SDA, a kernal SDA, a service SDA, a library SDA, an interface SDA, a single module SDA, and a java application SDA.

27. The machine readable medium of claim 25, having further instructions stored therein which when executed cause a machine to perform a set of operations further comprising:

replacing a set of files in the database with files from the software deployment archive.

28. A machine readable medium, having instructions stored therein which when executed cause a machine to perform a set of operation comprising:

receiving a command to remove a software component from a database, the database providing the software component to a set of servers to provide a service; and

removing the software component from the database.

29. The machine readable medium of claim 28, having instructions stored therein which if executed cause a machine to perform a set of operation comprising:

tracking references to a software resource and initiating a removal of the software resource when no references to the software resource exist.

30. The machine readable medium of claim 28, having further instructions stored therein which when executed cause a machine to perform a set of operations further comprising:

locating the software component in the database.