>262 into the platform software 206 which is then capable of applying the isolation requirements 201 to a customer organization or tenant by provisioning the isolation requirements 201 as part of a unique customer organization's variant (e.g., the specific codebase unique to that customer organization). This is accomplished via platform software 206 applying an isolation layer 207 with the variously defined isolation features on top of a common base layer for the customer organization 208, so as to create a unique variant of the customer organization 209, also known as an “isolation edition.”

The unique variant of customer organization 209 is then deployed to a customer organization, also known as Tenant A 211, at cloud computing infrastructure 210. Thus, deploying platform software 206 to create a unique variant of customer organization 209 may be done via declarative programming, i.e. before a customer organization (“tenant”) is created. Thus, the platform software 206 may apply the isolation requirements 201 via the isolation layer 207 after a customer organization such as Tenant A 111 is created. In other words, platform software 206 does not need to be re-deployed each time a customer organization desires that isolation requirements 201 be applied to them.

Existing customer organizations such as Tenant C 213 desiring isolation requirements 201 to be applied to them may upgrade to unique variant of customer organization 209 via an upgrade path 214.

Thus, within cloud-computing infrastructure 210, there is a multi-tenant environment in which isolation requirements 201 are applied to certain tenants desiring isolation such as a new tenant, Tenant A 211, and an existing tenant, Tenant B 212. Thus, such tenants may cohabitate cloud-computing infrastructure 210 along with other tenant(s) such as Tenant C 213 that have no isolation requirements 201 applied to them. Tenants that choose to have isolation requirements 201 applied to them, for example Tenant A 211 and Tenant B 112, may also have different levels or types of isolation applied to them, as determined by their permissions. Thus, tenants with differing or the same isolation requirements 201 applied to them may also cohabitate cloud-computing infrastructure 210.

As a result, isolation is driven on a per-tenant basis instead of blanket parameters for one isolation environment. For example, pseudo code that applies blanket parameters for isolation may perform the following function:

if(Environment.isIsolated( ) )

{

dontShowLink( ) ;

} else {

showLink( );

}

In contrast, per-tenant isolation pseudo code drives isolation on a per-tenant basis while still using the same pseudo code across different versions of a program. For example:

if(Tenant.shouldShowLinkedIn( ) )

{

showLink( ) ;

} else {

dontShowLink( ) ;

}

While the subject matter disclosed herein has been described by way of example and in terms of the specific embodiments, it is to be understood that the claimed embodiments are not limited to the explicitly enumerated embodiments disclosed. To the contrary, the disclosure is intended to cover various modifications and similar arrangements as are apparent to those skilled in the art. Therefore, the scope of the appended claims are to be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. It is to be understood that the above description is intended to be illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reading and understanding the above description. The scope of the disclosed subject matter is therefore to be determined in reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

FIG. 3 depicts another exemplary architecture 300 in accordance with described embodiments.

As shown here, there is a GUI 310 executing at a computing device 399, such as a user device of the system administrator, with the GUI 310 being pushed to the computing device 300 by the isolation requirements mapper 180 of the host organization 110 (see FIG. 1).

As shown here, the system administrator 391 may create a new customer organization 395 and view the isolation group or a system administrator 391 may alternatively load an existing customer organization and view the existing isolation group via the GUI 310 within the Customer Org Isolation requirements definition interface 382.

As shown here, via GUI 310, the administrator has selected isolation requirements 393 to be applied to the customer organization, for instance, shown here selecting Data Export Control. Other isolation requirements may be applied, such as air-gap network controls, content compliance controls, or custom defined and configured controls. Further depicted is the ability to specify which call-out function or functions are to be applied 394. As shown, a per-country or country specific call-out function is selected. Still further depicted is the ability to indicate whether or not government approval is required 392, for instance, such as whether or not it is permissible to alter the settings or whether or not application or removal of isolation requirements requires governmental approval or if merely self-regulated compliance is sufficient.

According to a particular embodiment, displaying the GUI interface to the user device is achieved by executing instructions stored in the memory of a system via the processor, in which the instructions cause the system to transmit the GUI interface from a receive interface of the system to a user device communicably interfaced with the system over the network. Further operations may include receiving the input at the system from the GUI interface.

