DB2 OLAP Server Installation Guide

Samples for DB2 OLAP Server

This section describes how to set up the sample applications for DB2 OLAP Server.

Loading the sample databases for DB2 OLAP Server

To prepare the sample databases for use, you must load data into them. Each of the sample databases has a corresponding data load file.

Table 17 shows the sample applications, the databases that are contained within them, and their corresponding data load files:

Table 17. Sample databases and data load files

Application Database Data load file
Sample Basic Calcdat
Interntl Currcalc
Xchgrate Rates
Demo Basic Data
Samppart Company Calccomp
Sampeast East Calceast

To load data into the sample databases, choose an application and database and the corresponding data load file from Table 17 and complete these steps.

  1. Open Application Manager.
  2. Connect to the server on which the application is installed.
  3. From the Applications list box, select one of the applications.
  4. From the Databases list box, select one of the databases.
  5. From the Database drop-down menu, select Database > Load Data. The Data Load dialog box is displayed. The Data Load dialog box is described in detail in the Application Manager online help, and in the Database Administrator's Guide.
  6. Click the Find button above the Data files list box to locate a data file to load. The Open Server Data File Objects dialog box is displayed.
  7. Ensure that List Objects of Type is Text files.
  8. From the Objects list box, select a data load file.
  9. Click OK to close the dialog box. DB2 OLAP Server updates the Data Load dialog box to display the file you selected.
  10. Click OK to load the selected file. The data file is a fully calculated data set. It may take several minutes to load, and then the Data Load Completed dialog box is displayed.
  11. Click Close.

Providing user access to the sample applications

DB2 OLAP Server provides a comprehensive security system for a secure multiple user environment. By default, the sample applications are created with a security access level of None, which means that no user can connect to the sample databases unless the user is defined as a supervisor.

The system supervisor, defined when the server component was installed, automatically has supervisor privilege. Therefore, the system supervisor can make the sample applications available to other users.

To provide all users with Write access to the sample databases, repeat the following procedure for each database.

  1. Log on using the system supervisor account.
  2. Open the Application Manager.
  3. Connect to the server on which the application for which you want to provide access is installed.
  4. From the Applications list box, select the application.
  5. Select Application > Settings. The Application Settings dialog box is displayed.
  6. From the Minimum Database Access group, select the Write option and clickOK to save the setting. DB2 OLAP Server closes the dialog box and returns you to the Application Desktop window.

You can also use Administration Services to perform this task, using the Application Properties window. See the Administration Services Online Help for more information.

The applications are now ready for use. If you want to use the Partitioning applications, follow the instructions in Setting the environment for the partitioning sample applications. If you do not want to use the Partitioning applications, your next step might be to create the appropriate user names to be able to log on to DB2 OLAP Server. See the Database Administrator's Guide for information on creating users.

Setting the environment for the partitioning sample applications

DB2 OLAP Server includes two sample applications and databases that show the features of Partitioning:

These applications and databases include partition definitions stored in .ddb files. The .ddb files define the map between member combinations in the target database, Company, and the source database, East. The Database Administrator's Guide describes Partitioning, member combinations, and the differences between target and source databases.

For these applications to work in your environment, you need to match or change the information contained in the .ddb files.

To use the applications:

  1. Create a user named partitionuser. This is necessary because the sample partitions use this user name to transfer data between the Company database and the East database.
  2. Change the server name that is embedded in the applications.

    Do not edit the .ddb files to change this information. Instead, complete the steps in the following sections: Creating the partition user describes how to create the required user name, so that your users can use these applications. Changing embedded server names in the sample partition definitions describes how to change the embedded server name to your server name.

Creating the partition user

You must create a user named Partitionuser before you work with the Samppart and Sampeast applications. Partitionuser must have Application Designer access to both applications.

