Deploy Callback System for Decoupled Application Logic
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 deploy callback system facilitates communication between servers and clients by registering a deploy listener to receive status information on application deployment, allowing for improved management and scalability through a multi-tiered architecture with J2EE and non-J2EE containers, enabling flexible deployment and management of applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a two-tiered client-server architecture is used, then the system structure is simple, but the business logic, presentation logic, and user interface logic are tightly coupled, making it difficult to maintain and update applications
Solution Approach 1:
The patent applies segmentation by dividing the monolithic client application into separate logical components: business logic, presentation logic, and user interface logic. This is achieved through the deployment of EJB components in EJB containers and servlets/JSP in web containers, allowing each component type to be independently deployed, managed, and updated without affecting the others.
Solution Approach 2:
The patent introduces intermediaries in the form of EJB containers and web containers that act as mediators between the client and the various logic components. These containers provide standardized interfaces and deployment mechanisms, enabling loose coupling between different parts of the system while maintaining a relatively simple overall architecture.
2Adaptability or versatility
If business logic is changed frequently in response to changing business rules, then the system is adaptable to dynamic environments, but the tight coupling in two-tiered architecture makes updates extremely hard
Solution Approach 1:
Business logic is segmented into independent EJB components that can be deployed and updated separately from the user interface and presentation logic. This allows frequent changes to business rules without requiring updates to client-side applications, as the EJB components are managed server-side through standardized deployment mechanisms.
Solution Approach 2:
The EJB container provides universal deployment mechanisms that can handle various types of EJB components (session beans, entity beans, message-driven beans) through a common interface and deployment descriptor format. This universality enables consistent management and updating of business logic components regardless of their specific type or function.
3Adaptability or versatility
If a multi-tiered architecture is implemented to separate logic components, then scalability and flexibility are improved, but the system complexity increases
Solution Approach 1:
The patent uses EJB containers and web containers as intermediaries that simplify the multi-tiered architecture. These containers provide standardized interfaces and deployment mechanisms that abstract away the complexity of distributing logic across multiple tiers, allowing developers to work with a relatively simple component model while benefiting from the scalability and flexibility of the multi-tiered structure.
Solution Approach 2:
The EJB container and web container provide universal services that handle deployment, lifecycle management, and component instantiation across different tiers. This multi-functionality reduces the need for custom infrastructure code at each tier, thereby reducing overall system complexity despite the multi-tiered architecture.
4Reliability
If client-side applications are updated to reflect business logic changes, then the system remains consistent, but installing and maintaining up-to-date applications on a large number of different clients is a difficult task
Solution Approach 1:
The EJB container acts as an intermediary that hosts the business logic server-side, eliminating the need to update client-side applications when business rules change. The container provides a stable interface to clients while allowing the underlying EJB components to be updated independently through server-side deployment mechanisms.
Solution Approach 2:
The patent extracts the business logic from the client application and places it in server-side EJB components managed by the EJB container. This extraction allows business logic to be updated independently on the server without affecting client applications, thereby maintaining system consistency while simplifying deployment.
Data Source
AI summary
A system and method are described for facilitating communication between a server and a client using a deploy callback system. In one embodiment, deploy listener is registered to receive status information regarding deployment of application or deploy operations relating to the deployment of the application. Such status information is provided to the deploy listener.