Abstract: Techniques for script-based runtime assembly of object graphs using native instructions compiled by an ahead-of-time compiler are disclosed, including: generating, based on a data structure that defines a business process, a script including instructions for assembling an object graph that represents relationships between objects used by the business process; obtaining, at runtime by a business process execution engine compiled to native instructions by an ahead-of-time compiler, the script; assembling, at runtime by the business process execution engine, the object graph based at least on the instructions in the script.

Abstract: Described herein are systems and methods for sharing vitals among service replicas to enable processing of long running workflows within a container orchestration system. A method can provide a container orchestration system that provides within one or more container orchestration environments, a runtime for containerized workloads and services. The method can provide a healthbus within the container orchestration system, the healthbus comprising a memory. The method can deploy a plurality of pods within the container orchestration system, each pod comprising a memory. The method can periodically publish, by each pod, a health message to the healthbus, the health message comprising at least an indication of an identification of the pod and an indication of a time interval in which the pod has been active. The method can periodically query, by each pod, the healthbus to determine a world view of the container orchestration system.

Abstract: Systems and methods for supporting dynamically partitioned multi-tenant namespaces. A method can provide a computer including one or more microprocessors, a cloud infrastructure environment, and a containerized application provider within the cloud infrastructure environment. The method can define a plurality of partitions by the containerized application provider. The method can populate, by the containerized application provider, one or more pods of a plurality of pods within each of the plurality of partitions. The method can assign each of plurality of partitions a uniquely addressable namespace. The method can assign, respectively, each of a plurality of tenants, to a partition of the plurality of partitions.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Techniques for encoding node locations are provided. In some examples, a node in a hierarchy such as a document object model (DOM) may be expressed as a location path from the root node of the hierarchy to the node. Each node on the location path may be encoded using a mapping between the type and/or index of the node and a set of characters such as ASCII characters. The encoding of each node on the path be concatenated to form the encoded location path. The encoding seeks to minimize the length of the encoded location path. For example, in an embodiment, a single ASCII character may be used to encode both the type and the index of a node. In an embodiment, breakpoint locations may be encoded using methods provided to reduce storage and computing resource required.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Techniques for encoding node locations are provided. In some examples, a node in a hierarchy such as a document object model (DOM) may be expressed as a location path from the root node of the hierarchy to the node. Each node on the location path may be encoded using a mapping between the type and/or index of the node and a set of characters such as ASCII characters. The encoding of each node on the path be concatenated to form the encoded location path. The encoding seeks to minimize the length of the encoded location path. For example, in an embodiment, a single ASCII character may be used to encode both the type and the index of a node. In an embodiment, breakpoint locations may be encoded using methods provided to reduce storage and computing resource required.

Abstract: Techniques for encoding node locations are provided. In some examples, a node in a hierarchy such as a document object model (DOM) may be expressed as a location path from the root node of the hierarchy to the node. Each node on the location path may be encoded using a mapping between the type and/or index of the node and a set of characters such as ASCII characters. The encoding of each node on the path be concatenated to form the encoded location path. The encoding seeks to minimize the length of the encoded location path. For example, in an embodiment, a single ASCII character may be used to encode both the type and the index of a node. In an embodiment, breakpoint locations may be encoded using methods provided to reduce storage and computing resource required.

Abstract: 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.