US-12619483-B2 - System and method to automate discovery of middleware instances during installation of a failsafe middleware starting procedure framework

Abstract

An apparatus may comprise a memory communicatively coupled to a processor. The memory may be configured to store an installer script configured to install multiple middleware scripts in an admin server, and one or more installed middleware instances. The processor may be configured to trigger initiation of the installer script, install the middleware scripts over a predefined time period, determine whether the one or more installed middleware instances comprises an installed middleware instance, and determine whether an operation performed by the admin server is associated with the installed middleware instance in response to determining that the one or more installed middleware instances comprises the installed middleware instance. Further, the processor may be configured to generate a middleware flag indicating that the installed middleware instance is active, and generate multiple start-up files comprising a middleware instance corresponding to the installed middleware instance.

Inventors

• Rakesh Jain
• John David Weber

Assignees

• BANK OF AMERICA CORPORATION

Dates

Publication Date

20260505

Application Date

20230719

Claims (20)

1. 1 . An apparatus, comprising: a memory, configured to store: an installer script configured to install a plurality of middleware scripts in an admin server; and one or more installed middleware instances, each installed middleware instance being an operation performed by the admin server; and a processor communicatively coupled to the memory and configured to: trigger initiation of the installer script; install the plurality of middleware scripts over a predefined time period; determine whether the one or more installed middleware instances comprises a first installed middleware instance; in response to determining that the one or more installed middleware instances comprises the first installed middleware instance, determine whether a first operation performed by the admin server is associated with the first installed middleware instance; generate a first middleware flag indicating that the first installed middleware instance is active; and generate a plurality of start-up files comprising a first middleware instance corresponding to the first installed middleware instance.
2. 2 . The apparatus of claim 1 , wherein the processor is further configured to: determine whether the one or more installed middleware instances comprises a second installed middleware instance; and in response to determining that the one or more installed middleware instances comprises the second installed middleware instance, determine whether a second operation performed by the admin server is associated with the second installed middleware instance.
3. 3 . The apparatus of claim 2 , wherein the processor is further configured to: in response to determining that the second operation is associated with the second installed middleware instance, generate a second middleware flag indicating that the second installed middleware instance is active; and update the plurality of start-up files to comprise a second middleware instance corresponding to the second installed middleware instance.
4. 4 . The apparatus of claim 2 , wherein the processor is further configured to: in response to determining that the second operation is not associated with the second installed middleware instance, generate a second middleware flag indicating that the first installed middleware instance is inactive.
5. 5 . The apparatus of claim 1 , wherein the processor is further configured to: in response to determining that the one or more installed middleware instances do not comprise the first installed middleware instance, trigger completion of the installer script.
6. 6 . The apparatus of claim 1 , wherein: the admin server is communicatively coupled to one or more managed servers.
7. 7 . The apparatus of claim 1 , wherein: the installer script is triggered by a reboot operation of the apparatus.
8. 8 . A method, comprising: triggering initiation of an installer script configured to install a plurality of middleware scripts in an admin server; installing the plurality of middleware scripts over a predefined time period; determining whether one or more installed middleware instances comprises a first installed middleware instance of one or more installed middleware instances, each installed middleware instance being an operation performed by the admin server; in response to determining that the one or more installed middleware instances comprises the first installed middleware instance, determining whether a first operation performed by the admin server is associated with the first installed middleware instance; generating a first middleware flag indicating that the first installed middleware instance is active; and generating a plurality of start-up files comprising a first middleware instance corresponding to the first installed middleware instance.
9. 9 . The method of claim 8 , further comprising: determining whether the one or more installed middleware instances comprises a second installed middleware instance; and in response to determining that the one or more installed middleware instances comprises the second installed middleware instance, determining whether a second operation performed by the admin server is associated with the second installed middleware instance.
10. 10 . The method of claim 9 , further comprising: in response to determining that the second operation is associated with the second installed middleware instance, generating a second middleware flag indicating that the second installed middleware instance is active; and updating the plurality of start-up files to comprise a second middleware instance corresponding to the second installed middleware instance.
11. 11 . The method of claim 9 , further comprising: in response to determining that the second operation is not associated with the second installed middleware instance, generating a second middleware flag indicating that the first installed middleware instance is inactive.
12. 12 . The method of claim 8 , further comprising: in response to determining that the one or more installed middleware instances do not comprise the first installed middleware instance, triggering completion of the installer script.
13. 13 . The method of claim 8 , wherein: the admin server is communicatively coupled to one or more managed servers.
14. 14 . The method of claim 8 , wherein: the installer script is triggered by a reboot operation.
15. 15 . A non-transitory computer readable medium storing instructions that when executed by a processor cause the processor to: trigger initiation of an installer script configured to install a plurality of middleware scripts in an admin server; install the plurality of middleware scripts over a predefined time period; determine whether one or more installed middleware instances comprises a first installed middleware instance of one or more installed middleware instances, each installed middleware instance being an operation performed by the admin server; in response to determining that the one or more installed middleware instances comprises the first installed middleware instance, determine whether a first operation performed by the admin server is associated with the first installed middleware instance; generate a first middleware flag indicating that the first installed middleware instance is active; and generate a plurality of start-up files comprising a first middleware instance corresponding to the first installed middleware instance.
16. 16 . The non-transitory computer readable medium of claim 15 , wherein the processor is further caused to: determine whether the one or more installed middleware instances comprises a second installed middleware instance; and in response to determining that the one or more installed middleware instances comprises the second installed middleware instance, determine whether a second operation performed by the admin server is associated with the second installed middleware instance.
17. 17 . The non-transitory computer readable medium of claim 16 , wherein the processor is further caused to: in response to determining that the second operation is associated with the second installed middleware instance, generate a second middleware flag indicating that the second installed middleware instance is active; and update the plurality of start-up files to comprise a second middleware instance corresponding to the second installed middleware instance.
18. 18 . The non-transitory computer readable medium of claim 16 , wherein the processor is further caused to: in response to determining that the second operation is not associated with the second installed middleware instance, generate a second middleware flag indicating that the first installed middleware instance is inactive.
19. 19 . The non-transitory computer readable medium of claim 15 , wherein the processor is further caused to: in response to determining that the one or more installed middleware instances do not comprise the first installed middleware instance, trigger completion of the installer script.
20. 20 . The non-transitory computer readable medium of claim 15 , wherein: the admin server is communicatively coupled to one or more managed servers; and the installer script is triggered by a reboot operation.

