Abstract: Services development/deployment for backend system integration includes metadata-based identification of assets of a backend system, and building metadata specifications as available constructs from which to develop services for deployment, each metadata specification corresponding to a given backend asset that uses a first data format and defining translations between the first data format and a second data format that is agnostic to selected service endpoints and endpoint deployment architecture(s) to provide agnostic development of the services, providing a development interface to a user, and obtaining a user-defined flow as a generic definition of a service agnostic to any specific service endpoint and endpoint deployment architecture on which the service is to be deployed.

Abstract: A method provides a server a request for server transaction processing, the request being a session request of an outer non-persistent session between a client and the server, the outer non-persistent session including the session request to initiate the outer non-persistent session and a session response to terminate the outer non-persistent session. The method includes, for each inner non-persistent session between the client and the server performed as part of a server transaction, receiving a session request from the server that initiates the inner non-persistent session and provides a response to a client request to process a corresponding first transaction portion, and providing a session response to the server that terminates the inner non-persistent session and provides a client request to process a corresponding second transaction portion. The method also includes receiving from the server the session response of the outer non-persistent session to terminate the outer non-persistent session.

Abstract: A method provides a server a request for server transaction processing, the request being a session request of an outer non-persistent session between a client and the server, the outer non-persistent session including the session request to initiate the outer non-persistent session and a session response to terminate the outer non-persistent session. The method includes, for each inner non-persistent session between the client and the server performed as part of a server transaction, receiving a session request from the server that initiates the inner non-persistent session and provides a response to a client request to process a corresponding first transaction portion, and providing a session response to the server that terminates the inner non-persistent session and provides a client request to process a corresponding second transaction portion. The method also includes receiving from the server the session response of the outer non-persistent session to terminate the outer non-persistent session.

Abstract: A method receives from a client a request for server transaction processing, the request being a session request of an outer non-persistent session between the client and a server, the outer non-persistent session including the session request and a session response, the session request to initiate the outer non-persistent session and the session response to terminate the outer non-persistent session. The method commences processing of a server transaction on the server, the server transaction to be processed in transaction portions. The method initiates inner non-persistent session(s), each including (i) a session request providing a response to a client request to process a corresponding first transaction portion, and (ii) a session response providing a client request to process a corresponding second transaction portion. Based on termination of a final inner non-persistent session, the method provides the session response of the outer non-persistent session to terminate the outer non-persistent session.

Abstract: A method receives from a client a request for server transaction processing, the request being a session request of an outer non-persistent session between the client and a server, the outer non-persistent session including the session request and a session response, the session request to initiate the outer non-persistent session and the session response to terminate the outer non-persistent session. The method commences processing of a server transaction on the server, the server transaction to be processed in transaction portions. The method initiates inner non-persistent session(s), each including (i) a session request providing a response to a client request to process a corresponding first transaction portion, and (ii) a session response providing a client request to process a corresponding second transaction portion. Based on termination of a final inner non-persistent session, the method provides the session response of the outer non-persistent session to terminate the outer non-persistent session.

Abstract: Development of interfaces for legacy programs. A system includes a client device displaying a series of screens output from a legacy program in a terminal emulator. The system further includes a tracking module logging activity in the terminal emulator in a trail file, and an analysis module adapted to analyze the trail file and produce, based on the analysis, a REST API based upon the analysis that supports a collection of different REST API calls corresponding to the series of screens output from the legacy program. The REST API is a stateless API utilized in a stateful manner in which each REST API call of the collection of REST API calls provides direct access to a corresponding screen of the series of screens.

Abstract: Method for autonomous safe emergency landing of a powered unmanned aerial vehicle (UAV) in the event of an engine failure. A landing approach trajectory is generated, including a downwind leg, initiating at an initiation point of the trajectory, an upwind leg, terminating at a selected touchdown point, and a U-turn leg, joining between the downwind leg and the upwind leg. The UAV is directed to the initiation point to follow the downwind leg. A glide ratio of the UAV is repeatedly determined based on current flight conditions. A current turning point is repeatedly determined along the downwind leg based on the determined glide ratio, the U-turn leg initiating at the current turning point. When the UAV arrives at the current turning point, the UAV is directed to follow the U-turn leg and the upwind leg, for landing the UAV at the selected touchdown point.

Abstract: Method for autonomous safe emergency landing of a powered unmanned aerial vehicle (UAV) in the event of an engine failure. A landing approach trajectory is generated, including a downwind leg, initiating at an initiation point of the trajectory, an upwind leg, terminating at a selected touchdown point, and a U-turn leg, joining between the downwind leg and the upwind leg. The UAV is directed to the initiation point to follow the downwind leg. A glide ratio of the UAV is repeatedly determined based on current flight conditions. A current turning point is repeatedly determined along the downwind leg based on the determined glide ratio, the U-turn leg initiating at the current turning point. When the UAV arrives at the current turning point, the UAV is directed to follow the U-turn leg and the upwind leg, for landing the UAV at the selected touchdown point.