Deploying a variety of containers in a Java 2 Enterprise Edition-based architecture

• US 20050262477A1
• Filed: 05/24/2004
• Published: 11/24/2005
• Est. Priority Date: 05/24/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kovachka-Dimitrova, Monika M., Angelova, Rumiana G.
• Granted Patent: US 7,721,283 B2
• Time in Patent Office: Days
• US Class Current: 717/118
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A system and method are described for deploying non-J2EE containers on a J2EE server. In one embodiment, non-J2EE containers are created and deployed on the J2EE server in communication with J2EE containers already deployed on the J2EE server.

Claims

1. A method, comprising:

creating one or more non-Java 2 Enterprise Edition (J2EE) containers; and

deploying the one or more non-J2EE containers on a J2EE server in communication with one or more J2EE containers already deployed on the J2EE server.

2. The method of claim 1, wherein the creating of the one or more non-J2EE containers is performed by a provider including SAP AG, the one or more non-J2EE containers include one or more SAP containers.

3. The method of claim 1, further comprises deploying non-J2EE components on the one or more non-J2EE containers.

4. The method of claim 3, further comprises creating one or more non-J2EE applications using the non-J2EE components.

5. The method of claim 1, wherein the deploying of the one or more non-J2EE containers is performed using a deploy service via one or more of the following:

a deploy service application programming interface (API) and a container API.

6. The method of claim 5, wherein the container API provides a bi-directional communication between the deploy service and the one or more non-J2EE containers.

7. The method of claim 3, wherein the deploying of the non-J2EE components is performed using the deploy service and the container API.

8. The method of claim 7, wherein the one or more non-J2EE containers and the one or more J2EE containers via the container API use one or more of the following services and interfaces:

Java Naming Directory Interface (JNDI), Java Database Connectivity (JDBC), J2EE connector Architecture (JCA), Remote Invocation (RMI), Java Transaction API (JTA), Java Transaction Service (JTS), Java Message Service (JMS), Java Mail, Java Cryptography Architecture (JCA), Java Cryptography Extension (JCE), Java Authentication and Authorization Service (JAAS), Enterprise JavaBean (EJB) service, servlet_jsp service, application service, connector service, dbpool service, Java management service (JMS)_connector service, Webservices service, Webdynpro service, log_configurator service, and Java monitoring service.

9. The method of claim 3, wherein the non-J2EE components comprise one or more of the following:

Portlets of Enterprise Portals and WebDynPro.

10. A J2EE architecture, comprising:

a J2EE server havingone or more J2EE containers, and

one or more non-J2EE containers deployed on the J2EE server in communication with the one or more J2EE containers; and

a client coupled with the J2EE server.

11. The J2EE architecture of claim 10, wherein the J2EE server includes a deploy service to facilitate the deployment of the one or more non-J2EE containers.

12. The J2EE architecture of claim 11, wherein the deploy service is further to deploy non-J2EE components on the non-J2EE one or more non-J2EE containers.

13. The J2EE architecture of claim 12, wherein the non-J2EE components are to facilitate assembling of non-J2EE applications.

14. The J2EE architecture of claim 12, wherein the deploy service is in bi-directional communication with the one or more J2EE and non-J2EE containers and the client via a deploy service API and a container API.

15. The J2EE architecture of claim 14, wherein the deploy service is further to deploy entities on to the J2EE and non-J2EE containers via a container interface of the container API.

16. The J2EE architecture of claim 14, wherein the deploy service is further to receive information relating to the J2EE and non-J2EE containers via a deploy communicator of the container API.

17. The J2EE architecture of claim 10, wherein the client comprises a visual administrator to display the information received from the J2EE and non-J2EE containers via the deploy service, the information including status information or events regarding deployment operations in the J2EE and non-J2EE containers.

18. The J2EE architecture of claim 17, wherein the visual administrator includes a viewer having one or more of the following:

a Graphical User Interface (GUI)-based viewer and a Web-based viewer.

19. The J2EE architecture of claim 18, wherein the Web-based viewer includes a browser having one or more of the following:

a Microsoft Internet Explorer and a Netscape Navigator.

20. The J2EE architecture of claim 10, wherein the client comprises a deploy tool to deploy one or more entities including one or more of the following:

applications, components, and containers.

21. The J2EE system, comprising:

a J2EE server having one or more J2EE containers and one or more non-J2EE containers, the non-J2EE containers having non-J2EE components to facilitate assembling of non-J2EE applications;

a client, coupled with the J2EE server, having a viewer to display the non-J2EE applications.

22. The J2EE system of claim 21, wherein the one or more non-J2EE containers are created by a provider including SAP AG.

23. The J2EE system of claim 21, wherein the one or more non-J2EE containers are deployed on the J2EE server using a deploy service.

24. The J2EE system of claim 23, wherein the deploy service comprises a module in communication with the one or more J2EE containers, the one or more non-J2EE containers, and the client.

25. The J2EE system of claim 23, wherein the client includes a deploy tool to deploy one or more entities on the J2EE server via the deploy service.

26. The J2EE system of claim 23, wherein the viewer includes at least one or more of the following:

a GUI-based viewer and a Web-based browser.

27. A machine-readable medium having stored thereon data representing sets of instructions which, when executed by a machine, cause the machine to:

create one or more non-J2EE containers; and

deploy the one or more non-J2EE containers on a J2EE server in communication with one or more J2EE containers already deployed on the J2EE server.

28. The machine-readable medium of claim 27, wherein the creating of the one or more non-J2EE containers is performed by a provider including SAP AG, the one or more non-J2EE containers include one or more SAP containers.

29. The machine-readable medium of claim 27, wherein the sets of instructions, when executed by the machine, further cause the machine to deploy non-J2EE components on the one or more non-J2EE containers.

30. The machine-readable medium of claim 29, wherein the sets of instructions, when executed by the machine, further cause the machine to create one or more non-J2EE applications using the non-J2EE components.

31. The machine-readable medium of claim 27, wherein the deploying of the one or more non-J2EE containers is performed using a deploy service via one or more of the following:

a deploy service application programming interface (API) and a container API.

32. The machine-readable medium of claim 31, wherein the container API provides a bi-directional communication between the deploy service and the one or more non-J2EE containers.

33. The machine-readable medium of claim 29, wherein the deploying of the non-J2EE components is performed using the deploy service and the container API.

34. The machine-readable medium of claim 33, wherein the one or more non-J2EE containers and the one or more J2EE containers via the container API use one or more of the following services and interfaces:

Java Naming Directory Interface (JNDI), Java Database Connectivity (JDBC), J2EE connector Architecture (JCA), Remote Invocation (RMI), Java Transaction API (JTA), Java Transaction Service (JTS), Java Message Service (JMS), Java Mail, Java Cryptography Architecture (JCA), Java Cryptography Extension (JCE), Java Authentication and Authorization Service (JAAS), Enterprise JavaBean (EJB) service, servlet_jsp service, application service, connector service, dbpool service, Java management service (JMS)_connector service, Webservices service, Webdynpro service, log_configurator service, and Java monitoring service.

35. The machine-readable medium of claim 29, wherein the non-J2EE components comprise one or more of the following:

Portlets of Enterprise Portals and WebDynPro.