Abstract: Systems and methods include determination of an integration style of a first interface between two or more applications, determination of a first message flow of the first interface, the first message flow between two of the two or more applications and associated with an integration domain and the integration style, determination of a first one or more key characteristic values associated with the first message flow, determination of a plurality of integration components associated with the integration domain and the integration style, each of the determined plurality of integration components associated with fulfillment data of each of a plurality of key characteristic values, determination, for each of the plurality of integration components, of an integration score based on fulfillment data associated with the integration component for the first one or more key characteristic values, and determination of one or more of the plurality of integration components to implement the first message flow based on th

Abstract: Systems and methods include determination of an integration style of a first interface between two or more applications, determination of a first message flow of the first interface, the first message flow between two of the two or more applications and associated with an integration domain and the integration style, determination of a first one or more key characteristic values associated with the first message flow, determination of a plurality of integration components associated with the integration domain and the integration style, each of the determined plurality of integration components associated with fulfillment data of each of a plurality of key characteristic values, determination, for each of the plurality of integration components, of an integration score based on fulfillment data associated with the integration component for the first one or more key characteristic values, and determination of one or more of the plurality of integration components to implement the first message flow based on th

Abstract: The disclosure generally describes computer-implemented methods, software, and systems, including a method for querying extension point information and providing extension patterns for core process models. Information for a core process model user interface is provided to a client device for displaying a core process model as a visualization including core process model steps and dedicated extension points for inserting user-defined extensions. The information is provided by a server from a core process model meta-model. Selections of the extension points and customization of extensions associated with the extension points are received from a client device. A core process model instance including the core process model and customizations of the extensions is stored. Information is provided for use at the client device for presenting a process extension query interface. A query is received from the client device.

Abstract: The disclosure describes methods, software, and systems, including a method for providing extension points for core process models. Extension points are provided for a core process model associated with a core process. The extension points are pre-defined and annotated with constraints that specify restricted behavior of extensions plugged into the core process model at the extension points. The extension points are formulated in a process extension constraint definition language and allow a restriction of runtime behavior. The process extension constraint definition language is based on temporal logic and enhances existing property specification patterns with specific support to formulate constraints at an extension task type level for activities included in a process extension. Instructions are received from a user to plug selected extensions into an instance of the core process model. Each selected extension includes user-customized behavior for the extension.

Abstract: The disclosure describes methods, software, and systems, including a method for providing extension points for core process models. Extension points are provided for a core process model associated with a core process. The extension points are pre-defined and annotated with constraints that specify restricted behavior of extensions plugged into the core process model at the extension points. The extension points are formulated in a process extension constraint definition language and allow a restriction of runtime behavior. The process extension constraint definition language is based on temporal logic and enhances existing property specification patterns with specific support to formulate constraints at an extension task type level for activities included in a process extension. Instructions are received from a user to plug selected extensions into an instance of the core process model. Each selected extension includes user-customized behavior for the extension.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems, including a method for querying extension point information and providing extension patterns for core process models. Information for a core process model user interface is provided to a client device for displaying a core process model as a visualization including core process model steps and dedicated extension points for inserting user-defined extensions. The information is provided by a server from a core process model meta-model. Selections of the extension points and customization of extensions associated with the extension points are received from a client device. A core process model instance including the core process model and customizations of the extensions is stored. Information is provided for use at the client device for presenting a process extension query interface. A query is received from the client device.

