Application hub for analytics services platform applications

Abstract

An application hub is provided for analyzing applications of a service platform. The analysis service platform can receive data from an analysis device and provide services, such as filtering, processing, and visualizing data. The application hub can act as a landing site for users on a client device to launch applications of the analysis service platform. The application hub can provide a web page to the client device via a network, and the network provides a user interface that lists applications for the analysis service platform. The user can launch the application through the user interface, such as by selecting a user interface element of the application. The user interface can identify the application that has been installed on the client device and the application that has not been installed. The user interface can also identify when an application needs to be upgraded. Since the application hub is intended to be a single landing site for all applications, a single sign-on can be provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 62 / 913,603, filed on October 10, 2019, which is hereby incorporated by reference in its entirety. Background Art

[0003] Users of mass spectrometry systems and liquid chromatography systems must contend with disjoint landscapes of software tools. There may be separate tools for different types of systems. Furthermore, there may be separate software tools for each type of functionality, such as data acquisition, data processing, visualization, reporting, and consistency. Furthermore, users must log into each tool separately to use the tool. Summary of the invention

[0004] There is a need for an integrated solution for software tools for analytical devices such as mass spectrometers and liquid chromatography devices. The exemplary embodiments attempt to address this need.

[0005] According to an exemplary embodiment, a method is performed by a client computing device. According to the method, a user interface is received at the client computing device from an application hub running on an application hub computing device. The application hub serves as a landing site, where a client can launch an application for an analysis service platform on the client computing device, and the user interface identifies a selected application in the application as not installed on the client computing device. An input is received via the user interface on the client computing device. The input indicates a request to install the selected application on the client device. Based on the received communication, the selected application is retrieved from an application repository, and the retrieved selected application is installed on the client computing device.

[0006] The application hub client may be installed on the client computing device, and the application hub client service may be installed on the client computing device. The retrieval of the selected application may include sending a request to the application hub client service to retrieve the selected application from the application hub client. The retrieval of the selected application may include receiving the selected application from an application repository at the application hub client service. The installation of the selected application may be initiated by the application hub client service. The application hub client service may have administrative privileges on the client computing device.

[0007] According to an exemplary embodiment, a method is performed by a client computing device. In the method, a user interface is received from an application hub running on an application hub computing device at a client computing device. The application hub serves as a landing site where a client launches an application for an analytics service platform via the client computing device. The user interface identifies a selected application as requiring an update. Based on input received via the user interface at the client computing device, an update to the selected application is obtained. The update of the selected application on the client computing device is performed as a background process.

[0008] The application hub client service may be installed on the client computing device. The obtaining of the update may include the application hub client service retrieving an updated version of the selected application from an application repository. The application repository may be remote from the client computing device. Performing the update may include installing the retrieved selected application on the client computing device. The installation of the retrieved selected application may include the application hub client service launching an installation program to install the retrieved selected application. The input received via the user interface may indicate a user interface element of the user interface selected for the selected application. The method may also include determining whether the version of the selected application is a current version.

[0009] According to an exemplary embodiment, a method is performed on an application hub computing device. According to the method, a user login user interface is sent from an application hub running on the application hub computing device to a client computing device. The user login user interface prompts the user to provide credentials for logging into the application hub. The credentials are received at the application hub from the client computing device. The credentials are sent from the application hub to an authentication service. An indication is received at the application hub that the user has been authenticated. Access to one or more applications for an analytics service platform to be executed by the user via the application hub is granted, wherein the user does not need to authenticate again to execute the one or more applications.

[0010] An authorization code may be requested, and the authorization code may be received in response to the request. An application may be launched, and the authorization code may be an application repository. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 A block diagram is depicted of an environment suitable for practicing exemplary embodiments.

[0012] Figure 2A A block diagram of an illustrative client computing device is depicted.

[0013] Figure 2B A block diagram of an illustrative server computing device is depicted.

[0014] Figure 3A block diagram depicts illustrative components of an application hub.

[0015] Figure 4 A flow chart depicting steps that may be performed in an exemplary embodiment for a user to log into an application hub.

[0016] Figure 5 An illustrative login user interface for an application hub is depicted.

