Abstract: The present disclosure relates to software, computer systems, and computer implemented methods for providing centralized process integration (PI) domain alert monitoring. One process includes identifying at least one alert rule at a central rules repository, the at least one alert rule associated with at least one message inter-communication within a process integration (PI) domain, where the PI domain includes at least one PI component, and where the message inter-communications within the PI domain occur between PI components. At least one alert consumer registration associated with at least one alert consumer system for an identified alert rule is identified. Information associated with the at least one identified alert rule from the central rules repository is distributed to the corresponding PI component associated with the message inter-communication linked to the alert rule and to the at least one registered alert consumer system.

Abstract: A computer implemented method may include identifying one or more business process runtime events received at an events queue of a process integration runtime component. One or more errors associated with the business process runtime events may be identified. The one or more errors may be evaluated based, at least in part, on one or more rules associated with the business process runtime event and configuration information associated with the process integration runtime component. The one or more rules may be associated with the business process runtime event and configuration information associated with the process integration runtime component having the same format. An alert for the one or more errors associated with the business process runtime event can be stored.

Abstract: The present disclosure relates to software, computer systems, and computer implemented methods for providing centralized process integration (PI) domain alert monitoring. One process includes identifying at least one alert rule at a central rules repository, the at least one alert rule associated with at least one message inter-communication within a process integration (PI) domain, where the PI domain includes at least one PI component, and where the message inter-communications within the PI domain occur between PI components. At least one alert consumer registration associated with at least one alert consumer system for an identified alert rule is identified. Information associated with the at least one identified alert rule from the central rules repository is distributed to the corresponding PI component associated with the message inter-communication linked to the alert rule and to the at least one registered alert consumer system.

Abstract: In a distributed landscape, different levels of data caches, such as a memory cache and prefetch tables, are provided for storing status and other information about a remote system to a client. Status information may be provided to the client from a memory cache if available and up to date. The memory cache may be updated using information stored in the one or more prefetch tables or by reading the data from the remote system(s). The prefetch tables may be updated by reading information from the remote systems. The data caches are dynamically updated to store the most up-to-date status information available. The data stored in each data cache level may be updated at predetermined intervals or upon a request by the client. Status messages for the one or more remote systems selected are displayed, providing the client with a status overview of the distributed landscape.

Abstract: A computer implemented method may include identifying one or more business process runtime events received at an events queue of a process integration runtime component. One or more errors associated with the business process runtime events may be identified. The one or more errors may be evaluated based, at least in part, on one or more rules associated with the business process runtime event and configuration information associated with the process integration runtime component. The one or more rules may be associated with the business process runtime event and configuration information associated with the process integration runtime component having the same format. An alert for the one or more errors associated with the business process runtime event can be stored.

Abstract: In a distributed landscape, different levels of data caches, such as a memory cache and prefetch tables, are provided for storing status and other information about a remote system to a client. Status information may be provided to the client from a memory cache if available and up to date. The memory cache may be updated using information stored in the one or more prefetch tables or by reading the data from the remote system(s). The prefetch tables may be updated by reading information from the remote systems. The data caches are dynamically updated to store the most up-to-date status information available. The data stored in each data cache level may be updated at predetermined intervals or upon a request by the client. Status messages for the one or more remote systems selected are displayed, providing the client with a status overview of the distributed landscape.

Abstract: Methods and apparatus, including computer program products, are provided for executing, by a first framework, a service provided by a second framework. The method may include initiating, by the first framework, a request to access the service provided by the second framework. The method may also include identifying metadata for the service, the metadata being stored in a metamodel runtime repository. The method may further include translating the metadata into a format that the first framework can use to invoke the service and executing, using the translated metadata, the service provided by the second framework.

Abstract: Methods and apparatus, including computer program products, are provided for executing, by a first framework, a service provided by a second framework. The method may include initiating, by the first framework, a request to access the service provided by the second framework. The method may also include identifying metadata for the service, the metadata being stored in a metamodel runtime repository. The method may further include translating the metadata into a format that the first framework can use to invoke the service and executing, using the translated metadata, the service provided by the second framework.