Setting Up DataStage for EPM

This chapter provides an overview of IBM WebSphere DataStage setup and discusses how to:

• Set up DataStage projects

• Configure environmental parameters

• Import *.dsx files

Understanding IBM WebSphere DataStage Setup and Configuration

This section provides an overview of DataStage setup and configuration.

Setting Up DataStage for EPM

In order for IBM WebSphere DataStage to work properly with EPM, you must perform the following setup and configuration steps:

• Create projects: Projects are used to import your *.dsx file metadata, which include ETL jobs.

• Setup and configure environmental parameters: Every ETL job uses environmental parameters and you must configure the default parameters.

• Import *.dsx files into projects: You must specify a project to hold your DataStage metadata, including ETL jobs.

Setting Up DataStage Projects

This section discusses considerations regarding the design of your DataStage projects and how to create a project.

Project Structure Considerations

Before you create your DataStage projects, you should consider how many projects you need to create. The number of projects you need depend on the following factors:

• The PeopleSoft source transaction system that you are using.

• The license codes for the Data Marts and/or EPM Applications you have purchased, or plan to implement.

• Disk space management based on storing hash files, log files, and *.dsx files.

• Common jobs necessary to all products (you may wish to create a separate project for the common jobs if you are implementing more than one data mart).

Based on the preceding information, you have the following options:

• Create one project per PeopleSoft source.

  For example, you can create a project called HCM_EPM91 for bringing data from a PeopleSoft Human Capital Management (HCM) source database.

• Create one project per EPM Warehouse (such as HCM or SCM warehouses).

  For example, you can create a project called CRM_EPM90 to handle all CRM-related Data Marts or EPM applications.

• Create one project for all the EPM Warehouses.

  For example, you can create a project called EPM90_ALL which will manage ETL jobs relating to all of the EPM Warehouses.

Because you need to create projects based on the preceding requirements, ensure that you have understood your long-term needs and requirements before creating suitable projects for importing the jobs.

Note. Certain operating systems, such as Unix, have a limit to the number of objects that can be created under one project or directory. Please check your operating system specifications before proceeding with project creation.

Note. There is no naming convention for projects.

Creating Projects

Use the following steps to create DataStage projects:

1. In the DataStage Administrator, enter the following information in the Attach to DataStage box:

   • Domain: Enter the name of the domain server machine.

     You can enter localhost if the client and server are installed on the same machine.

   • User name: Enter the user name that is required to log onto the machine on which the domain server is installed.

     The user name is the Windows login (if the server is running on a Windows platform) or the Administrator user that was used during the install (if the server is running on a Unix platform).

   • Password: Enter the password that is required to log onto the machine on which the domain server is installed.

   • DataStage server: Select the name of the server machine on which the DataStage engine is installed.

2. Click OK.

3. Click the Projects tab to view a list of available projects on the server.

4. Click the Add… button.

   The Add Project box displays.

5. Enter the project name in the Name field . You can specify your own naming convention in this field.

   Remember the project name is case-sensitive and you cannot change the project name after you have imported the dsx files. If you want to update or change the project, you only have the option to create a new project and import the dsx files again. DataStage Administrator automatically appends the project to the default location for a new project.

   Click the Browse button to select another location if the default location is not desirable (due to disk space constraints). Do not select the Create protected project check box as this would cause the project to be read-only.

6. Click OK to create the project on the server.

   This creates an empty project on the DataStage server. The updated list of projects displays after the copy is finished.

7. Repeat steps five through seven to create any additional projects.

8. When you are finished, click Close.

See Setting Project Properties.

See Also

WebSphere DataStage Administration: Administrator Client Guide

Configuring Environmental Parameters

This section discusses how to copy the DSPARAMS file and add values for environmental variables. You must configure default environmental parameters for each project you are using, as every job uses a subset of the environmental variables.

Copying the DSPARAMS File

Copying the DSPARAMS file enables you to bypass entering the parameters manually. Use the following steps to copy the DSPARAMS file:

1. Locate the DSPARAMS file using the following path on the installation CD:

   <PSHOME>\SRC\ETL.

2. In DataStage Administrator, navigate to the projects tab to determine the project home directory.

   The project home directory path can be found under Project Pathname field.

3. Select your project name.

4. Use the project home directory path to navigate to your DSPARAMS file.

