Abstract: An order management system comprises a middle tier and a computer-based automatic rule code generation system. The middle tier comprises a state transition engine that manages rule-based state transitions of trade orders for financial products from one state to a next state in progressions of the trade orders. The computer-based automatic rule code generation system: (i) receives a human-readable state transition file that specifies one or more state transition rules and a corresponding condition for each of the one or more state transition rules; and (ii) generates, at compile time, a configuration file that comprises rule code for the one or more state transition rules from the state transition file. The state transition engine runs the rule code in the configuration file at runtime to manage the state transitions for the trade orders.

Abstract: Computer systems and methods test applications of an enterprise computer system. The enterprise computer system comprises a test orchestration engine that is configured to receive a human-readable configuration file that comprises: a test script model that specifies testing activities for an application of the enterprise computer system; an application model that specifies attribute values for the application for the testing of the application; and a script model that specifies context parameters for the testing of the application. The test orchestration engine generates, at compile time, metadata code artifacts from the configuration file; and orchestrate, at run time, testing of the application based on the metadata code artifacts generated from the configuration file.

Abstract: An efficient reusable, extensible light weight framework statelessly orchestrates system activities in any application which involves a series of sequential or parallel set of activities involving computational logic, data retrieval and persistence services. Actual orchestration steps and activities and computational logic are specified into configuration files, separate from the orchestration engine itself, thereby eliminating the need to code for such logic and activities. The framework can eliminate the need to code business logic and orchestration of data retrieval services by externalizing them into configuration files, resulting in lower costs to implement, test and maintain such system during its lifespan.

Abstract: An order management system comprises a middle tier and a computer-based automatic rule code generation system. The middle tier comprises a state transition engine that manages rule-based state transitions of trade orders for financial products from one state to a next state in progressions of the trade orders. The computer-based automatic rule code generation system: (i) receives a human-readable state transition file that specifies one or more state transition rules and a corresponding condition for each of the one or more state transition rules; and (ii) generates, at compile time, a configuration file that comprises rule code for the one or more state transition rules from the state transition file. The state transition engine runs the rule code in the configuration file at runtime to manage the state transitions for the trade orders.

Abstract: A computer-implemented system and method to track a transaction that is executed by a series of applications in a workflow. Each application in the workflow generates an application log file that includes a standard header, which in turn includes a transaction ID associated with the transaction, an outcome associated with a step of the transaction executed by each of the applications, and a timestamp associated with the step of the transaction. The application log file with the header is received and stored by the computer system. The computer system can thereafter retrieve and display the entire transaction history for the transaction across all of the applications in response to a user query. The standard header is appended to the application log file and agnostic to the underlying technology used to implement the application system so that any transaction can be reconstructed end-to-end regardless of the form of the application system.

Abstract: Efficient, reusable, extensible light weight framework orchestrates discrete mainframe service calls as a single composite service call. The single composite call requires a single mainframe socket and the mainframe disaggregates the composite service call upon receipt to process the individual service calls therein, thereby allowing the mainframe to handle more services calls simultaneously. A similar framework orchestrates distributed service calls from a mainframe client.

Abstract: An efficient, light weight framework executes business rules for an asset class-agnostic order management system. The business rules are specified in metadata configuration files separated from the rules execution engine. The metadata utilized by the rules engine also includes entity model and instructions for stateless orchestration to be performed during the process of rules execution. This metadata is automatically generated from human readable artifacts that capture business rules, entity model and orchestration steps in an easy to understand format.

Abstract: An efficient reusable, extensible light weight framework statelessly orchestrates system activities in any application which involves a series of sequential or parallel set of activities involving computational logic, data retrieval and persistence services. Actual orchestration steps and activities and computational logic are specified into configuration files, separate from the orchestration engine itself, thereby eliminating the need to code for such logic and activities. The framework can eliminate the need to code business logic and orchestration of data retrieval services by externalizing them into configuration files, resulting in lower costs to implement, test and maintain such system during its lifespan.

