Oracle International Corporation

Larry Harris

George Albert Buzsaki

Sowmya Subramanian

Michael John De Groot

Thomas W Nickerson

Sandeep Khemani

Rajesh Raheja

John Joseph Jakubik

Kanchan Shringi

Alan Fothergill, Ii

Oliver Steinmeier, Iii

George H Colliat

Barry J Lind

Liza Lyons

Vivek Salgar

Christopher Broadbent

David Bowin

Michael Stillger

Peter Moore

Methods and systems for supporting multiple deployment models for enterprise business applications, are described. In one embodiment, the method may include designating pillars associated with an enterprise business application. Each pillar may include application units which comprise logical groupings for application units used in the enterprise business application. The method may further include determining which of the application units are dependent to more than one of the pillars. Furthermore, based on the determination of the dependent application units, the method may generate deployment code associated with the dependent application units which is configured to be deployment model independent. The method may then receive, at deployment time, a deployment model designation indicating a type of deployment model selected to be used for the enterprise business application. Then, the enterprise business application may be deployed according to the deployment model designation.

Methods and systems for supporting multiple deployment models of enterprise business applications

Methods and apparatus for enabling efficient testing of application programming interface (API) frameworks and application code are disclosed. According to one aspect of the present invention, a method for capturing a call to an API using a framework including an execution engine that communicate with an adapter to cause the API call to be executed involves making the API call and constructing an object using metadata associated with the API call. The constructed object is converted into a node that is of a declarative metadata format, and the node is stored.

Integration functionality for a test tool for application programming interfaces

Methods and apparatus for enabling efficient testing of application programming interface (API) frameworks and application code are disclosed. According to one aspect of the present invention, a framework suitable for use to test an API includes a metadata provider arrangement that stores declarative metadata and a metadata provider interface that obtains the declarative metadata associated with a test from the declarative metadata provider. A first test adapter includes logic used to process the declarative metadata, and a diagnostic test interface cooperates with the first test adapter to execute the test. The first test adapter is effectively interfaced with the diagnostic test interface. Finally, a diagnostics execution engine is arranged to communicate with the diagnostic test interface to cause the test to be executed.

Application functionality for a test tool for application programming interfaces

Methods and apparatus for enabling the framework and the application code associated with an application programming interface (API) to be efficiently and comprehensively tested are disclosed. According to one aspect of the present invention, a structure that defines an API test in declarative metadata includes an entity to be tested, a first metadata arrangement, and a second metadata arrangement. The first metadata arrangement includes any data to be used when the entity is tested, and the second metadata arrangement includes any expected outputs associated with testing the entity.

Test tool for application programming interfaces

A method and apparatus are provided for supplying data to users through &ldquo;query objects&rdquo;, where the data corresponds to attributes of domain objects and is stored in a relational database. The query objects create a bridge between the information the user wants to see (as expressed in the user interface presented to the user), the object model in which domain logic is implemented, and the relational model in which the data is stored. Thus, data used to populate the user interface is queried directly from the data model and returned in the shape required by the user interface. As the query results are read into memory, objects that model the data using object-oriented techniques are instantiated. Subsequent manipulation of the data is redirected to those objects, thereby preserving data encapsulation and allowing reuse of existing logic.

Accessing domain object data stored in a relational database system

Growing community of inventors

Belmont, CA, United States of America

Larry Harris