Application Server Object Relevance Display
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In J2EE enterprise applications, identifying design usage patterns among deployed objects is difficult due to the large number of objects and lack of design usage pattern information in current runtime configuration data, making it challenging for developers to design and develop new applications efficiently.
Innovation Solution
The solution involves determining the number of references to objects within a multi-tier application framework by examining metadata from configuration data sources, calculating an object relevance value based on these references, and displaying this information in a user-friendly format such as a molecular display or tree hierarchy, with the option to weight references from different metadata sources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If deployed objects are listed alphabetically by name in the application server UI, then the display is simple and easy to implement, but design usage patterns among objects become difficult to identify
Solution Approach 1:
The patent changes the sorting parameter from alphabetical order to relevance-based order. The relevance of each object is determined by calculating how many other deployed objects reference it, creating a new parameter (reference count) that reflects design usage patterns. This allows developers to identify frequently reused objects at the top of the list without losing the simplicity of automated sorting.
Solution Approach 2:
The patent introduces an intermediary calculation process that analyzes reference relationships between objects. By computing a relevance metric based on the number of references each object receives from others, the system creates an intermediate representation that reveals design usage patterns hidden in the raw configuration data, then uses this metric to reorder the display.
2Adaptability or versatility
If the application server hosts a large variety and number of deployed objects, then the system provides greater functionality and reusability, but identifying design usage patterns becomes more difficult
Solution Approach 1:
The patent extracts the relevant information (reference counts) from the large set of deployed objects and their configuration data. By pulling out only the reference relationship data and computing a relevance metric based on this extracted information, the system cuts through the complexity of hosting numerous objects and presents a simplified view that highlights design usage patterns.
Solution Approach 2:
The patent transforms the unstructured configuration data into a structured relevance metric. By changing from raw configuration files to a computed relevance parameter that quantifies how many objects reference each deployed object, the system makes design usage patterns measurable and visible even as the number of deployed objects grows.
3Reliability
If runtime configuration data is derived from JVM configuration files, then the data accurately reflects deployment state, but design usage pattern information is not included
Solution Approach 1:
The patent performs a preliminary analysis of the configuration data to extract reference relationships before the data is used for display. By pre-computing the relevance metrics from the raw configuration files, the system captures design usage pattern information that would otherwise be lost, while maintaining the reliability of the deployment state data as the foundation for this analysis.
Data Source
AI summary
In embodiments, the number of references to an object which is deployed into an application server framework may be determined by examining metadata extracted from configuration data sources within a multi-tier application framework. In embodiments, an object relevance value based on the extracted number of references to an object may be associated with the object. In embodiments, the number of references extracted from a data source may be weighted using a weight factor that is associated with the data source. In embodiments, the number of references to a source object may be extracted by traversing a source inheritance hierarchy and parsing the objects within the hierarchy. In embodiments, an object relevance display of a set of objects may be generated based in part on object relevance values of the set of objects. In embodiments, an object relevance display may be a molecular display, a flash tag cloud, and/or a source tree hierarchy.