MOM Provider with Multiple Logical Server Instances

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The multi-tiered architecture in enterprise systems faces challenges with scalability due to the constraints of a central Message-Oriented Middleware (MOM) provider, which also requires a brittle namespace scheme for message delivery, leading to complexity and inefficiency in managing distributed applications and components.

Innovation Solution

Implementing a MOM provider with multiple logical MOM server instances, each with a session container for managing sessions and a destination container for providing destinations, identified by a globally unique identifier, to facilitate scalable and flexible message delivery across distributed systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a central MOM provider is used in multi-tiered architecture, then message delivery is facilitated, but scalability is constrained and namespace management becomes brittle

Engineering Contradiction:

ImprovescalabilityVSAvoidnamespace management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the centralized MOM provider into multiple distributed MOM server instances, each capable of independently managing its own namespace. This segmentation eliminates the single point of constraint and allows the system to scale horizontally by adding more instances, directly resolving the scalability issue while distributing namespace management responsibilities.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimensional approach by allowing each MOM server instance to have its own independent namespace scope. Instead of a single global namespace hierarchy, the system now operates with multiple namespace dimensions, where each instance manages its own namespace independently, thereby reducing the brittleness of namespace management.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

2Productivity

If multiple MOM server instances are implemented, then scalability is enhanced, but system complexity increases

Engineering Contradiction:

Improvemessage delivery capacityVSAvoidsystem configuration complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

Each MOM server instance is designed as a universal, self-contained unit that can independently provide complete MOM functionality including session management, destination management, and message routing. This multi-functionality at the instance level allows the system to scale capacity by simply adding identical universal units, avoiding the need for complex specialized configurations.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent employs a copying strategy where additional MOM server instances are created as copies of a standardized template. Each instance replicates the necessary components (session container, destination container) and can be deployed independently. This copying approach simplifies system configuration because each instance follows the same structure and management rules.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS7634550B2Message-oriented middleware provider having multiple server instances

Publication Date: 2009.12.15 SAP SE

AI summary

A method, apparatus, and system are provided for a Message-Oriented Middleware (MOM) provider having multiple logical MOM server instances. In an embodiment, the MOM provider having multiple logical MOM server instances is implemented on an application server. Each MOM server instance may include a session container to manage one or more sessions and a destination container to provide one or more destinations. In an embodiment, a globally unique identifier identifies each destination.