Abstract: A view schema is generated from a view definition, wherein the view schema includes one or more relational views that are created by translating one or more object queries in the view definition into one or more relational queries. A report design schema is generated from the view definition by: creating one or more report tables that correspond to the one or more relational views of the view schema and extending the one or more report tables with one or more primary key constraints and one or more foreign key constraints. A reporting model is generated by reverse engineering the report design schema, wherein the reporting model includes the one or more primary key constraints and the one or more foreign key constraints. A report is generated using the reporting model, wherein the report includes the one or more primary key constraints and the one or more foreign key constraints.

Abstract: A view schema is generated from a view definition, wherein the view schema includes one or more relational views that are created by translating one or more object queries in the view definition into one or more relational queries. A report design schema is generated from the view definition by: creating one or more report tables that correspond to the one or more relational views of the view schema and extending the one or more report tables with one or more primary key constraints and one or more foreign key constraints. A reporting model is generated by reverse engineering the report design schema, wherein the reporting model includes the one or more primary key constraints and the one or more foreign key constraints. A report is generated using the reporting model, wherein the report includes the one or more primary key constraints and the one or more foreign key constraints.

Abstract: Methods and systems for enterprise data integration are described. The methods and systems take elements of a data integration process typically operating in a batch-mode, transform the elements in real time, and expose the results as a service that can be accessed by a business enterprise in real time, and optionally also in batch mode. The service can be accessed through a graphical user interface, providing automatic data integration in real time without additional coding. The service can also operate with mobile devices.

Abstract: A transformation function of an extract-transform-load data integration process is deployed as a service in a services oriented architecture. A method includes providing a module for a data integration function, the module being a data transformation module; providing a registry of services; providing an interface for the data transformation module; and identifying the data transformation module in the registry; wherein the data transformation module can be accessed as a service in a services oriented architecture. A system includes a data transformation module for a data integration function; a registry of services; and an interface for the data transformation module; wherein the data transformation module is identified in the registry; and wherein the data transformation module can be accessed as a service in a services oriented architecture.

Abstract: A loading function of an extract-transform-load data integration process is deployed as a service in a services oriented architecture by providing a module, the module being a data loading module for loading data into a target database that is associated with a data integration platform; by providing a registry of services; and by providing an interface for the data loading module; and identifying the data loading module in the registry; wherein the data loading module can be accessed as a service in a services oriented architecture.

Abstract: Real time data integration jobs are deployed in a services oriented architecture as services that allow multiple service bindings. In one aspect, a method includes providing a code module executing a data integration job and a registry of services for storing the code module. When the code module is identified in the registry, access is provided to the code module in the registry of services, in real time wherein the code module may be accessed by more than one type of service binding such that different applications can utilize the real-time integration service using different protocols to invoke the real-time integration service. At least one of the types of service bindings may be an EJB binding, a SOAP binding, a JMS binding, and a web service binding. The data integration job may include an extraction job, a data transformation job, a loading job, a metadata management job, and a data quality job.

Abstract: A user interface, or a component of a user interface, is deployed as a service in a services oriented architecture for use, for example, in a data integration platform.

Abstract: A security service is deployed as a service in a services oriented architecture for use, for example, in a data integration platform.

Abstract: A message broker is deployed as a service in a services oriented architecture for use, for example, in a data integration platform.

Abstract: A transformation function of an extract-transform-load data integration process is deployed as a service in a services oriented architecture.

Abstract: A client-side interface provides access to real time data integration jobs deployed as services in a services oriented architecture.

Abstract: A user interface, or a component of a user interface, is deployed as a service in a services oriented architecture for use, for example, in a data integration platform.

Abstract: Real time data integration jobs are deployed in a services oriented architecture as services that allow multiple service bindings.

Abstract: An application programming interface facilitates access to code modules, such as real time integration process code modules, deployed as services in a services oriented architecture.

Abstract: A logging service is deployed as a service in a services oriented architecture for use, for example, in a data integration platform.

Abstract: A loading function of an extract-transform-load data integration process is deployed as a service in a services oriented architecture.

Abstract: Real time data integration services are deployed in a services oriented architecture for supply chain management.

Abstract: An extraction function of an extract-transform-load data integration process is deployed as a service in a services oriented architecture.

Abstract: Code modules are deployed as services in a services oriented architecture to enable location-based real time data integration services.

Abstract: Real time data integration services are deployed in a services oriented architecture for inventory management.