Download pdf - RDM&CDS InstallGuide

8/9/2019 RDM&CDS InstallGuide

1/70

Corporate Data Store andReference Data M anager

I nstal lation Guide 2004-2006 Landmark Graphics Corporation

R2003.18.1 June 2006


2/70

2004-2006 Landmark Graphics CorporationAll Rights Reserved Worldwide

This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected byFederal copyright law. No part of this publicat ion may be copied or distributed, transmitted, transcribed, stored in a retrieval system,or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or

disclosed to third parties without the express written permission of:

Landmark Digital and Consulting Solutions2101 CityWest Blvd, Building 2, Houston, Texas 77042-3021, USA

P.O. Box 42806, Houston, Texas 77242, USAPhone: 713-839-2000FAX: 713-839-2401Web: www.lgc.com

Trademark Notice

3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance, Active Reservoir Surveillance,ADC, Advanced Data Transfer, ARIES, Asset Development Center, Asset Development Centre, Asset Performance, AssetView,

Atomic Meshing, BLITZPAK, CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store, Data Manager, DataStar,DBPlot, Decision Suite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpace AssetView, DecisionSpace

Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace Nexus, DecisionSpace PowerGrid,DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion,

DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Express3, DepthTeam Extreme, DepthTeam Interpreter,Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DFW, DIMS, Discovery, Discovery Asset, Drill-to-the-Earth Model,

Drillability Suite, Drilling Desktop, DrillModel, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EDM,eLandmark, Engineers Data Model, Engineer's Desktop, Engineers Link, Executive Assistant, ezFault, ezSurface, ezTracker,

FG+, FastTrack, FieldPlan, FieldWorks, FZAP!, GeoDataLoad, GeoGraphix (stylized), GeoGraphix Explorat ion System, GeoLink,GeoProbe, GeoProbe GF DataServer, GES, GESXplorer, GMAplus, GRIDGENR, Handheld Field Operator, I 2 Enterprise, iDIMS,

IsoMap, iWellFile, Landmark, Landmark and Design, Landmark logo and Design, Landmark Decision Center, LandScape,LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Magic Earth, MagicDesk, MagicStation, MagicVision, Make Great

Decisions, MathPack, Model Builder, MyLandmark, Nexus, Object MP, OpenBooks, OpenExplorer, OpenJournal, OpenSGM,OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView,

Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PowerCalculator, PowerExplorer, PowerHub, PowerInterpretation, PowerJournal, PowerModel, PowerSection, PowerView, Production Asset Manager, PRIZM, PROFILE, Project

Administrator, ProMAGIC, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx,QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RTOC, Real-Time Asset

Management Center, Real-Time Asset Management Centre, Real Time Knowledge Company, Real-Time Operations Center, RealTime Production Surveillance, Real Time Surveillance, Reference Data Manager, RESev, ResMap, RMS, SCAN, SeisCube,

SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisXchange, Sierra, Sierra (design), SigmaView, SimResults,SIVA, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap, Stratamodel, StrataSim, StratWorks, StressCheck,

STRUCT, Surf & Connect, SynTool, TDQ, Team Workspace, TERAS, Total Drilling Performance, TOW/cs, TOW/cs The OilfieldWorkstation, TracPlanner, Trend Form Gridding, Turbo Synthetics, VIP, VIP-COMP, VIP-CORE, VIP-DUAL, VIP-ENCORE,

VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Web OpenWorks, Well Seismic Fusion,Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellXchange, WOW, Xsection, You're in

Control. Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered trademarks or service marks of LandmarkGraphics Corporation.

All other trademarks are the property of their respective owners.

Note

The information contained in this document is subject to change without notice and should not be construed as a commitment byLandmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in thismanual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore,

this statement may not apply to you.


3/70

Landmark CDS and RDM Installation Guide

R2003.18.1 About this Manual: Introduction 1

In t roduc t ion

About this Manual

This manual provides basic instructions for new installations forCorporate Data Store (CDS) and Reference Data Manager (RDM).

The Corporate Data Store solution includes the use of several software packages from Landmark and other vendors. The installation of theCDS program as well as any special configurations for the third party

products is included in this manual. This manual does not cover

installation instructions for the third party products or for otherLandmark products. Please refer to their manuals for their installationinstructions.

Who Should Ins ta ll

CDS is a sophisticated database product that interacts with severalthird-party software packages. For best results, the individual or teamthat installs CDS should have experience in system administration anddatabase administration. Familiarity with third party products, such as

Oracle, is also needed for optimum results.

Database Schema Inform at ion

CDS has a primary schema through which the CDS database isaccessed with the help of the PowerHub dictionary schema. E&Pcorporate data is stored in additional schemas (POSC Epicentre andOpenWorks), which are managed via the main CDS schema.

CDS and RDM Docum entat ion The documentation issued with this release includes:

The CDS/RDM Installation Guide (.pdf file)

CDS Release Notes (.pdf file)


4/70

CDS and RDM Installation Guide Landmark

2 About this Manual: Introduction R2003.18.1

RDM Release Notes (.pdf file)

RDM User Guide (.pdf file located at $ PE_HOME/www/cds/ RDM_2003_18_0_User_Guide.pdf )

CDS data model and and entity relationship (ER) diagrams(electronic copy located at $ PE_HOME/www/cds/cdsDoc.zip )

After CDS is installed, the data model and ER diagrams can beaccessed in a browser at the URL

/cds/info_groups.htm or cds_model.htm. For example:

The PowerExplorer installation is at //pe_server/PowerE xpl orer/ pe/default/index.html .

The ER diagrams can be found at //pe_server/PowerE xpl orer/cds/

info_groups.htm .The data model can be found at //pe_server/PowerExpl orer/cds/ cds_model.htm .


5/70


R2003.18.1 Contents 1

Contents

Introduction ....................................................................................................................... 1About this Manual .............................................................................................................. 1

Who Should Install ...................................................................................................... 1Database Schema Information ..................................................................................... 1CDS and RDM Documentation ................................................................................... 1

Creating a New CDS/RDM Installation ................................................................ 3Pre-Installation Information................................................................................................ 3

Third Party products and Landmark products needed for installation ......................... 3CDS Configuration Scenario ....................................................................................... 3

Pre-Installation Instructions................................................................................................ 6Using the Installation Wizard ............................................................................................. 9Post-Installation Instructions .............................................................................................. 21

Starting the Server ....................................................................................................... 21Setting Permissions ...................................................................................................... 21Creating and Updating Oracle Database Statistics ...................................................... 22Linking RDM to ADT ................................................................................................. 22Configuring Users for Using ADT with CDS ............................................................. 23Updating OpenWorks Projects for Data Cleanup Tool ............................................... 24