To create the Partitionuser:

  1. Open the Application Manager.
  2. Using a user name that is a supervisor or that has Create/Delete Users, Groups privilege, connect to the server on which the Samppart and Sampeast applications are installed.
  3. Select Security > Users/Groups. The User/Group Security dialog box is displayed.
  4. Click New User. DB2 OLAP Server displays the New User dialog box.
  5. In the Username text box, type partitionuser. Be sure to use all lowercase letters.
  6. In the Password text box, type a password. DB2 OLAP Server displays asterisks in the place of the characters you type. Type the password again in the Confirm Password text box.
  7. Click App Access. DB2 OLAP Server displays the User/Group Application Access dialog box.
  8. From the Applications list box, select Sampeast and click App Designer in the Access group.
  9. Select Samppart from the Applications list box, then click App Designer in the Access group.
  10. Click OK to return to the New User dialog box.
  11. Click OK to return to the User/Group Security dialog box.
  12. Click Close.

You can also use Administration Services to perform this task, using the User Properties window. See the online help for Administration Services for more information.

Changing embedded server names in the sample partition definitions

The following steps change the embedded server name in the partition definition files (.ddb) to your server name. The .ddb files shipped with Samppart and Sampeast are based on the server name localhost.

To change the server name in the Samppart Company .ddb file:

  1. In the Application Desktop window, select the Samppart application and Company database.
  2. From the Database drop down menu, select Database > Partition Manager. After a brief pause, DB2 OLAP Server displays the Partition Manager dialog box. If the Partition Manager dialog box does not appear or if it contains no definition entries, you might not have purchased and installed Partitioning. Contact your DB2 OLAP Server system administrator to ascertain this.
  3. Under the Source Cube heading, select the first definition entry, Localhost: SampEast: East.
  4. Click Edit. The Dangling Remote Reference dialog box is displayed. Because you are not connected to a server named Localhost, DB2 OLAP Server warns you before it enables you to edit the definition.
  5. Click Advanced. The Fix Dangling Partition Reference dialog box is displayed.
  6. In the Action group, select Correct the invalid partition reference.
  7. In the Server text box in the Reconnect group, replace Localhost with your server name.
  8. Click Apply. DB2 OLAP Server displays the Partition Manager dialog box.
  9. In the Source Cube list, select the second definition entry, Localhost: Sampeast: East.
  10. Repeat 4 through 8.
  11. In the Target Cube list, select Localhost: Sampeast: East.
  12. Repeat 4 through 8.
  13. Select Partition > Close to return to the Application Desktop window.

To change the server name in the Sampeast East .ddb file, take the following actions:

  1. In the Application Desktop window, select the Sampeast application and East database.
  2. From the Database drop down menu, select Partition Manager. After a brief pause, DB2 OLAP Server displays the Partition Manager dialog box.
  3. Under the Source Cube heading, select Localhost: samppart: Company.
  4. Click Edit. The Dangling Remote Reference dialog box is displayed. Because you are not connected to a server named Localhost, DB2 OLAP Server warns you before it enables you to edit the definition.
  5. Click Advanced. The Fix Dangling Partition Reference dialog box is displayed.
  6. In the Action group, select Correct the invalid partition reference.
  7. In the Server text box in the Reconnect group, replace Localhost with your server name.
  8. Click Apply. DB2 OLAP Server displays the Partition Manager dialog box.
  9. In the Source Cube list, select the first definition entry, Localhost: samppart: Company.
  10. Repeat steps 4 through 8.
  11. In the Target Cube list, select Localhost: Sampeast: East.
  12. Repeat steps 4 through 8.
  13. Select Partition > Close to return to the Application Desktop window.

Loading Data into Samppart and Sampeast

After setting up the environment for the Samppart and Sampeast databases, you need to load data into each database. This topic shows you how to load the Samppart Company database.

  1. Open the Application Manager.
  2. Connect to the server on which Samppart is installed.
  3. From the Applications list box, select Samppart.
  4. From the Databases list box, select Company.
  5. From the Database drop-down list, select Load Data. The Data Load dialog box is displayed.
  6. From above the Data files list box, click the Find button. The Open Server Data File Objects dialog box is displayed.
  7. Ensure that List Objects of Type is Text files.
  8. From the Objects list box, select CALCCOMP.
  9. Click OK to close the dialog box.
  10. Click OK to load the selected file.
  11. Click Close.

Repeat for the Sampeast application, East database, and calceast data file.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]