[0017] Figure 6 Depicted are actions that an application may take to display an application on an application hub user interface in an exemplary embodiment.

[0018] Figure 7 An illustrative user interface for an application hub is depicted with an application installed and another application not installed.

[0019] Fig. 8A Depicted is a user interface showing the changing appearance of an application icon to indicate that the application is being installed.

[0020] Figure 8B Depicts the completion of the installation of an application that was not previously installed Fig. 8A User interface.

[0021] Fig. 9 Depicted are actions that may be taken to install an application on a client computing device in an exemplary embodiment.

[0022] Fig.10 Depicted are actions that a sending application may take in an exemplary embodiment.

[0023] Fig.11A An illustrative icon depicting an application that needs to be updated.

[0024] Fig. 11B Depicted Fig.11A The icon changes appearance to reflect that the application is being updated.

[0025] Fig.12 A flow chart depicts steps that may be performed in an exemplary embodiment to determine if an application needs to be updated.

[0026] Fig.13 Depicted is a block diagram of an environment for logging messages for an application in an exemplary embodiment. DETAILED DESCRIPTION

[0027] The exemplary embodiments described herein provide an application hub for analyzing the application of the service platform. The analysis service platform can receive data from the analysis device and provide services, such as but not limited to filtering, processing and visualizing the data. The application hub can serve as a landing site for users on the client device to start the application of the analysis service platform. In some exemplary embodiments, the application hub can provide a web page to the client computing device through a network. The web page can provide a user interface that lists the application of the analysis service platform. The user can start the application through the user interface, such as by selecting a user interface element for the application.

[0028] The user interface can identify applications that have been installed on the client device and applications that have not been installed. For example, a visual cue can be provided on the user interface to distinguish between installed applications and uninstalled applications. This provides a quick and easy way for the user to understand the applications for installation. The user interface can also provide a mechanism for the user to install uninstalled applications on the client computing device. In some exemplary embodiments, an icon is provided for each application, and an action is taken, such as selecting the icon or otherwise activating the icon, to initiate installation of the application on the client computing device.

[0029] The user interface may also identify when an application needs to be upgraded. For example, a visual cue that an upgrade is required may be provided. An icon associated with the application may have a modified appearance indicating that an upgrade is required. The need for an upgrade may be determined automatically, without user intervention, by comparing a version number of the application installed on the client device with a version number of the application available for installation. A user may initiate upgrading the application through the user interface. In one example, a user selects an icon associated with the application to initiate the upgrade. The upgrade is accomplished by installing the upgraded version of the application on the client device.

[0030] Because the application hub is intended to be a single landing site for all applications, a single sign-on may be provided. In particular, when seeking access to the application hub, the user may be prompted to provide their credentials. Once the user has successfully logged in, the user may not need to provide credentials again to launch the applications shown on the user interface. This simplifies the process of launching applications by eliminating the need for the user to log in or otherwise present credentials for each application.

[0031] Figure 1An example of an environment 100 that may be suitable for practicing the exemplary embodiments is shown. This depiction is intended to be illustrative and not limiting. Environment 100 may include analytical devices 102 and 104. The analytical devices may take many different forms. Examples of analytical devices include mass spectrometry (MS) devices, liquid chromatography (LC) devices, LC-MS systems, mass analyzer systems, ion mobility spectrometer (IMS) systems, high performance liquid chromatography (HPLC) systems, ultra high performance liquid chromatography (UPLC) systems, and the like. ® ) systems, ultra high performance liquid chromatography (UHPLC) systems, solid phase extraction systems, sample preparation systems, heaters (e.g., column heaters), sample managers, solvent managers, in vitro devices (IVDs), combinations thereof, components thereof, variations thereof, and equipment that more generally performs analytical services.

[0032] In an exemplary embodiment, an analytical service may include the process and any process information (e.g., parameters, settings, thresholds, etc.) required to perform a process, method, analysis, test, etc. on an analytical device. In some embodiments, an analytical service may be developed, refined, tuned, etc. using a primary analytical system.

