Oracle International Corporation

Yogesh Kumar

Michal Chmielewski

Murali Pottlapelli

Glenn Weiqun Mi

Simone Geib

Muruganantham Chinnananchi

Ronald Ten-Hove

Dennis Fuglsang

Aninda Sengupta

Rajeev Kumar Misra

Philippe Le Mouel

David Craft

Vikas Anand

Methods and systems for patching an instance of a composite executing in a runtime environment are provided. A method can include at a computer system comprising a processor and a memory executing, by an application server, one or more instances of a composite, and enabling a patch to be applied to the one or more instances of the composite without stopping execution of the one or more instances in the application server, wherein the patch comprises one or more changes to be made to the composite.

Composite instance patching

In accordance with an embodiment, described herein is a system and method for improving performance of an executable process defined by a process execution language in a service-oriented architecture (SOA) middleware environment. Flow states and audit data of a process instance can be stored in a dehydration store implemented on a distributed in-memory data grid, and transferred to a persistent storage at a configurable interval, or at certain state changes such as completions and faults of the process instance. A user interface can be used to configure the persistence policy for the process instance, and to retrieve the flow states and audit data from the persistent storage for process monitoring and diagnosis. The flow states data in the persistent storage can also be used for resuming execution of the process instance after a planned system maintenance, or a system crash.

System and method for using an in-memory data grid to improve performance of a process defined by a process execution language in a SOA middleware environment

A system and method for facilitating execution of a portion of a process via a subprocess. An example method includes encapsulating process logic of a portion of a parent process via the subprocess, wherein the parent process is encoded via a business process language characterized by process lifecycle management functionality; using an instance of a call activity in a scope of the parent process or subprocess to activate the subprocess, yielding a called subprocess in response thereto; and employing a business process runtime engine to adjust a scope of the subprocess to inherit the scope of the process used to call the subprocess, thereby enabling the process lifecycle management functionality to govern a lifecycle of the subprocess. In a more specific embodiment, the business process language includes standard Business Prosecution Execution Language (BPEL); the parent process represents a business process; and the subprocess includes a standalone subprocess.

Execution semantics for sub-processes in BPEL

In accordance with an embodiment, described herein is a system and method for supporting object notation (e.g., JavaScript Object Notation (JSON)) variables in a process defined by a process execution language for execution in a SOA middleware environment. An extension namespace can define additional methods and attributes to enable support for object notation variables in the process. With the support for object notation variables, the process can be defined to include a representational state transfer (REST) partner link, for directly receiving object notation payloads from an external service into an object notation variable in the process, where the object notation variable can be accessed and manipulated using JavaScript.

System and method for supporting object notation variables in a process defined by a process execution language for execution in a SOA middleware environment

In accordance with an embodiment, described herein is a system and method for supporting JavaScript activities in an executable process defined by a process execution language. A JavaScript activity can be added to the executable process using attributes defined in an extension namespace to the process execution language. A process execution engine, with an embedded JavaScript engine, can be provided in a SOA middleware environment, to interpret JavaScript artifacts within the JavaScript activity and to provide contextual information, states and payloads of variables in the executable process. Within the JavaScript Activity, JavaScript code can be used to access a plurality of custom JavaScript objects; XPath functions and custom functions defined by the process execution language; and different types of variables in the executable process. JavaScript code can also be used to manipulate these variables using the XPath functions and custom functions accessible within the JavaScript activity.

System and method for supporting javascript activities in a process defined by a process execution language for execution in a SOA middleware environment

In accordance with an embodiment, described herein is a system and method for supporting JavaScript as an expression language in an executable process defined by a process execution language. An extension namespace to the process execution language can be used to define additional attributes for supporting JavaScript as an expression language. Used as an expression language, JavaScript can be used to access contents of XML variables in the executable process without the need to walk through complicated XML structures of the XML variables. A JavaScript expression can be used anywhere an XPath expression can be used, and can additionally be used to access a plurality of functions and variables that cannot be accessed using an XPath expression. A process execution engine can be provided on one or more application servers in a SOA middleware environment to host the executable process, wherein the process execution engine can include a JavaScript engine to interpret JavaScript expressions in the executable process.

