Smart tool for enterprise-wide software integration and deployment
US-2019243742-A1 · Aug 8, 2019 · US
US11086757B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-11086757-B1 |
| Application number | US-201916438660-A |
| Country | US |
| Kind code | B1 |
| Filing date | Jun 12, 2019 |
| Priority date | Jun 12, 2019 |
| Publication date | Aug 10, 2021 |
| Grant date | Aug 10, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A mainframe deployment device for deploying code to a mainframe device in a stable, self-correcting manner is described. The mainframe deployment device is configured to receive a code section from the software management device, identify a set of valid sub-components from the code section using a dispatcher service associated with the dispatcher device, identify a set of elements in the code section identified for deployment, request the at least one testing service to perform at least one set of code diagnostics to determine whether the code section satisfies build requirements, attempt to create a deployment package from the code section, identify a production program running on the mainframe device, compare the production program to the deployment package to identify a set of synchronization errors, resolve the synchronization errors, and deploy the deployment package to the mainframe device upon resolving the set of synchronization errors.
Opening claim text (preview).
What is claimed is: 1. A mainframe deployment system for deploying code to a mainframe device in a stable, self-correcting manner, comprising: a software management device; a dispatcher device; at least one testing service; a mainframe device; and a mainframe deployment device including a processor and a memory device, wherein the processor is configured to: receive a code section from the software management device, wherein the code section includes a status identifier; upon determining that the status identifier is complete, identify a set of valid sub-components from the code section using a dispatcher service associated with the dispatcher device; upon determining that the identified set of valid sub-components are capable of creating a build, identify a set of elements in the code section identified for deployment; upon determining that the set of elements in the code section are deployable, request the at least one testing service to perform at least one set of code diagnostics to determine whether the code section satisfies build requirements; upon determining that the at least one set of code diagnostics satisfies a diagnostic goal for mainframe stability, create a deployment package from the code section; upon successfully creating the deployment package, transmit a cast request to perform a package casting process using the deployment package; upon determining that the package casting process succeeded, identify a production program running on the mainframe device; compare the production program to the deployment package to identify a set of synchronization errors; resolve the set of synchronization errors; and deploy the deployment package to the mainframe device upon resolving the set of synchronization errors. 2. The system of claim 1 , wherein the processor is further configured to: identify discrepancies between the deployment package and the production program; and upon determining that the discrepancies do not cause a failure, automatically resolve the set of synchronization errors and deploy the deployment package to the mainframe device. 3. The system of claim 1 , wherein the processor is further configured to: identify discrepancies between the deployment package and the production program; transmit a message to a system messaging device to request a synchronization resolution; upon receipt of the synchronization resolution indicating that the discrepancies are resolvable, resolve the set of synchronization errors based on the synchronization resolution; and deploy the deployment package to the mainframe device. 4. The system of claim 1 , wherein the processor is further configured to: perform a first code analysis of the code section to identify a code quality associated with the code section; identify a predefined threshold for code quality; and upon determining that the code section exceeds the predefined threshold, deploy the deployment package to the mainframe device. 5. The system of claim 1 , wherein the processor is further configured to: perform a first code coverage analysis of the code section to identify a code coverage score; identify a predefined threshold for code coverage; and upon determining that the code section exceeds the predefined threshold, deploy the deployment package to the mainframe device. 6. The system of claim 1 , wherein the processor is further configured to: transmit a message to a system messaging device to request an approval for deployment of the code section; and upon receiving the approval for deployment, deploy the deployment package to the mainframe. 7. The system of claim 1 , wherein the processor is further configured to: upon deployment of the deployment package, request the at least one testing service to perform a set of post-deployment testing to obtain a post-deployment testing score; identify a predefined threshold for the post-deployment testing score; and upon determining that the post-deployment testing score exceeds the predefined threshold, identifying the deployment as stable. 8. A mainframe deployment device for deploying code to a mainframe device in a stable, self-correcting manner, the mainframe deployment device including a processor and a memory device, the mainframe deployment device in communication with a software management device, a dispatcher device, at least one testing device, and a mainframe device, wherein the processor is configured to: receive a code section from the software management device, wherein the code section includes a status identifier; upon determining that the status identifier is complete, identify a set of valid sub-components from the code section using a dispatcher service associated with the dispatcher device; upon determining that the identified set of valid sub-components are capable of creating a build, identify a set of elements in the code section identified for deployment; upon determining that the set of elements in the code section are deployable, request the at least one testing service to perform at least one set of code diagnostics to determine whether the code section satisfies build requirements; upon determining that the at least one set of code diagnostics satisfies a diagnostic goal for mainframe stability, create a deployment package from the code section; upon successfully creating the deployment package, transmit a cast request to perform a package casting process using the deployment package; upon determining that the package casting process succeeded, identify a production program running on the mainframe device; compare the production program to the deployment package to identify a set of synchronization errors; resolve the set of synchronization errors; and deploy the deployment package to the mainframe device upon resolving the set of synchronization errors. 9. The mainframe deployment device of claim 8 , wherein the processor is further configured to: identify discrepancies between the deployment package and the production program; and upon determining that the discrepancies do not cause a failure, automatically resolve the set of synchronization errors and deploy the deployment package to the mainframe device. 10. The mainframe deployment device of claim 8 , wherein the processor is further configured to: identify discrepancies between the deployment package and the production program; transmit a message to a system messaging device to request a synchronization resolution; upon receipt of the synchronization resolution indicating that the discrepancies are resolvable, resolve the set of synchronization errors based on the synchronization resolution; and deploy the deployment package to the mainframe device. 11. The mainframe deployment device of claim 8 , wherein the processor is further configured to: perform a first code analysis of the code section to identify a code quality associated with the code section; identify a predefined threshold for code quality; and upon determining that the code section exceeds the predefined threshold, deploy the deployment package to the mainframe device. 12. The mainframe deployment device of claim 8 , wherein the processor is further configured to: perform a first code coverage analysis of the code section to identify a code coverage score; identify a predefined threshold for code coverage; and upon determining that the code section exceeds the predefined threshold, deploy the deployment package to the mainframe device. 13. The mainframe deployment device of claim 8 , wherein the processor is further configured to: transmit a message to a system messaging device to request an approval for deploy
Structural analysis for program understanding · CPC title
Incremental updates; Differential updates · CPC title
while running · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
for test results analysis · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.