[0033] In many cases, the analysis devices 102 and 104 may be present in a laboratory environment. A laboratory network device 106 may be provided to engage with the analysis devices 102 and 104 through a network such as a local area network (LAN). The laboratory network device 106 facilitates communication with the analysis device and enables data collected from the analysis devices 102 and 104 to be transferred to the network 112 and accessible by the client computing devices 108 and 110. The client computing device may be a workstation, a desktop computer, a laptop computer, or other types of computing devices. Users of the client devices 108 and 110 may communicate with the server 114 through the network 112. The server 114 may be a server computing device and may run computer program codes for the analysis service platform 116 and the application hub 118. The analysis service platform 116 and the application hub 118 do not have to reside on a single server 114. In addition, in some cases, the analysis service platform 116 may be spread over multiple servers a. The network 112 may be a wide area network (WAN), such as the Internet, and may include wireless network components as well as hard-wired network components.

[0034] The analysis service platform 116 can perform analysis services on the data obtained from the analysis devices 102 and 104. The analysis service platform 116 can provide data acquisition, processing, visualization, reporting, and configurable compliance tools within a network environment. A non-limiting example of an analysis service platform is the UNIFI Scientific Information System platform from Waters Corporation of Milford, Massachusetts.

[0035] As described above, the application hub 118 serves as a central hub where users can locate and execute application programs on client computing devices for the analytics services platform 116 .

[0036] Figure 2A A more detailed view of an illustrative client computing device 200 is depicted. The client computing device includes a processor 202. The processor 202 can take a variety of different forms. For example, the processor 202 can include a central processing unit (CPU) implemented as an integrated circuit, an application specific integrated circuit (ASIC), a programmable logic device (PLD), a digital signal processor (DSP), a field programmable gate array (FPGA), a system on a chip (SoC), or an electrical circuit. The processor 202 can include multiple cores. The processor 202 can execute computer executable instructions stored in the storage device 204.