Script for OpenWorks Instance .............................................................................. 24Script for OpenWorks Projects .............................................................................. 26

Directory Setup for ASCII Files .................................................................................. 28Correctly Defining OpenWorks Projects in PowerExplorer ........................................ 29Creating and Configuring New CDS Users ................................................................. 30

Creating New CDS Usernames .............................................................................. 30PowerExplorer Configurations .............................................................................. 32

Create Database Credentials ........................................................................................ 35Launching RDM .......................................................................................................... 36

Command Prompt .................................................................................................. 36OpenWorks Method ............................................................................................... 36

Data Administration Scripts ..................................................................................... 37

Uninstalling and Restoring from backup files for a CDS UpgradeInstallation .......................................................................................................................... 39

Uninstalling......................................................................................................................... 39Restoring ............................................................................................................................. 41


6/70


2 Contents R2003.18.1

Upgrading to CDS/RDM R2003.18.1 ..................................................................... 45Before Doing the Upgrade.................................................................................................. 45Using the Upgrade Wizard ................................................................................................. 48Post Installation Instructions............................................................................................... 56

Starting the Server ....................................................................................................... 56

Creating and Updating Oracle Database Statistics ...................................................... 56Updating OpenWorks Projects for Data Cleanup Tool ............................................... 57Script for OpenWorks Instance .............................................................................. 57Script for OpenWorks Projects .............................................................................. 58

Directory Setup for ASCII Files .................................................................................. 59Launching RDM .......................................................................................................... 60

Command Prompt .................................................................................................. 60OpenWorks Method ............................................................................................... 60

Appendix A : Configuration of Spatializer for Use with CDS ................ 63

Introduction......................................................................................................................... 63Configuration Steps ............................................................................................................ 64


7/70


8/70


9/70


10/70


6 Pre-Installation Instructions: Creating a New CDS/RDM Installation R2003.18.1

Pre-Installation Instructions

The installation of CDS and RDM is directed by an installation wizard.The steps for installing on Linux and Solaris are the same.

Prior to installing CDS/RDM, please ensure the following:

1. The PH server and 3rd party servers have been stopped beforedoing the back up process cd $PE_HOME/bin and type

r unSer ver Manager - st op_al l

2. $PE_HOME is set to the location where PowerExplorer has beeninstalled.

3. The environment variable $ORACLE_SID is set to the SID youcreated during the OpenWorks install. This SID must also bedefined in the tnsnames.ora file.

If you have multiple Oracle SIDs, please define the SID you wantto use for the CDS install. Initialize this SID prior to starting theCDS installation wizard.

4. $ORACLE_HOME is set to the same $ORACLE_HOME valueassociated with the OpenWorks Oracle installation.

NOTE: ORACLE_SID

The ORACLE_SID set for CDS/RDM needs to be a valid 2003.12.1.3 (or later)

OpenWorks instance, which can be an empty one created specifically for the purpose of housing CDS. The associated PowerExplorer data dictionary musthave the same ORACLE_SID.


11/70


R2003.18.1 Pre-Installation Instructions: Creating a New CDS/RDM Installation 7

5. Make Sure $ORACLE_HOME/bin is defined and embeddedwithin $PATH environment variable. The following error messagewill be displayed if this variable is not defined.

6. I t i s important that you back u p the PowerH ub dictionary(defaul t name is pe_dic) and the OpenWorks OWSYS schemaprior to installi ng CDS.

If a fatal error occurs during the CDS installation process, thePowerHub dictionary and the OpenWorks OWSYS schema can be

restored to their original state from these backups, greatlysimplifying the process of uninstalling (see Uninstalling andRestoring from backup files for a CDS Upgrade Installation on

page 39 ) and reinstalling CDS.

To back up the PowerHub dictionary, first log on with a user idthat can access the Oracle export utility, and then enter thefollowing command:

exp user i d=< dba_username >/@< Oracle_SID_of_CDS >f i l e=< PE_PH_Dictionary >. dmpl og=< PE_PH_Dictionary >. l ogowner =< PE_PH_Dictionary >

To back up the OpenWorks OWSYS schema, enter the followingcommand:


12/70


8 Pre-Installation Instructions: Creating a New CDS/RDM Installation R2003.18.1

exp user i d=< dba_username >/@< Oracle_SID_of_CDS > f i l e=owsys . dmpl og=owsys . l og owner =owsys

7. Backup the PowerExplorer and PowerHub server runtimeenvironment using the following commands:

cd $PE_HOME

t ar cvf < backup_path_to_pe.tar > .


13/70


R2003.18.1 Using the Installation Wizard: Creating a New CDS/RDM Installation 9

Using the Installation Wizard

This section shows the steps needed to run the installation wizard andexplains each of the screens in the wizard.

Note that a minimum of 2 GB of swap space is required for theinstallation process.

1. Log in as root and set up the CD-ROM drive. Place the installationcd with the correct platform in the drive.

2. Log on as the PowerExplorer owner.

3. Set the display to your local computer.

4. Make sure that the PowerHub and third server processes areshutdown completely using the commands:

cd $PE_HOME/ bi n; r unSer ver Manager - st op_al l

If everything is not shut down completely, use kill -9 to terminateany remaining PowerHub-related processes.

5. Change to the CDS 2003 directory on the CD-ROM.

6. To start the installation wizard enter:

For Linux: sh cds_linux_install.binFor Solaris: sh cds_solaris_install.bin

You may get the following error message after launching thewizard, which can be ignored:

Er r or r edi r ect i ng st dout . Out put wi l l be pl aced i nt o' out . t xt ' i ns t ead.


14/70


10 Using the Installation Wizard: Creating a New CDS/RDM Installation R2003.18.1

7. The installation wizard opens to introductory information. ClickNext to continue.


15/70



8. The first decision is to chose the product features to be installed.

There are three options for Install Set :

Typical - Install both CDS and RDM.

Minimal - Install CDS only.

Custom - Install CDS only (same as Minimal). Note that thisversion of RDM cannot be installed by itself. To install RDMonly, you will need RDM Standalone.

To see a description of what is included in CDS or RDM in theDescription panel, click on either Corporate Data Store orReference Data Manager in the upper panel.

After selecting the product features, click Next to proceed.


16/70



9. The next screen asks for the directory that contains PowerHubserver. If you have previously set this directory as PE_HOME, thisdirectory is listed under PowerExplorer Home.

To modify the location of PowerExplorer Home, click Choose to browse for the directory of choice.

Click Restore Default Folder after making a change to return toyour previously defined PE_HOME directory.

Click Next to proceed.


17/70


18/70



11. In the next screen, enter general information for the new CDSinstallation associated with the previously designatedORACLE_SID. The value for this ORACLE_SID is shown in thetext box.

Enter the name for this installation of CDS..

