Oracle International Corporation

Lsi Logic Corporation

Xsigo Systems

Lsi Corporation

Ariel Cohen

Fernando Alurralde Iturri

Boris Zemlyak

Ashok Krishnamurthi

Ronen Perets

Nicolas Damonte

Javier Espeche

Jonathan Lopez Lopez

Rajesh Tiwari

Qing Zhong

Shreyas Shah

Raymond Lim

David S Allison

Ming Fung Wong

Ganesh Sundaresan

Cheng Tang

Greg Lockwood

Dror Har-Chen

Viswanath Krishnamurthy

Frank Salzmann

Thomas Kauth

Gerald Cheung

Vikram Venkataraghavan

Patricio Barletta

Juan Allo Ron

Esteban Alejandro Capillo Carril

Yogeshwar Wamanrao Kuntawar

Naveed Cochinwala

Pierre Aulagnier

Pablo Hadziatanasiu

Steven Mayze

Abhinav Anand

Susheel Tadikonda

Process flow is created that represents a process-based software application. User specified connector creation information for creating connectors is received. User specified element information are received for associating elements with the process flow. One of the elements is a service task, and a connector is selected and configured from the connectors. The process-based software application is executed in a first computing environment. Interactions between the process-based software application and the connector framework are provided during the executing of the process-based software application in the first computing environment. The process-based software application is executed in a second computing environment. The process-based software application does not interact with the connector framework during the executing of the process-based software application in the second computing environment.

Executing a process-based software application in a first computing environment and a second computing environment

Resource-to-operation pairs are received at a user interface. The resource-to-operation pairs are stored in a model abstraction as a flat structure. The resource-to-operation pairs in the flat structure are converted into Representational State Transfer (REST) connectors. The REST connectors are encoded in a conventional interface description language. The REST connectors are stored in webpage code. A request is received at the webpage code from the client system for a service of a process step of the process-based software application. A REST connector in the webpage code translates the request to a message that conforms with the service. A response from the service is received at the webpage code. The response from the service is processed at the webpage code. Data retrieved by the processing of the response is accessed via a browser located at the client system.

Providing communication between a client system and a process-based software application

A layer of abstraction is provided for developing, configuring, displaying, selecting, and re-configuring connectors used through stages of predeployment, deployment, and post-deployment. A connector is created with the layer of abstraction, wherein the connector provides a first configuration of added functionality to software components for calling a web service. The connector is used to tie a step of a process-based software application to the web service. A different configuration of added functionality is provided for each of the stages of predeployment, deployment, and post deployment using the layer of abstraction.

Providing a different configuration of added functionality for each of the stages of predeployment, deployment, and post deployment using a layer of abstraction

An example system and method facilitates customization of and configuration of a software connector, such as a connector to an Application Programming Interface (API) or web service, in various types of computing environments, including both pre-deployment and post-deployment computing environments. A connectors framework provides a layer of abstraction between connectors maintained in the different environments and a connector editor of an application development system (which may be implemented via a server-side integrated development environment). The connector editor may provide User Interface (UI) functionality, including one or more UI controls for editing or otherwise modifying, customizing, and/or configuring connectors in pre-deployment and/or post deployment environments, which may represent or correspond to different connector and accompanying software development stages.

Pre/post deployment customization

An example system and method provides an enhancement to a software editor, enabling a user (e.g., developer) to visualize a REST API (also called a REST service herein) as a list of resources presented in a flat structure, i.e., a simple list of resources containing operations. The software editor may be a fully JS/HTML/CSS (JavaScript, HyperText Markup Language, Cascading Style Sheets) compliant editor that lets the user define connectors to REST API's in an easy and fluid way. Furthermore, the editor facilitates creation of a connector to the REST API in a generic fashion, without requiring user knowledge of any particular interface or description language, such as RAML, YAML, WADL, etc. The user, e.g., developer, may simply define resources and corresponding operations to thereby enable the editor to automatically generate a corresponding connector to the REST API. The enhanced software editor also facilitates creation of business objects from a JSON instance or schema.

