Abstract: Embodiments facilitate testing of software functions, by elaborating upon a small volume test sample originally provided by a developer. Where the original test sample is determined to be numerical, embodiments perform repetition techniques to generate corpuses of test data of varying scope representing operation over different timescales. For original test samples of greater complexity (e.g., including text and/or hierarchical output states of the software function), embodiments select a relevant Machine Learning (ML) model and apply that ML model to generate the corpuses of test data. These are then available for loading to measure one or more performance parameters (e.g., runtime, memory consumption; processing consumption; bandwidth) of the software function. Broadly reported non-linear behavior of performance parameter(s) may reveal lack of suitability of the generated data corpuses for testing. More specific non-linear behavior may indicate failure of the software function to pass certain tests.

Abstract: The present disclosure pertains to validation of runtime objects for a software deployment using a certificate. After creating the runtime objects during a build process, a certificate may be generated based on the runtime objects. The certificate may include a fingerprint of the runtime objects that may be used before deployment to determine whether the runtime objects have been changed. Before deployment, the runtime objects and the certificate may be obtained and the certificate may be validated. In addition, the runtime objects may be validated using the fingerprint included in the certificate. For instance, the fingerprint may be re-generating based on the runtime objects for deployment. The runtime objects may be validated by comparing the re-generated fingerprint to the fingerprint in the certificate. The runtime objects may be deployed if the certificate and the runtime objects are valid.

Abstract: Software User Assistance (UA) is afforded from captured User Interface (UI) screen images, with reference to persisted Machine Learning (ML) models. The captured screen images are processed—e.g., using rasterization, Optical Character Recognition (OCR), and/or establishment of a coordinate system—with individual UI elements being determined therefrom. Referencing the persisted ML models, the software application/application state for the captured image is identified. UA data relevant to that application/application state is generated from the model, and then provided to the user (e.g., in a text box overlying the UI screen). Through the capture and processing of UI screen images, embodiments afford a homogenous UA experience for installation, maintenance, and/or upgrade of heterogeneous members of a larger overall landscape, over software lifecycles. Embodiments may be deployed locally on a frontend computer, in order to avoid exporting UI images due to privacy and/or security concerns.

Abstract: Software User Assistance (UA) is afforded from captured User Interface (UI) screen images, with reference to persisted Machine Learning (ML) models. The captured screen images are processed—e.g., using rasterization, Optical Character Recognition (OCR), and/or establishment of a coordinate system—with individual UI elements being determined therefrom. Referencing the persisted ML models, the software application/application state for the captured image is identified. UA data relevant to that application/application state is generated from the model, and then provided to the user (e.g., in a text box overlying the UI screen). Through the capture and processing of UI screen images, embodiments afford a homogenous UA experience for installation, maintenance, and/or upgrade of heterogeneous members of a larger overall landscape, over software lifecycles. Embodiments may be deployed locally on a frontend computer, in order to avoid exporting UI images due to privacy and/or security concerns.

Abstract: Embodiments facilitate testing of software functions, by elaborating upon a small volume test sample originally provided by a developer. Where the original test sample is determined to be numerical, embodiments perform repetition techniques to generate corpuses of test data of varying scope representing operation over different timescales. For original test samples of greater complexity (e.g., including text and/or hierarchical output states of the software function), embodiments select a relevant Machine Learning (ML) model and apply that ML model to generate the corpuses of test data. These are then available for loading to measure one or more performance parameters (e.g., runtime, memory consumption; processing consumption; bandwidth) of the software function. Broadly reported non-linear behavior of performance parameter(s) may reveal lack of suitability of the generated data corpuses for testing. More specific non-linear behavior may indicate failure of the software function to pass certain tests.

Abstract: Methods, systems, and computer-readable storage media for receiving a record including a set of attributes, each attribute having an attribute value, the record representing automatic execution of an IT process within a managed system, retrieving a model representing historical executions of the IT process and including a set of distribution parameters associated with a first type of attribute and a set of probability distributions associated with a second type of attribute, determining, for a first attribute, a first score based on distribution parameters and a value, determining, for a second attribute, a second score based on a probability distribution and a value, the second attribute being of the second type of attribute, and selectively indicating that the IT process is anomalous based on an outlier score.