Please note that in the post-installation instructions, wherever the

installation name that you entered in this dialog is a required input,it is indicated by the variable name .

Select the Default Geographic Coordinate Systems and the Default Measurement Systems from the pulldown menus.

Click Next to proceed..

Naming Requirements for CDS Installations

Letters must be in lower case.

The CDS name cannot exceed 23 characters.

The prefix cds_ is automatically added to each name. For example, ifdev is input as the name, the installation will be labeled cds_dev .


19/70



12. On this screen, enter a name and filename for the CDS tablespace.

The usual location for the CDS tablespace in under /export/home/ oracle . However, this file can be placed in any directory, includinga directory on another server.

Click Next to proceed


20/70



13. On the following screen enter the path to the OpenWorks HomeDirectory:


21/70



14. The next two screens contain information that needs to bereviewed prior to installation.

To make changes, click Previous to navigate to the appropriatescreen.

When satisfied with the inputs, click Install . The installer begins building the CDS schema. Once the in stall ation pr ocess begin s,do not cli ck Cancel.

As the installation process begins, Java Runtime Environment isloaded and installation scripts are unpacked.


22/70



15. Use the instructions in the installation screen to run an OpenWorksconfiguration script.

The script sets up the OpenWorks schema as well as addingadditional triggers in the OpenWorks database.

The content of the script is as follows:

I t wi l l t ake about 10 - 20 mi nut es t o creat e t heCDS OpenWor ks pr oj ect .

Pl ease do not i nt er r upt t hi s scr i pt pr emat ur el y.

Cr eat i ng CDS OpenWor ks proj ect now. . .

Prior to running the create_ow_prj.sh script , you must set theORACLE_ SID, OWSYSSID, and ORACLE_HOME environmental variables

that are to be used for the CDS internal OpenWorks project.


23/70



OW_DEV: proj ect cr eat e successf ul

: i nt er nal CDS OW pr oj ect cr eat e successf ul

SQL*Pl us: Rel ease 8. 1. 7. 0. 0 - Pr oduct i on on Tue Aug5 09: 57: 35 2003

( c) Copyr i ght 1999 Or acl e Cor por at i on. Al l r i ght sr eser ved.

SQL> Connect ed.

SQL>

User al t er ed.

SQL> Connect ed.

SQL>

1 r ow del et ed.

SQL> 2

1 r ow cr eat ed.

SQL> Di sconnect ed f r omOr acl e8i Ent er pr i se Edi t i onRel ease 8. 1. 7. 4. 0 - Pr oduct i on

Wi t h t he Par t i t i oni ng opt i on

J Server Rel ease 8. 1. 7. 4. 0 - Pr oduct i on

16. Extend the newly created OpenWorks project by running the script$OWHOME/bin/extendAllProjectR2003_12_1_3 (or the correct

project extension script for version of OpenWorks being used).

You can close the window running the script when it has finishedrunning.

17. Click the Next button in the installer screen.

Epicentre and CDS installations begin. Several scripts will be runto load the databases used for CDS. While the installation isrunning, the following screen is displayed.


24/70



The installation takes an hour or more depending on the speed ofyour computer.

For approximately the first 20 minutes, the log file will not change.When the scripts begin running, changes are recorded in the logfile.

When the installation is complete, the wizard advances to theI nstallation Complete screen. If the installation was successful, amessage to that effect is displayed on the screen.

If there were errors during installation, an error message appearson the screen. If errors occurred, go to on page 36 forinstructions on how to uninstall CDS and begin the installation

process again. If you have additional problems, please contactLandmark support.

Click Done to close the installation wizard.

After installing CDS, electronic copies of the RDM Users Guide( RDM_2003.18.1_User_Guide.pdf ) and the CDS Data Model

(cdsDoc.zip ) are placed in the $ PE_HOME/www/cds directory.

The data model and ER diagrams can be accessed in a browser atthe URL

/cds/info_groups.htm orcds_model.htm.

For example, the PowerExplorer installation is at //pe_server / PowerExplorer/pe/default/index.html .

The ER diagrams will be found at //pe_server/PowerExpl orer/ cds/info_groups.htm .

The data model will be found at //pe_server/PowerE xpl orer/ cds/cds_model.htm .


25/70


26/70


27/70


R2003.18.1 Post-Installation Instructions: Creating a New CDS/RDM Installation 23

l n - s $ADT_HOME/ conf adt

Conf igur ing Users fo r Us ing A DT wi th CDS

For each user who will use ADT to move data to or from CDS, youneed to first add the OpenWorks username as an Oracle user and thengive the user access to CDS internal OpenWorks project. This is

because for ADT to work properly, the OpenWorks username must berecognized by both the OpenWorks project to (or from) which the datais being copied and the CDS internal OpenWorks project.

To add an OpenWorks username to the CDS internal OpenWorks project:

1. Log on to the machine that contains the CDS internal OpenWorks project (OW_< CDS_NAME >).

2. Set the OWHOME environmental variable to the path for theOpenWorks directory. For example:

expor t OWHOME=/ Landmar k/ OpenWor ks

3. Set the ORACLE_HOME environmental variable to the path forthe Oracle directory.

4. Change to the OpenWorks home directory.

cd $OWHOME/ bi n

5. Enter the following command:

. / or auser

6. When prompted, enter the username and password for Oracles

database administrator.

7. Use the orauser utility to add an OpenWorks username for any userwho will need to move data to or from CDS via ADT. When theorauser utility starts, select Option 1, which is Add a user to anOracle database . Accept the default to create an external user.Accept the defaults for tablespace.

Note: This step presumes that there is already an existing operating systemaccount.


28/70


24 Post-Installation Instructions: Creating a New CDS/RDM Installation R2003.18.1

Repeat for each user.

To give these same OpenWorks users access to the CDS internalOpenWorks project:

8. Log in as an OpenWorks user with OW_ADMINISTRATOR privileges and MANAGE access to the OW_< CDS_NAME > project.

9. Start OpenWorks.

s tar tow

10. In the OpenWorks Command Menu, select Project > ProjectAdmin .

11. In the Project Administration utility, highlightOW_< CDS_NAME >. Select User > Manager .

12. In the Project User Administration dialog, highlight the name ofthe user and click the dialogs right-pointing arrow to move theOpenWorks user to the User In Project box.

13. Exit when all users have been added to the project.

Updat ing Op enWorks Pro jects for Data Cleanup Tool

RDM R2003.18.1 requires some changes to OpenWorks projects at theOracle level in order to use the Data Cleanup tool. You will need to runtwo scripts that are located in $PE_HOME/dbadmin_scripts .

Script for OpenWorks Instance

The script create_rdm_fk_table.sh creates a table in the OWSYSschema of Foreign Key information that RDM reads during datacleanup. This must be run for all OpenWorks instances that RDM willconnect to, even if the instance had been updated using this script