Automatically generating an interface description in an interface description language

Provided is a novel approach for connecting servers to peripherals, such as NICs, HBAs, and SAS/SATA controllers. Also provided are methods of arranging peripherals within one or more I/O directors, which are connected to the servers over an Ethernet network. Such arrangement allows sharing the same resource among multiple servers.

Remote shared server peripherals over an ethernet network for resource virtualization

An example system and method facilitates developing and interacting with connectors that represent or are associated with services or interfaces to be implemented in a computing environment. The example system includes a connector editor backed by a connectors framework that specializes and links to the specific editor and dialogs that enables a developer to customize and configure any of plural available connectors for a specific purpose (e.g., to connect a process step to a particular type of web service). Furthermore, the connectors framework and associated editor(s) enable all of the connectors of available connector types to be configured using the same life cycle and to be automatically parameterized to use different data when running on the different environments, e.g., different test and production environments.

Connectors framework

Generic-flat structure rest API editor

A system and method for enhancing web application performance by selectively caching information used by different stages of server-side processing of a request for webpage content from a client system. An example method involves using a specialized cache requestor for selectively fetching and caching JavaBean properties once per request lifecycle. The cached JavaBeans properties may then be used by different request-processing stages of the lifecycle, thereby obviating the need to implement multiple external requests for JavaBeans properties, i.e., multiple accesses of dynamic context. The cache requestor may leverage functionality provided by a JSF phase listener (JSF phaseListener) and a JavaBean proxy (BeanProxy) to keep the retrieved state information accessible to the request processing and associated JSF container.

Request cache to improve web applications performance

A system and method for providing a process player for use with a business process design environment. In accordance with an embodiment, a user can select, configure, and play an instance of a business process being developed in the design environment. During play of a selected business process instance the user can configure and play interactive activities of the selected instance. For example, the user can walk through an instance of the business process, while impersonating different users or roles in its interactive activities.

System and method for providing a process player for use with a business process design environment

Provided is a novel approach for connecting servers to peripherals, such as NICs, HBAs, and SAS/SATA controllers. Also provided are systems for arranging peripherals within one or more I/O directors, which are connected to the servers over an Ethernet network. Such arrangement allows sharing the same resource among multiple servers.

Remote shared server peripherals over an Ethernet network for resource virtualization

Methods and apparatus are provided for transferring data between servers and a remote entity having multiple peripherals. Multiple servers are connected to a remote entity over an Remote Direct Memory Access capable network. The remote entity includes peripherals such as network interface cards (NICs) and host bus adapters (HBAs). Server descriptor rings and descriptors are provided to allow efficient and effective communication between the servers and the remote entity.

Efficient data transfer between servers and remote peripherals

Mechanisms provide hosts such as servers and mobile devices with access to virtualized I/O resources including virtual Host Bus Adapters (vHBAs) and virtual Network Interface Cards (vNICs) over a wireless I/O interconnect. Host applications access virtualized I/O resources using virtual device drivers that communicate with virtualized I/O resources on an I/O director using a reliable communication protocol running over a wireless network. I/O data is throttled if necessary based on wireless network considerations.

Wireless host I/O using virtualized I/O controllers

Mechanisms are provided to allow servers connected over an InfiniBand fabric to communicate using multiple private virtual interconnects (PVIs). In particular embodiments, the PVIs appear as virtual Ethernet networks to users on individual servers and virtual machines running on the individual servers. Each PVI is represented on the server by a virtual network interface card (VNIC) and each PVI is mapped to its own InfiniBand multicast group. Data can be transmitted on PVIs as Ethernet packets fully encapsulated, including the layer 2 header, within InfiniBand messages. Broadcast and multicast frames are propagated using InfiniBand.

Growing community of inventors

Cupertino, CA, United States of America

Ariel Cohen