Abstract: A method may include receiving, from a first client, a first message. The first message may be matched to a second user based on a similarity between a first keyword included in the first message and a second keyword included in a profile of a second user. The first keyword may be determined to be similar to the second keyword based on a distance between a first vector representation of the first keyword and a second vector representation of the second keyword not exceeding a threshold value. In response to the first message being matched with the second user, the first message may be sent to a second client associated with the second user. In response to receiving, from the second client, a second message responsive to the first message, the second message may be sent to the first client. Related systems and articles of manufacture are also provided.

Abstract: Embodiments offer early assessment of upgrade compliance checking upon software landscape production data, prior to actually executing a full impact analysis. In a pre-transport phase, discrete upgrade compliance checks are run and corresponding reports returned to individual developers. In a transport phase, batches of combined compliance checks (bundled into released transports) are run and corresponding reports returned to higher level users. According to certain embodiments, pre-transport and/or transport compliance checking is performed upon landscape production data condensed to a bi-value states. Such condensing can desirably reduce stored data volumes and impart security. According to some embodiments, pre-transport and/or transport compliance checking is performed upon production data merged across multiple landscapes. This avoids storing redundant upgrade check data.

Abstract: The present disclosure pertains to validation of runtime objects for a software deployment using a certificate. After creating the runtime objects during a build process, a certificate may be generated based on the runtime objects. The certificate may include a fingerprint of the runtime objects that may be used before deployment to determine whether the runtime objects have been changed. Before deployment, the runtime objects and the certificate may be obtained and the certificate may be validated. In addition, the runtime objects may be validated using the fingerprint included in the certificate. For instance, the fingerprint may be re-generating based on the runtime objects for deployment. The runtime objects may be validated by comparing the re-generated fingerprint to the fingerprint in the certificate. The runtime objects may be deployed if the certificate and the runtime objects are valid.

Abstract: The present disclosure pertains to validation of runtime objects for a software deployment using a certificate. After creating the runtime objects during a build process, a certificate may be generated based on the runtime objects. The certificate may include a fingerprint of the runtime objects that may be used before deployment to determine whether the runtime objects have been changed. Before deployment, the runtime objects and the certificate may be obtained and the certificate may be validated. In addition, the runtime objects may be validated using the fingerprint included in the certificate. For instance, the fingerprint may be re-generating based on the runtime objects for deployment. The runtime objects may be validated by comparing the re-generated fingerprint to the fingerprint in the certificate. The runtime objects may be deployed if the certificate and the runtime objects are valid.

Abstract: Embodiments relate to an incident handling system for individual components of an overall software system. In particular, an engine receives error data information from a source of error information in a software component. That error information source may comprise a log entry, a formal error message, an exception, or a system crash. In response, the engine queries an underlying metadata description of the software system to receive a query result with additional metadata (e.g., unique artifact identifier, name) relevant to the error. Analysis of the error data and error metadata allows the engine to create an incident that is dispatched to an existing error tracking system, for support ticket creation and handling by the appropriate party. Adapter(s) allow the incident handling system to convert error data into generic form for search/analysis, and then to convert the incident information back into the specific format expected by the existing error tracking system.

Abstract: Methods, systems, and computer-readable storage media for receiving a record including a set of attributes, each attribute having an attribute value, the record representing automatic execution of an IT process within a managed system, retrieving a model representing historical executions of the IT process and including a set of distribution parameters associated with a first type of attribute and a set of probability distributions associated with a second type of attribute, determining, for a first attribute, a first score based on distribution parameters and a value, determining, for a second attribute, a second score based on a probability distribution and a value, the second attribute being of the second type of attribute, and selectively indicating that the IT process is anomalous based on an outlier score.

Abstract: Methods, systems, and computer-readable storage media for receiving, by a personal digital operation assistant (Pedoa) system, user input, processing, by the Pedoa system, the user input to determine an intent and one or more entities related to at least a portion of a landscape, transmitting, by a dispatcher of the Pedoa system, a request to one or more services of the Pedoa system based on the intent and the one or more entities, receiving, by the dispatcher, one or more responses from the one or more services of the Pedoa system, each response being responsive to the request, and providing, by the Pedoa system, output data to a user through one or more user interfaces (UIs), the output data representative of activity of one or more components within the landscape.