during a previous installation of RDM.

Use the following procedure for each OpenWorks instance:

1. Change to the $PE_HOME/dbadmin_scripts directory.

2. Set the environmental variable $RDM_HOME.


29/70



RDM_HOME resides in the same place as PE_HOME; that is, twodirectory levels up from the RDM script runRDM_gui .

3. Enter on the command line:

cr eat e_r dm_f k_t abl e. sh

4. At the prompt, enter an Oracle userid with system DBA privileges.Click Enter .

5. At the prompt, enter the password for the above Oracle userid.Click Enter .

6. At the prompt, enter the OpenWorks database instance name(SID). Click Enter .

The script is then initiated.

When complete, the location of the log file created during the process is provided. For example:

Log f i l e l ocat ed at / t mp/ RDM_opt r on32_f kdat a_508


30/70


31/70



Removi ng t he t empor ar y manage r ol e f or t he t ar get OW pr oj ect .

Fi l es are l ocat ed at / t mp/ RDM_si d_pr oj name_const r ai nt s_2812. 0

The final line contains the location of the directory that containsthe log file and the control file used to drop and rebuild the

constraints, generated_constraints_redefine.sql .

Verify that the number of constraints before or after conversion isthe same. If there is a discrepancy, the control file can be used tomanually recover the constraints.

8. To continue with another project from the same OpenWorks SID,enter another OpenWorks project name.

To exit, click Enter . At the prompt, enter y.


32/70



Directo ry Setup f or A SCII Files

RDM allows you to move reference data in and out of ASCII filesusing the Reference Data Transfer Tool. In order for an ASCII file to beaccessible to RDM, it needs to be placed in the correct RDMconfigured directory, which was defined during installation as follows:

$RDM_HOME/ www/ cds/ r dm/ conf / asci i / OpenWor ks/ def aul t

In the above directory structure, ASCII is the file type, OpenWorks isthe database type, and default is the project name.

When you load data from an OpenWorks project to theASCII.OpenWorks.default project, a file is created for each data typethat is moved. The file names will correspond to the names of theOpenWorks data types and contain the extension .txt . The fields listedwithin these files will be those of the reference data types as they arestored in OpenWorks.

If you want to create a project name other than default , you mustmanually create a subdirectory with the desired project name. Forexample, to create an ASCII project called MY_LISTS, the followingdirectory must be created on the RDM server:

$RDM_HOME/ www/ cds/ r dm/ conf / asci i / OpenWor ks/ MY_LI STS

You do not need to create any files within this directory. This project islisted by RDM as ASCII.OpenWorks.MY_LIST .

The same requirements apply if you are moving data between CDS andASCII files, except CDS replaces OpenWorks . For example, the RDMconfigured directory defined during installation is:

$RDM_HOME/ www/ cds/ r dm/ conf / asci i / CDS/ def aul t

NOTE: Acceptable Characters for ASCII Projects

Only letters (upper and lower case), numbers, and underscore characters can beused to define the file type, database type, and project name. If any of these namescontains any other character, RDM will not recognize the ASCII project.


33/70



Correct ly Def ining OpenWo rks Projects in PowerExplorer

For RDM to work correctly, any OpenWorks project defined in thePowerExplorer dictionary must supply a correct value forTWO_TASK. Without this, RDM may give a null pointer errormessage and terminate after the initial login window.

To ensure TWO_TASK is set properly:

1. Log in to PowerExplorer as the system administrator. Default userid and password is system_admin .

2. In the task tree, select the task System Administrator >Dictionary > Topic > Databases .

3. In the Task Details panel, check the box next to TWO_TASK if itis not already checked.

4. Execute the task by clicking .

5. By default, TWO_TASK is set as OW2003 for the rows where theData Model is OW2003.

To correct this, switch to update mode and set the value ofTWO_TASK to agree with the name of the Oracle SID.

6. Do the same update for the Data Model SGL2000.

7. Click to save the changes.

The connection takes effect the next time PowerHub server isrestarted.


34/70



Creat ing and Co nfigu r ing New CDS Users

CDS usernames are created using the script create_cds_user (seeCreating New CDS Usernames on page 30 ) and then are configuredin PowerExplorer. As part of the CDS installation process, someconfiguration information is loaded in PowerExplorer to assist with this

process. The amount of manual configuration required for a givenusername depends on the user role and the degree of customizingdesired.

The three basic CDS user roles/PowerExplorer model user names are:

cds_full_access : Users have create/delete/read/update permissionsin CDS. They can move data in and out of CDS using RDM orADT.

New usernames created using the create_cds_user script areautomatically assigned to this role. That is, they are created inPowerExplorer with cds_full_access as the associated model user.Since this is the default user role, there is no need to do anyadditional configuration in PowerExplorer.

cds_data_admin : Users have create/delete/read/update permissions in CDS and OpenWorks. They can move data in andout of CDS using RDM or ADT.

For each username that is to be assigned to this user role, you will

need to change the model user from the default cds_full_access tocds_data_admin in PowerExplorer (see Reassigning ModelUser on page 34 ).

cds_read_access : Users have read permissions for CDS. They canmove data out of CDS using RDM or ADT.

Each of these user roles can be configured as described here or can be customized on a limited basis. You also have the option ofcreating customized model users. (see Reassigning Model Useron page 34 ).

Creating New CDS Usernames

For each new username, regardless of user role to which they will later be assigned, you need to set up a new Oracle user, give this Oracle user


35/70



access rights to CDS, and define the user in PowerExplorer. A script is provided in $ PE_HOME/dbadmin_scripts to do all this.

1. Log in as database administrator for the CDS Oracle instance.

Note that you need to use a SYSTEM Oracle user. An internalOracle user such as SYS cannot be used in the creation of a CDS

user.

2. At the command prompt enter:

cd $PE_HOME/ dbadmi n_scr i pt s


sql pl us system/ < password for system >@< SQL*Netalias for ORACLE_SID of target CDS >

Note that the SQL*Net alias must be supplied unless the Oracleserver is running on the same machine as the Oracle client.

4. At the SQL*Plus command prompt, enter:

@cr eat e_cds_user. sql cds_< cdsname > < New Username >

Limitation on CDS Usernames

There is a limitation on having the same usernames for OpenWorks and CDS: TheOS/External OpenWorks user running ADT cannot use the same username as theCDS login for any CDS server he attempts to connect to. For example:

Bill logs on to the ADT machine as BR and launched ADT. BR is an ExternalOpenWorks user.

When Bill connects to a CDS server as BR, he will not be able to access theOpenWorks project under CDS even thought his login is accepted by CDS.The connection to the OpenWorks project under CDS is required forcartographic conversions.

