Methods for adaptive organization of web application access points in webtops and devices thereof

Description

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 62/279,439, filed on Jan. 15, 2016, which is hereby incorporated by reference in its entirety.

FIELD

This technology generally relates to enterprise networks, and more particularly to methods and devices for adaptive presentation of web applications.

BACKGROUND

Increasingly, enterprises are supporting “bring your own device” (BYOD) policies for employees whereby the employees use their personal devices to connect to enterprise networks. By connecting to an enterprise network, employees can receive a desktop environment embedded in a web browser or client application executed by their personal devices, which is referred to herein as a webtop, that facilitates access to allowed enterprise web applications.

Secure access systems, referred to herein as access policy management (APM) apparatuses, regulate access to enterprise networks and associated web applications hosted by enterprise web application servers. Accordingly, APM apparatuses store access policies and evaluate the access policies in response to employee login requests in order to identify the allowed enterprise web applications to include with generated and provided webtops.

In some network environments, the number of allowed enterprise web applications can be relatively large resulting in employee difficulty locating access points (e.g., icons or links) for desired enterprise web applications, particularly on mobile devices with relatively small screens. Accordingly, locating enterprise web applications on webtops is currently inefficient and results in reduced productivity for users.

SUMMARY

A method for adaptive presentation of web applications includes identifying, by an access policy management (APM) apparatus, a plurality of web applications that are allowed for a user of a client device. A subset of the allowed web applications the user is likely to use is determined, by the APM apparatus based on stored historical application access pattern data. A webtop comprising access points for the allowed web applications is provided by the APM apparatus. The access points are organized based on the subset of the allowed web applications for presentation to the user on the client device.

An APM apparatus includes memory including programmed instructions stored in the memory and one or more processors configured to be capable of executing the programmed instructions stored in the memory to identify a plurality of web applications that are allowed for a user of a client device. A subset of the allowed web applications the user is likely to use is determined based on stored historical application access pattern data. A webtop comprising access points for the allowed web applications is provided. The access points are organized based on the subset of the allowed web applications for presentation to the user on the client device.

A non-transitory computer readable medium having stored thereon instructions for adaptive presentation of web applications includes executable code which when executed by one or more processors, causes the one or more processors to perform steps comprising identifying a plurality of web applications that are allowed for a user of a client device. A subset of the allowed web applications the user is likely to use is determined based on stored historical application access pattern data. A webtop comprising access points for the allowed web applications is provided. The access points are organized based on the subset of the allowed web applications for presentation to the user on the client device.

This technology has a number of associated advantages including methods, non-transitory computer readable media, and APM apparatuses that more effectively present web application in webtops, thereby facilitating more efficient access to the web application by users of client device, including enterprise network users. This technology advantageously provides a webtop with access points for web applications that are organized based on historical application access pattern data and an analysis of web applications most likely to be accessed by a user in a current session. Accordingly, this technology facilitates adaptive webtops that reduce the amount of time required to locate access points for web applications and improve user productivity.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram of a network environment with an exemplary access policy management (APM) apparatus;

FIG. 2 is a block diagram of the exemplary APM apparatus shown in FIG. 1;

FIG. 3 is a flowchart of an exemplary method for adaptive presentation of web applications;

FIG. 4 is a block diagram of an exemplary application of an access policy to identify allowed web applications for a user; and

FIG. 5 is a timing diagram of an exemplary method for adaptive presentation of web applications.

DETAILED DESCRIPTION

Referring to FIG. 1, an exemplary network environment 10 which incorporates an exemplary access policy management (APM) apparatus 12 is illustrated. The APM apparatus 12 is coupled to a plurality of web application servers 14(1)-14(m) and a plurality of client devices 16(1)-16(n) via communication network(s) 18, although the APM apparatus 12, web application servers 14(1)-14(m), and client devices 16(1)-16(n) may be coupled together via other topologies. Additionally, the network environment 10 may include other network devices such as one or more routers and/or switches, for example, which are well known in the art and thus will not be described herein. This technology provides a number of advantages including methods, non-transitory computer readable media, and APM apparatuses that advantageously adapt the presentation of web application access points in webtops based on access patterns, thereby facilitating more efficient access to web applications for users.

