Portal Server Web Traffic Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional web site traffic analysis methods fail to capture critical information about portal usage, such as portal page names, portlet states, and user interactions, due to dynamic server URLs and lack of easily extractable data, leading to incomplete and delayed data integration.
Innovation Solution
A method where portlets generate fragments of web pages with embedded code to collect and transmit data on web traffic to a facility, allowing for comprehensive analysis of portal and portlet traffic, including user interactions and portal states, even for cached pages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traditional web site traffic analysis methods are used, then data collection is simple, but critical information about portal usage (portal page names, portlet states, user interactions) cannot be captured
Solution Approach 1:
The patent introduces a portal server as an intermediary component that actively collects traffic data from portlets and transmits it to a data collection facility. This intermediary mechanism enables the capture of critical portal usage information (page names, portlet states, user interactions) without requiring complex modifications to the entire web traffic analysis system. The portal server mediates between the portlets and the analysis facility, centralizing the data collection function.
Solution Approach 2:
The patent implements preliminary data collection by having the portal server gather traffic information from portlets before the data is needed for analysis. The portal server proactively collects data including portal page names, portlet states, and user interactions, then transmits this pre-collected information to the data collection facility. This preliminary action ensures that comprehensive portal usage data is available for analysis without requiring complex real-time processing.
2Reliability
If server URLs are used to track web traffic, then implementation is straightforward, but URLs are highly dynamic and may no longer exist when analysis is performed
Solution Approach 1:
The patent uses the portal server as an intermediary that maintains stable references to portal pages and portlets through structured data collection. Instead of relying on dynamic server URLs, the portal server records identifying information about portal pages and portlets in a standardized format, then transmits this stable reference data to the data collection facility. This intermediary approach decouples the analysis system from URL volatility.
Solution Approach 2:
The patent creates a copy of the portal traffic data structure that includes stable identifying information about portal pages and portlets. The portal server generates a data structure containing portal page names, portlet names, and states, then transmits this copied information to the data collection facility. This copy mechanism preserves the relationship between portal components without relying on potentially changing URLs.
3Productivity
If the server gathers data about web site traffic, then centralized collection is achieved, but storage and computational resources are consumed excessively
Solution Approach 1:
The patent extracts only the necessary traffic data elements from the complete web traffic stream. The portal server selectively collects specific information including portal page names, portlet names, portlet states, and user interaction data, while filtering out unnecessary data. This extraction approach transmits only the essential portal usage information to the data collection facility, reducing storage and computational resource requirements.
Solution Approach 2:
The patent applies local quality by having the portal server perform data collection and preliminary processing at the portal level before transmission. Each portal server tailors the data collection to its specific portal's structure and requirements, gathering only the relevant portal-specific information (page names, portlet states) rather than attempting to collect all possible web traffic data. This localized approach reduces the overall data volume requiring centralized processing.
4Adaptability or versatility
If multiple log files are created for traffic data, then data storage is distributed, but integration of data becomes difficult without common identifiers
Solution Approach 1:
The patent merges the data collection function into a unified structure at the portal server level. Instead of creating separate log files for different data types, the portal server consolidates portal page information, portlet information, and user interaction data into a single integrated data structure. This merged data structure includes common identifiers that link all data elements, enabling straightforward integration at the data collection facility without requiring complex correlation between multiple log files.
Data Source
AI summary
Methods and arrangements to analyze web traffic of a portal are contemplated. Embodiments include transformations, code, state machines or other logic to analyze web traffic of a portal by a portlet receiving a request for web page content from the portal and generating a fragment of a web page. The fragment may include code to collect data from clients on web traffic of the portlet and to transmit the data to a facility for the collection of data on web traffic of the portal and the portlet. Some embodiments may involve a portal requesting web page content from a portlet, and the portal receiving a fragment of a web page from the portlet. The fragment may include code to collect data from clients on web traffic of the portlet and to transmit the data to the data collection facility.