There are two way to resolve the limitation:

Change the CDS user by creating a new CDS user on the CDS machine. Onthe ADT machine, BR stays as an External OpenWorks user with permissionsto the OpenWorks projects under CDS.

On the ADT machine, create a new OS and External OpenWorks user andgive this user permissions to the OpenWorks project under CDS. On the CDSmachine, no changes are necessary; log in to CDS as BR.


36/70



Repeat this step for each new username that you wish to create.Note that the username can be up to 30 characters in length andcan contain a period (.).


qui t

6. Restart the server.

PowerExplorer Configurations

When a new user is created using the script above, the new username isautomatically added as a PowerExplorer user and is assigned to themodel user cds_full_access. No further action is required for anyusername that is to be assigned the cds_full_access user role, other than

restarting the PowerHub server.

The sections below outline additional steps for creating users withcds_data_admin and cds_read_access user roles. You can also use these

procedures to create customized user roles.

Al l actions requi re that you log in to PowerExplorer as the systemadministrator (default login and password are system_admin ).

For a more comprehensive discussion of these topics, please see the PowerExplorer System Administrators Guide , which can be accessedfrom PowerExplorers Online Help.

Creating A Mod el User

When CDS is installed, three model users are automatically added toPowerExplorer: cds_full_access , cds_data_admin andcds_read_access .


37/70



User /Access Group A ssocia t ions

In general, a model user is associated with one or more capabilityaccess groups, which define the rights for that model user and allassociated users.

When CDS is installed, three groups are added to PowerExplorer:cds_all , cds_dic_info , and cds_read_only . To see a list of these groupsand any others that are currently defined in PowerExplorer, execute thetask System Administration > Manage Users > Groups .

Other groups in the list were created during the installation ofPowerExplorer and associated modules.

Capabi l i ty Access Rights

When CDS is installed, the capability access rights for the groupscds_full_access, cds_dic_info, and cds_read_only are created.


38/70



To view these, execute the task System Administration > ManageUsers > Capability access rights .

You can edit the entries in this table to customize the access rights of an pre-defined group, although it is best to limit these changes.

For major changes in access rights, we recommend that you create anew group and and define the capability access rights that meet theneeds for that group.

No action is required for the standard user roles cds_full_access,cds_data_admin, and cds_read_access.

Reass ignin g Mod el User

To assign the user roles cds_data_admin or cds_read_access to a newlycreated username, you will need to change the model user associationfrom cds_full_access to the model user of interest. To do this:

1. Execute the task System Administration > Manage Users >Users .

2. Enter Update Mode .


39/70



3. In each row where you wish to change to the user role, pick theappropriate model user from the pick list.


Create Database Cred entials

Use the following procedure to provide cds_full_access users permissions to use ADT to transfer data to CDS.

1. Log in to PowerExplorer as system_admin.

2. Execute the task System Administration > Manage Security >Database Credentials .

3. Enter Insert Mode .

4. Add a row to the table .

5. Enter the following:

DataModel Name: DICTIONARY Database Name: DICTIONARY DB Userid: < Oracle userid specified for PowerHub Dictionary

during PowerHub installation > DB Password: < password for DB Userid> User ID: cds_full_access Owner ID: cds_full_access Inheritable: TRUE

6. To provide cds_read_only users with permissions to move datafrom CDS to OpenWorks using ADT, add a second line with the


40/70



User ID and Owner ID entered as cds_read_only . All of the othercolumns are the same as in Step 5.


Launch ing RDM

You can launch RDMs graphical user interface (GUI) either from acommand prompt or from OpenWorks.

Command Prompt

To launch the RDM GUI from a command prompt:

1. Log on as an OpenWorks user or OpenWorks administrator.

2. If the OpenWorks home directory ($OWHOME) has been definedand $OWHOME/bin is embedded within the environment variable$PATH, go to the next step. Otherwise, go to $RDM_HOME/bin/

cds .3. Start RDM by typing runRDM_gui .

OpenWorks Method

Before launching RDM from the OpenWorks launcher you must definelaunching instructions in the launcher.dat file in the users homedirectory.

The recommended change is to add the following line after ProjectData Transfer on the Project menu:

" Ref er ence Dat a Manager " " $RDM_HOME/ bi n/ cds/r unRDM_gui 2>$HOME/ r un/ r dm. er r 1>&2 &"

NOTE: Do not launch RDM using Java Web Start

RDM R2003.18.1 should not be launched through Java Web Start orPowerExplorer as it requires an Oracle component that is not currently compatiblewith Java Web Start.


41/70


R2003.18.1 : Data Administration Scripts 37

Data Ad m inis t ra t ion Scr ip ts

If you created any new CDS users associated with the installation, theseneed to be removed before the server is stopped since the script to dropthe CDS users will not run if the PE server is shut down. Drop the CDSusers using the following steps:

1. Log in as database administrator for the CDS Oracle instance.




sql pl us system/ < password for system >@< SQL*Netalias for ORACLE_SID of target CDS >


dr op_cds_user . sql cds_

Repeat this step for each cds username that you wish to delete.

Note that you need to use a SYSTEM Oracle user.

Note that the SQL*Net alias must be supplied unless the Oracleserver is running on the same machine as the Oracle client.


42/70


38 : Data Administration Scripts R2003.18.1


43/70


44/70


40 Uninstalling: Uninstalling and Restoring from backup files for a CDS Upgrade Installation

dr op r ol e di c_< cdsname >_r w;

exi t ;

3. Run the OpenWorks Project Admin utility and delete theOpenWorks project called OW_< CDSNAME >.

I f you do not have a backup of the original PowerH ub dictionaryand OpenWorks OWSYS schema then the un in stall ation pr ocessis complete at th is step.

After deleting the OpenWorks project, make sure you exit OpenWorks.If this is not done, then you will not be able to execute the drop userowsys cascade command in step 4.

4. To reset and remove the CDS extensions applied to the PowerHubdictionary and OpenWorks OWSYS schema, use the followingcommands:

sql pl us < dba_username >/@< ORACLE_SID_of_CDS >

drop user < PE_PH_Dictionary > cas cade;

cr eat e user < PE_PH_Dictionary > i dent i f i ed by def aul t t abl espace pe t empor ar yt abl espace t emp account unl ock;

gr ant connect , r esour ce t o < PE_PH_Dictionary >;

dr op user owsys cascade;

cr eat e user owsys i dent i f i ed by owsys def aul tt abl espace owsys t emporar y t abl espace t emp;

grant connect , r esour ce t o owsys;

Note : When reinstalling without copies of the PowerHub dictionary and OWSYSschema, the CDS installation wizard will generate a number of non-criticaldatabase errors (for example: ORA-00001 unique constraint (XXXX) violated)

