WAS Administrating Server Grouping for Auto-Scaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for auto-scaling web servers and Web Application Servers (WAS) face challenges in sharing sessions between multiple applications and managing new connections during scaling operations, particularly when separate WAS administrating servers are involved, leading to difficulties in determining which application service newly added servers or WAS should provide and which TCP connections to use.
Innovation Solution
A method where a WAS administrating server groups web servers and WAS into pairs to provide application services, allowing these pairs to be scaled independently, and manages sessions across multiple application services without requiring a new WAS administrating server, enabling seamless sharing of sessions and connections between different application services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate WAS administrating servers are used for different application services, then each service can be managed independently, but it becomes difficult to share sessions between applications and requires additional servers for scaling
Solution Approach 1:
The patent merges multiple application services into a single WAS administrating server by creating multiple service groups within one server. Each service group manages a specific application service with its own web servers and WAS instances, but all groups share the same administrating server infrastructure, enabling session sharing across applications while avoiding the need for multiple separate administrating servers.
Solution Approach 2:
The patent segments the single WAS administrating server into multiple service groups, where each group independently manages a specific application service. This segmentation allows each service to be configured and scaled independently while still benefiting from the shared session management capabilities of the unified administrating server.
2Productivity
If web servers and WAS are scaled out independently, then service capacity increases, but it becomes difficult to determine which TCP connections to use for newly added servers
Solution Approach 1:
The WAS administrating server acts as an intermediary that automatically manages TCP connections between web servers and WAS instances. When new servers are scaled out, the administrating server handles the connection establishment and routing, eliminating the need for manual configuration and making it easy to determine which connections to use.
Solution Approach 2:
The system implements feedback mechanisms where the WAS administrating server continuously monitors the status of web servers and WAS instances, and automatically adjusts connection routing based on current system state. This ensures that newly scaled servers are properly integrated into the connection topology without manual intervention.
Data Source
AI summary
A method for auto-scaling at least one web server and at least one WAS (Web Application Server) is provided. The method includes a WAS administrating server grouping, as a first service group, both at least one first web server and at least one first WAS, which are connected with each other to provide a first application service, and grouping, as a second service group, both at least one second web server and at least one second WAS, which are connected with each other to provide a second application service, to thereby create at least two groups each of which includes at least its corresponding pair of web server and WAS, and the WAS administrating server allowing each of the grouped pairs of the web servers and the WAS's to be scaled out or scaled in, independently, by a process of scaling-out or scaling-in.