Once the input is received by the host organization or at the platform, it may be persistently stored via the multi-tenant database system for later reference and retrieval.

According to a particular embodiment, a system of the host organization implements a cloud computing platform providing on-demand cloud computing services on accessible to subscribers of the cloud computing platform and each of the customer organizations for which a unique variant (e.g., a unique codebase having the relevant isolation requirements encoded therein) corresponds to one of a plurality of customer organizations having subscriber access to the on-demand cloud computing services provided by the cloud computing platform.

FIG. 4 depicts a flow diagram illustrating a method 400 for implementing pre-configured pre-tenant isolation in a multi-tenant cloud based computing environment such as a database system implementation supported by a processor and a memory to execute such functionality to provide cloud based on-demand functionality to users, customers, and subscribers.

Method 400 may be performed by processing logic that may include hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions run on a processing device) to perform various operations such as operating, defining, declaring, associating, writing, receiving, retrieving, adding, transacting, training, distributing, processing, transmitting, analyzing, triggering, pushing, recommending, parsing, persisting, exposing, loading, generating, storing, maintaining, creating, returning, presenting, interfacing, communicating, querying, providing, determining, displaying, updating, sending, etc., in pursuance of the systems and methods as described herein. For example, the hosted computing environment 111, the isolation requirements mapped 180, and its database system 130 as depicted at FIG. 1, et seq., and other systems and components as described herein may implement the described methodologies. Some of the blocks and/or operations listed below are optional in accordance with certain embodiments. The numbering of the blocks presented is for the sake of clarity and is not intended to prescribe an order of operations in which the various blocks must occur.

With reference to the method 400 depicted at FIG. 4, the method begins at block 405, where processing logic creates an isolation group. According to such an embodiment, the creation of an isolation group includes the following:

At block 410, processing logic defines isolation requirements, identifying a group of features utilizing call-out functions, and selecting from among the group of features utilizing call-out functions a group of features having the defined isolation requirements.

At block 415, processing logic deploys platform software integrating the isolation requirements, wherein the platform software contains instructions to map the isolation requirements to a customer organization.

At block 420, processing logic creates the customer organization.

At block 425, processing logic creates a unique variant of the customer organization, where creating the unique variant of the customer organization includes declaratively applying an isolation layer specifying isolation requirements on top of a base layer for the customer organization.

At block 430, processing logic deploys the unique variant of the customer organization onto the customer organization's cloud computing infrastructure, wherein the unique variant validates per-tenant distinctions for various applications subjected to the isolation requirements.

According to another embodiment, method 400 further includes: receiving a request at the platform to apply an optionally specified tagging isolation feature; and in which the tagging isolation feature, when applied, forces the platform to trigger a call-out function for review and possible inclusion within a call-out isolation group.

According to another embodiment of method 400, the platform to trigger a call-out function for review and possible inclusion includes the platform automatically sending a message to a development group or systems administrator group for the platform with a request to review the call-out function for review and to make a determination whether or not to include the call-out function as a new isolation feature for one or more customer organizations utilizing the platform by configuring the respective unique variant for the one or more customer organizations to have the new isolation feature.

According to another embodiment, method 400 further includes: defining the isolation requirements to associate each customer organization with multiple different and distinct unique variants on a per-country basis; in which each of the multiple different and distinct unique variants include the defined isolation requirements as specified on the per-country basis; and in which the defined isolation requirements for the isolation group are determined and applied for each customer organization on the basis of data being transmitted into a country or jurisdiction from the platform or on the basis of data being received at the platform from a country or jurisdiction corresponding to the per-country defined one of the multiple different and distinct unique variants.

According to another embodiment, method 400 further includes: testing the call-out functions by simulating interactions with the platform utilizing the customer organization created to generate simulated output in compliance with the defined isolation requirements for the customer organization created; validating the call-out functions by comparing the simulated output with the defined isolation requirements; and returning a testing result by sending a message to a development group or systems administrator group for the platform with the testing result and with the simulated output.

According to another embodiment, method 400 further includes: validating all call-out functions defined for a customer organization pursuant to the isolation requirements are referenceable and correspond to one or more defined mappings to the isolation group created; and validating the platform software to be deployed includes source code declaratively linking each available isolation group with a corresponding isolation group definition specifying the group of features utilizing the call-out functions.

