Package oracle.AWAction

Contains classes that define actions to perform on an analytic workspace.

See:
Description

Class Summary

Alter	Alters the text attributes of an object in an analytic workspace.
Attach	Attaches an analytic workspace.
AWAction	An abstract class that specifies an action to perform on an analytic workspace.
BuildDatabase	Builds an analytic workspace by defining objects, loading data, and executing solves.
Commit	Commits the changes to an analytic workspace.
Create	Creates an object in an analytic workspace.
Delete	Deletes an object in an analytic workspace.
Detach	Detaches an analytic workspace.
Interaction	Assembles a series of actions into a unit of work to perform on an analytic workspace.

Package oracle.AWAction Description

Contains classes that define actions to perform on an analytic workspace. Action objects are assembled into units of work within Interaction objects.

The classes in the AWAction package implement a serial action model that you can store as XML and execute in an Oracle Database instance with the PL/SQL function INTERACTIONEXECUTE. For a diagram of the hierarchy of the classes in the package, see Action Model Classes. With the subclasses of AWAction, you can accomplish the same tasks in a non-interactive environment that a user of a Java application would initiate interactively.

Actions that Affect Metadata

Create, Delete, and Alter objects perform actions that affect object definitions in an analytic workspace; they do not affect data. For example, setting an AWXML.Cube as the base object of a Create object and then calling the Execute method of the Create object defines the structure of the measures and the dimensionality of the cube but does not load data or populate the dimensions. The actions of an Alter object affect the text attributes of an AWXML.AWObject object. For instance, you could use an Alter object to change the long and short descriptions of an AWXML.Dimension.

Actions that Affect the Workspace

Attach and Detach objects perform actions that affect the analytic workspace itself. The actions of a Commit object save your changes by storing them in the database tables.

Actions that Affect Data

To perform any action that involves data, you need to use a BuildDatabase object. The actions of a BuildDatabase object load data from the mapped data source and perform any predefined calculations on the data. Calculations, such as aggregations, allocations, and forecasts, are represented by Solve objects. The Solve objects for an analytic workspace are ordered within a SolveGroup. Calling the BuildDatabase.Execute method causes Oracle OLAP to execute the Solve object calculations of the SolveGroup in order.

Using the AWAction Package in Java Applications

The only way to affect the data in an analytic workspace is by using a BuildDatabase object. Unlike all the other action objects, you use a BuildDatabase in both batch and interactive environments. Whether you are building an interactive Java application or building XML for batch processing, you must use a BuildDatabase action object to load or calculate data in an analytic workspace.

Classes in the AWXML package have action methods for creating, deleting, and altering object definitions and for attaching, detaching, and commiting an analytic workspace. Those methods have an initial capital letter to distinguish them from other methods. The action methods of the AWAction classes simply call the AWXML action methods. For example, an AWXML.Cube object has a Create method that can store the definition of a cube within an analytic workspace. You could choose to use an AWAction.Create object to accomplish the same thing. To do so, you would pass in the Cube object to the setBaseObject method of the Create object and then call the Execute method of the Create object. The Create.Execute method then calls the Create method of the Cube object.