Abstract: A plurality of domain-specific service adaptation languages can be supported by a back-end service adaptation system to provide runtime access to a runtime instance of a data object comprising data stored in a repository. By defining a language-specific data access service and parser for each domain-specific service adaptation language, a single, service adaptation language-independent compiler and interpreter can prepare and execute a runtime load that includes an execution plan for retrieving and converting data from the repository for delivery in a data object according to a query request from a consumer runtime environment. A consumer using the consumer runtime environment can define the service adaptation language to be used and provide a parser and source code to enable access to business object data using the back-end service adaptation system.

Abstract: A back-end service adaptation system provides access to normalized data in a data repository for a consumer runtime environment sending a query request for denormalized data. The back-end service adaptation system can include a data access service layer, a parser layer, and a back-end service adaptation runtime layer. The consumer runtime can use a service adaptation definition language (SADL), and the parser and data access service can be configured to convert and translate the SADL request for the back-end service adaptation runtime layer.

Abstract: A system may include reception of the first instruction, execution of the business process in a first software work process, reception, during execution of the business process, of an indication of a business object process associated with the business process, determination of progress information associated with the business process based on the indication of the business object process, and storage of the progress information within a memory. Aspects may further include reception, at a second work process, of a request from the client application for progress information, retrieval of the progress information from the shared memory and provision of the progress information to the client application.

Abstract: Systems and methods for providing application services through business object views. In one aspect, a definition of at least one business object (BO) is included in a metadata of an application platform. The definition includes descriptions of entities of the BO, and an identification of a service provider of the BO. The service provider instantiates the business object in response to an application service request. In a further aspect, a definition of a business object view (BOV) is included in the metadata of the application platform. The definition includes description of entities of the BOV, and an identification of the BO. The BO is a data source of the BOV. In one other aspect, a transformation describes a mapping of BOV entities to data source BO entities. A service corresponding to a core service of a BOV entity is called at the BO service provider based on the mapping.

Abstract: Systems and methods are provided for managing content. In one implementation a system includes software constructs, each being associated with a context defining a class of content modules included in a respective construct. In the system, a context is selected and context data for a plurality of content modules is retrieved. The context data includes a primary context identifier that identifies the context in which each content module was created or modified. In addition, the context data includes at least one secondary context identifier identifying additional contexts in which the content module is permitted to be included. Based upon the context identifiers, it is determined whether a content module is permitted in the selected context and a collection of modules is generated including the content modules permitted in the selected context based on the determination.

Abstract: A computer-implemented system may include a data store to store business data, an application platform, and a business application. The application platform may include a repository to store metadata defining a plurality of business objects, each of the business objects comprising a respective model of data and associated logic, each business object associated with respective business object entities, and a framework in communication with the repository to provide access to the business data. The business application is to access the data via the framework and based on the metadata, wherein the metadata associates a first plurality of the business object entities with a RELEASED release status code, and wherein the metadata associates a second plurality of the business object entities with a DEPRECATED release status code.

Abstract: The subject matter disclosed herein provides methods and apparatus, including computer program products, for model driven state management of applications. In one aspect, there is provided a computer-implemented method. The method may include instantiating one or more business objects associated with an application. The transitions between states of the application may be checked using one or more models defined based on at least one of a context of the business object and a context of the application. An indication regarding the results of checking of the transitions may be provided to a user interface. Related apparatus, systems, methods, and articles are also described.

Abstract: Methods and apparatus, including computer program products, are provided for mockup data for a mockup object. In one exemplary embodiment, the method may include receiving, from a user, a name of the mockup object for which the mockup data should be created, wherein the object comprises one or more nodes. The method may also include receiving, from the user, a number of records to be created for each node of the object, determining whether to modify existing mockup data or create new mockup data for each node, receiving, from the user, a beginning range and an ending range for the mockup data, and generating, within the framework, the mockup data for each node of the object based on metadata stored within the framework and the beginning and ending range.

Abstract: Methods and apparatus, including computer program products, are provided for a mockup business object. The mockup business object implemented within a computer framework including other business objects. In one exemplary embodiment, the method may include generating, within the computer framework, the mockup business object based on a metadata stored within the computer framework, when the mockup business object does not exist within the computer framework. The method may also include determining whether a structure of the mockup business object has changed based on the metadata, when the mockup business object does exist within the computer framework. Moreover, the method may include modifying the mockup business object based on the result of the determining step.

