Component load procedure for setting up systems

• US 8,434,060 B2
• Filed: 08/17/2010
• Issued: 04/30/2013
• Est. Priority Date: 08/17/2010
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Driesen, Volker, Eberlein, Peter
• Primary Examiner(s): LE, HUNG D
• Application Number:
  US12/857,967
• Publication Number:
  US 20120047185A1
• Time in Patent Office: 987 Days
• Field of Search: None
• US Class Current: 717/107
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

Optional components are delivered to a software platform as a database load. A component is deployed to an application server of a first system. The component comprises at least a portion of the software to be delivered as a database load to a second system that implements the software platform. A component export tool in the first system identifies database table structures and database table entries created by the deployment of the component. The component export tool generates a load delivery package based on the identified database table structures and database table entries and then exports the load delivery package to the second system. A component load tool in the second system generates application tables based on the identified database table structures in the shipment package. The database table entries are then imported into the generated application packages in the load delivery package so that the component can be loaded into the software platform. Related apparatus, systems, techniques and articles are also described.

Claims

1. A method for delivering optional components to a software platform as a database load, the method comprising:

deploying a component to an application server of a first system, the component comprising at least a portion of the software to be delivered as a database load to a second system, the second system implementing the software platform;

identifying, by a component export tool in the first system, database table structures and database table entries created by the deployment of the component;

generating, by the component export tool, a load delivery package based on the identified database table structures and database table entries;

exporting, by the component export tool, the load delivery package to the second system;

generating, by a component load tool in the second system, application tables based on the identified database table structures in the load delivery package;

importing, by the component load tool, the database table entries into the generated application tables in the load delivery package;

loading the component into the software platform;

determining that at least a portion of a plurality of database artifacts on the first system cannot be mapped to the database table entries and require delivery to the second system by deployment; and

deploying the at least a portion of the plurality of database artifacts on the first system that cannot be mapped to the database table entries to the second system;

determining that at least one first database artifact can be delivered as a database load;

determining that at least one second database artifact cannot be delivered as a database load;

loading the at least one first database artifact to the software platform; and

deploying the at least one second database artifact to the software platform.

2. A method as in claim 1, wherein the first system and the second system are implementing a same version of the software platform.

3. A method as in claim 1, wherein generating the load delivery package comprises computing a Data Definition Language Statement (DDL) for the identified database table structures, and wherein the application tables are generated based on the DDL.

4. A method as in claim 1, wherein the determining is based on design-time information specifying that an associated application server requires deployment.

5. A method as in claim 1, wherein the determining is based on dynamic information indicating that the second system requires a deployment.

6. A method as in claim 1, further comprising:

adding, by the component export tool, information to a bill of material (BOM) characterizing a system and/or an interface version of the component.

7. A method as in claim 1, further comprising:

adding, by the component export tool, an identifier for all objects belonging to the component and to its type to a bill of material (BOM).

8. A method as in claim 7, further comprising:

adding, by the component export tool, information to the BOM characterizing which objects of the component are included in the load delivery package.

9. A method as in claim 8, further comprising:

adding, by the component export tool, information to the BOM characterizing which objects of the component are provided within the load delivery package as only a deployable artifact.

10. A method as in claim 9, further comprising:

reading, by the component load tool, the BOM to identify which objects specified by the BOM require deployment and which objects to load.

11. A method as in claim 8, further comprising:

reading, by the component load tool, the BOM to determine, for each item, whether the database table entries require deployment or can be loaded.

12. A method as in claim 1, further comprising:

checking, by the component load tool, a version of the second system to determine if the component has a version greater than a pre-defined version.

13. A method as in claim 12, wherein the component cannot be deployed if the component has a version less than or equal to the pre-defined version.

14. A method as in claim 1, further comprising:

checking, by the component load tool, a version of the first system and a version of second system to determine which objects are dependent on system versions.

15. A method as in claim 14, further comprising:

loading objects that are not dependent on system versions and deploying objects that are dependent on system versions.

16. A method as in claim 1, wherein a component export tool on a first system determines that the at least one first database artifact can be delivered as a database load and determines that the at least one second database artifact cannot be delivered as a database load.

17. A method as in claim 16, wherein the component export tool packages the database artifacts into a load delivery package for importing by a component load tool on a second system.

18. A non-transitory computer program product for delivering components to a software platform as a database load, the computer program product storing instructions, which when executed by at least one data processor, result in operations comprising:

deploying a component to an application server of a first system, the component comprising at least a portion of the software to be delivered as a database load to a second system, the second system implementing the software platform;

identifying, by a component export tool in the first system, database table structures and database table entries created by the deployment of the component;

generating, by the component export tool, a load delivery package based on the identified database table structures and database table entries;

exporting, by the component export tool, the load delivery package to the second system;

generating, by a component load tool in the second system, application tables based on the identified database table structures in the load delivery package;

importing, by the component load tool, the database table entries into the generated application tables in the load delivery package;

loading the component into the software platform;

determining that at least a portion of a plurality of database artifacts on the first system cannot be mapped to the database table entries and require delivery to the second system by deployment; and

deploying the at least a portion of the plurality of database artifacts on the first system that cannot be mapped to the database table entries to the second system,

determining that at least one first database artifact can be delivered as a database load;

determining that at least one second database artifact cannot be delivered as a database load;

loading the at least one first database artifact to the software platform; and

deploying the at least one second database artifact to the software platform.