File System Mediator for Messaging Administration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Novice application program developers face significant challenges in using traditional messaging system APIs due to the need for domain-specific knowledge and skills, requiring substantial time to learn and implement messaging system capabilities.

Innovation Solution

A data processing system comprising a file system, a messaging system, and a monitoring component that allows non-programmatic access for administrative actions, where changes in the file system are detected and mirrored in the messaging system, enabling users with low technical knowledge to make structural changes through a graphical user interface, thereby simplifying administrative tasks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional messaging system APIs are used, then messaging functions can be accessed with control over persistence and priority attributes, but novice developers require considerable domain-specific knowledge and skills, investing a lot of time to learn and implement

Engineering Contradiction:
ImproveEase of messaging system administrationVSAvoidTime to learn and implement messaging capabilities
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent introduces a file system as an intermediary layer between users and the messaging system. Instead of directly interacting with complex messaging APIs, users perform familiar file system operations (create, delete, move files and directories) that are automatically translated into corresponding messaging system administrative actions. This intermediary abstracts the complexity of messaging system administration while maintaining full control capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a file system representation that mirrors the messaging system's administrative structure. Files and directories in the file system correspond to messaging objects and their attributes. Users interact with this copied representation through standard file operations, and the system synchronizes changes between the file system view and the actual messaging system, eliminating the need to learn messaging-specific commands.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If traditional messaging APIs are used, then application developers can define persistence and priority attributes, but they require considerable domain-specific knowledge and skills before these APIs can be used

Engineering Contradiction:
ImproveControl over messaging attributesVSAvoidComplexity of API usage
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The file system acts as a mediator that translates simple file operations into complex messaging system administrative actions. Users create, delete, move, and rename files in the file system, and the monitoring component automatically performs the corresponding messaging system operations, preserving all messaging attributes like persistence and priority without requiring users to understand them.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes the file system universal for messaging system administration. The same file system operations can manage different types of messaging objects (queues, topics, connections) and their various attributes (persistence, priority, capacity) through a single unified interface, eliminating the need to learn multiple messaging-specific APIs or commands.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If messaging system administrative actions are performed directly, then full control over messaging functions is achieved, but access requires programmatic knowledge and direct system contact

Engineering Contradiction:
ImproveAccessibility of messaging administrationVSAvoidRequirement for programmatic access
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The file system serves as an accessible intermediary that any user can interact with using standard file operations, eliminating the need for programmatic knowledge. The monitoring component bridges the file system and messaging system, translating user-friendly file operations into the appropriate administrative actions on messaging objects.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system provides self-service messaging administration through the file system interface. Users can independently perform administrative tasks like creating queues, setting priorities, and managing persistence by simply manipulating files and directories, without requiring direct access to messaging system commands or programming expertise.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8756243B2Non-programmatic access to enterprise messaging administration
Publication Date: 2014.06.17 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8756243B2 patent drawing
  • US8756243B2 patent drawing
  • US8756243B2 patent drawing

AI summary

The present invention is directed to non-programmatic access to enterprise messaging administration. A method of operating a data processing system, wherein the data processing system includes a file system, a messaging system and a monitoring component, in accordance with an embodiment includes: monitoring the file system, detecting a change in the file system, and amending a structure of the messaging system, according to the detected change in the file system.