According to another embodiment, method 400 further includes: creating a new customer organization and specifying the isolation layer for the new customer organization; and inheriting the defined isolation requirements into the new customer organization created to create the unique variant of the customer organization while maintaining an existing upgrade path for the customer organization within the unique variant created.

According to another embodiment of method 400, deploying the unique variant of the customer organization onto the customer organization's cloud computing infrastructure, includes: provisioning the unique variant of the customer organization with functionality specific to the unique variant of the customer organization by incorporating into the unique variant of the customer organization all applications associated with the customer organization with the defined isolation requirements layered on top of the applications incorporated into the unique variant of the customer organization; in which deployment of each application incorporated into the unique variant of the customer organization is multi-tenant aware due to being uniquely tied to the unique variant of the customer organization; in which a first instance of a common application provisioned for a first customer organization co-exists within a compute pod with a second instance of the common application provisioned for a second customer organization within the compute pod, in which the first and the second instance of the common application share an identical base source code via the common application; and in which the first instance and the second instance of the common application operate distinctly within the compute pod on behalf of each of the first and the second customer organizations due to distinct isolation requirements defined for each of the first and the second customer organizations and applied to the identical base source code at the time of provisioning for each of the first and the second customer organization.

According to another embodiment of method 400, the customer organization is an existing customer organization, in which creating the unique variant of the customer organization involves an upgrade path to apply the isolation layer.

According to another embodiment of method 400, the cloud computing infrastructure is a multi-tenant organization environment, in which deploying the unique variant of the customer organization discriminates on a per-tenant basis based on the isolation requirements applied to the unique variant of the customer organization.

According to another embodiment of method 400, the isolation group is created based on an isolation.yaml file; and in which a plurality of isolation groups are created and deployed to the platform software utilizing the isolation.yaml file.

According to another embodiment of method 400, the isolation requirements are validated with the customer organization and its unique variant before deploying the unique variant of the customer organization onto the customer organization's cloud computing infrastructure.

According to another embodiment of method 400, declaratively applying the isolation layer specifying isolation requirements on top of a base layer for the customer organization includes: configuring the unique variant of the customer organization to operate within an air-gap network at the request of that customer organization; and in which the customer organization's cloud computing infrastructure air-gap network is not communicably interfaced with any other customer organization's computing infrastructure utilizing the platform via either wired or wireless communication interfaces.

According to another embodiment of method 400, declaratively applying the isolation layer specifying isolation requirements on top of a base layer for the customer organization includes: configuring the unique variant of the customer organization to transmit all data being transmitted to a different country or jurisdiction from that within which the platform operates through a data export filter prior to transmission to the different country or jurisdiction.

According to another embodiment of method 400, the data export filter operates in accordance with data export regulations as specified by the country or jurisdiction within which the platform operates.

According to another embodiment of method 400, a workflow governance is produced that specifies all changes between the customer organization and its unique variant based on the isolation requirements.

According to another embodiment of method 400, the system implements a cloud computing platform to provide on-demand cloud based computing services to subscribers of the cloud computing platform; and in which end users of the cloud computing platform are each associated with one of the plurality of customer organizations having subscriber access to the on-demand cloud based computing services provided by the cloud computing platform.

In accordance with a particular embodiment, there is a non-transitory computer-readable storage medium having instructions stored thereupon that, when executed by a processor of a system having at least a processor and a memory therein, the instructions cause the system to perform operations including: creating an isolation group, in which creating the isolation group includes: defining isolation requirements, identifying a group of features utilizing call-out functions, and selecting from among the group of features utilizing call-out functions a group of features having the defined isolation requirements; deploying platform software integrating the isolation requirements, in which the platform software contains instructions to map the isolation requirements to a customer organization; creating the customer organization; creating a unique variant of the customer organization, in which creating the unique variant of the customer organization includes declaratively applying an isolation layer specifying isolation requirements on top of a base layer for the customer organization; and deploying the unique variant of the customer organization onto the customer organization's cloud computing infrastructure, in which the unique variant validates per-tenant distinctions for various applications subjected to the isolation requirements.