that can be ignored.


45/70


R2003.18.1 Restoring: Uninstalling and Restoring from backup files for a CDS Upgrade Installation 41

Please stop here after step 4 if you are uninstalling because of a problem with a new CDS/RDM install.

Continue to step 5 if you are uninstalling because of a problem witha CDS/RDM upgrade.

5. Log on as the Oracle DBA and enter the following commands:

sql pl us /@;

cr eat e user CDS_ i dent i f i ed by CDS def aul t t abl espace CDS t empor ar yt abl espace t emp;

cr eat e ROLE CDS RO;

cr eat e ROLE CDS RW;

gr ant connect , r esour ce t o cds ;

cr eat e user EPI _ i dent i f i ed by EPI def aul t t abl espace CDS t empor ar yt abl espace t emp;

gr ant connect , r esour ce t o EPI ;

cr eat e ROLE DI C__RO;

cr eat e ROLE DI C__RW;

exi t ;

Restoring

1. To restore the OpenWorks OWSYS schema from a backup dumpfile, log on with a user id that can access the Oracle import utility,and enter the following command:

i mp user i d=< dba_username >/@< ORACLE_SID_of_CDS > f i l e=owsys . dmpf r omuser =owsys t ouser =owsys l og=owsys . l og

2. Log into SQL as the owsys user, and run this command:


46/70


42 Restoring: Uninstalling and Restoring from backup files for a CDS Upgrade Installation

sql pl us < owsys_username >/@< ORACLE_SID_of_CDS > del et e f r omow_sys_pr oj wher e pr oj ect _name = OW- ;

3. To restore the PowerHub dictionary, log on with a user id that canaccess the Oracle import utility, and then enter the followingcommand:

i mp user i d=< dba_username >/@< ORACLE_SID_of_CDS >f i l e=< PE_PH_Dictionary >. dmpf r omuser =< PE_PH_Dictionary >t ouser =< PE_PH_Dictionary >l og=. l og

4. To continue using the existing PowerExplorer/PowerHubinstallation without CDS, the existing $PE_HOME must berenamed and the previous $PE_HOME must be restored from a

backup copy of $PE_HOME using these commands:

mv $PE_ HOME ${PE_ HOME}_ bak

mkdi r - p $PE_HOME

cd $PE_ HOME

t ar xvf < backup_path_to_pe.tar>

5. Restore the CDS internal OpenWorks project calledOW_< cdsname > using the OpenWorks Project Admin utility.

6. Use the Oracle import utility command below to restore the CDSschema from a backup dump file:

i mp user i d=< dba_username >/@< Oracle_SID_of_CDS >f i l e=cds_< cdsname >. dmp f r omuser =cds_< cdsname >t ouser =cds_< cdsname > l og=/@< Oracle_SID_of_CDS >f i l e=epi _< cdsname >. dmp f r omuser =epi _< cdsname >t ouser =epi _< cdsname > l og=epi _. l og


47/70


R2003.18.1 Restoring: Uninstalling and Restoring from backup files for a CDS Upgrade Installation 43

8. Recompile broken triggers and and procs, if necessary, on theseusers below, using an Oracle utility:

CDS_ EPI - < PE_PH_Dictionary >

OW- OWSYS

9. Run the repair script in the $PE_HOME.bak/dba_admin/repairdirectory.

10. Restart the PE/PH server: cd $PE_HOME/bin and type:

r unSer ver Manager st ar t _al l

11. Run some smoke tests.

12. Shut down the PE/PH server: cd $PE_HOME/bin and type:

r unSer ver Manager st ar t _al l

13. Reinstall the CDS/RDM upgrade.


48/70


44 Restoring: Uninstalling and Restoring from backup files for a CDS Upgrade Installation


49/70


R2003.18.1 Before Doing the Upgrade: Upgrading to CDS/RDM R2003.18.1 45

Up g rad in g to CDS/RDM R2003.18.1

This section provides instructions for upgrading CDS and RDMR2003.18.0 and their associated programs to CDS and RDMR2003.18.1.

If you need to upgrade from CDS and/or RDM R2003.13.3, you willneed to upgrade to R2003.18.0 prior to running the R2003.18.1upgrader.

The upgrade of CDS and RDM is directed by an upgrade wizard. Thesteps for upgrading on Linux and Solaris are the same.

Before Doing the Upgrade

Prior to upgrading CDS/RDM, please do these important steps:

1. Make sure that the PowerHub and third server processes areshutdown completely using the commands:

cd $PE_HOME/ bi n; r unSer ver Manager - st op_al l

If everything is not shut down completely, use kill -9 to terminateany remaining PowerHub-related processes.

2. Backup and remove all custom Java classes from $PE_HOME/classes.

3. Backup the CDS internal OpenWorks project namedOW_< CDSNAME > using the OpenWorks Project Admin utility.

4. I t i s important that you back up your cur rent PowerH ub

dicti onar y (defaul t name is pe_dic) and the OpenWorks OWSYSschema prior to install ing CDS.

If a fatal error occurs during the CDS installation process, thePowerHub dictionary and the OpenWorks OWSYS schema can berestored to their original state from these backups, greatlysimplifying the process of uninstalling (see Uninstalling CDS inthe previous section) and reinstalling CDS.


50/70


46 Before Doing the Upgrade: Upgrading to CDS/RDM R2003.18.1 R2003.18.1

To back up the PowerHub dictionary, first log on with a user idthat can access the Oracle export utility, and then enter thefollowing command:

exp user i d=< dba_username >/@< Oracle_SID_of_CDS >f i l e=< PE_PH_Dictionary>. dmpl og=< PE_PH_Dictionary> . l ogowner =< PE_PH_Dictionary >

To back up the OpenWorks OWSYS schema, enter the followingcommand:

exp user i d=< dba_username >/@< Oracle_SID_of_CDS > f i l e=owsys . dmpl og=owsys . l og owner =owsys

5. Backup the existing CDS schema using the Oracle export utility byentering the following command:

exp user i d=< dba_username >/@< Oracle_SID_of_CDS >f i l e=cds_< cdsname >. dmp l og=cds_< cdsname >. l ogowner =cds_< cdsname >

6. Backup the existing Epicentre schema using the Oracle exportutility by entering the following command:

exp user i d=< dba_username >/@< Oracle_SID_of_CDS >f i l e=epi _< cdsname >. dmp l og=epi _< cdsname >. l ogowner=epi _< cdsname >

7. Backup the PowerExplorer and PowerHub server runtimeenvironment using the following commands:

cd $PE_HOME

t ar cvf < backup_path_to_pe.tar > .

8. Backup the OpenWorks home directory using the followingcommands:

cd $OWHOME

t ar cvf


51/70