Referring to FIGS. 1-2, the APM apparatus 12 may perform any number of functions including enforcing access policies and providing secure access to backend enterprise web applications hosted by the web application servers 14(1)-14(m) for users of the client devices 16(1)-16(n), managing network traffic, load balancing network traffic across the web application servers 14(1)-14(m), or providing security or firewall services, for example. The APM apparatus 12 includes one or more processor(s) 20, a memory 22, and a communication interface 24, which are coupled together by a bus 26 or other communication link, although the APM apparatus 12 may include other types and numbers of elements in other configurations.

The processor(s) 20 of the APM apparatus may execute programmed instructions stored in the memory 22 of the APM apparatus 12 for the any number of the functions identified above. The processor(s) 20 of the APM apparatus 12 may include one or more CPUs or general purpose processors with one or more processing cores, for example, although other types of processor(s) can also be used.

The memory 22 of the APM apparatus 12 stores these programmed instructions for one or more aspects of the present technology as described and illustrated herein, although some or all of the programmed instructions could be stored and executed elsewhere. A variety of different types of memory storage devices, such as random access memory (RAM), read only memory (ROM), hard disk, solid state drives, flash memory, or other computer readable medium which is read from and written to by a magnetic, optical, or other reading and writing system that is coupled to the processor(s) 20, can be used for the memory 22.

Accordingly, the memory of the APM apparatus 12 can store one or more applications that can include computer executable instructions that, when executed by the APM apparatus 12, cause the APM apparatus 12 to perform actions, such as to transmit, receive, or otherwise process messages, for example, and to perform other actions described and illustrated below with reference to FIGS. 3-5. The application(s) can be implemented as module or components of another application. Further, the application(s) can be implemented as operating system extensions, module, plugins, or the like.

Even further, the application(s) may be operative in a cloud-based computing environment. The application(s) can be executed within or as virtual machine(s) or virtual server(s) that may be managed in a cloud-based computing environment. Also, the application(s), including the APM apparatus 12 itself, may be located in virtual server(s) running in a cloud-based computing environment rather than being tied to one or more specific physical network computing devices. Also, the application(s) may be running in one or more virtual machines (VMs) executing on the APM apparatus 12. Additionally, in at least one of the various embodiments, virtual machine(s) running on the APM apparatus 12 may be managed or supervised by a hypervisor.

In this particular example, the memory 22 includes an application access pattern database 28 and access policies 30. The access policies 30 in this example are established by an administrator and enforced by the APM apparatus 12 to restrict access by users of the client devices 16(1)-16(n) to allowed backend enterprise web applications hosted by the web application servers 14(1)-14(m).

The application access pattern database 30 in this example stores historical application access pattern data including web application usage data correlated with temporal, user, and/or client device data for a plurality of users of the client devices 16(1)-16(n). The application access pattern database 30 facilitates identification of a subset of allowed web applications for a user upon which access points in a webtop generated for the user are organized. In one example, current temporal, user, and/or client device data for a user can be correlated with historical access pattern date for the user or a group of users sharing one or more characteristics in order to identify the subset of allowed web applications, as described and illustrated in more detail later.

The communication interface 24 operatively couples and communicates between the APM apparatus 12, the web application servers 14(1)-14(m), and the client devices 16(1)-16(n), which are all coupled together by the communication network(s) 18, although other types and numbers of communication networks or systems with other types and numbers of connections and configurations to other devices and elements can also be used.

By way of example only, the communication network(s) 18 can include local area network(s) (LAN(s)) or wide area network(s) (WAN(s)), and can use TCP/IP over Ethernet and industry-standard protocols, although other types and numbers of protocols and/or communication networks can be used. The communication network(s) 18 in this example may employ any suitable interface mechanisms and network communication technologies including, for example, teletraffic in any suitable form (e.g., voice, modem, and the like), Public Switched Telephone Network (PSTNs), Ethernet-based Packet Data Networks (PDNs), combinations thereof, and the like.

The communication network(s) 18 can also include direct connection(s) (e.g., for when a device illustrated in FIG. 1, such as the APM apparatus 12, client devices 16(1)-16(n), or web application servers 14(1)-14(m), for example, operate as virtual instances on the same physical machine). In some examples, the communication network(s) 18 can be the Internet, although other types of networks can also be included in the network environment 10.

While the APM apparatus 12 is illustrated in this example as including a single device, the APM apparatus 12 in other examples can include a plurality of devices or blades each with one or more processors (each processor with one or more processing cores) that implement one or more steps of this technology. In these examples, one or more of the devices can have a dedicated communication interface or memory. Alternatively, one or more of the devices can utilize the memory, communication interface, or other hardware or software components of one or more other devices.

