Job Execution System Agent Name Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing job execution systems face challenges in secure bidirectional communication between cloud and on-premises environments, particularly in multi-on-premises setups where agent identification is ambiguous, leading to performance issues due to frequent name changes and IP address checks.
Innovation Solution
A job execution system utilizing on-premises and cloud-side DNS servers, relay servers, and logical name management tables to establish and manage connections securely, allowing for job registration, start, and completion notifications through relay servers, ensuring accurate routing and minimizing performance impact.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If relay servers are used to transfer communication between cloud and on-premises sides, then security is improved, but communication efficiency deteriorates due to additional routing steps
Solution Approach 1:
The patent introduces relay servers as intermediary components between the cloud-side and on-premises-side systems. The cloud-side relay server receives notifications from the job management manager server and forwards them to the on-premises relay server, which then delivers them to the appropriate job execution agent. This intermediary mechanism enables secure communication through controlled relay points while maintaining system functionality.
2Adaptability or versatility
If dummy addresses are set for IP addresses in communication content to handle same logical names, then communication between hosts with same names is enabled, but transfer performance deteriorates due to frequent checking and changing of logical names
Solution Approach 1:
The patent performs preliminary actions by establishing the relay server connection infrastructure and configuring the notification forwarding rules before job executions occur. The cloud-side relay server is pre-configured with the job management manager server's address, and the on-premises relay server is pre-configured with agent addresses. This eliminates the need for frequent checking and changing of logical names during job execution, as the relay servers maintain stable routing relationships.
3Ease of operation
If fixed transfer destination is used on on-premises side, then communication is simplified, but ability to determine specific agent deteriorates in multi-on-premises environment
Solution Approach 1:
The patent applies local quality by enabling the on-premises relay server to identify and route notifications to specific agents based on their unique identifiers. The relay server examines the notification content to determine the target agent's address and forwards the notification accordingly. This allows fixed transfer destination configuration while maintaining precise agent identification capability through intelligent routing at the relay server.
Data Source
AI summary
It is made possible to realize bidirectional communication safely on the cloud side, and on-premises side in a job execution system.It is checked whether or not there is an agent with the same logical name at time of agent registration. In a case that there is the same logical name, transfer performance required of each agent is checked, and communication is performed by rewriting a logical name during transfer by using an existing logical name for an agent required of the highest transfer performance, and using a logical name which is a new unique alias for the other agent.