[0037] Storage device 204 may include one or more types of storage devices. For example, the storage device 204 may include various types of computer-readable storage media and / or systems in the form of one or more higher-speed memory units, such as read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory (such as ferroelectric polymer memory, bidirectional memory, phase change or ferroelectric memory), silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, device arrays (such as redundant array of independent disks (RAID) drives), solid-state memory devices (e.g., USB memory, solid-state drives (SSDs), and any other type of storage medium suitable for storing information. In addition, the storage device 204 may include various types of computer-readable storage media in the form of one or more lower-speed memory units, including internal (or external) hard disk drives (HDDs), magnetic floppy disk drives (FDDs), optical disk drives for reading or writing removable optical disks (e.g., CD-ROMs or DVDs), solid-state drives (SSDs), etc.

[0038] Storage device 204 can hold data, files, and computer programs. Figure 2A In the depiction of , the storage device stores application programs 208 and components 206 and 208 related to the application hub. Specifically, the components include an application hub client that serves as a client of the application hub and an application hub client service 206 that provides client services and has management rights. These components 206 and 208 will be described in more detail below.

[0039] The client computing device 200 may include a display device 212 such as a liquid crystal display (LCD) or light emitting diode (LED) display, etc. The client computing device 200 may include a network interface 216 for interfacing with a network and input devices 214 such as a keyboard, mouse, finger pad, etc.

[0040] Figure 2B A more detailed view of an illustrative server computing device 240 is shown. Server computing device 240 may include processor 240. The processor may take many different forms, such as those described above for processor 202. Server computing device 240 may include a network interface 244 for connecting to a network, such as network 112 ( Figure 1). The server computing device 240 may include a storage device 246. The storage device may contain different types of storage components and / or devices described above for the storage device 204. The storage device 246 is shown as storing an application store 250 and an application hub server 248. As will be described in more detail below, the application store is an application repository and the application hub server 248 is a server component of the application hub. The storage device may also store an analysis service platform 252.

[0041] The application hub may have a server-side component and a client-side component. The application hub may follow a client / server paradigm, where a server serves a client. Figure 3 Diagram 300 depicting an illustrative configuration is shown. Diagram 300 shows a client computing device 302 and a server computing device 304. Application hub client 306 and application hub client service 308 are on the client computing device. Application hub server 310 and application store API are on server computing device 304.

[0042] As mentioned above, App Hub facilitates single sign-on for users across multiple applications. Figure 4 A flowchart 400 is shown of steps that may be performed for such a single sign-on functionality. Initially, the application hub may send a login interface to the client computing device 402. In some embodiments, the user interface may be part of a web page sent as an HTML file, an XML file, or another format for display at the client computing device. Figure 5 An example of an illustrative login user interface 500 is shown. A text box 502 is provided for the user to enter a username. A text box 504 is provided for the user to enter a password. Once the username and password are entered, a login button 506 can be activated (such as by clicking on the login button 506). Then, the credentials (i.e., username and password) are sent and received (404) and sent to the identity server (406). The identity server can reside on the server computing system and be provided as part of the analysis service platform. The identity server determines whether the correct username and password are entered (408). If valid credentials are provided, access to the application hub is granted and an access token is provided to the client (410). When launching the application, the access token can then be submitted to display access permissions. If valid credentials are not provided, access to the application hub is denied (412).

[0043] Several different steps must be taken in order for the App Hub to display a user interface that displays a list of applications for the Analysis Services platform. Figure 6A diagram showing what steps may be performed. First, a user 602 requests 604 to load an application. A first request 608 may be made to obtain a list of applications suitable for the user, but when the user is not logged in, it is returned as unauthorized 612. As described above, the user logs in and sends credentials to the identity server 616. In the case of providing valid credentials, an access token is returned 618 from the identity server 616. Another request 628 to obtain an application may be submitted to the application hub server 610. A request 622 for obtaining a list of applications from an application store 624 may be sent in response. The application store 624 returns a list 626 of applications that are available and suitable for the user. The list may include information for each application, such as an application ID, application name, and icon. In some exemplary embodiments, the list may be sent as a JavaScript Object Notation (JSON) file. The information in the list may then be sent 628 to the client and used to display the application in a list of the application hub user interface 630. The application may include applications installed on the client computing device and applications installed on the server and accessed at the client computing device, such as through a web browser on a network interface.

[0044] Figure 7 An example of a user interface 700 showing applications available to a user is shown. In this case, a first icon 702 is displayed for a console demo application, and a second icon 704 is displayed for a platform management center. The names of these applications and the information displayed in the icons can be derived from a JSON file list of applications. The background of icon 702 is filled with a single color, indicating that the console demo application has been installed on the client computing device and the server is not installed. A list of installed applications can be maintained and used to determine whether the application has been installed. In contrast, the background of icon 704 is transparent to indicate that the platform management center application is available but has not been installed. Other visual cues can be used to distinguish between installed applications and non-installed applications. For example, different colors of icons can be used, the shape of the icons can vary, text can be provided in the icons to identify installed or non-installed applications, etc.

[0045] The user can initiate the installation of the application by taking a specified action via the user interface, such as, for example, by pointing a cursor at an icon, and clicking can trigger the installation of the application. It should be understood that other actions of selecting an application icon or activating the icon can be used. In addition, user interface elements such as menus and activatable controls can be used to initiate the installation of the application. Figure 7In the example of , clicking icon 704 can start the installation of the platform application console. Once icon 704 is selected, the appearance of the icon can change to be similar to Fig. 8A The appearance of icon 802 in the user interface shown in FIG. 1 changes to indicate that the installation is in progress. Icon 802 of the console demonstration does not change. Once the installation is complete, icon 804 ( Figure 8B ) to have a solid background instead of a transparent background to indicate that the Platform Management Console is installed.

[0046] Fig. 9 A diagram 900 depicting the steps that may be taken to install an application in an exemplary embodiment is shown. When a user 902 clicks 904 on an icon of an uninstalled application displayed as part of an application hub user interface 906 on a client computing device 904, the installation may be initiated. As described above, in some exemplary embodiments, other actions via the user interface may trigger the installation of an uninstalled application. In response to clicking on the icon of the uninstalled application, an application ID 908 of the uninstalled application is provided to an application hub client service administrator 910. The hub client service 910 initiates a request 912 to obtain an installer for an uninstalled application with a specified application ID via an application store API. The installer is received 916 by the application hub client service 910. The application is then installed locally on the client computing device using the installer, and the display of the installed application is updated 918. The installed application is displayed as installed 920 in the application hub user interface 922.

[0047] Once the application has been installed, it can be launched for use by the user on the client computing device. Fig.10 Actions taken to launch an installed application are depicted. A user 1002 may take an action, such as clicking on an install application icon 1004 of an application hub user interface 1006, to begin launching an installed application. A request 1008 is sent to obtain detailed information about the application from an application store 1010. These details are returned 1012 from the application store 1010 and used to formulate a request for an authorization code for the application 1014 that is sent to an identity server 1016. If the user is authorized, the identity server returns 1018 an authorization code for the application. The application is launched, and the authorization code is transmitted 1020 to the application store 1022. The application store 1022 requests an access token 1024, which is transmitted 1026 from the identity server 1016 to the application store 1022. The access token 1028 is used to call an authorization service.

[0048] As described above, a user interface from the application hub may indicate that an installed application requires an update. Fig.11AAn example of an icon 1102 on an application hub user interface 1100 is provided indicating that an update to the console demo application is required. The icon 1102 includes the text "Upgrade Required" to provide a visual cue that an update is warranted. An action such as clicking on the icon 1102 may initiate an update of the application. In some embodiments, other user interface actions may initiate an update. The icon 1102 may change color such as Fig. 11B , indicating that an update is in progress. Updates are accomplished by installing a newer version of the application, such as described above with respect to Fig. 9 described.

[0049] The display of an icon indicating a need for an upgrade may be prompted by a user selecting the icon or by a process that is executed periodically to ensure that all applications on the client computing device are current. Fig.12 A flowchart 1200 of steps that may be performed to determine whether an installed application on a client computing device is current is provided. Version information for an application installed on the client computing device is obtained (1202). In some instances, this may require viewing a product code and an upgrade code for the installed application. In some cases, this information may be associated with a performance. Version information may also be obtained for a version provided by an application store (1204). Version information about the application is compared, and a determination is made as to whether an update to the installed application is required (1206). If an update is required, an icon or other user interface element may be modified to note that an update is required (1208). If an update is not required, no further action is required.

[0050] Exemplary embodiments may support recording event information from applications. Fig.13 As shown, environment 1300 includes applications: application hub client 1302, application hub client service administrator 1304 and application hub server 1306, as described above. Recorder 1308 records events that occur in applications 1302, 1304 and 1306. In some embodiments, recorder 1308 can be implemented as a recording library, such as Serilog, which provides the functions of recording events, filtering and forwarding log entries about events to a specified location. Other recording tools can be used. Recorder 1308 records events in log 1310. Separate logs can be provided for each application. For example, log viewing tools can be used to view log entries, such as Glogg or Bare Tail.

[0051] The logger 1308 may allow logging to be customized on an application-by-application basis. Logging may be customized to specify a logging level. The level specifies the amount of information about the event and the type of information that is logged. This table provides information about appropriate log levels and provides examples:

[0052] Recording level More Information Example of logging levels in a configuration file lengthy Very low level debugging / internal information #timg# debug Low level control logic, diagnostic information #timg# information Non-internal information - what the system is doing #timg# warn Information about possible problems #timg# error Unexpected failures - the system can still continue #timg# Lead to failure Stopping this system, unable to continue #timg#

[0053] These messages may include timestamps, level information, and text information about the event. In an exemplary embodiment, recorder 1308 may record information messages, debug messages, and error messages for an application. These information messages provide information about events in the application, and these error messages provide information about errors that occur in the application. As described above, these debug messages provide diagnostic information and low-level control logic.

[0054] Here are some examples of information and error log messages for the Application Hub Client 1302:

[0055] Client Information Message:

[0056] • Message: "Application started"

[0057] • Message: "The application has quit"

[0058] • Message: "Use application id <applicationid>Call AppClick()

[0059] • Information: "Use URL <url>Call LaunchDefaultBrowser()

[0060] • Information: "Process <processname>It has already begun.”

[0061] • Information: "Requested url <address>”

[0062] Client Error Message:

[0063] • mistake:" <appconfigerrors>" / / Unable to read application configuration

[0064] • Error: "Application terminated with <exception details>"

[0065] • Error: "Unhandled exception <exception details>" / / / Unhandled exception on startup of waters_connect hub

[0066] • Error: "Communication with the application hub failed <exception details>"

[0067] • Error: "Clicked an unknown application type <applicationid>”

[0068] • Error: "LaunchDefaultBrowser() error: <Exception details>"

[0069] • Error: "Error in AppClick() on desktop application: <Exception details>"

[0070] • Error: "Error in AppClick() on web app: <Exception details>"

[0071] • Error: "Unable to start process <fileorurl><Exception details>"

[0072] • Error: "Unable to start process <processname><Exception details>"

[0073] • Error: "AppsPageController.GetApps() error: <Exception details>"

[0074] • Error: "Cannot display the page; <Exception details>"

[0075] • Error: "The requested url is not allowed: <absoluteuri>!”

[0076] Here are some examples of information and error messages that can be instigated for the App Hub Client Service:

[0077] Application Hub Client Service Information Message:

[0078] • Information: "Application <applicationid>Installation Status: <isinstalled>”

[0079] • Message: "Starting installation application: <applicationid>”

[0080] • Information: "Application <applicationid>Installation Status: <isinstalled>”

[0081] • Info: "Get list of installed applications to display in client"

[0082] • Info: "Installs the app (if not available) and returns the app details for the app id: <applicationid>”

[0083] • Message: "Application started"

[0084] • Info: "Starting Server"

[0085] • Information: "Configure Services"

[0086] • Info: "Configuring Server"

[0087] • Warning: "Server running in developer mode"

[0088] App Hub Client Service Error Message:

[0089] • Error: "Call to the App Store endpoint GetApplications failed with status:<AppStoreResponse StatusCode> <Exception details><Exception details>"

[0090] • Error: "Call failed for <applicationid>The app store endpoint GetWebApplication, which states:<AppStore Response StatusCode> <Exception details>"

[0091] • Error: "Call failed for <applicationid>The App Store endpoint GetDesktopApplication<Exception Details>"

[0092] • Error: "Call failed for <applicationid>The App Store endpoint GetDesktopApplication, which states:<AppStore Response StatusCode> <Exception details>"

[0093] • Error: "The path to the installer is incorrect <installerpath>”

[0094] • Error: "Installation failed for <installerpath><Exception details>"

[0095] • Error: "Unable to download the app from the App Store <applicationid>Installer for . Return <installerresponsestatuscode>”

[0096] • Error: "Error in GetApplications <exception details>"

[0097] • Error: "Error: "The App Store is not available. Contact your system administrator. <Exception details>"

[0098] • Error: "Installation Error". Unable to install on the hub <applicationname>. Contact your system

[0099] Administrator <Exception details>"

[0100] • Error: "InternalServerError<Exception details>"

[0101] • Error: InternalServerErrorThe app store is not available. <Exception details>"

[0102] • Error: "Unable to get network application: <applicationid><Exception details>"

[0103] • mistake:" <appconfigerrors>" / / Unable to read application configuration

[0104] Here are some examples of information and error messages that can be logged for an Application Hub server:

[0105] Application Hub Server Information Message:

[0106] • Message: "Application started"

[0107] • Info: "Starting Server"

[0108] • Information: "Configure Services"

[0109] • Info: "Configuring Server"

[0110] • Warning: "Server running in developer mode"

[0111] Application Hub Server Error Message:

[0112] • Error: "Unable to get local resource". File not found

[0113] • Error: "Unable to obtain local resource; <exception details>"

[0114] • mistake:" <appconfigerrors>" / / Unable to read application configuration.

[0115] The resulting log 1310 can be monitored to obtain ongoing information about the applications 1302, 1304, and 1306. In addition, false alarms can be triggered based on the logged information, metrics can be collected from the logged information in the log 1310, and useful debugging information can be extracted from the logged information in the log 1310.

[0116] Each log in log 1310 may have a size limit so that when the limit is reached, a new log is automatically created. In addition, there may be a limit on the number of log files. When the limit is reached, the oldest log file may be deleted and a new log file may be created.

[0117] Although the present invention has been described with reference to exemplary embodiments herein, those skilled in the art will understand that various changes in form and details may be made without departing from the intended scope of the invention as defined in the following claims.< / appconfigerrors> < / appconfigerrors> < / applicationid> < / applicationname> < / installerresponsestatuscode> < / applicationid> < / installerpath> < / installerpath> < / applicationid> < / applicationid> < / applicationid> < / applicationid> < / isinstalled> < / applicationid> < / applicationid> < / isinstalled> < / applicationid> < / absoluteuri> < / processname> < / fileorurl> < / applicationid> < / appconfigerrors> < / address> < / processname> < / url> < / applicationid>

Claims

1. A method performed by an application hub computing device, the method comprising: forwarding a user interface from an application hub running on the application hub computing device to a client computing device, wherein the application hub serves as a landing site, wherein a client is able to launch an application for an analytics service platform on the client computing device, wherein the analytics service platform interfaces with at least one analytics device to receive data from the at least one analytics device and perform one of the following actions: filtering the received data or processing the received data, wherein the at least one analytics device comprises a chromatography device or a mass spectrometer, and the user interface identifies a selected one of the applications as not installed on the client computing device; receiving, via the user interface on the client computing device, input indicating a request to install the selected application on the client device; retrieving the selected application from an application repository based on the received communication; and The retrieved selected application is caused to be installed on the client computing device. 2 . The method of claim 1 , wherein the application repository is remote from the client computing device. 3 . The method of claim 1 , wherein the input received via the user interface indicates a selection of a user interface element of a user interface for a selected application.

4. A method performed by an application hub computing device, the method comprising: forwarding a user interface from an application hub running on the application hub computing device to a client computing device, wherein the application hub serves as a landing site, wherein a client launches an application for an analysis service platform via the client computing device, wherein the analysis service platform interfaces with at least one analysis device to receive data from the at least one analysis device and perform one of the following actions: filtering the received data or processing the received data, wherein the at least one analysis device comprises a chromatography device or a mass spectrometer, and wherein the user interface identifies the selected application as requiring updating; obtaining an update to the selected application based on input received via the user interface at the client computing device; and The updating of the selected application is caused to be performed as a background process on the client computing device. The method of claim 4 , wherein the application repository is remote from the client computing device.

6. The method of claim 4, wherein the input received via the user interface indicates selection of a user interface element of the user interface for the selected application.

7. The method of claim 4, further comprising determining whether the version of the selected application is a current version.

8. A non-transitory computer-readable storage medium retaining computer-executable instructions that cause an application hub computing device to: forwarding a user interface from an application hub running on the application hub computing device to a client computing device, wherein the application hub serves as a landing site, wherein a client is able to launch an application for the analytics service platform on the client computing device, wherein The analytical services platform interfaces with at least one analytical device to receive data from the at least one analytical device and to perform one of the following actions: filtering the received data or processing the received data, wherein the at least one analytical device comprises a chromatography device or a mass spectrometer, and the user interface identifies a selected one of the applications as not installed on the client computing device; receiving, via the user interface on the client computing device, input indicating a request to install the selected application on the client device; retrieving the selected application from an application repository based on the received communication; as well as The retrieved selected application is caused to be installed on the client computing device.

9. The non-transitory computer-readable storage medium of claim 8, wherein the application repository is remote from the client computing device.

10. The non-transitory computer-readable storage medium of claim 8, wherein the input received via the user interface indicates a selection of a user interface element of a user interface for a selected application.

11. A non-transitory computer-readable storage medium retaining computer-executable instructions that cause an application hub computing device to: forwarding a user interface from an application hub running on the application hub computing device to a client computing device, wherein the application hub serves as a landing site, wherein a client launches an application for an analytics service platform via the client computing device, wherein The analytical service platform interfaces with at least one analytical device to receive data from the at least one analytical device and to perform one of the following actions: filtering the received data or processing the received data, wherein the at least one analytical device comprises a chromatography device or a mass spectrometer, and wherein the user interface identifies the selected application as requiring updating; obtaining an update to the selected application based on input received via the user interface at the client computing device; as well as The updating of the selected application is caused to be performed as a background process on the client computing device.

12. The non-transitory computer-readable storage medium of claim 11, wherein the application repository is remote from the client computing device.

13. The non-transitory computer-readable storage medium of claim 11, wherein the input received via the user interface indicates selection of a user interface element of the user interface for the selected application.

14. The non-transitory computer-readable storage medium of claim 11, further storing instructions for determining whether the version of the selected application is a current version.

Images