Database Reference
In-Depth Information
Table 3.2
Stud
io Console Commands
dumps
Displays information on a current server
threads
pconf
Displays state of the Studio server (threads,
resources, etc.)
squeue
Displays and lets you set number of tasks
waiting to be executed by the Studio server
sthd
Sets the number of threads being used by the
Studio server
sres
Sets the number of concurrent tasks being
executed by the Studio server (20 is the default)
While much of this chapter talks about ideas on prototyping with Studio, this section
is more relevant for those situations when you are using Studio in an ongoing produc-
tion scenario. The commands in table 3.2 may never need be changed from their default
settings, but it is useful to understand how to monitor and modify how Studio uses
threads and other system resources.
All of these commands can be executed directly in the Studio server. For example,
you can display the server threads and set concurrent tasks by issuing the following
commands in the Studio server window:
pconf
sres 250
realistically, however, the Studio server is likely running as a service. As such, you
can place these commands in the Studio Server.Properties file. For instance, to set the
number of server resources (sres), you include this line in the Server.Properties file:
server.resourceCount=250
Note:
Any commands issued directly in the Studio server temporarily override con-
flicting commands in the Server.Properties file.
3.7.5 Retrofitting Existing Models
Another common question when working with Essbase Studio is the ability (or inability)
to leverage an existing Essbase cube. If you want to leverage Studio for an ongoing pro-
duction deployment, what do you do with your existing Essbase cubes? Can you convert
the current models quickly into Studio? Can you simply add drill-through reports to an
existing Essbase cube?
The realistic answer is: It depends. Studio is a long-term replacement for EIS. If
you have an existing deployment leveraging EIS, then you can use the EIS catalog
migration wizard in Figure 3.45 to migrate the mini-schema, hierarchies and other
artifacts to the Studio catalog environment. While this does not create a perfect rep-
lica of the EIS deployment, it does provide a solid foundation for migrating an existing
deployment.
If you are leveraging Load rules for the current deployment, you cannot import these
rules into Studio. The hierarchies they represent, including any transformations, need
