# US 2023/0401046 A1 · Low-/no-code packaging of application based on artifacts and universal tags

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0401046 A1
- Document ID: US20230401046A1
- Status: Published application
- Kind: A1
- Application number: 17/839,787
- Filed: 2022-06-14
- Published: 2023-12-14
- Earliest claimed: 2022-06-14
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Yi Quan Zhou; Qiu Shi Wang
- Web page: https://patentgrep.com/patent/US20230401046A1

## CPC

- G06F 8/60: Software deployment
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 8/34: Graphical or visual programming
- G06F 8/36: Software reuse
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, systems, and computer-readable storage media for receiving, by an application studio, user input indicating two or more artifacts of an enterprise application developed using the application studio, generating, by an enterprise application artifact composer of the application studio, an enterprise application artifact as a universal tag that provides an abstract representation of the enterprise application, and during deployment of the enterprise application: retrieving the enterprise application artifact, determining a target runtime that the enterprise application is to be deployed to, determining a set of dependencies for each artifact of the enterprise application, and for any dependency in the set of dependencies that is absent from the target runtime, retrieving binary code of the dependency from a library to deploy the dependency to the target runtime.

## Claims

### Claim 1

A computer-implemented method for deploying enterprise applications to runtime environments, the method being executed by one or more processors and comprising:
receiving, by an application studio, user input indicating two or more artifacts of an enterprise application developed using the application studio;
generating, by an enterprise application artifact composer of the application studio, an enterprise application artifact as a universal tag that provides an abstract representation of the enterprise application; and
during deployment of the enterprise application:
retrieving the enterprise application artifact,
determining a target runtime that the enterprise application is to be deployed to,
determining a set of dependencies for each artifact of the enterprise application, and
for any dependency in the set of dependencies that is absent from the target runtime, retrieving binary code of the dependency from a library to deploy the dependency to the target runtime.

### Claim 2 (depends on 1)

The method of claim 1, wherein the enterprise application artifact is generated by the enterprise application artifact composer in response to user input to the application studio indicating a release of the enterprise application.

### Claim 3 (depends on 1)

The method of claim 1, wherein, for at least one artifact of the two or more artifacts, the enterprise application artifact comprises metadata indicating at least one dependency.

### Claim 4 (depends on 1)

The method of claim 1, wherein each dependency in the set of dependencies comprises an artifact.

### Claim 5 (depends on 1)

The method of claim 1, wherein each artifact of the two or more artifacts comprises one of a service and a component.

### Claim 6 (depends on 1)

The method of claim 1, wherein the enterprise application artifact comprises metadata indicating a central repository that stores the enterprise application.

### Claim 7 (depends on 1)

The method of claim 1, wherein the target runtime comprises one of a cloud runtime and a mobile runtime.

### Claim 8

A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for deploying enterprise applications to runtime environments, the operations comprising:
receiving, by an application studio, user input indicating two or more artifacts of an enterprise application developed using the application studio;
generating, by an enterprise application artifact composer of the application studio, an enterprise application artifact as a universal tag that provides an abstract representation of the enterprise application; and
during deployment of the enterprise application:
retrieving the enterprise application artifact,
determining a target runtime that the enterprise application is to be deployed to,
determining a set of dependencies for each artifact of the enterprise application, and
for any dependency in the set of dependencies that is absent from the target runtime, retrieving binary code of the dependency from a library to deploy the dependency to the target runtime.

### Claim 9 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein the enterprise application artifact is generated by the enterprise application artifact composer in response to user input to the application studio indicating a release of the enterprise application.

### Claim 10 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein, for at least one artifact of the two or more artifacts, the enterprise application artifact comprises metadata indicating at least one dependency.

### Claim 11 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein each dependency in the set of dependencies comprises an artifact.

### Claim 12 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein each artifact of the two or more artifacts comprises one of a service and a component.

### Claim 13 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein the enterprise application artifact comprises metadata indicating a central repository that stores the enterprise application.

### Claim 14 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein the target runtime comprises one of a cloud runtime and a mobile runtime.

### Claim 15

A system, comprising:
a computing device; and
a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for deploying enterprise applications to runtime environments, the operations comprising:
during deployment of an enterprise application:
retrieving an enterprise application artifact as a universal tag that provides an abstract representation of the enterprise application, the enterprise application artifact being generated by an enterprise application artifact composer of an application studio that, during development, receives user input indicating two or more artifacts of the enterprise application developed using the application studio,
determining a target runtime that the enterprise application is to be deployed to,
determining a set of dependencies for each artifact of the enterprise application, and
for a dependency in the set of dependencies that is absent from the target runtime, retrieving binary code of the dependency from a library to deploy the dependency to the target runtime.

### Claim 16 (depends on 15)

The system of claim 15, wherein the enterprise application artifact is generated by the enterprise application artifact composer in response to user input to the application studio indicating a release of the enterprise application.

### Claim 17 (depends on 15)

The system of claim 15, wherein, for at least one artifact of the two or more artifacts, the enterprise application artifact comprises metadata indicating at least one dependency.

### Claim 18 (depends on 15)

The system of claim 15, wherein each dependency in the set of dependencies comprises an artifact.

### Claim 19 (depends on 15)

The system of claim 15, wherein each artifact of the two or more artifacts comprises one of a service and a component.

### Claim 20 (depends on 15)

The system of claim 15, wherein the enterprise application artifact comprises metadata indicating a central repository that stores the enterprise application.