Additionally, one or more of the devices that together comprise the APM apparatus 12 in other examples can be standalone devices or integrated with one or more other devices or applications, such as one of the web application servers 14(1)-14(m) or a network traffic management device coupled to the communication network(s), for example. Moreover, one or more of the devices of the APM apparatus 12 in these examples can be in a same or a different communication network including one or more public, private, or cloud networks, for example.

Each of the web application servers 14(1)-14(m) includes a processor, a memory, and a communication interface, which are coupled together by a bus or other communication link, although other numbers and types of network devices could be used. The web application servers 14(1)-14(m) in this example process requests received from the client devices via the communication network(s) 18 according to the HTTP-based application RFC protocol, for example. Various backend enterprise web applications may be operating on the web application servers 14(1)-14(m) and transmitting data (e.g., files or Web pages) to the client devices 16(1)-16(n) via the APM apparatus 12 in response to requests from the client devices 16(1)-16(n). The web application servers 14(1)-14(m) may be hardware or software or may represent a system with multiple servers in a pool, which may include internal or external networks.

Although the web applications servers 14(1)-14(m) are illustrated as single web application servers, one or more actions of one or more of the web application servers 14(1)-14(m) may be distributed across one or more distinct network computing devices. Moreover, the web application servers 14(1)-14(m) are not limited to a particular configuration. Thus, the web application servers 14(1)-14(m) may contain a plurality of network computing devices that operate using a master/slave approach, whereby one of the network computing devices of the web application servers 14(1)-14(m) operate to manage and/or otherwise coordinate operations of the other network computing devices. The web application servers 14(1)-14(m) may operate as a plurality of network computing devices within a cluster architecture, a peer-to peer architecture, virtual machines, or within a cloud architecture.

Thus, the technology disclosed herein is not to be construed as being limited to a single environment and other configurations and architectures are also envisaged. For example, one or more of the web application servers 14(1)-14(m) depicted in FIG. 1 can operate within the APM apparatus 12 itself rather than as a stand-alone web application server communicating with the APM apparatus 12 via the communication network(s) 18. In this example the one or more web application servers 14(1)-14(m) operate within the memory 22 of the APM apparatus 12.

The client devices 16(1)-16(n) can include any type of computing device that can receive, render, and facilitate user interaction with a webtop, such as mobile computing devices, desktop computing devices, laptop computing devices, tablet computing devices, virtual machines (including cloud-based computer), or the like. Each of the client devices 16(1)-16(n) in this example includes a processor, a memory, and a communication interface, which are coupled together by a bus or other communication link, although other numbers and types of network devices could be used.

The client devices 16(1)-16(n) may run interface applications, such as standard Web browsers or standalone client applications, which may provide an interface to make requests for, and receive content stored on, one or more of the web application servers 14(1)-14(m) via the communication network(s) 18. In particular, the Web browsers of the client devices 16(1)-16(n), or standalone client applications executing on the client devices 16(1)-16(n), can render a webtop provided by the APM apparatus 12 that provides access points to web applications hosted on the web application servers 14(1)-14(m). The client devices 16(1)-16(n) may further include a display device, such as a display screen or touchscreen, and/or an input device, such as a keyboard for example. The client devices 16(1)-16(n) could be implemented as applications on the APM apparatus 12 itself in some examples.

Although the exemplary network environment 10 with the APM apparatus 12, web application servers 14(1)-14(m), client devices 16(1)-16(n), and communication network(s) 18 are described and illustrated herein, other types and numbers of systems, devices, components, and elements in other topologies can be used. It is to be understood that the systems of the examples described herein are for exemplary purposes, as many variations of the specific hardware and software used to implement the examples are possible, as will be appreciated by those skilled in the relevant art(s).

One or more of the components depicted in the network environment 10, such as the APM apparatus 12, client devices 16(1)-16(n), or web application servers 14(1)-14(m), for example, may be configured to operate as virtual instances on the same physical machine. In other words, one or more of the APM apparatus 12, client devices 16(1)-16(n), or web application servers 14(1)-14(m) illustrated in FIG. 1 may operate on the same physical device rather than as separate devices communicating through the communication network(s) 18 as depicted in FIG. 1. There may be more or fewer APM apparatuses 12, client devices 16(1)-16(n), or web application servers 14(1)-14(m) than depicted in FIG. 1.

