Updating an OLAP Server outline from a flat file

Use the Update outline from file (ESSOTL1) program to update an OLAP Server outline from a source flat file using load rules. The OLAP Server can be a DB2 OLAP Server or an Essbase server.

When you select a step that uses this program, link a source file to the step, but do not link the step to a target table.

../byb.gif Authorities and privileges

../rule.gif

To update an OLAP Server outline from a source flat file using load rules:

  1. Open the step notebook.

  2. Specify information for your step:

  3. On the Parameters page, in the OLAP Server system name field, type the name of the OLAP server to use.

  4. In the OLAP Server application name field, type the name of the OLAP Server application to use.

  5. In the OLAP Server database name field, type the name of the OLAP Server database that has the default calc script to call.

  6. In the OLAP Server user ID field, type the user ID to use to connect to the OLAP Server database.

  7. In the OLAP Server password field, type the password for the user ID.

  8. In the Verify OLAP Server password field, type the password again.

  9. In the Load rules file name field, type the name of the load rules file that you want the program to use. If the file is on the OLAP Server, the file name cannot have an extension. If the file is located on the agent site, you must specify the fully qualified file name.

  10. In the Load rules file location flag area, click the location of the rules file.

  11. In the Source file location flag area, click the location of the source file.

  12. On the Processing Options page, in the Agent Site list, select an agent site where you want your step to run. The selections in this list are agent sites that are common to the source tables, the target table, and the transformer or program that you are defining.

  13. If you want to have the option to to run your step at any time, select the Run on demand checkbox. Your step must be in test or production mode before you can run it.

  14. Optional: Select the Populate externally check box if the step is populated externally, meaning that it is invoked in some way other than by the Data Warehouse Center. The step does not have to have any other means of running in the Data Warehouse Center in order to change the mode to production.

    If Populate externally is not selected, then the step must either have a schedule, be linked to a transient table that is input to another step, or be started by another program in order to change the mode to production.

  15. In the Retry area, specify how many times you want the step to run again if it needs to be retried and the amount of time that you want to pass before the next run of the step.

  16. Click OK to save your changes and close the step notebook.

Related information

Moving and transforming data

Population type descriptions

List of steps and step subtypes

Data Warehouse Center concepts