System and method for supporting javascript as an expression language in a process defined by a process execution language for execution in a SOA middleware environment

In accordance with an embodiment, described herein is a system and method for reusing JavaScript code in a service orchestration process in a SOA middleware environment. The system can include a unified runtime environment on an application server, wherein the unified runtime environment includes a process execution engine with an embedded JavaScript engine, and an executable process defined by a process execution language executing on the process execution engine. The system can further include a plurality of JavaScript libraries, each defining JavaScript variables with one of a SOA server scope, a component scope, or a process scope. These scopes and an execution scope of a JavaScript variable can form a JavaScript scope chain. When a JavaScript variable in an executable process is being resolved, the JavaScript engine can start in an execution scope of the JavaScript variable, and searches down the scope chain until the variable is resolved or the scope chain is exhausted.

System and method for reusing JavaScript code available in a SOA middleware environment from a process defined by a process execution language

Embodiments of the present invention provide improved concurrency by reducing the time period (also referred to herein as a locking window or contention window) during which a record is locked. This provides the benefits of pessimistic locking schemes by preventing transaction due to concurrent updates, while also reducing the time during which a record is exclusively locked. This improves user experience and performance.

Techniques to reduce contention windows

A system and method for facilitating reuse of a portion of process logic by different processes. An example method includes providing a subprocess that is adapted to perform the process logic in a file accessible to a composite system, wherein the subprocess is adapted to be called by a first parent process via a subprocess extension to a business process language employed to encode the first parent process; using a call activity defined as part of the subprocess extension, and included in a scope of the first parent process to facilitate access to functionality of the subprocess by the parent process; and employing a business process engine to facilitate instantiating the subprocess, resulting in an instantiated subprocess in response thereto; and using a second parent process to share use of the instantiated subprocess with the first parent process.

Using sub-processes across business processes in different composites

A system and method for enabling reuse of a portion of a business process. An example method includes employing a business process language to facilitate accessing a definition of a subprocess characterizing the process logic, wherein the definition indicates one or more parameters to be used by the subprocess to implement a task specified by the process logic; and employing the definition to facilitate: using one or more variables of a parent process as one or more arguments that are passed to an instantiated version of the subprocess, and mapping the one or more arguments to the one or more parameters. In a more specific embodiment, the example method further includes characterizing a behavior of the subprocess via one or more dynamic scoping rules. The business process language includes a version of Business Process Execution Language (BPEL), and a BPEL extension activity facilitates defining the subprocess.

Subprocess definition and visualization in BPEL

A system and method for enhancing performance of a business process execution engine, utilizing a database, a cache, and a lock management system operating in cache. The lock management system, upon receiving a request for a stored business process instance, determines by accessing the cache whether stored business process instance is locked and if the lock is expired. The stored business process object is served to the business process execution engine if it is not locked or the lock is expired. The lock functionality is implemented by writing, rewriting, and/or erasing a companion lock object stored in the cache such that no database access is required to determine whether a stored business process instance is locked.

System and method for object lock management using cached lock objects

A system and method are disclosed for providing BPEL support for correlation aggregation. The system can comprise a business process engine, executing on one or more application servers organized in a cluster. The system can comprise a database including a table which stores records relating to message groups and business process instances. When a message is received by the business process engine, the business process engine can determine an identity associated with the message, and check the database to determine if there is an entry associated with the identity. If there is no entry associated with the identity, then the business process engine can instantiate a first business process instance associated with the identity, and if there is an entry associated with the identity, then the business process engine can route the message to a business process instance associated with the identity.

Growing community of inventors

Sunnyvale, CA, United States of America

Yogesh Kumar