Oracle International Corporation

Alvin H To

Rahim Mohamed Yaseen

Jon Degenhardt

Sanjin Tulac

Sudhakar Kaki

Yu Sui

Min Lu

Kaushik Roy

Maria Elisabeth Kaval

Christopher Scott Nash

Kanchan Shringi

Vipul Shroff

Dejia Wang

Sean Kevin Frogner

Yee Wah Lee

Dieter Gawlick

Hasan Rizvi

Sandeep Jain

Sashikanth Chandra

Premal Shah

In one embodiment, a method for handling subtasks within a business task includes providing a plurality of user interfaces (UIs) pertaining to the business task having at least one subtask step. The subtask step has a subtask defined within the business task by an intermediate user to reuse a portion of another business task. The method further includes allowing an end user to navigate back and forth through the plurality of UIs.

Sub-task mechanism for development of task-based user interfaces

A method for building wizard-style user interfaces (UIs) for a business task is disclosed. The method includes receiving metadata at a computer system, where the metadata comprises information regarding the business task, generating an analysis by analyzing the metadata, generating user guidance information, and executing flow and business logic of the business task. The user guidance information is with regard to the business task, and the user guidance information is based on the analysis.

Declarative task-based user interfaces

In one embodiment, a method for building wizard-style user interfaces (UIs) for a business task includes identifying a collection of metadata associated with the business task, and processing the collection of metadata to provide a set of wizard-style UIs pertaining to the business task.

An advanced message queuing system is integrated into a database system. A queue is an ordered list of messages. Messages are requests for processing by an application. Messages are database objects and can represent events or data. Messages comprise user data and control information such as a queue name. Each queue is part of a table in a relational database. A queue table holds a set of queues. Dictionary tables store configuration information describing queues and queue tables. Messages are entered into a queue by instructing the database system using an enqueuing command attached to a message and control information. The control information describes how to order, schedule, and execute the message, and can include a result queue name into which a result message is written after execution. The system responds to a dequeuing command by delivering a copy of a message from the queue. A user can define message order within a queue, message delay factors, and exception processing. Messages may be retained in their queues after delivery and can be preserved, queried, documented, correlated, reviewed and tracked, alone or in a set comprising a transaction, regardless of message state or execution state. The system can be used to develop large-scale, message-oriented distributed applications. Existing development tools for database applications can also be used to develop queuing applications. Administrative functions to create, delete, and specify access control for queues are provided. The system provides transactional integrity; a single transaction applies to both the database and the queue. A single transaction log is maintained.

Apparatus and method for message queuing in a database system

Growing community of inventors

Redwood City, CA, United States of America

Alvin H To