FIG. 5 shows a diagrammatic representation of a system 501 within which embodiments may operate, be installed, integrated, or configured. In accordance with one embodiment, there is a system 501 having at least a processor 590 and a memory 595 therein to execute implementing application code for the methodologies as described herein. Such a system 501 may communicatively interface with and cooperatively execute with the benefit of a hosted computing environment, such as a host organization, a multi-tenant environment, an on-demand service provider, a cloud based service provider, a client-server environment, etc.

According to the depicted embodiment, system 501, which may operate within a host organization, includes the processor 590 and the memory 595 to execute instructions at the system 501. According to such an embodiment, system 501 further includes a non-transitory machine-readable storage medium that provides instructions that, when executed by the set of one or more processors 590, the instructions stored in the memory 595 are configurable to cause the system 501 to perform operations including: creating an isolation group (e.g., on the basis of isolation requirements 541 received via the GUI 540 or on the basis of export compliance regulations 589 provided by the access to the external export control 599 entities, or on the basis of the third party provided filters 586, etc). According to such an embodiment, creating the isolation group includes: defining isolation requirements 541, identifying a group of features utilizing call-out functions, and selecting from among the group of features utilizing call-out functions a group of features having the defined isolation requirements; deploying platform software integrating the isolation requirements, for instance, with the deployment or provisioning being done via the deployment interface 543. With such an embodiment, the platform software contains instructions to map the isolation requirements to a customer organization and the system 501 then creates the customer organization, pursuant to which application of the isolation requirements enables the creation of the unique variant 539 of the customer organization, and further in which creating the unique variant of the customer organization includes declaratively applying an isolation layer specifying isolation requirements 541 on top of a base layer for the customer organization. Still further, the system 501 deploys the unique variant 539 of the customer organization onto the customer organization's cloud computing infrastructure, in which the unique variant validates per-tenant distinctions for various applications subjected to the isolation requirements.

A receive interface 526 of the system 501 is to receive the isolation requirements 541 according to certain embodiments.

Bus 555 interfaces the various components of the system 501 amongst each other, with any other peripheral(s) of the system 501, and with external components such as external network elements, other machines, client devices, cloud computing services, etc. Communications may further include communicating with external devices via a network interface over a LAN, WAN, or the public Internet. Authenticator 550 provides authentication services for users seeking access to the database systems 546, clouds, and other services of the host organization.

FIG. 6 illustrates a diagrammatic representation of a machine 600 in the exemplary form of a computer system, in accordance with one embodiment, within which a set of instructions, for causing the machine/computer system 600 to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments, the machine may be connected (e.g., networked) to other machines in a Local Area Network (LAN), an intranet, an extranet, or the public Internet. The machine may operate in the capacity of a server or a client machine in a client-server network environment, as a peer machine in a peer-to-peer (or distributed) network environment, as a server or series of servers within an on-demand service environment. Certain embodiments of the machine may be in the form of a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, switch or bridge, computing system, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines (e.g., computers) that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The exemplary computer system 600 includes a processor 602, a main memory 604 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc., static memory such as flash memory, static random access memory (SRAM), volatile but high-data rate RAM, etc.), and a secondary memory 618 (e.g., a persistent storage device including hard disk drives and a persistent database and/or a multi-tenant database implementation), which communicate with each other via a bus 630. Main memory 604 includes a scheduling service 624 and a mapper 625 and isolation filter engine(s) 623 by which to communicate with customer organizations desiring isolation, including retrieving and applying an isolation layer to create a unique variant of the customer organization, in accordance with described embodiments. Main memory 604 and its sub-elements are operable in conjunction with processing logic 626 and processor 602 to perform the methodologies discussed herein. Main memory 604 and its sub-elements are operable in conjunction with processing logic 626 and processor 602 to perform the methodologies discussed herein.

Processor 602 represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processor 602 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 602 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. Processor 602 is configured to execute the processing logic 626 for performing the operations and functionality which is discussed herein.

The computer system 600 may further include a network interface card 608. The computer system 600 also may include a user interface 610 (such as a video display unit, a liquid crystal display, etc.), an alphanumeric input device 612 (e.g., a keyboard), a cursor control device 614 (e.g., a mouse), and a signal generation device 616 (e.g., an integrated speaker). The computer system 600 may further include peripheral device 636 (e.g., wireless or wired communication devices, memory devices, storage devices, audio processing devices, video processing devices, etc.).

