Oracle International Corporation

Michael John De Groot

George Albert Buzsaki

Sowmya Subramanian

John Smiljanic

Thomas W Nickerson

Larry Harris

Sandeep Khemani

Sekhar Chandra Korupolu

Christopher Brumme

Henry John Wagner

Amit Ganesh

Bipul Sinha

Srinivas Vemuri

Priscilla C Fung

Shailesh Vinayaka

Ralph Lemke

Ronald Van Grinsven

Nagarajender Rao Katoori

Mahesh Bansal

Frank Dancs

Namita Varma

Eric W Bing

Debugger requests are for debugging a script injected into a web application during a debug session are received. Each of the debugger requests include the same debug session identifier. A different one of the debugger requests is associated with each of the break points set for debugging the script. For each of the debugger requests: a new stateless debugger node is connected with a single stateless target tester node. Stateless debugger nodes and stateless target tester nodes reside inside of the multi-node cloud system. The script is debugged on the same stateless target tester node while the debugging is controlled from a developer computer system that is outside of the multi-node cloud system. After completion of each of the debugger requests: a current stateless debugger node is disconnected, and state stored in the multi-node cloud system used for servicing a current debugger request is destroyed.

Stateless injected script debugging

A debug session identifier representing a debug session for the web application is stored in local storage. The web application is located in multi-node cloud storage. The local storage resides on a developer computer system that executes outside of the multi-node cloud system. A stateless debugger node and a stateless target tester node are selected from at least one node pool in the multi-node cloud system. The stateless debugger node and the stateless target tester node are separate from each other. An internal connection is provided between the stateless debugger node and the stateless target tester node within the multi-node cloud system based on the debug session identifier during the debug session. The script that is injected into the web application is debugged while the web application executes on the stateless target tester node.

Stateless debugging of a script injected into a web application that is located in a mult-node cloud system

An adapter can execute a test script in parallel relative to separate tenant installations in a multi-tenant environment. Such tenant installations can be established within a cloud computing environment. Multiple tenant installations may share some installation components, such as an application server and/or a database, so that these shared installation components are not duplicated. While executing the test script in parallel, the adapter can translate selected values for each test script execution so that those values are distinguished from corresponding values within other test script executions. The values can be translated to reflect the identity of the tenant whose installation the test script execution targets. Furthermore, while executing the test scripts in parallel, the adapter can cause the test script executions to synchronize at specified points within the test script, so that all of the test script executions are guaranteed to have executed to a common point before proceeding.

System to enable multi-tenancy testing of business data and validation logic on the cloud

A query result set is an example of a type of body of data whose content is defined by a query. Modifications to a database can change the result of a query and therefore what the content of such a body of data, such as a result set, should be. Active Queries is an approach that enables a database server to detect database changes that alter the result of a query registered for a client and to notify a client of those changes. The notifications may be sent to, for example, a cache manager responsible for maintaining coherency of a result set cache generated by the query. The notification notifies the cache manager of when and/or what changes are needed to maintain the coherency of the cache.

Query based invalidation subscription

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 uniform object model integrates objects defined by foreign type systems into a single integrated object oriented system. The type system for the integrated object oriented system supports a superset of features from foreign object systems. The uniform object model approach converts foreign objects into uniform object model objects defined by the integrated type system and layers onto the uniform object model objects additional members supported by the integrated type system. Adapters integrate foreign objects and data sources into the integrated object oriented system by implementing foreign objects as full fledged objects of the system. The foreign object adapters are bi-directional such that objects, registered in the system, are exposed to foreign object systems. During run time, clients obtain a connection to the data source adapter, which supports the target data source, to execute transactions in the target data source. When executing transactions in the target data source, the data source adapter operates as an object access mechanism by generating an object populated with data from the target data source. The data source adapters support a single predetermined dialect of a query language, regardless of the target data source, and generate a query statement compatible with the target data source. The data source adapters also support persistence of objects in the data sources.

Uniform object model having methods and additional features for

A class signature interface exposes members of an object class in an object oriented software system by exposing access information to the member. The class signature interface has application for use with object models that require client objects to utilize the functionality of server objects through interfaces, such as required by the Component Object Model (COM). Class signature interfaces expose interfaces supported by the object class to provide time constant access to the interfaces of the object class. The class signature interfaces also expose attributes and methods, defined directly on the class level. The class signature interface has further application for use in an object oriented software system to add additional class members to an object class without adding the class members to a separate interface. The class signature interfaces are implicitly generated in an interface definition language (IDL) compiler, or a user specifies the class signature interfaces through the IDL syntax, and the IDL compiler generates the class signature interfaces in accordance with the IDL syntax specified.

Growing community of inventors

Cupertino, CA, United States of America

Michael John De Groot