Description

TECHNICAL FIELD The present disclosure relates generally to operation of a system configured to enable execution of middleware instances, and more specifically to a system and method to automate discovery of middleware instances during installation of a failsafe middleware starting procedure framework. BACKGROUND Middleware operations comprise communication and data management between operating systems and distributed applications running on operating systems. The distributed applications may require processing resources and memory resources to start. In some cases, middleware operations cannot be performed because a given application is not identified as part of a start-up process of a server executing the middleware operations. In other cases, middleware operations cannot be performed because the memory resources and the memory resources are not available during initiation of a given application. In these cases, the given application may be considered to be unreachable. SUMMARY OF THE DISCLOSURE In one or more embodiments, a system and the method enable reduce, prevent, or eliminate connectivity failures while a server gathers processing resources and memory resources to initiate a middleware instance. Middleware instances (e.g., middleware operations) comprise communication and data management between operating systems and distributed applications running on the operating systems. The middleware instances may be attempts to initiate implementation of the distributed applications. In some embodiments, the system and the method enable middleware instances to be performed by ensuring that a given application is identified as part of a start-up process of a server executing the middleware instances. In other embodiments, the system and the method enable middleware instances to be performed by ensuring that the processing resources and the memory resources are available during initiation of a given application. In this regard, the system and the method prevent the given application from being considered to be unreachable. Automate Discovery of Middleware Instances During Installation of a Failsafe Middleware Starting Procedure Framework In one or more embodiments, a system and a method are configured to automate discovery of middleware instances during installation of a failsafe middleware starting procedure framework. In particular, the system and the method are configured to automatically discover installed middleware instances as a middleware starting procedure framework is installed in an administration (admin) server. The system and the method are configured to generate operational parameters to check for installed instances currently configured in the admin server. In this regard, the method and the system reduce, prevent, or eliminate failures while enabling starting procedures for middleware instances. In particular, the system and the method trigger initiation of an installer script a first time a server is being programmed with the middleware starting procedure framework. The admin server may identify whether any installed instances are associated with active middleware instances in the admin server. Further, the system and the method may check for existing configuration of the admin server and products currently associated with the admin server. The admin server may generate multiple start-up files based at least in part upon results evaluating whether the admin server already comprises existing configuration to perform the middleware starting procedures and any middleware products associated to the middleware starting procedures in the network. In one or more embodiments, the system and the method described herein are integrated into a practical application of reducing, preventing, or eliminating negative impacts of missing middleware instances during start-up operations. For example, the system and the method automatically determine any installed middleware instances in an admin server and determine which of these instances are considered to be active in an event that the admin server is installing a starting framework. As a result, the system and the method may generate start-up files comprising middleware instances that are confirmed to be part of ongoing operations of the admin server. The results may then be compiled in multiple start-up files that account for all active middleware instances to initiate during the starting procedure. In some embodiments, significant human resources, processing resources, and memory resources may be saved when instances of the admin server are automatically determined as the starting procedure is installed and start-up files are generated. In some embodiments, the system and the method prevent the admin server from going into a hung state or from being unresponsive. In one or more embodiments, the system and method are directed to improvements in computer systems. Specifically, the system and the method reduce processor and memory usage in the admin server by