In addition, two or more computing systems or devices can be substituted for any one of the systems or devices in any example. Accordingly, principles and advantages of distributed processing, such as redundancy and replication also can be implemented, as desired, to increase the robustness and performance of the devices and systems of the examples. The examples may also be implemented on computer system(s) that extend across any suitable network using any suitable interface mechanisms and traffic technologies, including by way of example only teletraffic in any suitable form (e.g., voice and modem), wireless traffic networks, cellular traffic networks, Packet Data Networks (PDNs), the Internet, intranets, and combinations thereof.

The examples may also be embodied as one or more non-transitory computer readable media having instructions stored thereon for one or more aspects of the present technology as described and illustrated by way of the examples herein, which when executed by one or more processors, cause the processors to carry out the steps necessary to implement the methods of the examples, as described and illustrated herein.

An exemplary method of adaptive presentation of web applications will now be described with reference to FIGS. 1-5. Referring more specifically to FIG. 3, in step 300 in this example, the APM apparatus 12 receives login credentials from one of the client devices 16(1)-16(n) associated with a user. In one example, the user is an employee of an enterprise and the login credentials are submitted via a login web page. The login web page can be received from the APM apparatus 12 and can originate from one of the web application servers 14(1)-14(m), and can be rendered via a web browser of the one of the client devices 16(1)-16(n) or a client application executing on the one of the client devices 16(1)-16(n), for example.

In step 302, the APM apparatus 12 determines whether the user is authenticated based on the login credentials, such as by communicating with an active directory server, as needed. If the APM apparatus 12 determines that the user is not authenticated, then the No branch is taken back to step 300 and login credentials are again obtained from the one of the client devices 16(1)-16(n) or another of the client devices 16(1)-16(n). However, if the APM apparatus 12 determines in step 302 that the user is authenticated, then the Yes branch is taken to step 304.

In step 304, the APM apparatus 12 obtains temporal data, user data for the user, and client device data, although other types and/or amounts of other data may be obtained. In this particular example, the temporal data includes one or more of a time of day, a day of the week, or a date of the month, although other temporal data could be used in other examples. Accordingly, the temporal data can be obtained from a local clock, a calendar application. or a database, for example, although the temporal data can also be obtained from other sources.

The user data in this example includes one or more of a role, a group, or a location, although other user data can also be used in other examples. The role can be a position of the user in the enterprise (e.g., manager or executive), the group can be a department in the enterprise (e.g., IT, engineering, or legal), and the location can be an office location within the enterprise (e.g., a city or geographic coordinates). Accordingly, the user data can be obtained from an enterprise database or via active directory queries to an active directory server, for example, although the user data can also be obtained from other sources.

In this particular example, the client device data includes one or more of a web browser type, an operating system type, or a standalone application type, for example, wherein the type can include a version or any other characteristic of the web browser, operating system, or standalone application. Other client device data can also be used in other examples. Accordingly, the client device data can be obtained based on header(s) included with the login request that included the login credentials or by querying the one of the client devices 16(1)-16(n), for example.

In some examples, one or more portions of the user data or client device data can be static and stored locally or in an enterprise database as associated with the user (e.g., based on the login credentials). The client device data can also be obtained from other sources and other types and numbers of client device data can also be obtained in other examples.

In step 306, the APM apparatus 12 identifies enterprise web applications (e.g. that may be hosted by the web application servers 14(1)-14(m)) that are allowed for the user. The enterprise web application can be identified based on an application of one or more of the access policies 30 to one or more portions of the temporal data, user data, or client device data obtained in step 304.

Referring more specifically to FIG. 4, a block diagram illustrating an exemplary application of one of the access policies 30 to identify allowed enterprise web applications for the user is illustrated. In this particular example, the APM apparatus 12 sends an active directory query in step 304 to an active directory server associated with the enterprise, using a unique identifier for the user, to obtain user data including the user group (e.g., engineering or sales). Additionally, the APM apparatus 12 retrieves OS type information from the one of the client devices 16(1)-16(n) in step 304.

