System and method for bundling deployment descriptor files within an enterprise archive for fast reliable resource setup at deployment time

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

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Arnaudov, Nikola Z., Gatev, Andrei A.
• Application Number:
  US10/857,106
• Publication Number:
  US 20050267918A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

System and method to bundle deployment descriptors with enterprise archives (“EAR”). An application is bundled with at least one deployment descriptor file within an EAR. The deployment descriptor file defines properties to establish connectivity to network services. Syntax of the deployment descriptor files is verified with reference to rules definition files included within the application server. Connectivity to the network services is established based on the properties defined in the deployment descriptor files, if the syntax of the deployment descriptor files verifies as valid.

Claims

1. A computer-implemented method, comprising:

deploying an enterprise archive (“

EAR”

) including an application and at least one deployment descriptor (“

DD”

) file onto an application server executing on a server node, the at least one DD file defining properties to establish connectivity to network services;

verifying syntax of the at least one DD file with reference to a rules definition file (“

RDF”

) included in the application server; and

establishing connectivity to the network services based on the properties defined in the DD file, if the syntax of the DD file verifies as valid.

2. The method of claim 1, wherein establishing connectivity to the network services based on the properties defined in the DD file comprises:

generating connectivity objects based on the DD file; and

binding the connectivity objects into a Java Naming and Directory Interface (“

JNDI”

) namespace to provide access to the connectivity objects.

3. The method of claim 2, further comprising:

communicating with a remote node coupled to the server node via a communication link using the network services.

4. The method of claim 1, wherein the DD file comprises an extensible markup language (“

XML”

) file.

5. The method of claim 4, wherein the RDF conforms to a document type definition (“

DTD”

) file format.

6. The method of claim 1, wherein the at least one DD file defines properties to establish a Java Database Connectivity (“

JDBC”

) connection to access a remote database node.

7. The method of claim 1, wherein the at least one DD file defines properties to establish connectivity to a Java Messaging Service (“

JMS”

).

8. The method of claim 7, wherein the at least one DD file defines properties to establish a JMS Connection Factory.

9. The method of claim 7, wherein the at least one DD file defines properties to establish a JMS Destination object.

10. The method of claim 1, wherein the at least one DD file defines at least one alias pointing to a data source object to provide connections to a remote node communicatively coupled to the server node, the at least one alias to time-share the connections.

11. The method of claim 1, wherein the application server comprises one of a Java 2 Enterprise Edition (“

J2EE”

) application server and a .NET application server.

12. A machine-accessible medium that provides instructions that, if executed by a machine, will cause the machine to perform operations comprising:

executing an application server to receive an application and to provide network services to the application, the application server including at least one rules definition file (“

RDF”

), the RDF to verify syntax of a deployment descriptor (“

DD”

) file defining properties to establish connectivity between the application and network services;

receiving the application along with the DD file deployed from an enterprise archive (“

EAR”

); and

verifying the syntax of the DD file with reference to the RDF.

13. The machine-accessible medium of claim 12, further providing instructions that, if executed by the machine, will cause the machine to perform further operations, comprising:

providing the network services to the application based on the properties defined in the DD file, if the verifying with reference to the RDF verifies the syntax of the DD file as valid.

14. The machine-accessible medium of claim 13, wherein the RDF defines syntax of an extensible markup language (“

XML”

) deployment descriptor file.

15. The machine-accessible medium of claim 14, wherein the RDF conforms to a document type definition (“

DTD”

) file format.

16. The machine-accessible medium of claim 13, wherein the RDF includes information to verify syntax of a Java Messaging Service (“

JMS”

) Destination descriptor file.

17. The machine-accessible medium of claim 16, wherein the information includes syntax rules for a JMS destination descriptor, a name of an associated JMS Connection Factory descriptor, a username descriptor, and a password descriptor.

18. The machine-accessible medium of claim 14, wherein the RDF includes information to verify syntax of a data source descriptor file for establishing a Java DataBase Connectivity (“

JDBC”

) interface to a database.