R2003.18.1 Before Doing the Upgrade: Upgrading to CDS/RDM R2003.18.1 47

9. Upgrade OpenWorks R2003.12.1.2 to OpenWorks R2003.12.1.3.This includes extending the internal CDS OpenWorks projects as

per the instructions that accompany the patch.

10. Upgrade PowerExplorer and PowerHub server to R2003.18.1versions.


52/70


48 Using the Upgrade Wizard: Upgrading to CDS/RDM R2003.18.1 R2003.18.1

Using the Upgrade Wizard

This section shows the steps needed to run the installation wizard andexplains each of the screens in the wizard.

Note that a minimum of 2 GB of swap space is required for the update process.

1. Log in as root and set up the CD-ROM drive.

2. Log on as the PowerExplorer owner.

3. Set the display to your local computer.

4. Change to the CDS 2003 directory on the CD-ROM.

5. To start the installation wizard enter:

For Linux: sh cds_linux_upgrade.binFor Solaris: sh cds_solaris_upgrade.bin

You may get the following error message after launching thewizard, which can be ignored:

Er r or r edi r ect i ng st dout . Out put wi l l be pl aced i nt o' out . t xt ' i ns t ead.


53/70


R2003.18.1 Using the Upgrade Wizard: Upgrading to CDS/RDM R2003.18.1 49

6. The installation wizard opens to introductory information. ClickNext to continue.


54/70



7. The first decision is to chose the product features to be upgraded.

There are three options for Install Set :

Typical - Upgrade both CDS and RDM.

Minimal - Upgrade CDS only.

Custom - Upgrade CDS only (same as Minimal).

Highlight either Corporate Data Store or Reference Data Managerin the upper panel to see a description of what is included in eachin the Description panel.

After selecting the product features, click Next to proceed.


55/70



8. The next screen asks for the directory that contains PowerHubserver. If you have previously set this directory as PE_HOME, thisdirectory is listed under PowerExplorer Home.

To modify the location of PowerExplorer Home, click Choose to browse for the directory of choice.

Click Restore Default Folder after making a change to return toyour previously defined PE_HOME directory.



56/70



9. Enter your Oracle username and password. This user must havesystem administrator privileges.



57/70



10. In the next screen, all CDS installations in the target databaseinstance are listed in the upper text box.

Enter the name for of the CDS installation to be upgraded. Do notinclude the prefix cds_ that was added during the originalinstallation process.

Click Next to proceed..


58/70



11. The next screen contains information that needs to be reviewed prior to installation.

To make changes, click Previous to navigate to the appropriatescreen.

When satisfied with the inputs, click Install to begin the upgrade.Once the upgrade process begin s, do not cl ick Cancel.


59/70



12. When the installation is complete, the wizard advances to theUpgr ade Complete screen. If the upgrade was successful, amessage to that effect is displayed on the screen.

If there were errors during installation, an error message appearson the screen. If errors occurred, please contact Landmark support.

Click Done to close the upgrade wizard.


60/70


56 Post Installation Instructions: Upgrading to CDS/RDM R2003.18.1 R2003.18.1

Post Installation Instructions

Start ing the Server

To start the PowerExplorer server, follow the steps below.

1. Enter cd $PE_HOME/ bi n

2. Start the server by entering:

r unSer ver Manager - st ar t _al l

Creat ing and Updat ing Oracle Database Sta t is t ics

To create and update the Oracle database statistics for CDS:

1. Log in to the Oracle 9i database server machine as the Oracle Unixuser. Note that you will need to log into the physical machine asthis step cannot be done remotely.



Alternatively, you may need to ftp the analyze_cds.sql script fromthe directory above to a temporary directory on the Oracle serverin order to read and execute the script.

3. To connect to SQL*Plus, enter on the command line:

sql pl us / nol og

4. Enter the following commands:

SQL> connect / as sysdba;

SQL> @anal yze_cds cds_< cdsname >

where cdsname refers to the name given to the CDS instanceduring installation.

SQL > exi t


61/70


R2003.18.1 Post Installation Instructions: Upgrading to CDS/RDM R2003.18.1 57

Updat ing Op enWorks Pro jects for Data Cleanup Tool

RDM R2003.18.1 requires some changes to OpenWorks projects at theOracle level in order to use the Data Cleanup tool. You will need to runtwo scripts that are located in $PE_HOME/dbadmin_scripts .

Script for OpenWorks Instance

The script create_rdm_fk_table.sh creates a table in the OWSYSschema of Foreign Key information that RDM reads during datacleanup. This must be run for all OpenWorks instances that RDM willconnect to, even if the instance had been updated using this scriptduring a previous installation of RDM.

Use the following procedure for each OpenWorks instance:


2. Set the environmental variable $RDM_HOME.



cr eat e_r dm_f k_t abl e. sh

4. At the prompt, enter an Oracle userid with system DBA privileges.Click Enter .

5. At the prompt, enter the password for the above Oracle userid.Click Enter .

6. At the prompt, enter the OpenWorks database instance name(SID). Click Enter .

The script is then initiated.

When complete, the location of the log file created during the process is provided. For example:

Log f i l e l ocat ed at / t mp/ RDM_opt r on32_f kdat a_508


62/70



Script for OpenWorks Projects

The script process_OWProject_constraints.sh adds a PL/SQL procedure to the project and redefines the Foreign Key constraints sothey can be deferred. It is recommended that you backup yourOpenWorks projects before running this script. This script must be run

for each OpenWorks project.

To run the script:


2. If not already done, set the environmental variable$RDM_HOME.



pr ocess_OWPr oj ect _cont r ai nt s. sh

4. At the prompt, enter an Oracle userid with system DBA privileges.

5. At the prompt, enter the password for the above Oracle userid.

6. At the prompt, enter the OpenWorks database instance name(SID).

7. At the prompt, enter the OpenWorks project name.

The script is then initiated, with information about how the scriptis preparing the project for updates being written to the screen.

After the session is altered, you will see statements similar to thefollowing example:

Connect ed.*** Cr eat i ng RDM_CONSTRAI NT_PKG PL/ SQL * **

** * Gener at i ng t he const r ai nt DROP/ ADD st at ement s ***1029** * Number of const r ai nt s bef ore conver si on i s 1029 ***** * Changi ng t he For ei gn Key const r ai nt s t o DEFERRABLE ***1029** * Number of const r ai nt s af t er conver si on i s 1029 ** **** Al l Done ***Connect ed.Removi ng t he t empor ar y ow_admi ni st r at or r ol e.


63/70


R2003.18.1 Post Installation Instructions: Upgrading to CDS/RDM R2003.18.1 59

Removi ng t he t empor ar y manage r ol e f or t he t ar get OW pr oj ect .

Fi l es are l ocat ed at / t mp/ RDM_si d_pr oj name_const r ai nt s_2812. 0

