Implementing InterSystems Business Intelligence
Performing the Initial Setup
This chapter describes setup activities to perform before you create cubes. It discusses the following topics:
Setting Up the Web Applications
The application name has an effect on how the application can be accessed; see the table below.
Note that the sample web application /csp/samples
is already configured to provide access to Business Intelligence and InterSystems IRIS NLP.
Placing the Business Intelligence Globals in a Separate Database
When you use Business Intelligence in a given namespace, that increases the amount of data stored in the database (or databases) used by that namespace. If the source table is large, the system correspondingly stores a large amount of its own data. The Business Intelligence caches further increase the storage needs. As a consequence, it is generally a good idea to map some of the Business Intelligence globals to different databases. You can map all the Business Intelligence globals to a single database or you can define multiple mappings. As an example, the following steps describe how to place all the Business Intelligence globals in a single separate database:
When you do so, you might consider pre-expanding the database (that is, setting its initial size), to avoid disk fragmentation created by runtime expansion.
Add a global mapping in the namespace that contains the classes that you plan to use with Business Intelligence. When you do so:
Also see the next section
for more specific mappings you might use.
Recompile all cube, subject area, and KPI classes in this namespace.
Alternative Mappings for the Globals
In some cases, you might want to separately map the Business Intelligence and related globals to separate databases. The following table lists the key globals:
This is not a comprehensive list; the system uses additional globals with names that start ^DeepSee
. Globals not listed here typically contain only small amounts of data or are typically defined only briefly.
Adjusting the Web Session Timeout Period
The User Portal respects the web session timeout period for the namespace you are working in. The default session timeout period is 15 minutes, which might not be long enough.
To increase the web session timeout period:
Go to the Management Portal.
in the row for the namespace in which you are using Business Intelligence.
Change the value of Session Timeout
, which specifies the default timeout period for the web session, in seconds.