19. The machine-accessible medium of claim 18, wherein the information includes syntax rules for a data source name descriptor, a connection expiration control descriptor, and a maximum number of connections descriptor.

20. The machine-accessible medium of claim 14, wherein the RDF includes information to verify syntax of a Java Messaging Service (“

JMS”

) Connection Factory descriptor file.

21. The machine-accessible medium of claim 20, wherein the information includes syntax rules for a factory-name descriptor and a connection-factory-type descriptor.

22. The machine-accessible medium of claim 14, wherein the RDF includes information to verify syntax of a data source alias descriptor file to enable time-sharing of data source connections to a database.

23. The machine-accessible medium of claim 12, wherein the application server comprises one of a Java 2 Enterprise Edition (“

J2EE”

) application server and a .NET application server.

24. An application server, comprising:

an application to provide business logic to an enterprise environment;

network services to provide the application access to remote nodes within the enterprise environment;

a deployment descriptor (“

DD”

) file bound to the application to configure connectivity between the application and the network services; and

a container to encapsulate the application within a runtime environment, the container including a rules definition file (“

RDF”

), the RDF to verify syntax of the DD file upon deployment of the application and DD file.

25. The application server of claim 24, wherein the DD file comprises an extensible markup language (“

XML”

) deployment descriptor file.

26. The application server of claim 24, wherein the RDF conforms to a document type definition (“

DTD”

) file format.

27. The application server of claim 24, wherein the DD file is to configure connectivity between the application and a Java Messaging Service (“

JMS”

).

28. The application server of claim 27, wherein the DD file is further to establish a JMS Connection Factory.

29. The application server of claim 27, wherein the DD file is further to establish a JMS Destination Object.

30. The application server of claim 24, wherein the DD file is to establish a data source object and configure Java Database Connectivity (“

JDBC”

) connections between the data source object and one of the remote nodes.

31. The application server of claim 30, further comprising:

another DD file bound to the application to establish an alias pointing to a data source object, the alias to time-share the JDBC connections; and

another RDF included within the container, the another RDF to verify the syntax of the another DD file.

32. The application server of claim 24, wherein the application server comprises a Java 2 Enterprise Edition (“

J2EE”

) application server.

33. A system, comprising:

means for providing business logic to an enterprise environment;

means for automatically configuring network connectivity between the means for providing business logic and remote nodes within the enterprise environment; and

means for verifying syntax of the means for automatically configuring.

34. The system of claim 33, further comprising:

means for encapsulating the means for providing the business logic within an runtime environment, wherein the means for verifying the syntax is bound to the means for encapsulating.

35. The system of claim 34, further comprising:

means for deploying the means for providing the business logic into the means for encapsulating, wherein the means for deploying includes the means for providing the business logic bundled with the means for automatically configuring the network connectivity.

36. The system of claim 35, wherein the means for deploying comprises an enterprise archive (“

EAR”

), the means for providing the business logic comprises a business application, and the means for automatically configuring the network connectivity comprises a deployment descriptor file.

37. An enterprise archive, comprising:

an application including one of business logic and presentation logic to deploy onto an application server; and

a deployment descriptor (“

DD”

) file defining properties to establish connectivity between the application and network services after deployment to the application server, the syntax of the DD file automatically verifiable with reference to a rules definition file (“

RDF”

) includable with the application server.

38. The enterprise archive of claim 37, wherein the application comprises one of an Enterprise Java Bean (“

EJB”

), a Servlet, and a Java Server Page (“

JSP”

).

39. The enterprise archive of claim 37, wherein the DD file comprises an extensible markup language (“

XML”

) deployment descriptor file.

40. The enterprise archive of claim 37, wherein the DD file defines properties to configure at least one of a connection to a Java Messaging Service (“

JMS”

), a Java DataBase Connectivity (“

JDBC”

) connection to a database, and an alias pointing to a data source including multiple network connections for time-sharing the network connections.