Deploying Non-J2EE Containers on J2EE Servers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional two-tiered client-server architectures are inefficient for large enterprises due to tight coupling of business logic, presentation logic, and user interface logic, making it difficult to maintain and update applications, especially in dynamic environments.

Innovation Solution

A system and method for deploying non-J2EE containers on a J2EE server, allowing for communication between J2EE and non-J2EE containers, enabling flexible and scalable multi-tiered architecture with unified life cycle management and container API for easy deployment and management of both J2EE and non-J2EE components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a two-tiered client-server architecture is used, then the system structure is simple, but the coupling between business logic, presentation logic, and user interface logic is tight, making maintenance and updates difficult

Engineering Contradiction:

Improvesystem structureVSAvoidease of maintenance and updates

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent segments the monolithic client application into separate J2EE containers (enterprise beans, servlets, JSP pages) that can be independently developed, deployed, and maintained on the server side, while the thin client only handles user interface interactions

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts business logic and presentation logic from the client-side application and relocates them to server-side J2EE containers, leaving only the user interface logic on the client side, thereby enabling independent updates of business logic without affecting the client

Inventive Principle:

Principle #2Taking out (Extraction)

2Adaptability or versatility

If a multi-tiered architecture with J2EE containers is implemented, then the architecture becomes more flexible and scalable, but the device complexity increases

Engineering Contradiction:

Improveflexibility and scalabilityVSAvoidarchitecture complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent employs universal J2EE containers (enterprise bean containers, web containers) that can host multiple types of components and handle various functions (business logic, presentation logic, data access) through standardized interfaces and protocols, reducing the need for custom architecture design

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces J2EE specification-based containers as intermediary layers between the thin client and the database/backend systems, providing standardized communication protocols and abstraction mechanisms that simplify integration while enabling flexibility

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If non-J2EE containers are deployed on a J2EE server, then the system can support diverse application components, but the deployment complexity increases

Engineering Contradiction:

Improvesupport for diverse componentsVSAvoiddeployment complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal container deployment mechanism on the J2EE server that can accommodate both J2EE-standard containers and non-J2EE containers through a common deployment interface and lifecycle management system, allowing diverse components to be managed uniformly

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7721283B2Deploying a variety of containers in a Java 2 enterprise edition-based architecture

Publication Date: 2010.05.18 SAP SE

AI summary

A system and method are described for deploying non-J2EE containers on a J2EE server. In one embodiment, non-J2EE containers are created and deployed on the J2EE server in communication with J2EE containers already deployed on the J2EE server.