SYSTEM AND METHOD FOR PROVIDING AN ENTERPRISE DEPLOYMENT TOPOLOGY WITH THICK CLIENT FUNCTIONALITY

• US 20130179874A1
• Filed: 05/10/2012
• Published: 07/11/2013
• Est. Priority Date: 01/10/2012
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Aliminati, Janga
• Granted Patent: US 8,856,295 B2
• Time in Patent Office: Days
• US Class Current: 717/176
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 63/0209 Architectural arrangements, e.g. perimeter networks or demilitarized zones
• CPC Class Codes: H04L 63/0218 Distributed architectures, e.g. distributed firewalls
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

In accordance with an embodiment, one or more software application products, such as Oracle Fusion Applications, can be installed and/or configured according to an integration and deployment design/blueprint that is built or optimized for use within a multi-tiered deployment topology at an organization'"'"'s (i.e., customer'"'"'s) data center. Based on the customer site topology, provisioning of the software applications can be optimized; and application life cycle operations performed. This enables each product to be aware of the topology, which in turn provides customers with an “out-of-the-box” solution. The topology can also be optimized for security, performance and simplicity. In accordance with an embodiment, the deployment topology can include thick client functionality.

Claims

1. A system for providing an enterprise deployment topology, for use with applications such as Fusion Applications, comprising:

a data center having a plurality of application hosts and applications provided according to a deployment topology;

an administrative subnet at the data center for use by thick clients hosted within the data center;

wherein the applications at the data center can communicate with one another, within the data center, using HTTP and internal URLs, to process requests from the users; and

wherein the applications can also be accessed by users via virtual hosts and external URLs, wherein different portions or aspects of the functionality can be made available to Intranet-based users, and/or to Internet-based users, depending on the particular requirements of each application, and the particular needs of the enterprise.

2. The system of claim 1, wherein the administrative subnet is located within a DMZ-secured public zone or web tier of the data center, and includes one or more provider clients, and wherein a thick-client workstation, located outside of the data center, can access the administrative subnet via a VPN and socket connection, to communicate requests from the thick-client workstation to the application hosts and applications.

3. The system of claim 1, wherein the requests are communicated via the thick client or administrative subnet and forwarded to the application hosts using a variety of protocols such as HTTP, or ODBC, depending on the particular requirements of each application, and the particular needs of the enterprise.

4. A method of providing an enterprise deployment topology, for use with applications such as Fusion Applications, comprising the steps of:

providing at a data center a plurality of application hosts and applications according to a deployment topology;

providing an administrative subnet at the data center for use by thick clients hosted within the data center;

wherein the applications at the data center can communicate with one another, within the data center, using HTTP and internal URLs, to process requests from the users; and

wherein the applications can also be accessed by users via virtual hosts and external URLs, wherein different portions or aspects of the functionality can be made available to Intranet-based users, and/or to Internet-based users, depending on the particular requirements of each application, and the particular needs of the enterprise.

5. The method of claim 4, wherein the administrative subnet is located within a DMZ-secured public zone or web tier of the data center, and includes one or more provider clients, and wherein a thick-client workstation, located outside of the data center, can access the administrative subnet via a VPN and socket connection, to communicate requests from the thick-client workstation to the application hosts and applications.

6. The method of claim 4, wherein the requests are communicated via the thick client or administrative subnet and forwarded to the application hosts using a variety of protocols such as HTTP, or ODBC, depending on the particular requirements of each application, and the particular needs of the enterprise.

7. A non-transitory computer readable medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising:

providing at a data center a plurality of application hosts and applications according to a deployment topology;

providing an administrative subnet at the data center for use by thick clients hosted within the data center;

wherein the applications at the data center can communicate with one another, within the data center, using HTTP and internal URLs, to process requests from the users; and

wherein the applications can also be accessed by users via virtual hosts and external URLs, wherein different portions or aspects of the functionality can be made available to Intranet-based users, and/or to Internet-based users, depending on the particular requirements of each application, and the particular needs of the enterprise.

8. The non-transitory computer readable medium of claim 7, wherein the administrative subnet is located within a DMZ-secured public zone or web tier of the data center, and includes one or more provider clients, and wherein a thick-client workstation, located outside of the data center, can access the administrative subnet via a VPN and socket connection, to communicate requests from the thick-client workstation to the application hosts and applications.

9. The non-transitory computer readable medium of claim 7, wherein the requests are communicated via the thick client or administrative subnet and forwarded to the application hosts using a variety of protocols such as HTTP, or ODBC, depending on the particular requirements of each application, and the particular needs of the enterprise.