Simultaneous maintenance of multiple versions of a web-based business information system
First Claim
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 comprisesreceiving 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.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
21 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. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
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. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
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. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21)
-
Specification