Oracle International Corporation

John Smiljanic

Shailesh Vinayaka

Michael John De Groot

James Driscoll

Sekhar Chandra Korupolu

Henry John Wagner

Namita Varma

Ronald Van Grinsven

Nagarajender Rao Katoori

Mahesh Bansal

Computer code is received that is written using a dynamic Domain Specific Language (DSL) running in a General Purpose Language (GPL) computing environment. A compiler performs static compiler analysis on the computer code. The static compiler analysis includes referencing a security policy defining one or more unacceptable program behaviors. During compile time at the compiler, runtime security checking functionality is performed leveraging compiler extensions, type information, and environment specific compile context. Results of the static compiler analysis are used to indicate when execution of the computer code would result in performance of the one or more unacceptable program behaviors. The one or more unacceptable program behaviors include modifying preexisting computer code to incorporate the computer code written using the DSL.

Determining based on static compiler analysis that execution of compiler code would result in unacceptable program behavior

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 example system and method for securing computer code of a dynamic Domain Specific Language (DSL) that leverages a General Purpose Language (GPL). An example method includes enhancing compile-time security enforcement functionality for computer code written using the DSL, in part by using a compiler to perform static analysis on the DSL computer code. The static analysis includes referencing a security policy defining one or more unacceptable program behaviors; and indicating when execution of the computer code would result in performance of the one or more unacceptable program behaviors based on results of the static analysis.

Method for static security enforcement of a DSL

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

Various arrangements for debugging logic being executed by a webserver is presented. A virtual machine of the webserver may execute runtime threads for a plurality of remote users. The web server may compile business logic code received from a developer computer system via a web-based interface into an logic insight injected code. The logic insight injected code may be compiled from the business logic code to include debugging functionality. The virtual machine of the webserver may execute the logic insight injected code concurrently with the runtime threads being executed for the plurality of remote users. The debugging functionality of the logic insight injected code being executed may not affect execution of the runtime threads for the plurality of users.

Debugging analysis in running multi-user systems

A system is provided that automatically manages data consistency of a web application. When the system sends a data entity to a user interface component that the system has determined is an updatable user interface component, the system stores a version indicator for the data entity within a resource scope. When the system receives a request to update the data entity, the system compares the version indicator stored within the resource scope with a version indicator stored within a data store. When the two version indicators are identical, the system updates the data entity. When the two version indicators are not identical, the system raises an exception.

Automatic management of client data consistency

Various arrangements for debugging code are presented. A computer system, such as a web server, may compile code into compiled code. The code may contain one or more subsections, include a first taskflow. A selection of the first taskflow may be received from a remote, developer computer system via a network. The selection of the first taskflow may indicate that the first taskflow is to be debugged. Execution of the first taskflow of the compiled code may occur by the computer system. While the computer system is executing the first taskflow of the compiled code, debugging functionality of the first taskflow may be provided to the developer computer system.

Targeted cloud-based debugging

Systems and methods for debugging domain specific languages are provided. In accordance with an embodiment, one such system can comprise a web which includes a virtual machine, a debug execution machine, and a domain specific language (DSL)-specific tool interface. The web server is configured to compile DSL code received from a developer computer. During compilation the DSL code is instrumented to include debugging information received from the developer computer. The web server is also configured to execute, by the virtual machine, the instrumented code. During execution the instrumented code communicates with the debug execution machine such that a state of the debug execution machine mirrors a state of the virtual machine.

Growing community of inventors

Austin, TX, United States of America

John Smiljanic