The final line contains the location of the directory that containsthe log file and the control file used to drop and rebuild the

constraints, generated_constraints_redefine.sql .

Verify that the number of constraints before or after conversion isthe same. If there is a discrepancy, the control file can be used tomanually recover the constraints.

8. To continue with another project from the same OpenWorks SID,enter another OpenWorks project name.

To exit, click Enter . At the prompt, enter y.

Directo ry Setup f or A SCII Files

RDM allows you to move reference data in and out of ASCII filesusing the Reference Data Transfer Tool. In order for an ASCII file to beaccessible to RDM, it needs to be placed in the correct RDMconfigured directory, which was defined during installation as follows:

$RDM_HOME/ www/ cds/ r dm/ conf / asci i / OpenWor ks/ def aul t

In the above directory structure, ASCII is the file type, OpenWorks is

the database type, and default is the project name.

When you load data from an OpenWorks project to theASCII.OpenWorks.default project, a file is created for each data typethat is moved. The file names will correspond to the names of theOpenWorks data types and contain the extension .txt . The fields listedwithin these files will be those of the reference data types as they arestored in OpenWorks.

If you want to create a project name other than default , you mustmanually create a subdirectory with the desired project name. For

example, to create an ASCII project called MY_LISTS, the followingdirectory must be created on the RDM server:

$RDM_HOME/ www/ cds/ r dm/ conf / asci i / OpenWor ks/ MY_LI STS

You do not need to create any files within this directory. This project islisted by RDM as ASCII.OpenWorks.MY_LIST .


64/70



The same requirements apply if you are moving data between CDS andASCII files, except CDS replaces OpenWorks . For example, the RDMconfigured directory defined during installation is:

$RDM_HOME/ www/ cds/ r dm/ conf / asci i / CDS/ def aul t

Launch ing RDM

You can launch RDMs graphical user interface (GUI) either from a

command prompt or from OpenWorks.

Command Prompt

To launch the RDM GUI from a command prompt:

1. Log on as an OpenWorks user or OpenWorks administrator.

2. If the OpenWorks home directory ($OWHOME) has been definedand $OWHOME/bin is embedded within the environment variable$PATH, go to the next step. Otherwise, go to $RDM_HOME/bin/ cds .

3. Start RDM by typing runRDM_gui .

OpenWorks Method

Before launching RDM from the OpenWorks launcher you must definelaunching instructions in the launcher.dat file in the users homedirectory.

NOTE: Acceptable Characters for ASCII Projects

Only letters (upper and lower case), numbers, and underscore characters can beused to define the file type, database type, and project name. If any of these namescontains any other character, RDM will not recognize the ASCII project.

NOTE: Do not launch RDM using Java Web Start

Unlike earlier versions of Reference Data Manager, RDM R2003.18.1 should not be launched through Java Web Start or PowerExplorer as it requires an Oraclecomponent that is not currently compatible with Java Web Start.


65/70


66/70




67/70


R2003.18.1 Introduction: Appendix A : Configuration of Spatializer for Use with CDS 63

A pp end ix A : Conf igu rat ion o f Spat ial izerfor Use w i th CDS

Introduction

The Spatializer is an application that can be used to copy spatial datafrom CDS into an ESRI data repository. Once the data has beenaggregated into shapefiles or SDE layers, any ESRI-based applicationsuch as ArcGIS, ArcExplorer, or ArcIMS can access the data. Theseshapefiles and SDE layers can also be loaded and used within

PowerExplorer.

The Spatializer application is packaged and installed withPowerExplorer. For detailed installation instructions, see the

PowerExplorer Installation Guide . For more detailed informationabout the Spatializer, see the PowerExplorer System AdministrationGuide . Both of these guides can be accessed from the PowerExplorerOnline Help.

This appendix describes how to configure the Spatializer for use withCDS. Shapefiles and SDE layers can be created for the following CDS

data types:

well wellbore path well surface location wellbore wellbore at surface wellbore bottom hole

Prior to configuring the Spatializer for CDS, you must have already

installed PowerExplorer, including the Spatializer application

installed CDS

set the environmental variable PE_HOME

set the environmental variable PATH=$PE_HOME/bin:$PATH


68/70


64 Configuration Steps: Appendix A : Configuration of Spatializer for Use with CDS R2003.18.1

Configuration Steps

Use the following steps to configure the Spatializer for use with CDSdata. Please note that some steps are specific to the creation of

shapefiles and others are specific to the creation of SDE layers.

1. Go to the directory $PE_HOME/spatializer/conf .

2. Open the cds.properties file for editing.

3. Change the line

j ava. ut i l . l oggi ng. Fi l eHandl er . pat t er n=$PE_HOME/spat i al i zer / l ogs / cds . l og

such that the variable $PE_HOME is replaced by the actual path toPE_HOME.

4. Save and exit the cds.properties file.

5. Go the the directory $PE_HOME/spatializer/jobs .

6. Open the cds.xml file for editing.

7. As necessary, edit the following lines

such that the highlighted variables, indicated by @ signs, arereplaced by the actual values. You need to edit those variables within to be able to create SDE layers. To create

shapefiles, replace the variables in .For example


69/70


R2003.18.1 Configuration Steps: Appendix A : Configuration of Spatializer for Use with CDS 65

8. As necessary, edit the following lines

such that the highlighted variables, indicated by @ signs, arereplaced by the actual values. PHS refers to PowerHub server andSrc refers to the source database, which in this case is the CDSdatabase.

If you do not want to create a shapefile, delete the ShapefileName=... line. If you wish to create a SDE layer for this topic, you need to adda LayerName line above TopicName.

In the example transfer job shown below, both a shapefile and a SDElayer will be created.

9. Repeat the preceding step for each of the layers to be generated.

10. Save and exit the cds.xml file.


70/70


11. If you plan to create SDE layers, you need to

change to the directory $PE_HOME/spatializer/sde

open the sde.env file for editing

edit the SDE environment variables

SDEHOME: provide full path SDEINSTANCE: database instance (this is usually 5151) SDESERVER: SDE server name SDEUSER: name of SDE user account SDEPASSWORD: password for SDE user account

save and exit the sde.env file

12. To create SDE layers, you also need to copy the following files tothe directory where SDE is installed:

cds_well.run cds_well_surface_location.run cds_wellbore.run cds_wellbore_at_surface.run cds_wellbore_bottom_hole.run cds_wellborepath_layer.run sde.env

13. Execute the copied files. For example, enter

. / cds_wel l . run

14. To run the Spatializer, change to the directory $PE_HOME/spatializer/bin and enter

. / r unSpzCDS

After the Spatializer finishes, any shapefiles created are written tothe directory specified in cds.xml and SDE layers are written to the