Persistent Authorized Server Address Space via XML Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of managing multiple service address-spaces in a mainframe environment, coupled with the need for flexible software development and efficient software updates, is exacerbated by the tight coupling of service address-space hosting and authorization functions with specific product releases, leading to management challenges and software maintenance complexities.
Innovation Solution
A method and system for dynamically initializing and hosting authorized server address space functions using a generic XML protocol, allowing unauthorized requestors to access authorized services by parsing product definition documents and creating unique identifiers for software products, thereby decoupling the service address-space from specific application service functions and enabling flexible management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If service address-spaces are tightly coupled to specific product releases, then authorization functions can be properly controlled, but management complexity increases and software updates become difficult
Solution Approach 1:
The patent segments the service address-space into a persistent authorized host (ASAS) and transient unauthorized requestors. The ASAS maintains authorization control while requestors are dynamically created and destroyed based on software releases, eliminating the need to couple the entire service address-space to each release cycle.
Solution Approach 2:
The ASAS acts as an intermediary between the authorized environment and unauthorized requestors. It receives requests from unauthorized components, processes them through authorized channels, and returns results, thereby maintaining authorization control while allowing flexible software updates.
2Adaptability or versatility
If multiple service address-spaces are propagated for different product releases, then each can be independently managed, but the overall system complexity increases
Solution Approach 1:
The patent merges multiple service address-space instances into a single persistent ASAS. Instead of having separate address-spaces for each product release, the ASAS dynamically creates and manages unauthorized requestor address-spaces as needed, reducing overall system complexity while maintaining independent management capabilities.
Solution Approach 2:
The persistent ASAS serves multiple functions: it hosts authorized environment services, manages unauthorized requestors, processes requests from multiple product releases, and maintains authorization control. This universal approach eliminates the need for separate specialized address-spaces for each function.
3Reliability
If service address-spaces are tightly coupled to product releases, then authorization is maintained, but software updates and deployments become rigid
Solution Approach 1:
The patent introduces dynamics by making the requestor address-spaces transient rather than persistent. The ASAS dynamically creates address-spaces for unauthorized requestors when needed and destroys them when not needed, allowing flexible software updates while maintaining authorization through the persistent ASAS.
Solution Approach 2:
The ASAS is pre-configured with authorization credentials and RACF security settings before software releases are deployed. This preliminary setup allows the system to maintain authorization control while accommodating subsequent software updates without requiring reconfiguration of the authorized environment.
Data Source
AI summary
Disclosed are systems and methods to provide a persistent authorized server address space (ASAS). The ASAS can host components from product suites that are not able to execute in an authorized state. To host other product's components, the ASAS receives “messages” from the unauthorized product components in the form of a generic eXtensible Markup Language (XML) protocol. These messages may request product initialization/administration or performance of a function by the ASAS on behalf of the requesting product. Security constraints are also provided to ensure system and data integrity. Further, the ASAS is not tightly coupled to any requesting product so that flexibility of product update or update to the ASAS itself may not be unnecessarily constrained.