Abstract: A computer-implemented system and method to track a transaction that is executed by a series of applications in a workflow. Each application in the workflow generates an application log file that includes a standard header, which in turn includes a transaction ID associated with the transaction, an outcome associated with a step of the transaction executed by each of the applications, and a timestamp associated with the step of the transaction. The application log file with the header is received and stored by the computer system. The computer system can thereafter retrieve and display the entire transaction history for the transaction across all of the applications in response to a user query. The standard header is appended to the application log file and agnostic to the underlying technology used to implement the application system so that any transaction can be reconstructed end-to-end regardless of the form of the application system.

Abstract: An efficient reusable, extensible light weight framework statelessly orchestrates system activities in any application which involves a series of sequential or parallel set of activities involving computational logic, data retrieval and persistence services. Actual orchestration steps and activities and computational logic are specified into configuration files, separate from the orchestration engine itself, thereby eliminating the need to code for such logic and activities. The framework can eliminate the need to code business logic and orchestration of data retrieval services by externalizing them into configuration files, resulting in lower costs to implement, test and maintain such system during its lifespan.

Abstract: A computer-implemented system and method to track a transaction that is executed by a series of applications in a workflow. Each application in the workflow generates an application log file that includes a standard header, which in turn includes a transaction ID associated with the transaction, an outcome associated with a step of the transaction executed by each of the applications, and a timestamp associated with the step of the transaction. The application log file with the header is received and stored by the computer system. The computer system can thereafter retrieve and display the entire transaction history for the transaction across all of the applications in response to a user query. The standard header is appended to the application log file and agnostic to the underlying technology used to implement the application system so that any transaction can be reconstructed end-to-end regardless of the form of the application system.

Abstract: Efficient, reusable, extensible light weight framework orchestrates discrete mainframe service calls as a single composite service call. The single composite call requires a single mainframe socket and the mainframe disaggregates the composite service call upon receipt to process the individual service calls therein, thereby allowing the mainframe to handle more services calls simultaneously. A similar framework orchestrates distributed service calls from a mainframe client.

Abstract: A data services framework workflow processing system and method is disclosed. The method includes receiving a request for data from a client and based on the request, determining a workflow to process the request. The method also includes based on the workflow, generating a plurality of backend calls. Additionally, the method includes based on the plurality of backend calls, selecting one or more data sources from a plurality of data sources. The method also includes transmitting one or more of the plurality of backend calls to the selected data sources and receiving, from each the selected data sources, a response to the plurality of backend calls.

Abstract: A data services framework visibility component is disclosed. A method includes receiving a request for data from a client and selecting, based at least in part on the request, a workflow to process the request. The method also includes selecting, based at least in part on the request, a visibility profile. The method also includes based on the request, generating a plurality of backend calls and based on the selected visibility profile, filtering the plurality of backend calls. Additionally, the method includes transmitting one or more of the plurality of filtered backend calls to one or more data sources and receiving, from each of the selected data sources, a response to the plurality of filtered backend calls. The method also includes transmitting the response to the client.

Abstract: A data services framework workflow processing system and method is disclosed. The method includes receiving a request for data from a client and based on the request, determining a workflow to process the request. The method also includes based on the workflow, generating a plurality of backend calls. Additionally, the method includes based on the plurality of backend calls, selecting one or more data sources from a plurality of data sources. The method also includes transmitting one or more of the plurality of backend calls to the selected data sources and receiving, from each the selected data sources, a response to the plurality of backend calls.

Abstract: A data services framework visibility component is disclosed. A method includes receiving a request for data from a client and selecting, based at least in part on the request, a workflow to process the request. The method also includes selecting, based at least in part on the request, a visibility profile. The method also includes based on the request, generating a plurality of backend calls and based on the selected visibility profile, filtering the plurality of backend calls. Additionally, the method includes transmitting one or more of the plurality of filtered backend calls to one or more data sources and receiving, from each of the selected data sources, a response to the plurality of filtered backend calls. The method also includes transmitting the response to the client.