5. Rename the DSPARAMS file located in the project home directory folder to DSPARAMS_old and paste the copied file.

   Now, you can see a DSPARAMS file under this path.

6. Repeat steps one through five for each project you have created.

Adding Values for Environmental Variables

You must add suitable values for each environmental parameter you plan to use. For example, if you are only implementing an EPM Warehouse, you need not update OWE related parameters.

Use the following steps to add values for environmental variables:

1. In DataStage Administrator, select the Projects tab of the DataStage Administrator box to view a list of available projects on the server.

2. Select the project you would like to configure.

3. Click the Properties button.

   The Project Properties window displays.

4. Click the Environment… button.

   The Environment Variables box displays.

5. In the Categories navigation frame, select User Defined.

6. Scroll to the bottom of the list and enter the default values based on the warehouse setup.

   Ensure you do not include any trailing spaces in the values.

Note. Ensure that you perform a detailed analysis of the various environmental variables that impact your requirements with respect to the project created and the corresponding values. Use defaults wherever required. If you have not provided the correct values for the chosen environmental variables, the related jobs may abort or not work as required.

See Environmental Parameters Information.

Importing Delivered .DSX Files

After you have created your projects and configured the project-level environmental parameters, you can import the .dsx files into the projects. PeopleSoft prepackaged .dsx files contain server jobs, job sequencers, and other metadata. The prepackaged jobs may belong to any of the following categories:

• Source to OWS

• Source to MDW (for CRM online marketing applications only)

• OWS to OWE

• OWS to MDW

• OWE to MDW

This section discusses preparations for importing .dsx files and how to import each type of .dsx file.

See Importing and Exporting Repository Components.

Preparing to Import *.DSX Files

Before you begin importing your *.dsx files, you should be thoroughly familiar with the DSX Files Import Description document located in the appendix of this guide.

See DSX File Import Descriptions.

The DSX Files Import Description document contains the following information:

• The first column provides information on the order in which .dsx files should be imported.

• The second column indicates whether the .dsx file corresponds to a specific warehouse/SKU or generic file.

• The third column describes the type of jobs the .dsx file contains, such as OWS, OWE, and setup.

• The fourth column describes the source system associated with the .dsx file.

• The fifth column provides the name of the .dsx file.

• The sixth column provides the location of the .dsx file on the installation CD.

• The seventh column provides a detailed description of the .dsx file.

In order to import the .dsx files, you must be able to link to the Windows File Server from the IBM WebSphere DataStage Client.

Note. The .dsx files are delivered as zip files and must be unzipped before importing.

Note. The .dsx files can only be installed on a Microsoft Windows client operating system. If you have installed EPM on UNIX, you must access the files from the Windows file server.

Steps to Import a .DSX File

Use the following steps to import a .dsx file:

1. In DataStage Designer, select Import, DataStage Components from the menu.

   The DataStage Repository Import window displays.

2. Click the Import from file browse button to locate the .dsx file you want to import.

   Do not select the Perform impact analysis check box unless you want to perform usage analysis. Selecting this check box increases the time it takes to import the .dsx files into a project.

3. Select Import All and click OK to import the file.

   Once the import process is complete, the Import Progress window closes.

Importing .DSX Files for EPM Analytical Applications Only

If you are planning to implement only the EPM Analytical Applications, the following sections provide a guide to .dsx files you need.

Import the following common .dsx files:

• COMMON_UTILITIES.dsx

• COMMON.dsx

• OWE.dsx

Import any or all of the following .dsx files, depending upon the number of PeopleSoft source transaction systems that you may have:

• WCS_OWS.dsx (For a PeopleSoft Campus Solutions database)

• WCR_OWS.dsx (For a PeopleSoft CRM source database)

• WFN_OWS.dsx (For a PeopleSoft FMS source database)

• WHR_OWS.dsx (For PeopleSoft HRMS and Learning Management source database)

• WSC_OWS.dsx (For a PeopleSoft SCM source database)

See DSX File Import Descriptions.

Importing .DSX Files for EPM Warehouses Only

If you are planning to implement only EPM Warehouses, import the following common .dsx files:

• COMMON_UTILITIES.dsx

• COMMON.dsx

Each EPM Warehouse (for example, Campus Solutions Warehouse or HCM Warehouse) requires a unique list of *.dsx files to import.

The appendix ETL Reference Documents helps you determine which .dsx files you need to import for your warehouse.

See DSX File Import Descriptions.