Patent Application
20130253904
This application relates generally to enterprise software systems and more specifically to enterprise resource planning (ERP) systems and plugins for web servers of the ERP systems for interacting with different types of client devices and selective optimization and rendering of content based on the types of the client devices.
ERP systems were originally developed in the 1980s and the 1990s to support access by desktop terminals and/or personal computers. These systems are complex, difficult to implement, and heavily customized by customers. Most ERP systems have unique business rules and stringent regulatory and security functionality, which are difficult to create and later reconfigure.
From a user experience perspective, current ERP systems require keyboards, high resolution screens with wide aspect ratios, and accurate selection devices in trackballs, mice, and touchpads. Mobile devices, on the other hand, have narrow aspect ratios screens and typically use touch features of the screen for selection and data entry. Therefore, deploying ERP systems as delivered by the software provider and implemented on premise (or hosted) on mobile devices requires re-implementation, purchasing of additional hardware, integrating systems, and re-deploying customizations. As mobile devices become important tools in modern enterprises and gain widespread use, there is a need for solutions that allow organizations to use their existing ERP systems without additional efforts.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Provided are the system and method for automatic selective optimization and rendering based on characteristics of a client device of content from an ERP system. A client device can be a desktop, a laptop, a netbook, an ultrabook, a smartphone, and a tablet computer. In some embodiments, the method for automatic selective optimization and rendering of content based on characteristics of a client device may be based on receiving the content from a enterprise system, with the enterprise system being pre-configured based on specific business rules; analyzing the content to determine properties associated with the content; selectively optimizing the content, based on the properties associated with the content and the characteristics of the client device, thereby producing optimized content; and facilitating selective rendering of the optimized content on the client device, thereby providing for the selective optimization and rendering of the content without having to reconfigure the enterprise system.
Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements.
ERP systems integrate internal and external management information across an entire organization, embracing various relationships within the organization, such as finance/accounting, manufacturing, sales and service, and customer relationship management. ERP systems automate many of these activities with an integrated software application. The purpose of ERP systems is to facilitate the flow of information between all business functions inside the boundaries of the organization and manage the connections to outside stakeholders. ERP systems can run on a variety of computer hardware and network configurations and typically employ a database as a repository for information.
Many ERP systems started moving toward web-centric designs, allowing various functions of such ERP systems to be accessed and run via a web browser on mobile telephones, tablet computers, laptops, or desktop computers from remote locations. To enable this, ERP systems require re-implementation, purchasing of additional hardware, integrating systems, and re-deploying customizations.
The system for automatic selective optimization and rendering of content based on characteristics of a client device described herein may enable interactions with client devices of different types without additional re-implementations and re-deploying customizations while extending ERP system output instead of replacing it.
The system may automatically perform selective optimization of content from an ERP system by working with the user interface generated by the ERP system. The optimization may be performed based on characteristics of a client device. For example, optimization for client devices with touch screens may include replacing of mouse-optimized controls, optimized ERP system navigation, tagging of data entry fields with field types to show an appropriate keypad.
In some embodiments, optimization of content of an ERP system for client devices may include optimization for various screen sizes, specifically, re-flowing of pages to be in portrait rather than in portrait orientation, based on a size of the client device screen, and pivoting wide grids for improved user experience. This approach may allow the content layout to match the size of the client device screen, thereby improving the usability and user experience.
In some embodiments, the system for automatic selective optimization and rendering of content may enable customizations and upgrades of an ERP system. This approach may allows organizations to avoid having to provide custom modifications to various client devices as the system for automatic selective optimization and rendering of content may render the content efficiently for any client device. In some embodiments, the system for automatic selective optimization and rendering of content may be a plug-in that exists on the web server between the browser of the end-user on a client device and the ERP application server and ERP application database. The system for automatic selective optimization and rendering of content may leverage the output of the ERP system as the starting point for marking it up for client device access. The output may be analyzed by the system to read the code/definitions of the ERP system to understand relationships between elements in the user interface and the meaning of fields and controls on the user interface. The existing application infrastructure may be leveraged by using a J2EE web server plug-in (servlet filter) to inject the optimization logic into the processing stream. Interactions between the ERP system and client devices (requests, sessions, and requested content) may be captured by the system for automatic selective optimization and rendering of content to allow rules to control security and content rendering. This allows the same web server to handle both mobile and non-mobile traffic.
In some embodiments, the functionality of the system for automatic selective optimization and rendering of content may be represented by the admin services component, navigation component, user interface component, mobile extensions component, security component, and metadata services component.
The admin services component may control the overall processing of the system for automatic selective optimization and rendering of content. Because it is intended to function as a seamless part of the ERP application infrastructure, it is designed to work in conjunction with the processing already done on the web server of the ERP system. As such, it may make decisions about displaying client device rendering, allowing access to content, level of logging performed, type of content to be served, and/or necessity to reload access rules from the database. In order to make these decisions, the system for automatic selective optimization and rendering of content may understand a profile of the user/device accessing the system, state of the plug-in, and type of request being made to the system.
The admin services component may use the following attributes of the user/device to control access to the system: the browser/operating system making the request to the system (this is used to determine whether a mobile device is accessing the system and will make a decision as to whether to perform mobile rendering) and the location from which the user is accessing the system (this is used to determine whether to grant or deny access to content based on location).
In some embodiments, the type of content requested from the system may be used to control the request processing. If the request is for HyperText Markup Language (HTML) content for the system, the HTML generated by the application will be used as the starting point for mobile rendering. If the request is for navigation menus, then the plug-in will request the raw menu information from the system and generate its own mobile rendering. If the request is for portal content, then the plug-in will either start with the HTML generated by the application or request the raw data, depending on whether the request is related to navigation or content.
If the request is to change the state of the mobile product, it will override whether mobile rendering will be performed (or not performed) for the current session; change the logging level of the mobile product; re-load the configuration data from the database to the plug-in; purge the server cache of the metadata (see metadata services); turn the plug-in on or off; and turn the security functions on or off.
In some embodiments, the navigation component may read navigation rules of the ERP system and repurpose content for client device access. Services performed by the navigation component may include reading the hierarchy of menu titles and descriptions to be presented in a mobile format as users drill through the menus; pruning navigation to parts of the system that are disabled either due to location security or device access rules; and keeping track of the breadcrumbs and maintaining a breadcrumb menu to allow easy access without hitting the back button. The latter may include navigating through menu relationships in the navigation definitions of the application; identifying navigation collections (pages defined for the purpose of navigation) and displaying them in a menu form; and identifying when the system was accessed from an external system and embedding the breadcrumb for it in the breadcrumb menu. To perform these services, the infrastructure of the navigation component may include JQuery mobile menu and navigation components; role-based caching of navigation menus to minimize the need to request information from the ERP system about who can access what content; and metadata services to allow the web server to access the menus, rules, and the like that drive the presentation and navigation within the system.
In some embodiments, the user interface component may take the user interface generated by the ERP application and modify it to work properly on client devices. This may include marking up the HTML generated by the ERP system. Marking up the HTML may involve several operations. First of them is marking the HTML as valid HTML5 syntax. Then, it may involve identifying the meaning of the content on the generated user interface by looking at the HTML and Asynchronous Javascript And XML(AJAX XML) generated by the application. The metadata services component may be used in combination with the structure of the user interface (UI) to decide on an association of page elements, such as page containers (group boxes), labels, fields, and page controls; movement of groups of entities within the user interface, so that pages can be displayed in narrow mode and still be meaningful; tagging of fields as to the type of field (i.e., numeric, date, time, alphanumeric); honoring of multilingual translations within the ERP system; changing controls to touch-optimized controls using JQuery mobile (or similar library); and removing extraneous HTML markup (such as extra tables and width tags) intended to optimize UI for wide screen monitors.
Another operation that may be part of marking up the HTML is managing javascript generated by the ERP system. This may consist of stripping out extraneous javascript not needed on mobile device and embeding javascript to perform processing on the device to minimize the number of server trips and improve performance (such as navigating between multiple items within a page).
Also, marking up the HTML may include rules-based templating infrastructure to minimize code serving to process UI services, thereby allowing rapid iterations and deployments without requiring re-compilation of code; and deciding on logic for making modifications to user interface without requiring expensive processing to walk the document object model (DOM) for each page being rendered.
In some embodiments, the mobile extensions component may provide a capability for injecting customer-defined logic to the end-product of the user interface component. This allows the customer to make additional UI tweaks to the ERP system without requiring modification of either the core ERP application or the core mobile code of the plug-in. The UI tweaks may include injecting modifications without changing the plug-in at different locations within the generated UI. This may be done based on understanding properties of the session/user/and content in the ERP system, leveraging the same rules-based templating infrastructure in the UI services to allow robust processing rules based on content, user, session, or application data; and allowing calls to any javascript library that is enabled in the system. The modifications are defined and administered in relational database pages that are deployed within the user interface of the ERP system.
In some embodiments, the security component may provide device and location security features to allow easy control, management, and auditing of mobile access. This may include rules-based means of identifying whether to allow or block access to parts of the ERP system in mobile access; generating detailed logs of all mobile traffic, including date/time, Internet Protocol (IP) address, user identity, content accessed, data accessed, and actions taken; and automatic pruning of navigation UI based on rules.
In some embodiments, the metadata services component may represent the bridge between the product processing on the server and the rules by which it performs this processing. The metadata services component may provide services that extract rules that define how the ERP system is defined and structured and services that extract rules that drive how the plug-in should operate on top of the ERP system. By understanding the meaning of the different parts of the ERP system to be rendered, the plug-in is able to automatically transform the UI of the ERP application. For all of these services, the metadata services component may read the definitions from relational tables and application programming interfaces (APIs) in the ERP system; store the definitions in a cache on the web server to be processed locally; and manage the reading and storing of the definitions at either web server start-up time or as content is requested.
The metadata services component may extract the meaning of all of the pieces of the user interface generated by the ERP system. Because the plug-in understands at a granular level the meaning of all pieces of the ERP system, whether developed by the original software developer or modified by the customer, it is able to automate the mobile-optimized rendering of the user interface. The types of metadata read from the ERP system to be used as part of the plug-in may include page element structure, element properties, control properties, navigation rules, and user identity and permissions.
As the metadata services component is configured and administered from pages within the ERP system delivered by the plug-in, it may also include services to read and cache the client device configuration on the web server (i.e., branding rules, mobile extensions, additional CSS and Javascript rules).
In some embodiments, because the plug-in contains location-based security capabilities, the rules that define the access control and logging are also managed as part of the metadata services.
Referring now to the drawings,
Client devices 150 may be connected to web server 130 using a network (not specifically shown in
The systems and methods described herein may also be practiced in a wide variety of network environments including, for example, Transmission Control Protocol (TCP)/IP-based networks, telecommunications networks, wireless networks, and the like. In addition, the computer program instructions may be stored in any type of computer-readable media. The program may be executed according to a variety of computing models including a client/server model, a peer-to-peer model, a stand-alone computing device, or according a distributed computing model in which various functionalities described herein may be effected or employed at different locations.
As explained above, client devices 150 are capable of supporting web browsers to generate user interfaces. Web browsers allow users and administrators to access various applications and administrative tools of an ERP system. Each client device 150 used for communicating with an ERP system has a browser software installed therein. Generally, no additional software (specific to the ERP system) needs to be installed on client devices 150 to implement described methods and systems.
Web server 130 may be a Java-enabled web server for supporting browser transaction requests and the application messaging technology. Web server 130 may be used to install a collection of servlets (e.g., Java servlets) designed to handle a wide range of ERP transactions. Some examples of a web server include an Apache web server, Internet Information Services (IIS) web server, nginx web server, Google web server, and Resin web server. The main function of web server 130 is to deliver web pages based on requests from client devices 150. This means delivery of HTML documents and any additional content that may be included by a document, such as images, style sheets, and scripts. The web browser described above typically initiates communication by making a request for a specific resource using HyperText Transfer Protocol (HTTP), and web server 130 server responds with the content of that resource or an error message if unable to do so. Web server 130 may also be used to receive content from client devices 150. This feature is used for submitting web forms, including the uploading of files. Web server 130 may support server-side scripting using Active Server Pages (ASP), PHP, or other scripting languages. Additional features of web server 130 specific to ERP functions are described below.
ERP application server 120 is another part of an ERP system. ERP application server 120 executes business logic. It may also be configured to issue SQL to ERP application database 110. In other words, ERP application server 120 serves as a link between web server 130 and ERP application database 110. ERP application server 120 may include various services and server processes that handle transaction requests. ERP application server 120 may be also responsible for maintaining the SQL connection to ERP application database 110 for browser requests. Some examples of middleware platforms that may be used on ERP application server 120 include TUXEDO (Transactions for Unix Extended for Distributed Operations) and Jolt. For example, TUXEDO may be used to manage database transactions, while Jolt may be used to facilitate transaction requests issued from the Internet.
ERP application database 110, which is sometimes referred to as a database server, is yet another component of an ERP system. ERP application database 110 contains one or more database engines and databases. These, in turn, include object definitions, system tables, application tables, and data. ERP application database 110 may be running one of the supported relational database management system (RDBMS)/operating system combinations. The relationship between ERP application database 110 and ERP application server 120 may be according to a one-to-many model. That is, a single ERP application database 110 can have multiple ERP application servers 120 connecting to it. ERP application database 110 may be configured to simultaneously handle multiple application server connections, development environment connections, and batch programs. A component of an ERP system that is not shown in
As stated above, a system for automatic selective optimization and rendering of content 200 on web server 130 is configured to communicate with client devices 150. In certain embodiments, the system for automatic selective optimization and rendering of content 200 is implemented as a web server plug-in, which is a set of software components that adds specific functionalities to a larger software application provided on web server 130. This plug-in enables customizing the functionality of web server 130.
To provide this functionality, system for automatic selective optimization and rendering of content 200 includes multiple modules, as illustrated in
Based on the type of the client device, an access level available for this type of client device may be determined during operation 406. Method 400 may then proceed with processing the request at an application server of the ERP system based on the access level during operation 408. This processing operation may generate an HTML output. It may involve retrieval of ERP information from an application database of the ERP system.
Method may proceed with processing the HTML output at the ERP interface based on the type of the client device to generate a client specific HTML output during operation 410 and transmitting the client specific HTML output to the client device during operation 412.
The method 600 may commence at operation 602 with the communication module 202 receiving a request from a client device. The type of browser/OS of the client device may be determined at operation 604 in order to determine whether a mobile device 606 is accessing the ERP system. If the request has not from a mobile device, the standard rendering is performed at operation 608. If, on the other hand, the request has come from a mobile device, the method 600 may proceed to the optimized rendering at operation 610. At operation 612, the location from which the system is accessed may be determined. The eligibility of the location for accessing the ERP system may be ascertained at operation 614. If the location is not eligible for access, the access is denied. If, on the other hand, the location is eligible, the access is granted and the type of the requested content is determined at operation 620. It should be understood that the location as used herein is not limited to a physical location of the client device and includes a network associated with the client device. Furthermore, besides the location-based security, the security can be based on, for example, various rules associated with multiple-factor authentication and time-based conditions, a proxy involved in routing of the content, application data, screens associated with the content, and functionality associated with the content.
If the request is for HTML content, the HTML generated by the ERP application can be used as the starting point for mobile rendering at operation 622. If the request is for navigation menus, then the plug-in may request the raw menu information from the ERP system at operation 628. If the request is for portal content, then the plug-in, depending on whether the request is related to navigation or content 634, may either start with the HTML generated by the ERP application or request the raw menu information. The content generated by the ERP system may be marked up at operation 624 and necessary modifications injected at operation 626. The raw menu information, received at operation 628, may be read to determine navigation rules at operation 630 and repurposed for mobile access at operation 632. Thereafter, the content may be rendered on the client device at operation 636.
The exemplary computer system 700 includes a processor or multiple processors 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), and a main memory 708 and static memory 714, which communicate with each other via a bus 728. The computer system 700 may further include a video display 706 (e.g., a liquid crystal display (LCD)). The computer system 700 may also include an alphanumeric input device 712 (e.g., a keyboard), a cursor control device 716 (e.g., a mouse), a voice recognition or biometric verification unit (not shown), a disk drive unit 720, a signal generation device 726 (e.g., a speaker) and a network interface device 718. The computer system 700 may further include a data encryption module (not shown) to encrypt data.
The disk drive unit 720 includes a computer-readable medium 722 on which is stored one or more sets of instructions and data structures (e.g., instructions 710) embodying or utilizing any one or more of the methodologies or functions described herein. The instructions 710 may also reside, completely or at least partially, within the main memory 708 and/or within the processors 702 during execution thereof by the computer system 700. The main memory 708 and the processors 702 may also constitute machine-readable media.
The instructions 710 may further be transmitted or received over a network 724 via the network interface device 718 utilizing any one of a number of well-known transfer protocols (e.g., HTTP).
While the computer-readable medium 722 is shown in an exemplary embodiment to be a single medium, the term “computer-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-readable medium” shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine and that causes the machine to perform any one or more of the methodologies of the present application, or that is capable of storing, encoding, or carrying data structures utilized by or associated with such a set of instructions. The term “computer-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals. Such media may also include, without limitation, hard disks, floppy disks, flash memory cards, digital video disks, random access memory (RAM), read only memory (ROM), and the like.
The exemplary embodiments described herein may be implemented in an operating environment comprising software installed on a computer, in hardware, or in a combination of software and hardware.
Although embodiments have been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the system and method described herein. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
