Setting Deployment Options

In the “Cube deployment options” page of the Cube Deployment Wizard, you specify load information and rejected records settings. You can also choose to save the deployment information in a MaxL script for deployment at another time.

To specify deployment options:

In the Cube deployment options page of the Cube Deployment Wizard, choose a load option from the Load task type group:
- Build outline—Adds dimensions or members (without data) to an Essbase outline.
- Load data—Populates an Essbase database with data. Loading data establishes actual values for the cells defined by the structural outline of the database.
- Build outline and load data—Adds dimensions and members without data to an Essbase outline and populates an Essbase database with data.
In the Load data options group, select one of the following options:
- Add to existing data—Select to add values in the data source to the existing values in the cube.
- Subtract from existing data—Select to subtract the values in the data source from the existing values in the cube.
- Overwrite existing data—Select to replace the values in the cube with the values in the data source.
Note:
These options are enabled only if you chose a data load option in step 1.
Optional: Select Delete all members first if you want to delete all dimensions and members in an existing Essbase outline.
When you delete all members, Essbase Studio removes all members from the Essbase database outline and then uses the member levels of the cube schema to recreate the outline. Because deleting all members can be slower than creating or updating an Essbase outline without deleting all members, Oracle recommends using this option only if you have a reason to do so. You should delete all members if, for example, you know that some members have been removed from an Essbase model and you want to build a smaller Essbase outline that contains the smaller set of members.
Note:
This check box is not enabled when you choose to only load data.
Optional: Select Delete and restore database to delete all members and data in the Essbase database before performing a member load or a member and data load.
This action clears the Essbase database outline of members and data before the outline build occurs, significantly reducing the time required for the load.
Note:
This check box is not enabled when you choose to load only data.
Optional: Select Incremental Load to select specific dimensions or members to update in the Essbase outline.
This check box is not enabled when you choose to only load data. It is also not enabled if, when building an outline, you select the Delete all members first option or the Delete and restore database option.
Note:
When you select this option, click the Next button and complete the tasks in Setting Up an Incremental Load for Cube Deployment.
Optional: Select Create and save rule file only to use later to load members and data from Administration Services Console.
Rules files generated by Essbase Studio contain SQL statements that specify the changes Essbase should make to members and data from a data source while loading them into the Essbase database.
The data source is not changed.
About Rules and Rules Files
Rules define operations that Essbase performs on data values or on dimensions and members when it processes a data source. Use rules to map data values to an Essbase database or to map dimensions and members to an Essbase outline.
Rules are stored in rules files. An Essbase Studio-generated rules file contains SQL statements that describe which build method to use, whether data values or members are sorted or are in random order, and how to transform data values or members before loading them. Essbase Studio creates a separate rules file for each dimension; however, if a measures dimension exceeds 250 members, then Essbase Studio creates one rules file for every 250 members.
Rules files are saved to the app directory of your Essbase installation.
For more information, see Rules File Limitations and Guidelines.
In Rejected records settings, perform these tasks:
1. For Number of records to keep, choose an option:
  - All—To keep all rejected records in the error file
  - Limit—To keep the number of rejected records in the error file that you specify in the text box at the right. The default is keep 200 records.
2. For Error file name, choose an option:
  - Default—To give the error file the default file name. The default file name has the following format:
```
app_name.db_name_timestamp.err
```
    For example:
```
myesbapp.myesbdb_05–02–08_11_30–38.err
```
  - File name—To specify a custom file name. For example, you may want to name the error file, errors.err.
    You may also specify a different location for the error file. By default, the error file is placed in:
```
EPM_ORACLE_HOME/products/Essbase/EssbaseStudio/server/ess_japihome/data
```
    To place the error file in a location other than the default, enter the relative path in the “File name” text box. For example, to name the error file errortest, and place the file in a folder called errors under the ess_japihome/data directory, enter the following:
```
errors/errortest.err
```
    To name the error file testerrors and place the file in a folder called errorlogs under the Essbase Studio server directory, enter the following:
```
../../errorlogs/testerrors.err
```
3. Optional: Select Stop the data load when the first record is rejected to stop a data load after Essbase encounters the first error during the load process.
  This option is enabled when the “Load data” or “Build outline and load data” option is selected.
In Scheduling Options, perform an action:
- To deploy the cube immediately, verify that Deploy now is selected.
  The “Deploy now” option is selected by default.
- To create a MaxL load script containing the deployment information, select Save as MaxL load script, click Browse and navigate to the location where the MaxL script will be saved, and then click Save.
Note:
At least one option from the Scheduling Options group must be selected.
Perform an action:
- If you selected the Incremental Load option, click Next and complete the tasks in Setting Up an Incremental Load for Cube Deployment.
- Click Finish to deploy the cube.
  The Deployment Succeeded dialog box is displayed for successful deployments, containing status information about the deployment.
  Note:
  If you encounter an out-of-memory error during cube deployment, increase the virtual memory setting for Essbase Studio Console, as described in Configuring Virtual Memory.
  Deployed cubes are displayed in the Metadata Navigator as children of the Essbase model from which they were deployed.
  After deployment, launch Administration Services Console to view and edit the outline. You can also query the cube using Smart View or Essbase Spreadsheet Add-in.
  If you chose to save the deployment information to a MaxL script, note that shell variables, $1 and $2, are used for the user name and password parameters respectively in the script.
  For example:
```
deploy all from model 'cs1Model' in cube schema '\CubeSchemas\cs1' login $1 identified by $2 on host 'poplar-pc1' to application 'cs2' database 'cs2' add values using connection 'Connection1' keep 200 errors on error ignore dataload write to default;
```
  In the above example, when using this script, you would make the following substitutions at the command line for Essbase login information:
  - $1 = user name
  - $2 = password