Abstract: In some embodiments, a logging framework reserves space in an in-memory storage for a log entry upon receiving a first function call from an application being executed. Upon receiving a second function call from the application being executed, the framework writes the log entry in the space in the in-memory storage. Upon receiving a third function call from the application being executed, the framework selects a configuration for the application and comparing an indicator that is generated based on the executing of the application to the configuration. When the indicator meets a condition of the configuration, the framework copies the log entry from the space in the in-memory storage to a persistent storage space. The log entry is deleted from the space in the in-memory storage at a time after performing the comparing.

Abstract: Embodiments offer early assessment of upgrade compliance checking upon software landscape production data, prior to actually executing a full impact analysis. In a pre-transport phase, discrete upgrade compliance checks are run and corresponding reports returned to individual developers. In a transport phase, batches of combined compliance checks (bundled into released transports) are run and corresponding reports returned to higher level users. According to certain embodiments, pre-transport and/or transport compliance checking is performed upon landscape production data condensed to a bi-value states. Such condensing can desirably reduce stored data volumes and impart security. According to some embodiments, pre-transport and/or transport compliance checking is performed upon production data merged across multiple landscapes. This avoids storing redundant upgrade check data.

Abstract: The present disclosure pertains to validation of runtime objects for a software deployment using a certificate. After creating the runtime objects during a build process, a certificate may be generated based on the runtime objects. The certificate may include a fingerprint of the runtime objects that may be used before deployment to determine whether the runtime objects have been changed. Before deployment, the runtime objects and the certificate may be obtained and the certificate may be validated. In addition, the runtime objects may be validated using the fingerprint included in the certificate. For instance, the fingerprint may be re-generating based on the runtime objects for deployment. The runtime objects may be validated by comparing the re-generated fingerprint to the fingerprint in the certificate. The runtime objects may be deployed if the certificate and the runtime objects are valid.

Abstract: Embodiments offer early assessment of upgrade compliance checking upon software landscape production data, prior to actually executing a full impact analysis. In a pre-transport phase, discrete upgrade compliance checks are run and corresponding reports returned to individual developers. In a transport phase, batches of combined compliance checks (bundled into released transports) are run and corresponding reports returned to higher level users. According to certain embodiments, pre-transport and/or transport compliance checking is performed upon landscape production data condensed to a bi-value states. Such condensing can desirably reduce stored data volumes and impart security. According to some embodiments, pre-transport and/or transport compliance checking is performed upon production data merged across multiple landscapes. This avoids storing redundant upgrade check data.

Abstract: Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives, from an application, a request to schedule a notification. The program further generates a pending notification. The program also stores the pending notification in a queue. The program further periodically iterates through the queue to check whether an expiration time of the pending notification has elapsed. Upon determining that the expiration time of the pending notification has elapsed, the program also deletes the pending notification from the queue without processing the pending notification. Upon receiving from the application a second set of interactions performed on the application that matches the defined set of interactions specified in the pending notification, the program further processes the pending notification by sending the recipient specified in the pending notification a notification comprising the message specified in the pending notification.

Abstract: Embodiments offer early assessment of upgrade compliance checking upon software landscape production data, prior to actually executing a full impact analysis. In a pre-transport phase, discrete upgrade compliance checks are run and corresponding reports returned to individual developers. In a transport phase, batches of combined compliance checks (bundled into released transports) are run and corresponding reports returned to higher level users. According to certain embodiments, pre-transport and/or transport compliance checking is performed upon landscape production data condensed to a bi-value states. Such condensing can desirably reduce stored data volumes and impart security. According to some embodiments, pre-transport and/or transport compliance checking is performed upon production data merged across multiple landscapes. This avoids storing redundant upgrade check data.

Abstract: A method may include receiving, from a first client, a first message. The first message may be matched to a second user based on a similarity between a first keyword included in the first message and a second keyword included in a profile of a second user. The first keyword may be determined to be similar to the second keyword based on a distance between a first vector representation of the first keyword and a second vector representation of the second keyword not exceeding a threshold value. In response to the first message being matched with the second user, the first message may be sent to a second client associated with the second user. In response to receiving, from the second client, a second message responsive to the first message, the second message may be sent to the first client. Related systems and articles of manufacture are also provided.