Abstract: An embodiment identifies, by a deployment restart engine, a change in a configuration from a first version to a second version. The embodiment determines, by the deployment restart engine, based on the change, whether to restart a deployment associated with the configuration. The embodiment determines, by the deployment restart engine, a deployment dependency associated with the deployment. The embodiment restarts, by the deployment restart engine, responsive to a determination to restart the deployment, based on the deployment dependency, the deployment.

Abstract: Contactless payment data can be received from a mobile device via a contactless payment terminal. Responsive to receiving the contactless payment data from the mobile device, a token can be communicated to the mobile device via the contactless payment terminal, the token configured to be processed by the mobile device to initiate a particular communication functionality by the mobile device.

Abstract: Contactless payment data can be received from a mobile device via a contactless payment terminal. Responsive to receiving the contactless payment data from the mobile device, a token can be communicated to the mobile device via the contactless payment terminal, the token configured to be processed by the mobile device to initiate a particular communication functionality by the mobile device.

Abstract: A method for integration-testing a microservices-based application is performed by an automated software-testing system by using mock software entities. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: A computer obtains an integration document comprising integration instructions that, when executed, causes two or more software applications to interact to perform an integration task. The computer determines, from the integration instructions of the integration document, task information representative of at least the integration task. The computer generates, based on the task information, a conversation databank entry for a natural language interface, wherein the conversation databank entry is usable by the natural language interface to determine whether a user desires the integration task to be performed, by processing the conversation databank entry and a natural language input provided by the user to the natural language interface.

Abstract: Method and system are provided for generating a chatbot interface for an application programming interface (API) that interacts with networked applications. The method may include: receiving as an input a definition document for an API that interacts with networked applications and parsing the definition document to identify intents and entities and obtain examples of the identified intents and entities. The method may convert the definition document to a chatbot data structure including: extracting the intents and entities and their relationship to objects and fields in the API from the definition document; and training the chatbot data structure with the example intents and entities to generate a conversation specification in the chatbot data structure. The method may then generate a chatbot interface for the API.

Abstract: The present invention is a method and system for an application server to process failed events of a predetermined software flow. An event generator generates an event to include event data and a related processing flow of a software application which processes the event. Each processing flow has a unique flow ID. An event queue is populated with events, and the processing flow is processed by an event processor. When an event fails, the application server deletes the event and its related processing flow from the event queue, then inserts and links the failed event, its related software application and processing flow, and one or more reasons for failure into a failed event queue.

Abstract: A first search request is received. Keywords of the first search request is identified. A request in a protocol for the first search request is transmitted to a web service. A response in the protocol for the first search request is received from the web service. Whether the first search quest is similar to a previously submitted search request, is determined. Responsive to determining that the first search request is similar to the previously submitted search request, the protocol response is modified to include contact information of a user that previously submitted the similar search request. The modified protocol response is transmitted to the client computer system from which the first search request originated.

Abstract: A computer obtains an integration document comprising integration instructions that, when executed, causes two or more software applications to interact to perform an integration task. The computer determines, from the integration instructions of the integration document, task information representative of at least the integration task. The computer generates, based on the task information, a conversation databank entry for a natural language interface, wherein the conversation databank entry is usable by the natural language interface to determine whether a user desires the integration task to be performed, by processing the conversation databank entry and a natural language input provided by the user to the natural language interface.

Abstract: A method for integration-testing a microservices-based application is performed by an automated software-testing system by using mock software entities. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: Automated software-testing systems and computer program products use mock software entities to perform integration testing on a microservices-based application. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: A method for integration-testing a microservices-based application is performed by an automated software-testing system by using mock software entities. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: Contactless payment data can be received from a mobile device via a contactless payment terminal. Responsive to receiving the contactless payment data from the mobile device, a token can be communicated to the mobile device via the contactless payment terminal, the token configured to be processed by the mobile device to initiate a particular communication functionality by the mobile device.

Abstract: A first search request is received. Keywords of the first search request is identified. A request in a protocol for the first search request is transmitted to a web service. A response in the protocol for the first search request is received from the web service. Whether the first search quest is similar to a previously submitted search request, is determined. Responsive to determining that the first search request is similar to the previously submitted search request, the protocol response is modified to include contact information of a user that previously submitted the similar search request. The modified protocol response is transmitted to the client computer system from which the first search request originated.

Abstract: Contactless payment data can be received from a mobile device via a contactless payment terminal. Responsive to receiving the contactless payment data from the mobile device, a token can be communicated to the mobile device via the contactless payment terminal, the token configured to be processed by the mobile device to initiate a particular communication functionality by the mobile device.

Abstract: Automated software-testing systems and computer program products use mock software entities to perform integration testing on a microservices-based application. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system. The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: A method for integration-testing a microservices-based application is performed by an automated software-testing system by using mock software entities. The mock entities emulate the behavior of other microservices or external software applications that would normally interact with the tested microservices in a production environment. The mock entities are managed by a mock server that communicates with the test system through a messaging system The mock server determines how the mock entities should respond to the tested application's service requests by referring to test guidelines stored in a behavior store. During testing, the test system dynamically updates the behavior store in response to the tested application's service requests and to other indicators of the current state of the tested application. If the tested application interacts with the mock entities during the test as expected, the test system deems the application to have passed the integration test.

Abstract: Method and system are provided for generating a chatbot interface for an application programming interface (API) that interacts with networked applications. The method may include: receiving as an input a definition document for an API that interacts with networked applications and parsing the definition document to identify intents and entities and obtain examples of the identified intents and entities. The method may convert the definition document to a chatbot data structure including: extracting the intents and entities and their relationship to objects and fields in the API from the definition document; and training the chatbot data structure with the example intents and entities to generate a conversation specification in the chatbot data structure. The method may then generate a chatbot interface for the API.

Abstract: The present invention is a method and system for an application server to process failed events of a predetermined software flow. An event generator generates an event to include event data and a related processing flow of a software application which processes the event. Each processing flow has a unique flow ID. An event queue is populated with events, and the processing flow is processed by an event processor. When an event fails, the application server deletes the event and its related processing flow from the event queue, then inserts and links the failed event, its related software application and processing flow, and one or more reasons for failure into a failed event queue.

Abstract: A first search request is received. Keywords of the first search request is identified. A request in a protocol for the first search request is transmitted to a web service. A response in the protocol for the first search request is received from the web service. Whether the first search quest is similar to a previously submitted search request, is determined. Responsive to determining that the first search request is similar to the previously submitted search request, the protocol response is modified to include contact information of a user that previously submitted the similar search request. The modified protocol response is transmitted to the client computer system from which the first search request originated.