Abstract: Systems and methods allow sharing and reuse of acquired customization knowledge of enterprise systems, utilizing collective customization experience. Particular embodiments employ Case-Based Reasoning (CBR) principles to manage customization experience in the context of both Software as a Service (SaaS) and Platform as a Service (PaaS) environments. Collective customization knowledge may be explicitly retrieved, adapted, shared, reused, and/or traded between tenants, partners, and optionally provider(s), of on-demand enterprise systems. A previous customization case stored within an experience base, may include one or more of the following: information allowing annotation of price information for trading the previous customization case (e.g.

Abstract: Systems and methods allow sharing and reuse of acquired customization knowledge of enterprise systems, utilizing collective customization experience. Particular embodiments employ Case-Based Reasoning (CBR) principles to manage customization experience in the context of both Software as a Service (SaaS) and Platform as a Service (PaaS) environments. Collective customization knowledge may be explicitly retrieved, adapted, shared, reused, and/or traded between tenants, partners, and optionally provider(s), of on-demand enterprise systems. A previous customization case stored within an experience base, may include one or more of the following: information allowing annotation of price information for trading the previous customization case (e.g.

Abstract: Systems and methods allow sharing and reuse of acquired customization knowledge of enterprise systems, utilizing collective customization experience. Particular embodiments employ Case-Based Reasoning (CBR) principles to manage customization experience in the context of both Software as a Service (SaaS) and Platform as a Service (PaaS) environments. Collective customization knowledge may be explicitly retrieved, adapted, shared, reused, and/or traded between tenants, partners, and optionally provider(s), of on-demand enterprise systems. A previous customization case stored within an experience base, may include one or more of the following: information allowing annotation of price information for trading the previous customization case (e.g.

Abstract: Implementations of the present disclosure include methods for provisioning services in a business network. In some implementations, methods include receiving data corresponding to a first service, receiving data corresponding to a second service, processing the data corresponding to the first service and the data corresponding to the second service using a computer-executable tool selected from a plurality of computer-executable tools to enable provisioning of a service using the business network, and the processing being performed in a situational modeling layer of a service provisioning framework, generating a kernel model corresponding to the service, the generating being performed in a kernel modeling layer of the service provisioning framework, and storing the kernel model in computer-readable memory.

Abstract: In one embodiment, a method for integrating a service into an application is provided. The method determines an application extensibility description for an application. The application extensibility description includes a set of application extension points. The method determines a service description for a service, the service description including a set of service elements. An adaptation pattern is determined and includes a first port connected to an application extension point in the set of application extension points and a second port connected to a service element in the set of service elements. A computing device generates an integration description based on the adaptation pattern having the first port connected to the application extension point and the second port connected to the service element. The integration description allows the application to be adapted or extended with the service.

Abstract: Systems and methods allow sharing and reuse of acquired customization knowledge of enterprise systems, utilizing collective customization experience. Particular embodiments employ Case-Based Reasoning (CBR) principles to manage customization experience in the context of both Software as a Service (SaaS) and Platform as a Service (PaaS) environments. Collective customization knowledge may be explicitly retrieved, adapted, shared, reused, and/or traded between tenants, partners, and optionally provider(s), of on-demand enterprise systems. A previous customization case stored within an experience base, may include one or more of the following: information allowing annotation of price information for trading the previous customization case (e.g.

Abstract: Embodiments relate to systems and methods for a case-based adaptation framework allowing adaptation of an existing customizing solution (from a previous case) to a new, unsolved integration, adaptation, or extension problem. Particular embodiments may rely upon an adaptation approach in which the problem solution of a retrieved case is transformed into a new problem solution of the query case by application of adaptation rules. In certain embodiments, a transformational adaptation method may be embedded into an interactive, semi-automatic customization procedure that provides recommendations on possible adaptation steps to the system integrator.

Abstract: A system may include determination of a business configuration of one or more tenants of a business application platform, determination of metadata of business applications associated with the business application platform, reception of a request from a user of the business application platform for one or more recommended business applications, and application of one or more filters to a set of business applications based on the business configuration and the metadata to determine a recommended business application from the set of business applications.

Abstract: In one embodiment, a method includes storing a set of integration cases previously used for adapting a standard enterprise system. The integration cases include a problem description and a problem solution for the adapting of the standard enterprise system. The method receives an integration problem for extending the standard enterprise system. The integration problem has a problem description and not a problem solution. A similarity between the problem description of the integration problem and the problem description of the set of integration cases is determined and one or more similar integration cases from the set of integration cases to the integration problem is determined based on the determined similarity. The method then outputs the one or more similar integrations cases to a user. The problem solution for a similar integration case is usable to determine the problem solution for the integration problem.

Abstract: In one embodiment, a method includes storing a set of integration cases previously used for adapting a standard enterprise system. The set of integration cases include a business function attribute selected from a business domain ontology (BDO) of an enterprise. The integration problem includes a business function attribute selected from the BDO of the enterprise. A similarity is determined between the business function attribute of each of the set of integration cases to the business function attribute of the integration problem. The similarity is determined based on a first position in the BDO of each business function attribute of the set of integration cases in relation to a second position in the BDO of the business function attribute of the integration problem. One or more similar integration cases in the set of integration cases is determined to the integration problem based on the determined similarity and output.

Abstract: Implementations of the present disclosure include methods for provisioning services in a business network. In some implementations, methods include receiving data corresponding to a first service, receiving data corresponding to a second service, processing the data corresponding to the first service and the data corresponding to the second service using a computer-executable tool selected from a plurality of computer-executable tools to enable provisioning of a service using the business network, and the processing being performed in a situational modeling layer of a service provisioning framework, generating a kernel model corresponding to the service, the generating being performed in a kernel modeling layer of the service provisioning framework, and storing the kernel model in computer-readable memory.

Abstract: In one embodiment, a method for integrating a service into an application is provided. The method determines an application extensibility description for an application. The application extensibility description includes a set of application extension points. The method determines a service description for a service, the service description including a set of service elements. An adaptation pattern is determined and includes a first port connected to an application extension point in the set of application extension points and a second port connected to a service element in the set of service elements. A computing device generates an integration description based on the adaptation pattern having the first port connected to the application extension point and the second port connected to the service element. The integration description allows the application to be adapted or extended with the service.