# US 2014/0208169 A1 · Domain scripting language framework for service and system integration

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

- Number: US 2014/0208169 A1
- Document ID: US20140208169A1
- Status: Published application
- Kind: A1
- Application number: 13/744,882
- Filed: 2013-01-18
- Published: 2014-07-24
- Earliest claimed: 2013-01-18
- Assignees: Unisys Corporation
- Applicants: Unisys Corporation
- Inventors: Pushpa Reghunath Randhir; Srikantaiah Siddaraju
- Web page: https://patentgrep.com/patent/US20140208169A1

## CPC

- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06F 8/70: Software maintenance or management
- G06F 11/0778: {Dumping, i.e. gathering error/state information after a fault for later diagnosis}
- G06Q 10/0633: Workflow analysis
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods are disclosed herein to a computer-implemented method of executing an enterprise application comprising: receiving, by a computer, an external request for a service provided by a runtime engine of the enterprise application; selecting, by a computer, a script from a plurality of scripts saved on a database based on the external request; referencing, by the computer, one or more tags stored in a tag library saved on the database that are called by the script, wherein the tags in the tag library define commands of the plurality of scripts and call one or more granular services of the enterprise application; loading, by a computer, the selected script and the tags referenced by the selected script; and executing, by a computer, instructions of the script to provide the service requested by the external request, wherein the selected script is updated in the database after executing instructions of the script.

## Claims

### Claim 1

A computer-implemented method of fault management for an enterprise application comprising:
executing, by a computer, a script by a runtime engine to provide a workflow for the enterprise application, wherein the script includes a fault management feature;
determining, by a computer, that an error has occurred during the workflow specified by the script;
creating, by a computer, a snapshot of a state of the workflow and saving the snapshot in a database, wherein the snapshot is a placeholder of a point in the workflow before an error occurred and processed data of the workflow with any updates to the processed data that occurred during or after the error removed;
stopping, by a computer, the workflow specified by the script; and
moving, by a computer, the snapshot into a fault queue.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the fault management feature may be included in a tag library and referenced by the runtime engine before executing the workflow specified by the script.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, after stopping the workflow of the script, retrying, by a computer, the command specified by the script where the error occurred a predetermined number of times.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, further comprising:
identifying, by a computer, faulty equipment by determining that fault messages are commonly occurring at one point in the workflow.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, further comprising:
resuming, by a computer, the workflow specified by the script after remedying the error from placeholder of the snapshot.

### Claim 6

A computer program product for executing a fault management feature of an enterprise application comprising a non-transient computer readable medium having a computer readable program, wherein the computer readable program includes a runtime engine that when executed on a processor causes a computer to:
execute a script by a runtime engine to provide a workflow for the enterprise application, wherein the script includes a fault management feature;
determine that an error has occurred during the workflow specified by the script;
create a snapshot of a state of the workflow and saving the snapshot in a database, wherein the snapshot is a placeholder of a point in the workflow before the error occurred and processed data of the workflow with any updates to the processed data that occurred during or after the error removed;
stop the workflow specified by the script; and
move the snapshot into a fault queue.

### Claim 7 (depends on 6)

The computer program product of claim 6, wherein the fault management feature may be included in a tag library stored in a database and referenced by the runtime engine before executing the workflow specified by the script.

### Claim 8 (depends on 6)

The computer program product of claim 6, after the workflow of the script is stopped, retry the command specified by the script where the error occurred a predetermined number of times.

### Claim 9 (depends on 6)

The computer program product of claim 6, further comprising:
identify, faulty equipment by determining that fault messages are commonly occurring at one point in the workflow.

### Claim 10 (depends on 6)

The computer program product of claim 6, further comprising:
resume the workflow specified by the script after remedying the error from the snapshot.

### Claim 11

A fault management system comprising:
a processor configured to execute a script having a fault management feature to provide a workflow for the enterprise application, determine that an error has occurred during the workflow specified by the script; create a snapshot, saving the snapshot in a database, stop the workflow of the script, and move the snapshot into a fault queue;
the database connected to the processor configured to save the snapshot of a state of a workflow in a fault queue, wherein the snapshot is a placeholder of a point in the workflow before an error occurred and processed data of the workflow with any updates to the processed data that occurred during or after the error removed; and
a computer readable medium used by the processor to execute commands of the script.

### Claim 12 (depends on 11)

The system of claim 11, wherein the fault management feature may be included in a tag library stored in the database and referenced by the processor before executing the workflow specified by the script.

### Claim 13 (depends on 11)

The system of claim 11, wherein the processor is further configured to retry the command specified by the script where the error occurred a predetermined number of times.

### Claim 14 (depends on 11)

The computer program product of claim 11, wherein the processor is further configured to resume the workflow specified by the script after remedying the error from the snapshot.