Abstract: Methods and apparatus, including computer program products, for using dynamic meta data for an enterprise service framework. There is a meta data element associated with a meta data element attribute. A value for the meta data element attribute is calculated in response to a request associated with the meta data element.

Abstract: Methods and apparatus, including computer program products, are provided for executing a service using a set of software plug-ins. The method may include generating, at a first computer, a service request to execute the service. The method may also include processing, at a second computer, the generated service request using the set of software plug-ins associated with the service to create a modified service request by executing each of the software plug-ins in a sequence. Further, the method may include executing, at a third computer, the service using the modified service request and processing, by a second set of software plug-ins based on the sequence, a result from the executing step.

Abstract: Business object templates which include a plurality of hierarchically arranged entities and characterize services associated with the entities can be used to generate new business objects. These new business objects are generated based on projections of the business object template. In some variations, the business objects include a subset of the entities defined by the business object template. In other variations, the business objects include all of the entities defined by the business object template but with only certain entities being activated.

Abstract: A system and method for message lifetime management. According to an embodiment of the invention, a front-end application process identifies during a user interface interaction cycle of the front-end application process at least one stateful message reported to the front-end application process by a back-end service process during a prior user interface interaction cycle of the front-end application process, the at least one stateful message having been stored in a message buffer by the front-end application process, queries the back-end service process to determine whether the at least one stateful message is currently valid, and removes the at least one stateful message from the message buffer if it is determined not to be currently valid.

Abstract: A method is provided for providing one or more services by a service provider to a service consumer. The method may include defining a meta-model describing at least one core service and at least one compound service; creating a model for the core service based on the meta-model; and implementing the core service on the service provider based on the model. The method may also include implementing the compound service on the service provider and implementing a generic access interface on the service consumer to dynamically access the core service and the compound service.

Abstract: A system for managing user interface events in user interface of a client system. The system includes a service layer including a business object. The system also includes an intermediate object layer comprising an intermediate object associated with the business object, wherein the intermediate object handles user interface messages raised by the business object and retrieves data from the business object for user interface. The system further includes a service manager that provides the retrieved data from the intermediate object for display on the user interface.

Abstract: Methods and apparatus, including computer program products, are provided for a mockup business object. The mockup business object implemented within a computer framework including other business objects. In one exemplary embodiment, the method may include generating, within the computer framework, the mockup business object based on a metadata stored within the computer framework, when the mockup business object does not exist within the computer framework. The method may also include determining whether a structure of the mockup business object has changed based on the metadata, when the mockup business object does exist within the computer framework. Moreover, the method may include modifying the mockup business object based on the result of the determining step.

Abstract: Embodiments consistent with the principles of the invention check, before the data underlying a changed primary object is persistently save, for related objects whose data is also affected by the change. The related objects may be two or more degrees removed from the primary object. The changed primary object and all its changed related objects are then persistently saved together, so that the saved data is consistent across the related objects. Embodiments consistent with the principles of the invention also provide a state model for controlling access to services by clients and for making services available by servers.

Abstract: Methods and apparatus, including computer program products, for testing software involve generating a software build of source files and initiating tests on the software build. Each test is performed using a portion of the software build that corresponds to one or more of the source files. Results data relating to the tests, such as an indication of errors identified in the tests, is stored. The results data further identifies source files associated with each of the tests. A notification message relating to the results data is sent to a user.

Abstract: Systems, methods, and computer program products are provided for adapting service entities using a declarative approach in a service framework. In accordance with one implementation, a method is provided for adapting service entities. The method includes the steps of retrieving at least one software entity from a first repository in response to a first input and receiving a declaration from a user for adapting the software entity. The method further includes the steps of adapting the software entity to an adapted software entity based on the declaration and storing the adapted software entity in a second repository.

Abstract: Methods and systems for calling a service provider using a service manager and a local client proxy. In one exemplary embodiment, a method is provided to instantiate the service manager, the service provider, and the local client proxy. In response to the service provider, the local client proxy calls another service provider through the service manager to complete the call to the other service provider.