Flow Template Manager Automates External Service Deployment

Solution Overview

Problem

In visual programming tools for application software development, developers face inefficiencies when using external services due to the need for manual deployment and configuration of invoke nodes, which increases the development workload as the number of external services grows.

Innovation Solution

A system is established that integrates a flow template manager with a service deployment manager to automate the deployment of external services, where the invocation destination endpoint is set within the flow template, reducing the developer's preparation load by handling service deployment and configuration automatically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If developers manually deploy and configure external services for each invoke node, then service functionality is achieved, but development workload increases with the number of external services

Engineering Contradiction:

Improvedevelopment efficiencyVSAvoidpreparation work load

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system enables self-service by allowing the flow template to automatically trigger service deployment and configuration. When a flow template is downloaded, the system automatically deploys the required external services and configures the invoke nodes with the correct endpoint information, eliminating the need for manual developer intervention in service deployment tasks.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by deploying external services and configuring invoke nodes in advance when the flow template is downloaded, rather than requiring manual configuration at the time of use. The service deployment and endpoint configuration are prepared beforehand, so developers can directly use the flows without additional setup work.

Inventive Principle:

Principle #10Preliminary action

2Ease of operation

If developers manually configure invocation destination endpoints for each external service, then service integration is achieved, but time consumption increases

Engineering Contradiction:

Improveservice configuration easeVSAvoidpreparation time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The system enables self-service by allowing the flow template to automatically trigger service deployment and configuration. When a flow template is downloaded, the system automatically deploys the required external services and configures the invoke nodes with the correct endpoint information, eliminating the need for manual developer intervention in service deployment tasks.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by deploying external services and configuring invoke nodes in advance when the flow template is downloaded, rather than requiring manual configuration at the time of use. The service deployment and endpoint configuration are prepared beforehand, so developers can directly use the flows without additional setup work.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If the number of external services increases, then application functionality improves, but developer preparation workload increases proportionally

Engineering Contradiction:

Improveapplication functionalityVSAvoiddevelopment efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system enables self-service by allowing the flow template to automatically trigger service deployment and configuration. When a flow template is downloaded, the system automatically deploys the required external services and configures the invoke nodes with the correct endpoint information, eliminating the need for manual developer intervention in service deployment tasks.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system achieves universality by creating a general mechanism that handles service deployment and configuration automatically for any external service. The flow template system is designed to work with multiple different external services without requiring different manual configuration processes, making the solution applicable to diverse service integration scenarios.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11327724B2System and method that support application software development

Publication Date: 2022.05.10 HITACHI LTD

AI summary

When flow data of flow is to be downloaded from a flow template manager to a flow editor, a system receives a first request to deploy an external service corresponding to an invoke node in the flow, and transmits a second request to deploy an external service identified by the first request to a service deployment manager associated with a site corresponding to the external service. The service deployment manager deploys an external service identified by the second request on a service execution platform at the site, and returns a response associated with an invocation destination end point corresponding to the external service. The system returns a first response associated with an invocation destination end point set to a property of the invoke node by the flow template manager to a transmission source of the first request.