Accordingly, if the APM apparatus 12 determines that the user in this example is in the engineering user group and the one of the client devices 16(1)-16(n) has an iOS operating system, then the APM apparatus 12 evaluating the one of the access policies 30 identifies APP1-APP100 as being allowed web applications for the user. In another example, the APM apparatus 12 may apply a rule or perform a lookup based on the login credentials, or a portion thereof, obtained in step 300 in order to identify the enterprise web applications that are allowed for the user. Any other type, combination, or order of data or any other type of access policies 30 can also be used by the APM apparatus 12 to identify the allowed web application for the user in other examples.

Referring back to FIG. 3, in step 308, the APM apparatus 12 correlates the temporal, user, or client device data obtained in step 304 with historical application access pattern data stored in the application access pattern database 28 to determine a subset of the allowed web applications most likely to be accessed by the user of the one of the client devices 16(1)-16(n) in the current session, although other types and/or amounts of data could be correlated. Accordingly, in this example the historical application access pattern data includes temporal, user, or client device data correlated with web application usage data obtained based on monitoring historical usage of the web applications by the users of the client devices 16(1)-16(n), optionally including the particular user of the one of the client devices 16(1)-16(n) if previously obtained.

For example, the historical application access pattern data may indicate that user X is a developer in the engineering group that has used web applications Y and Z every business day for the last six months. In another example, the historical application access pattern data may indicate that user A is an accountant in the accounting group that has used web application C on the last day of each of the last 18 months. Other types of historical application access pattern data can also be used or stored in the application access pattern database.

Accordingly, the temporal, user, or client device data obtained in step 304 for a user of a current session is correlated with historical application access pattern data for the user and/or one or more other users to determine a subset of the allowed applications identified in step 306. In one example, the APM apparatus 12 optionally determines whether the authenticated login credentials for the user are received for a first time from the one of the client devices 16(1)-16(n). The determination can be based on whether there is an entry in the application access pattern database 28 corresponding to a unique identifier for the user, for example.

If the APM apparatus 12 determines that the authenticated login credentials for the user are received for the first time from the one of the client devices 16(1)-16(n), then the correlated historical application access pattern data in step 308 can be historical application access pattern data for one or more other users associated with a same enterprise as the user and sharing a portion of one or more of the user data, client device data, or temporal data. For example, if the user data indicates that the current user is also a developer in the engineering group and the temporal data indicates that it is a business day, then the APM apparatus 12 may include web applications Y and Z in the subset of the allowed web applications identified in step 304 in the example described earlier.

However, if the APM apparatus 12 determines that the authenticated login credentials for the user are not received for the first time from the one of the client devices 16(1)-16(n), then the correlated historical application access pattern data in step 308 can be historical application access pattern data for the user. Accordingly, in this example, the APM apparatus 12 can correlate the current temporal, user, or client device data with historical access pattern data for the same user to determine the subset of the allowed web applications.

In yet other examples, both historical application access pattern data for the user and for one or more other of the users can be correlated with the current temporal, user, or client device data in step 308 in order to determine the subset of the allowed web applications. Also optionally, the APM apparatus 12 determines the subset of the web applications based on statistical analysis, heuristics, or a percentage likelihood that the web applications will be used in the current session based on the strength of the correlation with the historical application access pattern data, for example, although other methods for analyzing the historical application access pattern data or determining the subset of the allowed web applications can also be used.

In step 310, the APM apparatus 12 generates a webtop including graphical access points for the allowed web applications hosted by one or more of the web application servers 14(1)-14(m) that are organized based on the subset of web applications determined in step 308. The access points can be icons, links, or any other selectable feature that generates an instance of an associated one of the web applications when selected by the user of the one of the client devices 16(1)-16(n).

In this example, the access points for the subset of the web applications are prioritized in the webtop based on an order or grouping, although the access points can be organized in other ways, in order to facilitate more efficient access to the subset of the web applications by the user of the one of the client devices 16(1)-16(n). In step 312, the APM apparatus 12 provides the webtop generated in step 310 to the one of the client devices 16(1)-16(n) to facilitate access to the allowed web applications by the user of the one of the client devices 16(1)-16(n).

Accordingly, with this technology, a relatively small subset of a relatively large number of web applications are prioritized based on an organization of associated access points in the webtop so as to reduce the amount of time required for a user to locate access points for web applications most likely to be used by the user in the current session, and thereby improve user productivity. Additionally, the subset of the web applications are advantageously determined based on historical application access pattern data for the user or one or more other users sharing one or more characteristics, which facilitates a more effective organization of associated access points than presenting the access points based on web applications most recently used by each user or presenting the same access points in a same order for all of the users, for example.