The secondary memory 618 may include a non-transitory machine-readable storage medium or a non-transitory computer readable storage medium or a non-transitory machine-accessible storage medium 631 on which is stored one or more sets of instructions (e.g., software 622) embodying any one or more of the methodologies or functions described herein. The software 622 may also reside, completely or at least partially, within the main memory 604 and/or within the processor 602 during execution thereof by the computer system 600, the main memory 604 and the processor 602 also constituting machine-readable storage media. The software 622 may further be transmitted or received over a network 620 via the network interface card 608.

FIG. 7A illustrates a block diagram of an environment 798 in which an on-demand database service may operate in accordance with the described embodiments. Environment 798 may include user systems 712, network 714, system 716, processor system 717, application platform 718, network interface 720, tenant data storage 722, system data storage 724, program code 726, and process space 728. In other embodiments, environment 798 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above.

Environment 798 is an environment in which an on-demand database service exists. User system 712 may be any machine or system that is used by a user to access a database user system. For example, any of user systems 712 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in FIG. 7A (and in more detail in FIG. 7B) user systems 712 might interact via a network 714 with an on-demand database service, which is system 716.

An on-demand database service, such as system 716, is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users). Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, “on-demand database service 716” and “system 716” is used interchangeably herein. A database image may include one or more database objects. A relational database management system (RDMS) or the equivalent may execute storage and retrieval of information against the database object(s). Application platform 718 may be a framework that allows the applications of system 716 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, on-demand database service 716 may include an application platform 718 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 712, or third party application developers accessing the on-demand database service via user systems 712.

The users of user systems 712 may differ in their respective capacities, and the capacity of a particular user system 712 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 712 to interact with system 716, that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 716, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.

Network 714 is any network or combination of networks of devices that communicate with one another. For example, network 714 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it is understood that the networks that the claimed embodiments may utilize are not so limited, although TCP/IP is a frequently implemented protocol.

User systems 712 might communicate with system 716 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 712 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at system 716. Such an HTTP server might be implemented as the sole network interface between system 716 and network 714, but other techniques might be used as well or instead. In some implementations, the interface between system 716 and network 714 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.

In one embodiment, system 716, shown in FIG. 7A, implements a web-based customer relationship management (CRM) system. For example, in one embodiment, system 716 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, webpages and other information to and from user systems 712 and to store to, and retrieve from, a database system related data, objects, and Webpage content. With a multi-tenant system, data for multiple tenants may be stored in the same physical database object, however, tenant data typically is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared. In certain embodiments, system 716 implements applications other than, or in addition to, a CRM application. For example, system 716 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by the application platform 718, which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 716.

One arrangement for elements of system 716 is shown in FIG. 7A, including a network interface 720, application platform 718, tenant data storage 722 for tenant data 723, system data storage 724 for system data 725 accessible to system 716 and possibly multiple tenants, program code 726 for implementing various functions of system 716, and a process space 728 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 716 include database indexing processes.

Several elements in the system shown in FIG. 7A include conventional, well-known elements that are explained only briefly here. For example, each user system 712 may include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. User system 712 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, a Mozilla or Firefox browser, an Opera, or a WAP-enabled browser in the case of a smartphone, tablet, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 712 to access, process and view information, pages and applications available to it from system 716 over network 714. Each user system 712 also typically includes one or more user interface devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a graphical user interface (GUI) provided by the browser on a display (e.g., a monitor screen, LCD display, etc.) in conjunction with pages, forms, applications and other information provided by system 716 or other systems or servers. For example, the user interface device can be used to access data and applications hosted by system 716, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user. As discussed above, embodiments are suitable for use with the Internet, which refers to a specific global internetwork of networks. However, it is understood that other networks can be used instead of the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 712 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 716 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such as processor system 717, which may include an Intel Pentium® processor or the like, and/or multiple processor units.

According to one embodiment, each system 716 is configured to provide webpages, forms, applications, data and media content to user (client) systems 712 to support the access by user systems 712 as tenants of system