Simultaneous maintenance of multiple versions of a web-based business information system

• US 9,009,313 B2
• Filed: 06/10/2013
• Issued: 04/14/2015
• Est. Priority Date: 07/12/2004
• Status: Active Grant

• Current Assignee: NetSuite Inc. (Oracle Corporation)
• Original Assignee: NetSuite Inc. (Oracle Corporation)
• Inventors: Rice, Theodore R., Rolls, Steven Ellis, Marenbach, Christian
• Primary Examiner(s): Lazaro, David
• Assistant Examiner(s): HENRY, MARIEGEORGES A
• Application Number:
  US13/914,019
• Publication Number:
  US 20140067780A1
• Time in Patent Office: 673 Days
• Field of Search: 709/225, 709/219, 717/170
• US Class Current: 709/225
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

A method, system, computer program product, and related business methods for phased rollout of an upgraded version of a web-based business information system are described. URLs associated with client requests remain the same even where the target subscriber accounts have been upgraded. Client requests for both upgraded and non-upgraded accounts are received by a common set of web servers. Client requests representing external entry points are trapped, and the receiving web server accesses a login router database to determine whether the target subscriber account is upgraded or non-upgraded, and then transfers the request to an appropriately-versioned application server. Application server sets are mapped to database sets according to system version, allowing the upgraded system database schema to be substantially different than the non-upgraded database schema. An early adopter program business method leveraging the abilities of such web-based business information system is also described. Applications to environments other than phased rollout are described, such as URL-agnostic differentiation and routing of client requests according to class-of-service of the target subscribing account.

Claims

1. A method for processing a client request in a web-based business information system, the web-based business information system being in a state of phased rollout from a current version to a newer version, the web-based business information system maintaining both upgraded and non-upgraded client accounts during the phased rollout, wherein the method comprises

receiving a client request at a server;

processing the client request to determine an identity of the client;

based on the identity of the client, determining a correct data center for servicing the request;

determining if the request was received at the correct data center for servicing the request;

if the request was not received at the correct data center, then modifying a destination address of the request to include an identifier for the correct data center;

processing the request at the correct data center to determine an application version for servicing the request, wherein determining an application version for servicing the request includes determining whether the client request is associated with a non-upgraded account or an upgraded account;

sending the client request to one of a first set of application servers at the correct data center if the client request is associated with a non-upgraded account, the first set of application servers configured to process client requests according to the current version of the web-based business information system; and

sending the client request to one of a second set of application servers at the correct data center if the client request is associated with an upgraded account, the second set of application servers configured to process client requests according to the newer version of the web-based business information system.

2. The method of claim 1, further comprising, sending the client request to one of the first or second sets of application servers based on a cookie or cookie-like data item accompanying the client request if processing the received request at the correct data center to determine an application version for servicing the request is not successful.

3. The method of claim 1, wherein processing the client request to determine an identity of the client further comprises comparing one or more parameters accompanying the client request to information contained in a database.

4. The method of claim 1, wherein processing the received request at the correct data center to determine an application version for servicing the request-further comprises processing the request to determine whether the client is associated with an upgraded or a non-upgraded account.

5. The method of claim 1, wherein the web-based business information system further comprises a plurality of databases, with each client account having its business data stored in a single one of the databases, the plurality of databases including a first database set associated with the first set of application servers, and including a second database set associated with the second set of application servers.

6. The method of claim 1, further comprising:

processing the request to create a response; and

providing the response to the client.

7. The method of claim 1, wherein modifying a destination address of the request to include an identifier for the correct data center further comprises modifying a URL to include the identifier for the correct data center.

8. A computer-implemented method of maintaining a plurality of versions of a web-based business information system, comprising:

identifying a set of subscriber accounts to be migrated from a first of the plurality of versions to a second of the plurality of versions, the first of the plurality of versions associated with a first database schema distinct from a second database schema associated with the second of the plurality of versions;

migrating data associated with the set of subscriber accounts from the first database schema to the second database schema, the first database schema maintained by a first set of database servers distinct from a second set of database servers maintaining the second database schema;

