Deep Inside the Essbase Java API - Developing Essbase Applications - page 286

for the cubeview, but, actually, it appears to have no purpose in Essbase 11.1.1.4 and
11.1.2 and higher. In those versions of Essbase, the Java API was changed to allow a
single simultaneous operation. That change is enforced via an exception that is thrown
if there is an attempt to create a second cubeview while the first cubeview is still open.
The cubeview is also the container for Essbase options that affect the Essbase opera-
tions. he IEssCubeView interface contains a number of methods used to set the Essbase
options. you will find most of the method names familiar as they have counterparts in
the options dialogs of the classic Excel add-in and Smart view.
// set some options
cv.setAliasNames(true);
cv.setSuppressMissing(true);
// properties don't take effect until updated
cv.updatePropertyValues();
you must call the updatePropertyValues method for the options to take effect. This is
because the properties are not automatically pushed into the internal API structures in
order to optimize performance. you may update Essbase options anywhere in the task
sequence prior to performing a given Essbase operation.
The next task in the sequence is to get the IEssGridView instance from the IEssCubeView
instance. The gridview object must be initialized before use in order to set its size. The
reason for this is that the grid size is not predetermined. The internal structures used to
store information inside the grid require an allocation of memory. As the developer, you
are in the unique position to know how large you need the grid to be. Because you know
the size, you can set the grid size based on your needs, minimizing unnecessary and
time-consuming memory allocations. There are certain operations, such as the zoom
In operation, that may increase the size of the grid. When you are sizing the grid before
an operation, you do not have to consider the postoperation size of the grid. The Essbase
server will resize the grid automatically during the operation.
// get the gridview from the cubeview
IEssGridView gv = cv.getGridView();
// set the size
gv.setSize(3, 5);
The internal grid is a zero-based, multidimensional array. The is e tVa lu e method is
used to place values into the cells. There are different overloads for placing member
names and data into the cells. In all of the overloads, the first two arguments are the
zero-based row and column sizes. The third argument is either a Java String data type
for member names or a Java double data type to represent Essbase data.
// layout the members to retrieve
gv.setValue(0, 1, "Actual");
gv.setValue(0, 2, "New York");
gv.setValue(0, 3, "Sales");
gv.setValue(1, 1, "Qtr1");
gv.setValue(1, 2, "Qtr2");
gv.setValue(1, 3, "Qtr3");
gv.setValue(1, 4, "Qtr4");
gv.setValue(2, 0, "Product");