In step 314, the APM apparatus 12 monitors usage of the web application(s) by the user of the one of the client devices 16(1)-16(n) during the current session. For example, the APM apparatus 12 can maintain usage data including which of the web applications were accessed by the user during the current session along with the number of times the web applications were accessed or the length of time that the user engaged with each of the web applications, for example, although other types of usage can be monitored in step 314.

In step 316, the APM apparatus 12 determines whether a termination of the session, initiated upon authentication of the login credentials for the user in step 302, has occurred. If the APM apparatus 12 determines that a termination of the current session has not occurred, then the No branch is taken and the APM apparatus 12 effectively continues monitoring usage of the web applications until a termination of the current session is determined. Accordingly, if the APM apparatus 12 determines that a termination of the current session has occurred, then the Yes branch is taken to step 318.

In step 318, the APM apparatus 12 updates the historical application access pattern data stored in the application access pattern database 28 based on the monitoring and associated collected usage data. Accordingly, the application access pattern database 28 is continually updated based on monitored usage of the web applications by users of the client devices 16(1)-16(n) to improve the accuracy of the determination of the subset of allowed web applications in step 308. Subsequent to updating the stored historical application access pattern data in the application access pattern database 28, or at any time during any of steps 302-318, the APM apparatus 12 receives login credentials from another one of the client devices 16(1)-16(n) in step 300.

Referring more specifically to FIG. 5, a timing diagram illustrating a method for adaptive presentation of web applications is shown. In step 500 in this example, a user of the client device 16 sends a login request to the APM apparatus 12. In step 502, the APM apparatus 12 authenticates the login credentials for the user, obtains temporal, user, or client device data, and identifies allowed web applications for the user by evaluating one or more access policies based on the temporal, user, or client device data.

In step 504, the APM apparatus 12 correlates the temporal, user, or client device data obtained in step 502 with stored historical application access pattern data for the user or one or more other users associated with a same enterprise, for example. As a result of the correlation, the APM apparatus 12 determines a subset of the allowed web applications identified in step 502. The subset of the allowed web applications includes web applications most likely to be used by the user of the client device 16 in the current session.

In step 506, the APM apparatus 12 generates a webtop based on the correlation in step 504. The webtop includes access points for the allowed web applications that are organized based on the determined subset of the allowed web applications. For example, the access points for the subset of the allowed web applications can be represented first, near the top, or in a particular grouping so as to facilitate more efficient access by the user of the client device 16 as compared to other of the allowed web applications. In step 508, the APM apparatus 12 provides the webtop generated in step 506 to the client device 16.

In step 510, the user of the client device 16 interacts with the allowed web applications by communicating requests and other data to the web application server 14 and receiving web pages or other data in response, for example. Concurrently, in step 512, the APM apparatus 12 monitors usage of the allowed web applications including which of the allowed web applications are accessed by the user of the client device 16 in the current session.

In step 514, the APM apparatus 12 determines whether the current session has been terminated by the user of the client device 16. If the APM apparatus 12 determines that the current session has not been terminated by the user of the client device 16, then No branch is taken back to step 512 and the APM apparatus 12 continues monitoring usage of the allowed web applications. However, if the APM apparatus 12 determines in step 514 that the user of the client device 16 has terminated the current session, then the Yes branch is taken to step 516.

In step 516, the APM apparatus 12 updates stored historical access pattern data based on the monitoring performed in step 512. Accordingly, the APM apparatus 12 can update the stored historical application access pattern data to include the temporal, user, or client device data obtained in step 502 correlated with an indication of which of the applications were accessed or other application usage data obtained in step 512, for example.

With this technology, access points for web applications are more effectively presented in webtops to facilitate more efficient access to web applications by users of client devices. Accordingly, this technology advantageously utilizes historical application access pattern data to determine a subset of allowed web applications most likely to be accessed by a user in a current session, and generates and provides a webtop with access points for web applications organized based on the determined subset of the allowed web applications. Thereby, this technology facilitates adaptive webtops that reduce the amount of time required to locate access points for web applications and improve user productivity.

Having thus described the basic concept of the invention, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested hereby, and are within the spirit and scope of the invention. Additionally, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes to any order except as may be specified in the claims. Accordingly, the invention is limited only by the following claims and equivalents thereto.