receiving a client request associated with a uniform resource locator and a set of parameters;

processing the client request to determine an identity of the client;

based on the identity of the client, determining a correct data center for servicing the request;

determining if the request was received at the correct data center for servicing the request;

if the request was not received at the correct data center, then modifying a destination address of the request to include an identifier for the correct data center;

processing the client request at the correct data center to determine an application version for servicing the request;

determining that the client request is associated with at least one of the set of migrated subscriber accounts by comparing one or more of the uniform resource locator and the set of parameters associated with the client request to information contained in a database; and

forwarding the client request to a set of application servers configured at least to process the client request in accordance with the second database schema.

9. The computer-implemented method of claim 8, wherein the client request specifies at least a portion of the uniform resource locator and the set of parameters.

10. The computer-implemented method of claim 8, wherein the set of parameters does not include a password.

11. The computer-implemented method of claim 8, wherein modifying a destination address of the request to include an identifier for the correct data center further comprises modifying a URL to include the identifier for the correct data center.

12. The computer-implemented method of claim 8, further comprising:

processing the request to create a response; and

providing the response to the client.

13. The computer-implemented method of claim 8, wherein the set of application servers configured at least to process the client request in accordance with the second database schema are configured to execute a set of business applications that include one or more of an [ERP] enterprise resource planning application and a [CRM] customer relationship management application.

14. A system for maintaining a plurality of versions of a web-based business information system, comprising:

a first data center with an associated set of application servers configured to execute a set of business applications;

a second data center with an associated set of application servers configured to execute a set of business applications;

a first server located in the first data center, the first server configured to receive a request from a client and to execute a process to;

process the request to determine an identity of the client;

based on the identity of the client, determine a correct data center for servicing the request;

determine if the request was received at the correct data center for servicing the request; and

if the request was not received at the correct data center, then modify a destination address of the request to include an identifier for the correct data center; and

a first database located in the first data center, the first database including data associating the client with the correct data center for servicing a request from the client.

15. The system of claim 14, further comprising:

a second server located in the second data center, the second server configured to receive a request from a client and to execute a process to;

process the request to determine an identity of the client;

based on the identity of the client, determine a correct data center for servicing the request;

determine if the request was received at the correct data center for servicing the request; and

if the request was not received at the correct data center, then modify a destination address of the request to include an identifier for the correct data center; and

a second database located in the second data center, the second database including data associating the client with the correct data center for servicing a request from the client.

16. The system of claim 15, wherein the first server located in the first data center and the second server located in the second data center that are configured to receive a request from a client and if the request was not received at the correct data center, then to execute a process to modify a destination address of the request to include an identifier for the correct data center, are further configured to modify a URL to include the identifier for the correct data center.

17. The system of claim 14, wherein the set of application servers associated with the first data center are configured to execute a set of business applications that include one or more of an [ERP] enterprise resource planning application and a [CRM] customer relationship management application.

18. The system of claim 14, wherein the set of application servers associated with the second data center are configured to execute a set of business applications that include one or more of an [ERP] enterprise resource planning application and a [CRM] customer relationship management application.

19. The system of claim 14, wherein the set of application servers associated with the first data center are configured to execute a first and a second version of one of the set of business applications, and further, wherein the first data center includes a server configured to:

process the request to determine an application version for servicing the request; and

based on the determined application version for servicing the request, route the request to either a server in the first data center executing the first version of the application or to a server in the first data center executing a second version of the application.

20. The system of claim 19, wherein the server in the first data center executing the first version of the application or the server in the first data center executing a second version of the application is further configured to:

process the request to create a response; and

provide the response to the client.

21. The system of claim 14, wherein the first server located in the first data center [and the second server located in the second data center that are] that is configured to receive a request from a client and if the request was not received at the correct data center, then to execute a process to modify a destination address of the request to include an identifier for the correct data center, [are] is further configured to modify a URL to include the identifier for the correct data center.