Edition 5.4 PVCS DIMENSIONS UNIX SYSTEMS INSTALLATION GUIDE

Transcription

1 Edition 5.4 PVCS DIMENSIONS UNIX SYSTEMS INSTALLATION GUIDE

2 Copyright 2002 MERANT. All rights reserved. PVCS and MERANT are registered trademarks, and PVCS Change Manager for Oracle, PVCS Dimensions, MERANT Collage, PVCS Content Manager, PVCS Metrics, PVCS Pulse, PVCS Replicator, PVCS TeamLink, PVCS Tracker, PVCS TrackerLink, PVCS Version Manager, PVCS VM I-Net and WishLink are trademarks of MERANT. All other trademarks are the property of their respective owners. ACKNOWLEDGEMENT. PVCS Dimensions is implemented using the ORACLE relational database management system. ORACLE is a registered trademark of Oracle Corporation, Redwood City, California. No part of this publication may be copied, photocopied, reproduced, transmitted, transcribed, or reduced to any electronic medium or machinereadable form without prior written consent of MERANT. Licensee may copy the software product user documentation contained on a CD-ROM, but only to the extent necessary to support the users with authorized access to the software in accordance with the license agreement applicable to the software. Any reproduction of such software product user documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification. U.S. GOVERNMENT RESTRICTED RIGHTS. It is acknowledged that the Software and the Documentation were developed at private expense, that no part is in the public domain, and that the Software and Documentation are Commercial Computer Software provided with RESTRICTED RIGHTS under Federal Acquisition Regulations and agency supplements to them. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in, among other sources, DFARS and , or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at FAR , as applicable. Contractor is MERANT, 3445 NW 211th Terrace, Hillsboro Oregon Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software. MERANT 3445 NW 211th Terrace Hillsboro, Oregon Part Number: MA-DIM72-UINST

3 3 Table of Contents Welcome to Dimensions Typographical Conventions Ordering Hard-Copy Manuals Contacting Technical Support Introduction Dimensions Component Binaries Dimensions Server Binaries Dimensions I-Net Binaries Dimensions WebDAV Binaries Host Requirements Hardware Software Installation Overview Introduction Summary of Installation Activities Default Installation Node Functionality Networking Installation Notes Optimizing Dimensions Performance Disk Utilization NFS Networked Disks Item Libraries

4 4 Table of Contents Memory and Swapping Character Set and Locale Very Large Files Pre-Installation Activities Preliminary Activities Summary Creating Operating System User Accounts 'oracle', 'pcms' and 'user2' to 'user6' Operating System Requirements Operating System Patches System Parameter uname Configuring System Kernel for Shared Memory and Semaphores Changes to the Default init<sid>.ora File Other Operating System Constraints, Updates, Etc Host ID for Dimensions Licensing Pre-Installation Requirements (Oracle Server Runtime and Dimensions Server) All Installations Existing Users of Dimensions Dimensions Server Installed Separately from the Oracle Server Runtime Mounting the Dimensions CD-ROM Sun Sparc Red Hat And SuSE Linux Starting the Installation Logging the Installation CD-1 Platform Files Default Non-Interactive New Installation Standard Interactive Installation

5 Table of Contents 5 4 Oracle Installation Installation Overview Oracle Server Runtime Installation Overview Dimensions Server Runtime Installation Overview Pre-Installation Checks Initiating the Oracle Runtime Installation New Installation of Oracle with Database Creation Error Conditions New Client Oracle Installation without Database Creation.. 65 Error Conditions Dimensions Installation Installation Overview Pre-Installation Checks Initiating the Installation A New or Upgrade Server Installation A Client Installation Dimensions Post-Installation Activities Setting Up Access to Dimensions Licensing Dimensions Products Licensing Dimensions Products with FLEXlm Dimensions Command Files Access to Dimensions Files Dimensions Runtime Parameters Dimensions Make Installed on a "Multi-Homed" Server Platform

6 6 Table of Contents Re-Boot of Oracle/Dimensions Standalone Process Model Installer Getting Started with Dimensions Introduction Accessing the Payroll Demonstration Product Dimensions Network Tests Dimensions I-Net and WebDAV Server Installation Introduction Dimensions I-Net Components WebDAV Server Components Before You Install System Requirements Server Prerequisites Upgrading from Dimensions Installing Dimensions I-Net and WebDAV Server Starting and Stopping Dimensions I-Net and WebDAV Server Configuring Apache Web Server Installing a Web Server Adapter Updating the Apache httpd.conf File Configuring iplanet and SunOne Web Servers Installing the Dimensions I-Net Client Uninstalling Dimensions I-Net and WebDAV Server

7 Table of Contents 7 A Guidelines for Estimating the RDBMS Database Size Factors which affect the Size of the RDBMS Database B Floating License Management Multiple Vendors Using FLEXlm Options File License Administration Tools lmhostid lmcheck lmstat lmdown lmremove lmreread lmcksum lmdiag lminstall C UNIX Environment for a Different Character Set and Locale Selecting a Suitable Environment D Dimensions Symbols Introduction User Database Assignment PCMSDB Sending Mail to Dimensions Users PCMS_MAIL PCMS_MAIL_SCRIPT Editing Items Default Editors

8 8 Table of Contents PCMS_EDT PCMS_EDT_SCRIPT Miscellaneous Shell Script File for Editing Items Editing Change Documents Default Editors PCMS_CHD_EDT PCMS_CHD_EDT_SCRIPT Shell Script File for Editing Change Documents Browsing Items and Change Documents Default Browsers PCMS_BROWSE PCMS_BROWSE_SCRIPT Shell Script for Browsing Items PCMS_CHD_BROWSE PCMS_CHD_BROWSE_SCRIPT Shell Script for Browsing Change Documents Paging Data Printing Data PCMS_PRINT PCMS_CHD_PRINT PCMS_CHD_PRINT_SCRIPT Shell Script for Printing Change Documents Deleting Unwanted Files Showing Item Differences Merging Item Revisions Replication PCMS_REMOTE_FILE_AREA Code Page Settings PCMS_CODEPAGE PCMS_EBCDIC_CODEPAGES

9 Table of Contents 9 PCMS_DEFAULT_CODEPAGE Command Security PCMS_FILE_ENCRYPTION Secure Users Running User Defined Reports Including SQL*Plus Statements Index

10 10 Table of Contents

11 11 Welcome to Dimensions Thank you for choosing MERANT PVCS Dimensions, a powerful process management and change control system that will revolutionize the way you develop software. Dimensions helps you organize, manage, and protect your software development projects on every level from storing and tracking changes to individual files, to managing and monitoring an entire development cycle. Purpose of this manual This guide documents the: pre-installation activities, installation procedure, and post-installation activities (including licensing) required for the Dimensions Server sub-components, and the bundled Oracle Server run-time with respect to Dimensionssupported UNIX platforms. Additionally, it describes how to access the payroll demonstration product that enables you to quickly get started using Dimensions. For more information Edition status There are also companion guides that describe: how to install the Dimensions Server and Oracle Server on Windows NT/2000 platforms; and how to install Dimensions Windows Client Components on Windows 98/NT/2000 platforms. Refer to the PVCS Dimensions Getting Started Guide for a description of the Dimensions documentation set, a summary of the ways to work with Dimensions, and instructions for accessing the Online Help. This is Edition 5.4 of the. The information in this edition applies to PVCS Dimensions Release 7.2. This edition supersedes earlier editions of this manual.

12 12 Welcome to Dimensions Typographical Conventions The following typographical conventions are used in the online manuals and online help. These typographical conventions are used to assist you when using the documentation; they are not meant to contradict or change any standard use of typographical conventions in the various product components or the host operating system. Convention italics bold UPPERCASE monospace monospaced italics monospace bold vertical rule brackets [] Explanation Introduces new terms that you may not be familiar with and occasionally indicates emphasis. Emphasizes important information and field names. Indicates keys or key combinations that you can use. For example, press the ENTER key. Indicates syntax examples, values that you specify, or results that you receive. Indicates names that are placeholders for values you specify; for example, filename. Indicates the results of an executed command. Separates menus and their associated commands. For example, select File Copy means to select Copy from the File menu. Also, indicates mutually exclusive choices in a command syntax line. Indicates optional items. For example, in the following statement: SELECT [DISTINCT], DISTINCT is an optional keyword.... Indicates command arguments that can have more than one value.

13 Ordering Hard-Copy Manuals 13 Ordering Hard-Copy Manuals As part of your Dimensions license agreement, you may print and distribute as many copies of the PVCS Dimensions manuals as needed. If you do not want to print each of these online manuals, you can order hard-copy versions from MERANT. To order, please contact your sales representative for assistance. Contacting Technical Support MERANT provides technical support for all registered users of this product, including limited installation support for the first 30 days. If you need support after that time, contact us using one of the methods below or purchase further support by enrolling in the SupportNet program. For more information about SupportNet, contact your sales representative. Technical support is available 24 hours a day, 7 days a week, with language-specific support available during local business hours. For all other hours, technical support is provided in English.

14 14 Welcome to Dimensions WWW SupportNet Customers can report problems and ask questions on the SupportNet web page: To submit an issue, click on the Report a Problem link and follow the instructions. The SupportNet Web site contains up-to-date technical support information, which you can access from the SupportNet web page. Our SupportNet Community shares information via the Web, automatic notification, newsgroups, and regional user groups. SupportNet Online is our global service network that provides access to valuable tools and information for an online community for users. SupportNet Online also includes a KnowledgeBase, which contains how-to information and allows you to search on keywords for technical bulletins. You can also download fix releases for your PVCS products. [email protected] Telephone Asia Pacific Australia Österreich België (Nederlands gesproken) Belgique (Langue Française) France Deutchland Hong Kong Italia Japan or (within Japan only) Nederland

15 Contacting Technical Support 15 All countries, for support in the following languages between and CET (Central European Time) New Zealand Singapore South Africa South Korea (Korean) España Suisse (Langue Française) Schweiz (Deutschsprachig) United Kingdom and Ireland USA, Canada, and Mexico Nederlands gesproken English Speaking Langue Française Deutschsprachig Idioma Italiano Habla Español Fax Asia Pacific, Australia, and New Zealand Europe, Middle East, and South or Africa Japan

16 16 Welcome to Dimensions Mail U.S NW 211th Terrace, Hillsboro, OR USA When you contact us, include the following information: The product serial number located on the Product Registration Information card in the box. The number will be checked to verify your eligibility to receive support. If you do not have a current SupportNet contract, we will ask that you speak with a sales representative. Your name and organization. On a first-time call, you may be asked for full customer information including location and contact details. The version and build number of the PVCS product you are using. The type and version of the operating system you are using. Any third-party software and other environmental information necessary to understand the problem. A brief description of the problem and the steps necessary to re-create it. Specific error messages are needed. Depending on the complexity of the problem, you may be asked to submit a re-creatable example demonstrating the problem. An assessment of the severity level of the reported problem.

17 17 1 Introduction In this Chapter For this section See page Dimensions Component Binaries 18 Host Requirements 20

18 18 Chapter 1 Introduction Dimensions Component Binaries Dimensions Server Binaries The Dimensions Server binaries for a particular UNIX platform are supplied on a single CD-ROM called CD-1. The UNIX subcomponents on CD-1 comprise: Oracle Server runtime PVCS Replicator [licensed option] Dimensions Change Dimensions Version Dimensions Network Dimensions ART Dimensions Motif Client Dimensions Process Modeler RDBMS foundation software Provides item and baseline replication and management across remote Dimensions databases via a command-line and/or GUI-forms administration interface. Enables all Dimensions change management tracking facilities. Enables Dimensions version management and IP build component. Enables Dimensions Network libraries, Dimensions PC Client and PVCS Replicator connectivity. Enables Dimensions with Archive and Retrieval (ART) facilities. Provides Motif GUI for Dimensions Version and Dimensions Change. Provides a GUI-forms interface to process model operations.

19 Dimensions Component Binaries 19 Dimensions Make Dimensions Network Administration Tool Provides GNU Make capabilities with Dimensions. Provides a GUI-forms interface to networking operations. Reference should be made to PVCS Dimensions Network User s Guide concerning post-installation tasks necessitating the use of the Dimensions Network Administration Tool when Dimensions is run in a network-aware manner in a client-server homogenous or heterogeneous network. Dimensions I-Net Binaries Dimensions I-Net is treated as a separate component. Its binaries are held on a separate CD-ROM called CD-4. It can be installed only after CD-1 has been installed. Please refer to Chapter 8, Dimensions I-Net and WebDAV Server Installation for specific instructions. Dimensions WebDAV Binaries Dimensions WebDAV is treated as a separate component. Its binaries are held on a separate CD-ROM called CD-4. It can be installed only after CD-1 has been installed. Please refer to Chapter 8, Dimensions I-Net and WebDAV Server Installation for specific instructions.

20 20 Chapter 1 Introduction Host Requirements Hardware CPU and RAM Database Server Installation Network Client Installation Minimum 256Mb RAM (this will normally support two to three simultaneous users) 90Mb RAM Recommended For each additional: Command-Line user: add 4Mb; Motif Client user: add 8Mb. Network Client: add 2Mb. 180Mb Disk Space The disk space requirements are detailed in the following table and can be met by using more than one disk. However, major groups of files (e.g. Oracle or Dimensions binaries), an individual Oracle Database file and a Dimensions item library, cannot span more than one disk. Particular Dimensions UNIX and Linux platforms will have different sized Dimensions and Oracle binaries. The values quoted in the following table are for rough guidance only, and you should refer to the README file for the actual platformspecific values.

21 Host Requirements 21 Additional disk space will be required for Dimensions operatingsystem libraries to house items according to size and method of storage (i.e. whether or not delta libraries are being used for items). NOTE In a NFS network, the disks for the database and log files must be local to the host running the Oracle server. Dimensions binaries: 120Mb Oracle runtime binaries 420Mb Database (minimum) (a) PCMS_DATA tablespace SYSTEM tablespace PCMS_RBS tablespace for rollback segments (b) PCMS_TEMP tablespace (c) Two redo logfiles: Database (installation defaults) (a) PCMS_DATA tablespace SYSTEM tablespace PCMS_RBS tablespace for rollback segments (b) PCMS_TEMP tablespace (c) Two redo logfiles Optional temporary installation workspace required for copying tar file to disk 100Mb 80Mb 20Mb 10Mb 2 x 4Mb (total) 500Mb 150Mb 50Mb 50Mb 2 x 4Mb (total) 218Mb 758Mb 600Mb

22 22 Chapter 1 Introduction a. For calculating the database size for larger installations, see Appendix A, Guidelines for Estimating the RDBMS Database Size. b. The installation process automatically assigns PCMS_RDBS to be the greater of either 10% of the size that you specify for PCMS_DATA during installation or 20Mb. c. The installation process automatically assigns PCMS_TEMP to be the greater of either 10% of the size that you specify for PCMS_DATA during installation or 10Mb. Software Operating System For the specific UNIX and Linux operating system types and associated versions supported by Dimensions 7.2 please refer to the README. Oracle Software For the Oracle Server versions supported by Dimensions 7.2 on specific UNIX and Linux operating system types please refer to the README. IMPORTANT! Dimensions 7.2 is only certified and supported by MERANT with the Oracle software distributed on Dimensions 7.2 installation CDs. Customers with their own Oracle software are strongly advised not to try and configure the Dimensions binaries to use that software, as such configurations have not been certified by MERANT. If, however, you have an existing Dimensions 6.0, 7.0 or 7.1 installation that was successfully configured to use a database created from your own installation of Oracle (i.e. you did not install Oracle from Dimensions CD-1) then you will still be able to

23 Host Requirements 23 upgrade to Dimensions 7.2 and retain your Oracle installation. See the related manual Upgrading from Dimensions 6 to 7 and the README for details. Network Software TCP/IP is required if Dimensions is to use a database residing on a remote node or to access remote Dimensions libraries. UNIX System Shared Memory Parameters A shared memory facility must be incorporated; for certain UNIX and Linux, the System V enhancements are required. Requirements for UNIX and Linux System parameters are noted in the README file. UNIX System Swap Space Requirements Swap space requirements for Dimensions and Motif Client depend on the number of parts, items and change documents accessed by the user. As this will vary greatly from one site to another, the following information is provided only as a guide. For a product with 80 parts, 400 items and 1300 change documents, the recommended minimum additional swap space per user is: Dimensions 7Mb Motif Client 14Mb In all circumstances, a minimum total swap space of at least twice the size of the node's RAM is highly recommended.

24 24 Chapter 1 Introduction SQL*Net Version Dimensions supports NET8 only. FLEXlm Version The exact versions of FLEXlm supported on Dimensions for a particular UNIX or Linux platform are detailed in the README file. Motif Version Motif Client requires Motif Version 1.2. Dimensions Delta Libraries As of Dimensions Release 5.0, all newly created delta libraries for item storage utilize the PVCS VM Developer Toolkit Delta mechanism. This software is automatically installed as part of the Dimensions installation and does not require any separate user installation. For backward compatibility, existing delta items in delta libraries utilizing the UNIX Source Code Control System (SCCS) utility can continue to be used for item storage this, of course, will require SCCS to be available on your UNIX platform.

25 25 2 Installation Overview In this Chapter For this section See page Introduction 26 Summary of Installation 26 Activities Default Installation 28 Node Functionality 28 Networking 29 Installation Notes 29

26 26 Chapter 2 Installation Overview Introduction The installation of the Dimensions products involves loading two major software packages on to the system: the Oracle Version 8 runtime and Dimensions itself. The sub-components Dimensions Change, Dimensions Version, Dimensions Network, Dimensions ART, Dimensions Process Modeler, Dimensions Make, Dimensions Motif Client and PVCS Replicator are all part of the Dimensions installation. Further sub-components Dimensions I-Net and Dimensions WebDAV are optional. This document details the first time installation of Oracle 8i and Dimensions 7.2 binaries, which are the only options supported by the installation script for Dimensions 7.2. For details of upgrading Dimensions and Oracle binaries from Dimensions Release 6.0, Release 7.0, or Release 7.1 to Release 7.2, please refer to the related document Upgrading from Dimensions 6 to 7. Summary of Installation Activities The installation procedure comprises a number of activities that have to be completed in the following order: 1 Pre-installation Activities. (Mandatory, see Chapter 3). 2 Oracle Server Installation. (Mandatory see Chapter 4). 3 Dimensions Installation. (Mandatory, see Chapter 5), including Motif Client.

27 Summary of Installation Activities 27 4 Post-installation Activities, including instructions for re-booting (if necessary) and licensing. (Mandatory, see Chapter 6). 5 Dimensions I-Net and/or Dimensions WebDAV (Optional see Chapter 8) It is possible to install the Oracle Server runtime on its own and then install the Dimensions Server in a later session. Normally, however, it is recommended that both are installed during one session as the Oracle environment will then be guaranteed to be in the required state for the Dimensions Server installation. Individual Dimensions 7.2 Client Components provided on CD-2 are Intel Windows clients that can be installed only on Windows platforms. Such installed clients can then partake in a client-server relationship with respect to the UNIX Oracle Server and Dimensions Server whose installation is described in this guide. For information on how to install such clients, please refer to the PVCS Dimensions Installation Guide for Windows Clients. Notes a For new installations of Oracle and Dimensions there is a default option that simply requests confirmation of the details of the default installation parameters. b The installation of Dimensions offers the option of creating a base database within the RDBMS database. This option must not be selected if either one of the following applies: The RDBMS database to be used by Dimensions resides on a remote node accessible by TCP/IP. The RDBMS database to be used by Dimensions already contains a base database created by a previous Dimensions release.

28 28 Chapter 2 Installation Overview c For the sake of clarity, throughout this installation guide it is assumed that the Oracle and Dimensions software will be installed in the operating-system directories /usr/oracle and /usr/pvcs respectively. You should substitute the appropriate operating-system directory identities according to your local environment. Default Installation Replies from the installer to installation questions are saved in a text file called pcms_reply.txt. By saving this file after an installation it may be used to provide the default answers for subsequent installations. Node Functionality There are three types of node: A server node that hosts the Dimensions database, has access to all the Dimensions functionality and can host item libraries. A DFS node that has access to all the Dimensions functionality and can host item libraries. A NET node that has the same functionality as a DFS node but cannot host item libraries.

29 Networking 29 Networking Installed as part of the Dimensions Server, the Network Administration Motif GUI-tool provides for setting up Dimensions Network data. It is invoked from: The Network Administration Tool option of Motif Client s Utilities pulldown menu. net_admin typed at the UNIX operating-system command line (provided, of course, that the Dimensions UNIX environment has been set up). The library access process dimensions_listener is started automatically whenever Dimensions Network is started. Dimensions Network must be stopped and restarted (as described in the PVCS Dimensions Network User s Guide) whenever changes to the network configuration affect the current machine. For further network restrictions (if any), please refer to the toplevel README file. Installation Notes Optimizing Dimensions Performance A Dimensions network can consist of DFS and NET nodes and it is desirable to configure the network to take advantage of the computing resources available. In addition to providing networking facilities to permit operations across both a homogenous and heterogeneous environment, Dimensions Network is able to spread the processing load in both a DFS and

30 30 Chapter 2 Installation Overview a NET configuration. The information relating to such issues are detailed in the PVCS Dimensions Network User s Guide and the top-level README file. NOTE The Oracle processes should execute on the fastest node in the network and if possible have no Dimensions logins on it. Also, the operating system parameters should be optimized with as much RAM as possible for each Dimensions Network node in the network. If a single user workstation is used on the network appropriate resources may need to be significantly increased to reduce paging/swapping. Disk Utilization In addition to processing power and memory, disk access is an essential performance factor from a Dimensions viewpoint. Often the performance of a Dimensions node can be significantly degraded if all the various files and system are resident on a single disk. The recommendation is to have at least five separate disks to best optimize disk access, although system configurations with fewer disks are also considered in this text. The key elements that need to be on separate disks are as follows: Disk1 Disk2 Disk3 Disk4 Disk5 UNIX System disk Page and swap files User files Database file(s) only (Oracle) Redo log files (Oracle) The other elements that need to be placed on these disks are listed below. They should be spread across the disks but this spread may be restricted to Disks 4 and 5 if local requirements or disk space restrictions make this necessary. The database files are associated with separate tablespaces SYSTEM, PCMS_TEMP, PCMS_RBS and PCMS_DATA. Improved performance may be

31 Installation Notes 31 achieved by separating the tablespaces to separate disks. The aim is to have a disk load that is balanced across all available disks. The table below shows examples of the use of disks in a number of configurations (1-5 disks). One Disk Two Disks Three Disks Four Disks Five Disks System Disk D1 D1 D1 D1 D1 Page and Swap D1 D1 D3 D3 D3 files User files D1 D2 D2 D2 D2 Database files D1 D2 D2 D2 D5 only Redo log files D1 D1 D3 D4 D4 Dimensions Programs D1 D1 Any Item Libraries D1 D2 Not D1 Database D1 D1 Any programs Anywhere but not the System Disk NFS Networked Disks If the installation is to be on a NFS network of nodes and it is not intended to use Dimensions Network, it is necessary that the NFS disks to be used for Dimensions are UNIX mounted with root setuid access permitted.

32 32 Chapter 2 Installation Overview Item Libraries Network Considerations In the case of item libraries it is important from an overall network perspective to ensure that they are defined on DFS nodes that can handle the load and are local to the users that most often require access to them. Impact of Changing an Item s Format Definition When an item file is put into a Dimensions item library, the item s format definition is queried to determine if the file is a text file or not. If the format definition says the file is TEXT then the file will be stored in the library converted to UNIX-style text format i.e. lines end with [LF] (Linefeed = ^J ) only, not [CR] + [LF] (Carriage-Return + Linefeed = ^M^J ). If the format definitions are changed later, then this could affect the data that is got (fetched) from the item library. These definitions can be changed using the Process Modeler Formats and MIME Types function refer to the related document PVCS Dimensions Process Modeling User s Guide. Memory and Swapping Memory and swapping are key factors that Dimensions performance is dependent upon. Memory requirements for Dimensions are detailed on page 20 and page 23. The Oracle binaries and the database parameters are tuned to the expected number of concurrent users by the Oracle Runtime installation script. Also, refer to Configuring System Kernel for Shared Memory and Semaphores on page 41 for instructions on setting up shared memory requirements prior to installation.

33 Installation Notes 33 Character Set and Locale By default the character set used by Oracle and Dimensions is US7ASCII and the locale is C. However some platforms support alternative character set and locales. Please refer to Appendix C, UNIX Environment for a Different Character Set and Locale and the top-level README file for specific information. Very Large Files Dimensions and Oracle have only been certified using files up to the 2Gbyte size limit. Although some UNIX operating systems allow the creation of files greater than this limit, this option must not be used for creating database files that are used by Dimensions.

34 34 Chapter 2 Installation Overview

35 35 3 Pre-Installation Activities In this Chapter For this section See page Preliminary Activities 36 Summary 36 Creating Operating System User 37 Accounts 'oracle', 'pcms' and 'user2' to 'user6' Operating System Requirements 40 Pre-Installation Requirements 44 (Oracle Server Runtime and Dimensions Server) Mounting the Dimensions CD-ROM 46 Starting the Installation 48

36 36 Chapter 3 Pre-Installation Activities Preliminary Activities During installation of Dimensions you will be prompted to select a particular process model from: Entry Level which deploys a sample Dimensions project called "The Learning Project", suitable for users with PVCS Professional experience who wish to introduce process into their company work practices. Intermediate which deploys a sample Dimensions project called "Payroll", suitable for users with established, stable process covering the software development lifecycle Other applicable to users who wish to use the standard generic process model or to advanced users who have their own generic process model. For further information please read the PVCS Dimensions - Deployment Guide before you start any installation actions. Summary Caution Before you attempt to install either Oracle or Dimensions on your UNIX machine, you must first ensure that the following pre-installation activities have been undertaken (failure to perform these actions may result in installation failure): The appropriate operating-system user accounts and groups have been created (see Creating Operating System

37 Creating Operating System User Accounts 'oracle', 'pcms' and 'user2' to 'user6' 37 User Accounts 'oracle', 'pcms' and 'user2' to 'user6' on page 37). The operating-system pre-installation requirements have been verified. This potentially involves changing the UNIX kernel (see Operating System Requirements on page 40). Once the above activities have been completed you can initiate the installation process as detailed on page 46. Creating Operating System User Accounts 'oracle', 'pcms' and 'user2' to 'user6' During installation you will be prompted for operating system user account names for: In all cases: The operating-system user account names for Oracle and Dimensions. NOTE Throughout the remainder of this manual, the operating-system user account names for use with Oracle and Dimensions are considered to be oracle and pcms respectively. It is emphasized here, however, that these names are used for example purposes only there is no reason why you cannot use other account names if you so wish, but we do recommend these names be used if possible. If, and only if, the (default) Intermediate Process Model is selected during Dimensions installation: The operatingsystem user account names for various defined users in the associated Payroll demonstration product, see Selecting Option 2 on page 78.

38 38 Chapter 3 Pre-Installation Activities NOTE Throughout the remainder of this manual, the operating-system user account names for use with the Payroll users are considered to be pcms user2, user3, user4, usr5 and user6. The level of detail given here is primarily to assist you in installing Dimensions, even if you have relatively little knowledge of the principles of the UNIX operating system. It assumes that the hostcomputer has been loaded and booted with a supported version of UNIX with its standard options. In any other circumstances, e.g. if system management tools such as Network Information Service (NIS) are enabled, then the following details may require some modification. If this is the case, guidance should be sought from the UNIX System Administrator. It is recommended that there should be two special accounts named oracle and pcms for Oracle and Dimensions respectively. It is also recommended that each of these should be in a group by itself with no other accounts in the same group. These two accounts will be set up as the owners of the Oracle and Dimensions files. Apart from this, they should only be used to carry out Oracle and Dimensions administration functions as described in the Database Administrator s Guide. To ensure the security of your system in that only oracle and pcms are assigned the necessary privileges for Oracle DBA operations, create a group called dba and assign the users oracle and pcms to this group. Alternatively, you can create different groups for these users and make them members of the dba group. This must be done prior to installation. The following gives an example of how the accounts oracle, pcms and the user accounts utilized in the Dimensions Payroll demonstration product may be set up with the above considerations in mind. The example assumes that these accounts are to be created by editing the UNIX user password file and group file directly. This may not be the case on some UNIX systems that provide an interactive utility for administrating

39 Creating Operating System User Accounts 'oracle', 'pcms' and 'user2' to 'user6' 39 users. Please check with your System Administrator before attempting to create the accounts. Example Login as root. Create users oracle, pcms plus any generalpurpose users required by editing the files /etc/passwd and /etc/group. Insert lines in each containing user and group definitions. For example, in /etc/passwd: oracle::201:102:oracle:/usr/oracle:/bin/csh pcms::202:102:dimens Tool Mgr:/usr/pvcs:/bin/csh user2::203:130:payroll Developer 1:/usr/user2:/bin/csh user3::204:130:payroll QA Engineer 1:/usr/user3:/bin/csh user4::205:130:payroll Team Leader:/usr/user4:/bin/csh user5::206:130:payroll Developer 2:/usr/user5:/bin/csh user6::207:130:payroll QA Engineer 2:/usr/user6:/bin/csh and in /etc/group: dba::102:oracle,pcms users::130:user2,user3,user4,user5,user6 In this example 102 and 130 are group numbers, while 201, 202, 203, 204, 205, 206, and 207 are user numbers. If the Bourne Shell (rather than the C Shell) is to be used, then substitute sh for csh. Make base directories and set up their ownership and group ids for each user created above, for example: % cd /usr % mkdir oracle pcms user2 user3 user4 user5 user6 % chown oracle oracle % chown pcms pcms % chown user2 user2 % chown user3 user3 % chown user4 user4 % chown user5 user5 % chown user6 user6 % chgrp dba oracle pcms % chgrp users user2 user3 user4 user5 user6

40 40 Chapter 3 Pre-Installation Activities If required, create an additional directory to hold the Oracle database files (see Chapter 4, Oracle Installation for details as to how this will be used). Operating System Requirements CAUTION! If you will be creating an RDBMS database as part of the Oracle installation on the host machine, then certain UNIX system parameters may need to be modified and certain operating system patches may need to be applied for your particular hardware platform. Failure to meet these requirements might cause the installation script to fail when attempting to create an RDBMS database. The following subsections describe general operating system requirements and definitions of various terms used with respect to operating system requirements, for example shared memory and semaphore definitions. Full details of the operating system requirements for the major UNIX and Linux platforms upon which Dimensions 7.2 is supported are given in the Dimensions top-level README file. Operating System Patches On the Dimensions 7.2 UNIX platforms, the Dimensions Oracle Server has only been certified for use if the operating system patches identified in the top-level README file have been applied. If these operating systems are not at the identified patch level, the Oracle/Dimensions installation may fail consult your UNIX System Administrator if you need further assistance.

41 Operating System Requirements 41 NOTE Platform manufacturers routinely update and renumber their patches. Your platform manufacturer s Customer Service Representative has the latest patch information. System Parameter uname Ensure that the search path for user root includes the location of the program uname. Configuring System Kernel for Shared Memory and Semaphores Oracle requires the system kernel to be configured for shared memory and semaphores. The RDBMS database will require one semaphore per Oracle user process (or Dimensions user), plus one. The maximum number of user processes is governed by the Oracle init.ora parameter "processes" which by default will be set by the Dimensions installation script to 100. It may thus be necessary to adjust the values of the following system parameters to meet this requirement: Parameter SHMMAX SHMMIN SHMMNI SHMSEG SEMMNI Description The maximum size in bytes of a single shared memory segment. The minimum size in bytes of a single shared memory segment. The number of shared memory identifiers. The maximum number of shared memory segments that can be attached by a process. The number of semaphore set identifiers in the system. SEMMNI determines the number of semaphore sets that can be created at any one time.

42 42 Chapter 3 Pre-Installation Activities Parameter SEMMNS SEMMSL Description The number of Semaphores system-wide. The maximum number of semaphores that can be in one semaphore set. Should be the same size as the maximum number of Oracle processes. The default settings for the above are usually sufficient, except where detailed in the top-level README file for particular UNIX platforms. CAUTION! Setting the above parameters to too high a value may prevent the machine from booting up. Refer to your operating system administration documentation for further information about these parameters. Changes to the Default init<sid>.ora File The system kernel configuration values listed in the top-level README file assume that you are using the default values from the init<sid>.ora file provided with Dimensions. If you change or re-configure these values, then you may need to rebuild the UNIX kernel to reflect these changes. The following table is provided to help you with this process: Kernel Parameter SHMMAX Formula to Calculate Value 0.5 * (physical memory present in machine)

43 Operating System Requirements 43 Kernel Parameter SEMMSL SEMMNS Formula to Calculate Value 10 + GREATEST ('PROCESSES' parameter of all the init<sid>.ora files in your Oracle installation) (SUM('PROCESSES' parameter of each init<sid>.ora file in your Oracle installation EXCEPT the greatest of those 'PROCESSES' values) + (GREATEST('PROCESSES' parameter of all the init<sid>.ora files in your Oracle installation)*2) + ((number of Oracle instances you have installed)*10)) Other Operating System Constraints, Updates, Etc. In addition to the following, also refer to the top-level README file. Reinstalling Dimensions 7.2 If you re-install Dimensions 7.2 on a Sun Solaris or a Linux machine you must first ensure that the files under the directory /var/opt/dimensions72/ have been deleted. Failure to do this may cause your installation to terminate with an error condition. Host ID for Dimensions Licensing To enable the PVCS Support Center to generate a license file for your particular Dimensions configuration, you need to fill in and return a License Key Request Form (see Licensing Dimensions

44 44 Chapter 3 Pre-Installation Activities Products on page 89). One particular detail required is the hostid of the node that is to be used as the license server node. Once FLEXlm (the default licensing mechanism) is installed as part of the Dimensions installation, the host-id is simply identified by running the utility lmhostid (see Appendix B, Floating License Management ) however this, of course, cannot be used prior to FLEXlm installation! The Ethernet alpha-numeric host-id address (typically eight or twelve hexadecimal characters) can be identified prior to Dimensions installation by the operating-system command: Solaris Linux /usr/bin/hostid /sbin/ifconfig eth0 grep HWaddr cut -d " " -f11 tr -d [:] Pre-Installation Requirements (Oracle Server Runtime and Dimensions Server) In addition to setting up the pcms and oracle operating-system user accounts as described on page 37, the following preinstallation procedures must be met and/or considered. All Installations Ensure that sufficient disk space is available for the installation of the Oracle Server runtime and Dimensions Server, now and in the foreseeable future. Ensure that you have available your FLEXlm license details for the server node provided by the PVCS Support Center as you will need to enter these as a post-installation activity.

45 Pre-Installation Requirements (Oracle Server Runtime and Dimensions Server) 45 Existing Users of Dimensions If you are an existing user of Dimensions and have a compatible export of your own generic process model, then this can be used at the time of the fresh installation. This will import your process model into the base database PCMS rather than the standard generic process model. If you wish to import your own process model, then please ensure that it is exported and available at the time of installation. Dimensions Server Installed Separately from the Oracle Server Runtime If within the same installation session, you elect to have the Dimensions Server installed straight after a successful Oracle Server runtime installation then the Oracle Version 8 runtime that is a pre-requisite for the Dimensions Server installation will already be installed and active. No further checks will be required (also information gathered during the Oracle Server runtime installation will automatically be carried forward into the Dimensions Server installation). However, if for any reason the Dimensions Server is installed in a session of its own (e.g. an Oracle Server of the exact same version as the Oracle Server runtime already exists or the machine has been re-booted following installation of the Oracle Server runtime), then you must perform the following additional pre-installation activities: Have available the operating-system directory name for the directory in which the Oracle software resides and the Oracle SID these will be prompted for during the Dimensions Server installation. If the Oracle Server runtime has been installed, then this information should have been recorded (if you have followed the recommendation given in the description of the installation in Chapter 4, Oracle

46 46 Chapter 3 Pre-Installation Activities Installation ); additionally, the previous answers to the Oracle Server runtime installation questions stored in the pcms_reply.txt file will, where appropriate, become the default answers for use in the Dimensions Server installation Check that the UNIX Oracle services ora_pmon_<orasid> ora_dbw0_<orasid> ora_lgwr_<orasid> ora_smon_<orasid> ora_ckpt_<orasid> are active. If not, then you need to start them up as described in Chapter 5, Dimensions Installation. Mounting the Dimensions CD-ROM Login to the root account. Mount the Dimensions CD-1, as described below, using either a CD-ROM drive located on your machine or via NFS using an NFS server with a CD-ROM drive. Notes 1 The Dimensions CD-1 is in ISO 9660 format (with Rock Ridge information). 2 The following instructions include example CD-ROM device and mount points. These will need to be modified to reflect your particular system.

47 Mounting the Dimensions CD-ROM 47 Sun Sparc If your machine uses Volume Management to automount CD-ROMs (vold(1m) daemon will be running), then the CD will automount. Otherwise mount the CD-ROM at the mount point as per the following example: # mount -r -F hsfs /dev/sr0 /cdrom Red Hat And SuSE Linux If your machine uses autofs, a kernel-based automounter for Linux, and it is configured to automatically mount your CD-ROM drive, then the CD will automount. If your machine uses autofs, but it is not configured search the /etc/fstab file contains a line similar to /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 then mount the CD-ROM using the following command $ mount /dev/cdrom If your machine does not use autofs, enter the following command $ mount -t iso9660 /dev/cdrom /media/cdrom

48 48 Chapter 3 Pre-Installation Activities Starting the Installation Logging the Installation It is good practice to keep a log of the installation using the UNIX command script if available. If keeping a log, then remember to exit from the log session after the installation. CD-1 Platform Files CD-1 is a single-platform release containing: A designated Dimensions distribution comprising a tar file in compressed format called pcms.tar. An associated installation script called install that will automatically uncompress the tar file as part of the installation process. The top-level README.UNIX file. The MERANT End User Software License file License.pdf. Default Non-Interactive New Installation This installation is a non-interactive method for a new installation of Oracle and Dimensions. The default installation method cannot be used for client installations. The default installation parameters are: Home directory for Oracle: Oracle SID used: <pwd>/oracle ora8i

49 Starting the Installation 49 NET8 service name: Owner of the Oracle files: Group owner of the Oracle files: Database files location: Database Character Set: Disk space required for database files: Home directory for Dimensions: Owner of the Dimensions files: Group owner of the Dimensions files: ORACLE SYSTEM password ORACLE SYS password PCMS_SYS database password Tool Manager for the Intermediate database Intermediate Process Model Developer 1 for Intermediate Process Model QA Engineer 1 for Intermediate Process Model Team Leader for Intermediate Process Model Developer 2 for Intermediate Process Model QA Engineer 2 for Intermediate Process Model Product Item library location for Entry Level Process Model Oracle Server machine name ora8i oracle dba?/dbs (under ORACLE_HOME) US7ASCII 758Mb <pwd>/dimensions7_2 pcms dba manager change_on_install pcms_sys pcms INTERMEDIATE user2 user3 user4 user5 user6 $PCMS_ROOT/demo /intermediate hostname (output from hostname command)

50 50 Chapter 3 Pre-Installation Activities When the installation script is run it assumes that the Dimensions tar filename is pcms.tar and the current directory is where the installation will be placed. It also assumes that the pcms.tar file is in the same directory as the install script install. For example, to install Oracle and Dimensions under /usr/pvcs from CD-ROM mounted on /cdrom, type the following initial commands for all UNIX or Linux platforms: # cd /usr/pvcs # script install.log # umask 022 Then type the following operating-system command: # sh /cdrom/install default NOTE Sun Sparc: If your machine uses Volume Management to automount CD-ROMs (vold(1m) daemon will be running), then instead of the above, type: # sh /cdrom/<volume_id>/install default where <volume_id> is the Volume Label of CD-1 e.g. cdrom0. A confirmation screen will be displayed detailing the installation pre-requisites. You must be sure that there is sufficient free space on the disk where the installation will reside for the Dimensions, Oracle and database files. A final confirmation screen is then displayed. This details the location of $PCMS_ROOT and $ORACLE_HOME, database size, passwords, etc. If these defaults are satisfactory then enter Y to start the installation. If the tar filename is not pcms.tar, then a second parameter is required, for example: # sh /cdrom/install default <tar_filename> This will perform a default installation of Oracle and Dimensions from the tar file <tar_filename>.

51 Starting the Installation 51 After the installation completes with success, the new Dimensions release is ready for use but check Chapter 6, Dimensions Post-Installation Activities first for licensing and any tailoring to meet local needs. Standard Interactive Installation This will allow you to configure the Oracle and Dimensions installation to suit your particular requirements such as a client installation. At various points the installation procedure displays messages and asks for the input of appropriate information. Where there is a default value, this is shown in square brackets. This will be used if the input is just the RETURN key. Start the installation procedure with the following initial commands for all UNIX or Linux platforms: # cd /usr/pvcs # script install.log # umask 022 Then type the following operating-system command: # sh /cdrom/install NOTE Sun Sparc: If your machine uses Volume Management to automount CD-ROMs (vold(1m) daemon will be running), then instead of the above, type: # sh /cdrom/<volume_id>/install where <volume_id> is the Volume Label of CD-1 e.g. cdrom0. The following messages and warnings will be displayed: Warning of preliminary requirements. The following prompt:

52 52 Chapter 3 Pre-Installation Activities Prompt Please confirm continue (y/[n]) Enter y to continue, or hit RETURN to exit. If a pcms_reply.txt file is not found in the current directory you will be prompted to supply the name of a directory containing a pcms_reply.txt file from a previous installation. If you haven't got a file, you must either enter c to create or q to quit the installation. The pcms_reply.txt file should be kept and will then provide the default answers for subsequent installations. Proceed as described in the following chapters for the installation of Oracle and Dimensions.

53 53 4 Oracle Installation In this Chapter For this section See page Installation Overview 54 Pre-Installation Checks 56 Initiating the Oracle Runtime 56 Installation New Installation of Oracle with 58 Database Creation New Client Oracle Installation 65 without Database Creation

54 54 Chapter 4 Oracle Installation Installation Overview As stated previously in this document, CD-1 contains the Oracle Server runtime and Dimensions Server binaries for installation on an UNIX platform that supports Dimensions. Normally, the Oracle Server runtime and Dimensions Server are installed in one installation session. This is the recommended option as information gathered is used for both the Oracle Server runtime installation and the Dimensions installation. Additionally, the Oracle environment will be guaranteed to be in the required state for the Dimensions installation. However, it is possible to install the Oracle Server runtime in one session and the Dimensions Server in a later session. This will require ensuring that the Oracle environment is in the requisite state - see Dimensions Server Installed Separately from the Oracle Server Runtime on page 45. CAUTION! In all circumstances, an Oracle environment matching that detailed on page 45 must exist before proceeding with the Dimensions installation. This will automatically be the case following successful installation of the MERANT Oracle runtime software. In addition to installation instructions for the Oracle runtime server, this chapter gives basic information about starting up and shutting down the product. Oracle Server Runtime Installation Overview The installation of Oracle Version 8 runtime includes: Renaming the Oracle home directory supplied by the installer if it appears that Oracle 8 has already been installed in that

55 Installation Overview 55 directory. This is done before the new Oracle files are loaded. The directory will be renamed by appending.old to the old directory, e.g. /usr/oracle will be renamed to /usr/oracle.old (and the new Oracle files will then be installed in /usr/oracle). Loading the Oracle files into the Oracle home directory, setting up the file protections appropriately, and performing consistency checks to identify any data corruption that might have taken place during the media to media file transfers. Optionally, creating an RDBMS database of the minimum (installation default) size specified in Disk Space on page 20 The creation process will generate four data files, two redo log files and a control file. It will also startup Oracle by creating a minimum of five processes with names similar to: ora_pmon_<orasid> ora_dbw0_<orasid> ora_lgwr_<orasid> ora_smon_<orasid> ora_ckpt_<orasid> where <orasid> is the Oracle SID (System Identifier) supplied by the installer. Creating Dimensions scripts NOTE You will not need to create an RDBMS database if you wish to use an existing database that resides on a different machine to the one you are installing on. If this is the case then you must ensure that the machine hosting the database is accessible by TCP/IP. However, the Dimensions Installation will assume the existence of two tablespaces, PCMS_DATA and PCMS_TEMP. See Chapter 5, Dimensions Installation if you are just installing Dimensions alongside an existing Oracle.

56 56 Chapter 4 Oracle Installation Dimensions Server Runtime Installation Overview The installation of the Dimensions Server is described in Chapter 5, Dimensions Installation with an overview being given in Installation Overview on page 54. Pre-Installation Checks Proceed only if the pre-installation activities in Chapter 1, Introduction and Chapter 3, Pre-Installation Activities have been checked and followed. If you have an earlier version of Dimensions installed which you intend to upgrade to Dimensions 7.2, then it must be Dimensions 6.0, 7.0 or 7.1. If its release level is earlier than 6.0, you must upgrade to Dimensions 6.0 first. Please refer to the edition of this document shipped with the Dimensions 6.0 Server (Edition 5.2) and to PVCS Dimensions Upgrading from Dimensions 5.0 to 6.0. Initiating the Oracle Runtime Installation Login as user root, mount CD-1 and invoke the installation setup as described in Mounting the Dimensions CD-ROM and Starting the Installation on page 46 and page 48 respectively. Prompt Do you wish to install Oracle? (y/[n]) Reply n if you wish to proceed with a Dimensions installation as described in Chapter 5, Dimensions Installation. Reply y if you wish to install Oracle as follows.

57 Initiating the Oracle Runtime Installation 57 The installation procedure offers you the following Oracle 8i installation options (see the top-level README file for the exact Oracle 8i version level): 1 A new installation of Oracle with database creation. 2 A new client installation of Oracle with no database creation. 3 An upgrade of an existing Oracle or Oracle installation to Oracle x (see the top-level README file for the exact Oracle 8i version level). Choose Option 1 Choose Option 2 Choose Option 3 If the local node will be using Dimensions in standalone mode or if it will be a DFS node or a NET node hosting the RDBMS database. Proceed as described in New Installation of Oracle with Database Creation on page 58. If the local node will either be a Dimensions NET node or a DFS node using an RDBMS database resident on a remote node accessible by TCP/IP. Proceed as described in New Client Oracle Installation without Database Creation on page 65. If you wish to upgrade an existing Dimensions 6.0, 7.0 or 7.1 Oracle Server to Dimensions 7.2. This upgrade is described in the document Upgrading from Dimensions 6 to 7.

58 58 Chapter 4 Oracle Installation New Installation of Oracle with Database Creation Prompt Enter installation medium (or Ctrl-C to quit) [/cdrom/pcms.tar] If the installation is being performed directly from the Dimensions 7.2 CD-ROM, the installation medium is the absolute pathname of the file pcms.tar located on the appropriate platform-specific CD. Alternatively, if you have copied the appropriate pcms.tar file from the CD to a disk of your choice, then that absolute pathname must be entered. Prompt Enter main Oracle directory [/usr/oracle] If the directory you specify does not exist then the following message will be displayed: Directory <directory> not found. It will be created. If this directory contains Oracle files, the installation procedure gives the message: WARNING!! Oracle appears already to be installed in this directory. Before installing the new Oracle, the installation script will rename this directory to /usr/oracle.old. Please confirm continue? (y/[n]) Unless y is entered, the message "Please choose a different directory to install Oracle" is displayed, and the installation procedure re-displays the previous prompt. (If you would prefer to restart you can do so below when you have been asked to confirm the parameters.) Prompt Enter the Oracle SID [ora8i] Example inputs: ora8i, a, pcms, etc.

59 New Installation of Oracle with Database Creation 59 The Oracle SID is a string of maximum length six characters that must have an alphabetic letter as the first character. It identifies a specific instance of Oracle. If you answer with <return> to the following question, the Oracle instance will be assumed to be ora8i. Prompt Enter the service name [ora8i] Enter the NET8 service name for this database. The default is the same as the Oracle SID. However, if there are other databases in the network with the same Oracle SID an alternative service name should be specified. Prompt Prompt Enter the name of the owner of the Oracle files [oracle] Enter the name of the group to own the Oracle files [dba] NOTE The group must already exist. Prompt Enter the name of the directory to hold the database files [?/dbs] The directory in which the database files are to be created need not be in the same file system. There may be an advantage in using two different disks. The default is the subdirectory dbs down from the oracle home directory. This is shown as?/dbs. If the default, or dbs which is taken to be equivalent to the default, is not chosen, then the directory name must be entered in full, from the system root directory (i.e. it must begin with an oblique character [/]). This directory must have been already created before the installation procedure is started and it must not be on a Remote disk (e.g. NFS mounted file system).

60 60 Chapter 4 Oracle Installation Prompt Enter the size of the PCMS_DATA tablespace (in megabytes) [500] Dimensions will create four tablespaces; PCMS_DATA for Dimensions base databases; PCMS_TEMP, a temporary sort area for Dimensions users; PCMS_RBS for rollback segments; and SYSTEM, for the Oracle data dictionary. Together they represent a minimum of 218Mb and a default of 758Mb. You can specify here a value other than 500Mb for the PCMS_DATA tablespace if so desired (100Mb is the minimum). The installation process automatically assigns PCMS_TEMP to be the greater of either 10% of the size that you specify for PCMS_DATA during installation or 10Mb. The installation process automatically assigns PCMS_RDBS to be the greater of either 10% of the size that you specify for PCMS_DATA during installation or 20Mb. Prompt Enter the size of the SYSTEM tablespace (in megabytes) [150] You can specify here a value other than 150Mb for the SYSTEM tablespace if so desired (80Mb is the minimum). Prompt Enter the size of the first redo log file (in megabytes) [4] For a database of size up to 100 Mbytes, a redo log file of size 2 to 5 Mbytes is appropriate. Prompt Enter the size of the second redo log file (in megabytes) [4] Screen Output It is recommended that the second redo log file has the same size as the first. Please enter the Oracle Database Character Set for the ORA8i instance. In most cases the default US7ASCII character set should be used. You must ensure this field contains a valid database character set.

61 New Installation of Oracle with Database Creation 61 Prompt Please Enter the database character set [US7ASCII] If you specify a character set that the installer software does not recognize, you will be prompted to verify whether or not you wish to continue with that character set. Reply y only if you are absolutely certain that the character set you have specified really is a valid Oracle Database Character Set. Unless you are confident that your platform can support a different character set you should not change the default. Please refer to Appendix C, UNIX Environment for a Different Character Set and Locale and the top-level README file which may provide you with additional information. If in any doubt please consult the PVCS Support Center. CAUTION! Once the character set is specified here, it cannot be changed later except by using a full Oracle system export, recreating an empty database and doing a full Oracle system import (see Appendix C, UNIX Environment for a Different Character Set and Locale ). Prompt Please confirm you wish to proceed with these parameters (y/[n]) Reply y to continue installation. Replying n will terminate the installation. Now the installation work is started with the following main messages appearing: Extracting Oracle files... Moving files to target directory... Setting up file protections and performing consistency checks...please wait Creating database files...please wait Loading System Data...Please wait

62 62 Chapter 4 Oracle Installation Creating additional Rollback Segment to enable Tablespace creation Creating separate tablespaces for PCMS_RBS, PCMS_TEMP and PCMS_DATA Creating necessary Rollback segments Creating NET8 configuration files Oracle Run-Time installation successfully completed The new RDBMS database is created with two DBA user databases: SYSTEM with password MANAGER SYS with password CHANGE_ON_INSTALL The passwords for these databases should be noted as they are required to install Dimensions, and later on changed to preserve the security of the database (see PVCS Dimensions Database Administrator s Guide for details). The installation will create the following configuration files for use with NET8: $ORACLE_HOME/network/admin/listener.ora $ORACLE_HOME/network/admin/tnsnames.ora $ORACLE_HOME/network/admin/sqlnet.ora If the database is to be accessed by client Dimensions installations on other machines then the following steps should be performed: The configuration files should be copied to the /etc directory (all platforms other than Solaris) or to the /var/opt/oracle directory (Solaris) or merged with existing files of the same name if present. Ensure that the Oracle service name entry (for example "ora8i") is available to each client by:

63 New Installation of Oracle with Database Creation 63 For Each Client Hosted on a UNIX System Copying (or merging) the database server s /etc/tnsnames.ora or /var/opt/oracle/tnsnames.ora to the client s /etc/tnsnames.ora or /var/opt/oracle/tnsnames.ora. For Each Client Hosted on a Windows System Entering the service-name (database alias) on the client using the client s Net8 Configuration Assistant utility. Error Conditions In the event of an unsuccessful installation, please observe the following important points before re-starting the installation: Before proceeding any further, determine whether the Oracle processes corresponding to your SID (instance) are running. To do so check the output given by the following command: % ps -ax grep ora(bsd UNIX) or % ps -ef grep ora(system V UNIX) If the instance is up, there will normally be a minimum of five processes running with names embedding the SID. If the Oracle instance is up, then first shut it down. To shut down an instance, say ora8i, do the following as user oracle on the Oracle server machine:

64 64 Chapter 4 Oracle Installation If C shell: echo $TWO_TASK (1) setenv ORACLE_SID ora8i setenv ORACLE_HOME /usr/oracle setenv LD_LIBRARY_PATH $ORACLE_HOME/lib (2) $ORACLE_HOME/bin/svrmgrl SVRMGR> connect internal/<sys_password> SVRMGR> shutdown immediate SVRMGR> exit If Bourne shell: echo $TWO_TASK (1) ORACLE_SID=ora8i; export ORACLE_SID ORACLE_HOME=/usr/oracle; export ORACLE_HOME LD_LIBRARY_PATH=$ORACLE_HOME/lib (2) export LD_LIBRARY_PATH (2) $ORACLE_HOME/bin/svrmgrl SVRMGR> connect internal/<sys_password> SVRMGR> shutdown immediate SVRMGR> exit Insufficient Disk Space Delete any files that may have been created and regain additional space. Oracle cannot be started: Check the system parameters and the setup of the account where Oracle is being loaded. Delete any files that may have been created and regain additional space. Remove shared memory segments taken up by Oracle, if still present: If the Oracle processes have been stopped abnormally using the UNIX kill command, then the use of the shared memory and semaphores will not have stopped automatically. Use the 1. Will normally be undefined if you are on the server. 2. LD_LIBRARY_PATH is different on some platforms.

65 New Client Oracle Installation without Database Creation 65 commands ipcs to display the shared memory and semaphores usage; and ipcrm -m and ipcrm -s to, respectively, remove the shared memory and semaphores usage owned by Oracle. New Client Oracle Installation without Database Creation Prompt Enter installation medium (or Ctrl-C to quit) [/cdrom/pcms.tar] If the installation is being performed directly from the Dimensions 7.2 CD-ROM, the installation medium is the absolute pathname of the file pcms.tar located on the appropriate platform-specific CD. Alternatively, if you have copied the appropriate pcms.tar file from the CD to a disk of your choice, that absolute pathname must be entered. Prompt Enter main Oracle directory [/usr/oracle] If the directory you specify does not exist then the following message will be displayed: Directory <directory> not found. It will be created. If this directory contains Oracle files, the installation procedure gives the message: WARNING!! Oracle appears already to be installed in this directory. Before installing the new Oracle, the installation script will rename this directory. Please confirm continue? (y/[n])

66 66 Chapter 4 Oracle Installation Unless y is entered, the message "Please choose a different directory to install Oracle" is displayed, and the installation procedure re-displays the previous prompt. (If you would prefer to restart you can do so below when you have asked to confirm the parameters.) Prompt Prompt Enter the name of the owner of the Oracle files [oracle] Enter the name of the group to own the Oracle files [dba] NOTE The group must already exist. A list of the Dimensions Oracle installation parameters is displayed. Prompt Please confirm you wish to proceed with these parameters (y/[n]) Reply y to continue installation. Replying n will terminate the installation. Now the installation work is started with the following main messages appearing: Extracting Dimensions and Oracle kit listings...please wait Extracting Oracle files... Setting up file protections and performing consistency checks...please wait Oracle Run-Time installation successfully completed

67 New Client Oracle Installation without Database Creation 67 Error Conditions Insufficient Disk Space. Abort the installation, delete any files that may have been created (it may be necessary first to alter the files' ownership), regain additional space and start the installation again.

68 68 Chapter 4 Oracle Installation

69 69 5 Dimensions Installation In this Chapter For this section See page Installation Overview 70 Pre-Installation Checks 71 Initiating the Installation 73 A New or Upgrade Server 74 Installation A Client Installation 81

70 70 Chapter 5 Dimensions Installation Installation Overview Upon conclusion of the Oracle runtime installation you have the option of: Remaining within the installation session and immediately commencing the Dimensions installation. This is the recommended option as information gathered during the Oracle installation will automatically be carried forward into the Dimensions installation and the Oracle environment will be guaranteed to be in the required state for the Dimensions installation. Exiting the installation session and performing the Dimensions installation in a later installation session. This will require ensuring that the Oracle environment is in the required state see Dimensions Server Installed Separately from the Oracle Server Runtime on page 45. CAUTION! In all circumstances, an Oracle environment matching that detailed on page 45 must exist before proceeding with the Dimensions installation. As stated above, this will automatically be the case following successful installation of the MERANT Oracle runtime software. In addition to installation instructions for Dimensions, this chapter gives basic information about starting up and shutting down the product. Installation of Dimensions includes the following steps: Renaming the Dimensions root directory supplied by the installer if it appears that Dimensions 7.x has already been installed in that directory. This is done before the new Dimensions files are loaded. The directory will be renamed by appending.old to the old directory, for example, /usr/pvcs/dimensions7_x will be renamed to

71 Pre-Installation Checks 71 /usr/pvcs/dimensions7_x.old (and the new Dimensions files will then be installed in /usr/pvcs/dimensions7_x). The installation will terminate with an error if /usr/pvcs/dimensions7_x.old already exists. Loading the Dimensions files into the Dimensions root directory, setting up the file protections appropriately, and performing consistency checks to identify any data corruption that might have taken place during the media to media file transfers. Optionally creating the Dimensions base database within the RDBMS database. Creating the following main Dimensions command files (described in Chapter 6, Dimensions Post-Installation Activities ): /usr/pvcs/dimensions7_x/pcmslogin /usr/pvcs/dimensions7_x/pcmsprofile /usr/pvcs/dimensions7_x/mmi/pcms_startup /usr/pvcs/dimensions7_x/mmi/pcms_shutdown /usr/pvcs/dimensions7_x/mmi/pcms_clientstartup /usr/pvcs/dimensions7_x/mmi/pcms_clientshutdown Pre-Installation Checks Proceed only if the pre-installation activities in Chapter 3, Pre-Installation Activities have been performed successfully. If you are creating a Dimensions base database, ensure that the Oracle Instance to be used by Dimensions is up and running. Note that this Oracle will be running if you are continuing installation from Oracle to Dimensions and have created an RDBMS database in the process.

72 72 Chapter 5 Dimensions Installation To determine whether the Oracle processes corresponding to your instance are running, check the output given by the following command: % ps -ax grep ora (BSD UNIX) or % ps -ef grep ora (System V UNIX and Linux) If necessary, start up the Oracle Instance, say ora8i, using the commands below. You should log in as the Oracle administrator to do this. If C shell: % setenv ORACLE_SID ora8i % setenv ORACLE_HOME /usr/oracle % $ORACLE_HOME/bin/svrmgrl SVRMGR> connect internal/<sys_password> SVRMGR> startup SVRMGR> exit If Bourne shell: $ ORACLE_SID=ora8i; export ORACLE_SID $ ORACLE_HOME=/usr/oracle; export ORACLE_HOME $ $ORACLE_HOME/bin/svrmgrl SVRMGR> connect internal/<sys_password> SVRMGR> startup SVRMGR> exit The above assumes that the Oracle root directory is /usr/oracle. If you are creating the base database PCMS and you are an existing Dimensions user wishing to import your own specific generic process model (as opposed to the standard generic process model) into the base database PCMS, then ensure that a database export of this process model is available at the time of installation.

73 Initiating the Installation 73 Initiating the Installation Assuming that the Oracle installation, described in the previous chapter, has been completed successfully. The same installation script continues as follows: Prompt Do you wish to install PVCS Dimensions? (y/[n]) Reply n to exit. This option should be taken only if the Oracle installation appears to be unsatisfactory and needs to be done again. The installation procedure then prompts you to install Dimensions either as a client or a server. A client installation does not host a local database; whereas, a server installation does. Enter the appropriate installation option: 1 A new or upgrade server installation (go to page 74). 2 A new client installation (go to page 81). Choose Option 1 If either one of the following two cases applies (proceed as described in A New or Upgrade Server Installation on page 74): You are installing Dimensions for the first time on a node hosting the Oracle RDBMS database (i.e. a server installation) and consequently wish to create a Dimensions base database within the RDBMS database. This depends upon which option is chosen see Preliminary Activities on page 36 for further details. The base database will contain Dimensions 7.x system information necessary for the correct functioning of your Dimensions 7.x installation.

74 74 Chapter 5 Dimensions Installation You are upgrading an existing Dimensions 6.0, Dimensions 7.0 or Dimensions 7.1 server installation Choose Option 2 You are installing Dimensions for the first time on a node not hosting the RDBMS database (i.e. a client installation) and consequently do not wish to create a base database within the RDBMS database. If the Dimensions installation immediately follows on from an Oracle installation, then the installation will use the values of the Oracle environment variables used in the Oracle installation, otherwise you will be prompted for their values. A New or Upgrade Server Installation Prompt Enter installation medium (or Ctrl-c to quit) [/cdrom/pcms.tar] This prompt is displayed only if you are installing Dimensions separately from Oracle i.e. you previously answered no to the prompt Do you wish to install Oracle?. If the installation is being performed directly from the Dimensions 7.2 CD-ROM, the installation medium is the absolute pathname of the file pcms.tar located on the appropriate platform-specific CD. Alternatively, if you have copied the appropriate pcms.tar file from the CD to a disk of your choice, then that absolute pathname must be entered.

75 A New or Upgrade Server Installation 75 Prompt Enter the directory in which the PVCS Dimensions files will be installed. This release of Dimensions will be installed in the subdirectory dimensions7_x (e.g. dimensions7_2) of the directory you enter as the Dimensions root directory. If this directory contains Dimensions files, the installation procedure gives the message: WARNING!!PVCS Dimensions appears already to be installed in this directory. Before the new PVCS Dimensions files are installed, the installation script will rename this directory. Please confirm continue? (y/[n]) Unless y is entered, the message "Please choose a different directory to install Dimensions" is displayed, and the installation procedure redisplays the previous prompt. (If you would prefer to restart you can do so below when you are asked to confirm the parameters.) Prompt Do you wish to install a demo license? (y/[n]) Replying y will lead to the following additional prompts: Prompt Please enter the expiry date using the format DD-MMM-YYYY [12-JUN-2001] Prompt Please enter the 12-digit license key [ ] Please refer to page 92 for additional information relating to demo licenses. Prompt Prompt Enter the name of the user to own the PVCS Dimensions files [pcms] Enter the name of the group to own the PVCS Dimensions files [dba] NOTE The group must already exist.

76 76 Chapter 5 Dimensions Installation Prompt Prompt Enter main Oracle directory [/usr/oracle] Enter the name of the owner of the Oracle files [oracle] These prompts are displayed only if you are installing Dimensions separately from Oracle i.e. you previously answered no to the prompt Do you wish to install Oracle?. Prompt Should PVCS Dimensions be installed in the Oracle database? [y/n] Reply n if you wish to use Dimensions with an RDBMS database residing on a remote node accessible by TCP/IP. Reply y if the RDBMS database resides on the local host. Replying n will lead to the following additional prompt: Prompt Enter the name of the remote node hosting the RDBMS database [] Prompt Enter the Oracle SID [ora8i] This prompt is displayed only if you are installing Dimensions separately from Oracle i.e. you previously answered no to the prompt Do you wish to install Oracle?. Please enter the Oracle SID to be used by this Dimensions installation. If you just enter <return>, the SID ora8i is used as default. Please enter the correct SID as there will be no checks against your input. If you replied n to the question 'Should PVCS Dimensions be installed in the Oracle database? (y/n)', then the following additional prompt is displayed:

77 A New or Upgrade Server Installation 77 Prompt Enter the service name [ora8i] Enter the NET8 identifier for connecting to the remote database. The default is the same as the default Oracle SID in the pcms_reply.txt file. The installation will create a number of Oracle users, the passwords of which can be changed. The mainline prompts (beginning 'Enter the Oracle SYSTEM Password [manager]' below) give you the opportunity to change these passwords or accept the defaults shown in the brackets. Prompt Prompt Prompt Prompt Enter the ORACLE SYSTEM Password [manager] Enter the ORACLE SYS Password [change_on_install] Enter the PCMS_SYS database password [pcms_sys] This is the password for the database user account used by Dimensions to store Dimensions system data. Please select the process model you wish to use from: 1 Entry Level 2 Intermediate (default) 3 Other: this option has to be chosen if you wish to use an existing process model (Oracle export file) Please choose from the above options (1 [2] 3) NOTE The standalone Process Model Installer enables you, as a post-installation activity, to install the Entry Level or Intermediate process models (together with their respective associated Learning Project and Payroll demonstration products). For example, if you choose the Intermediate process model at the time of installation, you can later additionally install the Entry Level process model. Please see the Deployment Guide for details.

78 78 Chapter 5 Dimensions Installation Selecting Option 1 Prompt Screen Output Prompt Prompt Please specify the location for the demo product files: [/usr/dimensions7_x/demo/entry_level] Please enter the operating system login id for the Tool Manager of the entry level process model demo product. Tool Manager [pcms] Enter the Oracle server machine [ hostname ] where hostname is the name of the current host system Selecting Option 2 Prompt Screen Output Prompt Prompt Prompt Prompt Prompt Prompt Prompt Please specify the location for the product libraries: [/usr/dimensions7_x/demo/intermediate] Please enter the operating system login ids for the users of the intermediate process model demo product Enter name of user to act as Tool Manager [pcms] Enter name of user to act as Developer1 [user2] Enter name of user to act as QA engineer1 [user3] Enter name of user to act as Team leader [user4] Enter name of user to act as Developer2 [user5] Enter name of user to act as QA engineer2 [user6] Enter the Oracle server machine [ hostname ] where hostname is the name of the current host system

79 A New or Upgrade Server Installation 79 Selecting Option 3 When you select Other you can specify your own process model export file or one of the three process model export files supplied with Dimensions 7.2: /usr/pvcs/dimensions7_2/dbase/generic.exp /usr/pvcs/dimensions7_2/process_models/ entry_level_cpl.exp /usr/pvcs/dimensions7_2/process_models/ intermediate_cpl.exp where: /usr/pvcs/dimensions7_2 must be replaced by your Dimensions server home directory. NOTE If you are an existing Dimensions user and you have a compatible export of your generic Dimensions process model then you can use it here. Otherwise, use the default given. Please check with the PVCS Support Center on the validity of your process model before attempting to import it. Prompt Prompt Enter the name of the process model export file [/usr/dimensions7_x/demo/generic.exp] Do you wish to install Published Views? (n/[y]) Enter Y if you wish Published Views in the PCMS base database Prompt Prompt Enter the PCMS base database password [pcms] This is the password for the Dimensions base database PCMS. Enter the name of the user to act a Tool Manager for the PCMS database [pcms] This is the operating system user id for the person to be to the Tool Manager for the Dimensions base database PCMS.

80 80 Chapter 5 Dimensions Installation Screen Output Prompt Optionally the installer can automatically create additional Dimensions users. To do so you will need to specify a file containing the user details. Please refer to the documentation for details of the format of the file. Do you wish to create additional user accounts ([n]/y) Replying Y, will lead to following additional prompt: Prompt Please specify location of the user file [ ] The format for the file holding any additional user accounts is as follows <OSLoginName> <DimensionsUserName> The two fields are separated by whitespace characters. Both fields must contain only alphanumeric characters or the underscore character (_) to a maximum of 25 characters. These entries are not case-sensitive, (i.e.user1 is the same as user1). For example dennis gareth pcms_dennis pcms_gareth The user creating these accounts must ensure that the operating system logins exist the Installer will not create them. Prompt Please confirm you wish to proceed with these parameters (y/[n]) Replying n will terminate the installation. If you chose to create a base database, then the installation script will send a mail message to the Tool Manager containing the passwords to the following Oracle users: SYSTEM SYS PCMS_SYS

81 A Client Installation 81 These passwords depend on the process model chosen, namely: Process Model Entry Level Intermediate Other Oracle Password entry_level intermediate pcms The installation script uses your responses to load and set up Dimensions files. It will give suitable messages indicating the task being performed at each stage. After the installation completes with success, the new Dimensions release is ready for use, but first check Chapter 6, Dimensions Post-Installation Activities. for licensing and any tailoring to meet local needs. A Client Installation Prompt Do you wish to install the forms-based administration components of Dimensions (such as the Process Modeler) which also result in the installation of Oracle Developer 6.0 runtime (y/[n]) Reply y if you intend to use the Dimensions Administration tools. These should not be required for client only installations. Prompt Enter installation medium (or Ctrl-C to quit) [/cdrom/pcms.tar] This prompt is displayed only if you are installing Dimensions separately from Oracle i.e. you previously answered no to the prompt Do you wish to install Oracle?. If the installation is being performed directly from the Dimensions 7.2 CD-ROM, the installation medium is the absolute pathname of the file pcms.tar located on the appropriate platform-specific CD.

82 82 Chapter 5 Dimensions Installation Alternatively, if you have copied the appropriate pcms.tar file from the CD to a disk of your choice, then that absolute pathname must be entered. Prompt Enter the directory in which the PVCS Dimensions files will be installed. This release of PVCS Dimensions will be installed in subdirectory dimensions7_2 of the directory you enter as the PVCS Dimensions root directory. If this directory contains Dimensions files, the installation procedure gives the message: WARNING!!PVCS Dimensions appears already to be installed in this directory. Before the new PVCS Dimensions files are installed, the installation script will rename this directory. Please confirm continue? (y/[n]) Prompt Prompt Prompt Prompt Prompt Enter the name of the user to own the PVCS Dimensions files [pcms] Enter the name of the group to own the PVCS Dimensions files [dba] Enter main Oracle directory [/usr/oracle] Enter the name of the owner of the Oracle files [oracle] Is the database to be used by PVCS Dimensions resident on this machine (y/n)) n Replying n if you wish to connect to a remote node hosting the Oracle RDBMS database. You will then be prompted for that remote host.

83 A Client Installation 83 Prompt Enter the remote node hosting the RDBMS database [ ] Prompt Enter the Oracle SID [ora8i] This prompt is displayed only if you are installing Dimensions separately from Oracle i.e. you previously answered no to the prompt Do you wish to install Oracle?. Please enter the Oracle SID to be used by this Dimensions installation. If you just enter <return>, the SID ora8i is used as default. Please enter the correct SID as there will be no checks against your input. Prompt Enter the service name [ora8i] Enter the NET8 identifier for connecting to the remote database. The default is the same as the default Oracle SID in the pcms_reply.txt file. The installation script uses your responses to load and set up Dimensions files. It will give suitable messages indicating the task being performed at each stage. After the installation completes with success, the new Dimensions release is ready for use, but first check Chapter 6, Dimensions Post-Installation Activities. for instructions on setting up access to Dimensions and any tailoring to meet local needs.

84 84 Chapter 5 Dimensions Installation

85 85 6 Dimensions Post-Installation Activities In this Chapter For this section See page Setting Up Access to Dimensions 86 Licensing Dimensions Products 89 Dimensions Command Files 94 Access to Dimensions Files 97 Dimensions Runtime Parameters 98 Dimensions Make Installed on a 98 "Multi-Homed" Server Platform Re-Boot of Oracle/Dimensions 99 Standalone Process Model 101 Installer

86 86 Chapter 6 Dimensions Post-Installation Activities If you wish to use Dimensions in DFS or NET mode then please refer to Chapter 7, Getting Started with Dimensions for further reading after completing this chapter. Setting Up Access to Dimensions In the rest of this chapter, the following assumptions have been made: Oracle has been installed in /usr/oracle. Dimensions has been installed in /usr/pvcs. The password for the Dimensions base database is entry_level, intermediate or pcms depending on which process model you chose during installation, namely: Entry Level, Intermediate (default) or your own. The user account pcms is the $TOOL-MANAGER ($TOOL-MANAGER is the role required to be able to Define New Products within Dimensions). The owner of the Dimensions installation is the user account pcms. The.login (or.profile) file of the Dimensions user account must have the following lines; these lines assume that Dimensions is installed in the dimensions7_x subdirectory (e.g. dimensions7_2) and choice of default intermediate process model: If C shell: % source /usr/pvcs/dimensions7_2/pcmslogin % source /usr/pvcs/dimensions7_2/x2_7/xpcmslogin % setenv PCMSDB intermediate_tool

87 Setting Up Access to Dimensions 87 If Bourne shell: $. /usr/pvcs/dimensions7_2/pcmsprofile $. /usr/pvcs/dimensions7_2/x2_7/xpcmsprofile $ PCMSDB=intermediate_tool; export PCMSDB Avoid issuing the command set -u until after invoking pcmsprofile. Failure to do so may result in the script failing to complete, leaving the environment incorrect for Dimensions. A symptom of this problem is the error message: USER: parameter not set Note that depending on whether the database resides remotely or locally, the Dimensions login procedure sets or unsets the Oracle environment variable TWO_TASK as appropriate. If, for example, the RDBMS database resided on a remote node which is accessible to the local host via TCP/IP then the variable TWO_TASK would be set to: <service_name> (as found in /var/opt/oracle/tnsnames.ora (Solaris only) or /etc/tnsnames.ora) The installation will create the following configuration files for use with NET8: Server Installation: $ORACLE_HOME/network/admin/listener.ora $ORACLE_HOME/network/admin/tnsnames.ora $ORACLE_HOME/network/admin/sqlnet.ora Client Installation: ${ORA_HOME}/network/admin/tnsnames.ora ${ORA_HOME}/network/admin/sqlnet.ora

88 88 Chapter 6 Dimensions Post-Installation Activities The following steps should then be performed: The configuration files should be copied to the /etc or /var/opt/oracle directory (Solaris only) or merged with existing files of the same name if present. Ensure that the Oracle service name entry (for example ora8i) is available to each client by: For Each Client Hosted on a UNIX or Linux System Copying (or merging) the database server s /etc/tnsnames.ora or /var/opt/oracle/tnsnames.ora to the client s /etc/tnsnames.ora or /var/opt/oracle/tnsnames.ora. For Each Client Hosted on a Windows NT System Entering the service-name (database alias) on the client using the client s Net8 Configuration Assistant utility. Start the NET8 TNS listener process for client connections by editing the pcms_startup script as described below: Search for the following comment: ##################################################################### # Uncomment the following line to start the NET8 TNS LISTENER process # for Client connections ##################################################################### Remove the comment character (#) from the front of the next line to make it say: su $ORAUSER -c 'sh -c ". $PCMS_ROOT/pcmsprofile;$ORACLE_HOME/bin/lsnrctl start"' and save your changes. Subsequent Dimensions users may be created using the Dimensions UREG or CUSR functions or the equivalent Process Modeler forms. These users will receive a mail message which

89 Licensing Dimensions Products 89 contains appropriate entries for the login file.login or.profile. The TOOL-MANAGER role may be changed to other valid users. See PVCS Dimensions Database Administrator s Guide. Licensing Dimensions Products The Dimensions product suite comprises two licensed products protected by license keys: All Dimensions binaries apart from PVCS Replicator. PVCS Replicator. In order to use these products from a Dimensions node, the node must first be licensed. A License Key Request Form is provided by the PVCS Support Center for the purposes of registering customer configuration details and also the Dimensions products PCMS or PCMS plus REPLICATOR to be licensed. The licensing of Dimensions UNIX servers is provided by the third-party FLEXlm "floating license mechanism". A Dimensions node can be: A Single Node The node contains the Dimensions binaries, the Oracle binaries, the RDBMS database and the Dimensions item libraries. In addition, the FLEXlm license manager resides on this node. One of a Number of Networked Nodes A number of nodes (on a network) can be connected to provide Dimensions facilities and access to Dimensions across the network. Nodes on the network can be defined to be:

90 90 Chapter 6 Dimensions Post-Installation Activities A license server node that monitors and controls access to Dimensions up to the limit defined by the number of licenses bought. A database server accessed by all Dimensions processes running on the network. This node can also hold Dimensions item libraries. A client node that may host Dimensions item libraries. Licensing Dimensions Products with FLEXlm FLEXlm supports floating licenses (token sharing across networks) and hence provides a license from a given license node to any client node on the network. Creating the license.dat File Based on your responses to the License Key Request Form, MERANT will provide you with the text of the license file. You must create (using for example: vi) a file called license.dat in the directory identified by the Dimensions environment symbol PCMS_LICENSE. This text will be similar to the following: SERVER moon 12a DAEMON sqld /usr/pvcs/dimensions7_2/prog/sqld FEATURE PCMS sqld permanent 1000 \ ABCDEF1234 \ VENDOR_STRING="A" DIST_INFO= An example of the file can be found in $PCMS_ROOT/examples/license.dat. NOTE See also Demo License on page 92 which has a different format and application.

91 Licensing Dimensions Products 91 SERVER Line The SERVER line identifies the server node. In this example moon is the node name, 12a45678 is the host id, and 7584 is the TCP/IP port number. You may change the node name or the port number on this line. You may omit the port number as long as you add the line: license 7584/tcp to the services database in /etc/services or the NIS services map. There may be up to three SERVER lines. They must all be entered into the license file. Once FLEXlm is initiated (see Starting the FLEXlm Daemon on Dimensions Servers on page 93), the host-id of the node to be used as the license server can be confirmed by executing the FLEXlm utility on the appropriate node lmhostid The equivalent operating-system commands that can be used to determine the host-id for use in initially filling in the License Key Request Form are described in Host ID for Dimensions Licensing on page 43. DAEMON Line In the DAEMON line sqld is the name of the license daemon. You may not alter this. The string /usr/pvcs/dimensions7_2/prog/sqld is optional and indicates the location of the license daemon. This is found in the PCMS_PROG directory. You must update this field to the value of PCMS_PROG; you may not use the environment variable itself. If omitted the $PATH variable is used to find sqld.

92 92 Chapter 6 Dimensions Post-Installation Activities FEATURE Line In the FEATURE line: 'PCMS' is the name of the product you have been licensed. If you have been licensed more than one product there will be more than one FEATURE line. 'permanent' indicates that your license is a permanent license i.e. there is no expiration date is the number of licenses provided (in this example for PCMS). For the first ('PCMS') FEATURE line only, a final field 'dist_info= ' indicates your 12-character serial number. The MERANT Distribution Department assigns this serial number to your Dimensions installation when you purchase your Dimensions media. Here, , is just an example. Once licensing is complete, the dist_info information for a particular Dimensions server can be displayed: From within PC Client, by accessing the menu option Help About. From within Motif Client, via the Control Panel logging window at initial connection. None of the information on the FEATURE line can be changed. Demo License If you chose to Enter a demo license, you will need to enter the date and license key using the license key information that accompanied your product shipment. These entries are not casesensitive.

93 Licensing Dimensions Products 93 This type of license has a fixed expiry date. Therefore, in order to gain maximum benefit from this new Version of Dimensions do not delay in its installation. A Demo license is an uncounted license and as such does not involve starting the FLEXlm license service. Starting the FLEXlm Daemon on Dimensions Servers Once your license.dat file has been created and placed in the directory $PCMS_LICENSE, you need to manually start the FLEXlm daemon before you can successfully run the Dimensions server. CAUTION! To be able to successfully start the FLEXlm daemon, you must ensure that the UNIX user who owns the Dimensions installation is also the owner of the license file license.dat, not root or anyone else (you will receive a "permission denied" error message if you fail to ensure this). This UNIX user is by default pcms, unless another user was specified during the installation procedure (see pages 78 and 79). To start the FLEXlm daemon now (and automatically for all subsequent restarts of Dimensions) on the license server node(s) only you must: Edit the command file $PCMS_MMI/pcms_startup to uncomment the lines that start the license daemon (calls to lmgrd). Edit the command file $PCMS_MMI/pcms_shutdown to uncomment the lines that stop the license daemon (calls to lmdown). Execute pcms_startup to start the Dimensions server.

94 94 Chapter 6 Dimensions Post-Installation Activities It is usual practice to ensure that the files pcms_startup and pcms_shutdown are run as part of your system boot and shutdown procedures respectively, although you can of course always execute them manually. Dimensions Clients If the server PCMS_LICENSE directory is not visible from a client you will need to create a local $PCMS_LICENSE directory and then copy the license.dat file into it. Further Information See Appendix B, Floating License Management, for further information on managing floating licenses. Dimensions Command Files The installation procedure provides the following six command files. (The following lines assume that Dimensions is installed in the dimensions7_x subdirectory, e.g. dimensions7_2) NOTE You are advised to make back ups of these files if you decide to customize them for your particular system. This will provide a known fallback position should you need to perform troubleshooting operations. pcmslogin Resident in $PCMS_ROOT directory. A C shell script for setting the environment variables required to run Dimensions. Invoke this script as part of the.login file of every Dimensions user using C shell, for example:

95 Dimensions Command Files 95 % source /usr/pvcs/dimensions7_x/pcmslogin pcmsprofile Resident in $PCMS_ROOT directory. This is the Bourne shell equivalent of pcmslogin. Invoke this script as part of the.profile file of every Dimensions user using Bourne shell, for example: $. /usr/pvcs/dimensions7_x/pcmsprofile pcms_startup Resident in $PCMS_MMI. A shell script for starting up Oracle. It should be run by root. This is appropriate only for the node that hosts the RDBMS database used by Dimensions. Run this as part of your system boot procedure. WARNING! After performing an installation and all the set up activities described in this chapter, Oracle will still be running. In these circumstances, Oracle must be first shut down before attempting to start Dimensions using this script, for example by using the pcms_shutdown script. NOTE This script also contains commented-out statements for starting up the Oracle listener process (for NET8), starting Dimensions Network, starting the PVCS Replicator listener, starting Tomcat server and also the FLEXlm daemon. Uncomment these statements if the database server node is either a NET node or a DFS node or FLEXlm is being used or you are running Dimensions I-Net. pcms_shutdown Resident in $PCMS_MMI. A shell script for shutting down Oracle. It should be run by root. This is appropriate only for the node that hosts the RDBMS database used by

96 96 Chapter 6 Dimensions Post-Installation Activities Dimensions. Run this script as part of the UNIX system shutdown procedure. NOTE This script contains commented-out statements for stopping the Oracle listener process (for NET8), stopping Dimensions Network, stopping the PVCS Replicator listener, stopping Tomcat server and also stopping FLEXlm. Uncomment these statements if the database server node is either a NET node or a DFS node running Tomcat server or is using FLEXlm. One of the following optional parameters may be specified with respect to shutting down the Oracle instance: NORMAL Oracle will wait for all connected users to disconnect from the database. This is the default. IMMEDIATE Oracle will not wait for connected users, but will rollback current transactions. Any recovery on subsequent startup is automatic. Use IMMEDIATE if the machine is going to be shut down, or the database is malfunctioning. ABORT Oracle will shut down instantaneously. Use ABORT if neither of the above methods work or you must shut it down instantaneously. This should only be used as a last resort. pcms_clientstartup Resident in $PCMS_MMI. A shell script containing commented-out statements for starting Dimensions Network and the PVCS Replicator listener on a node that does not host the RDBMS database used by Dimensions. Uncomment these

97 Access to Dimensions Files 97 statements if the node is either a NET node or a DFS node. Run this as part of your UNIX system boot procedure. pcms_clientshutdown Resident in $PCMS_MMI. A shell script containing commented-out statements for stopping Dimensions Network and the PVCS Replicator listener on a node that does not host the RDBMS database used by Dimensions. Uncomment these statements if the node is either a DFS node or a NET node. Run this script as part of your UNIX system shutdown procedure. Access to Dimensions Files It is recommended that the operating-system account pcms is placed in one group, with operating system accounts for other Dimensions users being placed in a different group. For security considerations, operating system accounts for ordinary Dimensions users should never be placed in the same group as the PCMS account. It is also recommended that only the operating-system accounts of Tool Managers are placed in the same group as the owner of the Dimensions installation. This will ensure that access to the Dimensions $PCMS_DBASE utilities are restricted to only valid Tool Managers, not ordinary Dimensions users. See also Item Libraries on page 32.

98 98 Chapter 6 Dimensions Post-Installation Activities Dimensions Runtime Parameters The procedure pcmslogin (or pcmsprofile) causes a number of Dimensions operating-system environment variable assignments for every user of that particular Dimensions installation. You are, on a per-user basis, able to override a particular installation-wide assignment by making an alternative local assignment to your own user environment via the.login (or.profile) login file or at the operating-system command prompt. These operating-system environment variable assignments are commonly referred to as Dimensions Symbols. The reason for this terminology is so that the same Dimensions symbolic name can be used for similar functional variable assignments in all the operating system types supported by Dimensions i.e. UNIX and Windows. The Dimensions Symbols applicable to UNIX are detailed in Appendix D, Dimensions Symbols. The symbol PCMSDB must be set before Dimensions can be invoked on an individual basis. Additionally, various symbols must be set to establish your Dimensions browsing, editing, printing and mailing environment these are all detailed in Appendix D. Dimensions Make Installed on a "Multi-Homed" Server Platform Certain types of server platform (usually called "multi-homed") have more than one network adapter card, and therefore have more than one TCP/IP address. As the rendezvous used by the Dimensions Make Slave Component contains a literal TCP/IP address, "multi-homed" Dimensions servers must have a special environment symbol MCX_LISTEN defined to specify the appropriate TCP/IP address to be used.

99 Re-Boot of Oracle/Dimensions 99 This should be done via the pcmslogin or pcmsprofile command file (see Dimensions Command Files on page 94). Re-Boot of Oracle/Dimensions If the node hosting the RDBMS database is shut down, Oracle (and Dimensions Network) will not be started up automatically at boot time unless the following shell scripts have been run as part of the system boot procedure. Please refer to Dimensions Command Files on page 94 for the customized changes you may need to make to these scripts before using them. Assuming that Dimensions is installed in /usr/pvcs/dimensions7_x, the command for starting Oracle and Dimensions (including Dimensions Network if applicable) is: % sh /usr/pvcs/dimensions7_x/mmi/pcms_startup The equivalent of this command for a node which does not host the RDBMS database is: % sh /usr/pvcs/dimensions7_x/mmi/pcms_clientstartup There is also a shell script for shutting down Oracle and Dimensions (including Dimensions Network if applicable) on the database server node. This is called pcms_shutdown and is located in the same directory as pcms_startup. The equivalent script for a client node is pcms_clientshutdown and is also located in the same directory. Notes and Cautions Ensure that no one is using Dimensions or Oracle before starting any installation, maintenance, or backup operation. When a new Dimensions user is defined (using the Dimensions CUSR command or the equivalent Process Modeler form), the main database must not be otherwise

100 100 Chapter 6 Dimensions Post-Installation Activities accessed while that operation is being executed, in order to avoid any locking problems. In the event of an improper system shutdown (e.g. a crash or a power failure) resulting in an abnormal termination of Dimensions and Oracle, a number of Oracle and Dimensions files may remain undeleted. These undeleted files might cause pcms_startup (or pcms_clientstartup) to fail, and if this is the case the steps required to restart Dimensions and Oracle are: From the oracle account, make sure the environment variables are correctly set up. If using Dimensions Network then the file: $PCMS_ROOT/dfs/<nodename>/<nodename>.dat must be removed manually (using the UNIX rm command) if present (as it will be if Dimensions Network has been stopped abnormally). Dimensions Network cannot be started on the node <nodename> if this file already exists. Force start Oracle and then shut it down normally using the following commands: % $ORACLE_HOME/bin/svrmgrl SVRMGR> connect internal/<sys_password> SVRMGR> startup force SVRMGR> shutdown SVRMGR> exit Run pcms_startup or pcms_clientstartup to start Dimensions or Dimensions Network respectively. On a Dimensions server Oracle will be restarted as part of the pcms_startup process.

101 Standalone Process Model Installer 101 Standalone Process Model Installer The standalone Process Model Installer enables you to postinstall the Entry Level or Intermediate process models (together with their respective associated Learning Project and Payroll demonstration products). For example, if you choose the intermediate process model at the time of installation, you can later additionally install the Entry Level process model. Please see the Deployment Guide for details.

102 102 Chapter 6 Dimensions Post-Installation Activities

103 103 7 Getting Started with Dimensions In this Chapter For this section See page Introduction 104 Accessing the Payroll 104 Demonstration Product Dimensions Network Tests 105

104 104 Chapter 7 Getting Started with Dimensions Introduction To enable you to rapidly get started with Dimensions, there are demonstration products within the Entry Level and Intermediate process models, as briefly described on page 36. Accessing the Payroll Demonstration Product If you chose the Intermediate process model (or workflow) option when installing Dimensions, then you will have access to a demonstration Dimensions product called the payroll project. To access payroll as a Tool Manager you must set your PCMSDB symbol to INTERMEDIATE_TOOL. This is a secure database so does not require a password. Other users must also set their own PCMSDB symbol. For example, if STEVE is the operating system name of the user that was specified in the Intermediate Users dialog, the PCMSDB symbol must be set to INTERMEDIATE_STEVE. Payroll is a demonstration Dimensions product which is intended to show by example the features and functionality of Dimensions. The payroll product includes a design part breakdown structure, various change documents and items for which baselines have been created. See the Deployment Guide for details.

105 Dimensions Network Tests 105 Dimensions Network Tests The chapter entitled "Dimensions Network Acceptance Tests" in the related document PVCS Dimensions Network User s Guide describes tests where it is assumed that Dimensions Network is running on two nodes. Please refer to the above guide and run the Dimensions Network Acceptance Tests if you will be using Dimensions Networking.

106 106 Chapter 7 Getting Started with Dimensions

107 107 8 Dimensions I-Net and WebDAV Server Installation In this Chapter For this section See page Introduction 108 Before You Install 110 Upgrading from Dimensions Installing Dimensions I-Net and 112 WebDAV Server Starting and Stopping Dimensions 114 I-Net and WebDAV Server Configuring Apache Web Server 116 Configuring iplanet and SunOne 118 Web Servers Installing the Dimensions I-Net 119 Client Uninstalling Dimensions I-Net and 120 WebDAV Server

108 108 Chapter 8 Dimensions I-Net and WebDAV Server Installation Introduction This chapter provides instructions for installing, configuring, and running Dimensions I-Net and WebDAV Server. In this chapter, you ll learn: The system requirements and installation prerequisites. How to complete the installation. How to start and stop Dimensions I-Net and WebDAV Server. How to configure the supported web servers to work with Dimensions I-Net and WebDAV Server. How to install and run the Dimensions I-Net client in your web browser. How to uninstall Dimensions I-Net and WebDAV Server. Refer to the PVCS Dimensions WebDAV Server Implementation Guide for information about: How to configure Dimensions to work with WebDAV Server. How to administer WebDAV Server. How to configure WebDAV clients. After installation, you can access the WebDAV Server Implementation Guide from <DimINet-Root>/ webdav_impl.pdf, where <DimINet-Root> is the path to your Dimensions I-Net/WebDAV Server installation.

109 Introduction 109 Dimensions I-Net Components The combined services of the Dimensions I-Net server, the web server, and the Dimensions I-Net client enable you to access Dimensions features remotely. Each component is described below: Dimensions I-Net server: Dynamically generates the HTML pages you view from Dimensions I-Net client and processes the tasks you initiate from Dimensions I-Net client. Tomcat: Servlet engine that enables Dimensions I-Net to run. It can be used standalone or in conjunction with any of the supported web servers. Web server: Enables information to be passed between the Dimensions I-Net server and the Dimensions I-Net client via HTTP. The web server must be running before you can access the Dimensions I-Net client. Dimensions I-Net client: Provides access to Dimensions features through a browser-based interface. WebDAV Server Components The combined services of WebDAV Server and its components allow you to work with Dimensions items and workset directories from within a supported WebDAV client, such as Microsoft Office and Macromedia Dreamweaver. Each component is described below: WebDAV Server: Receives requests from the WebDAV client, processes them according to the WebDAV protocol, and sends back responses. Delegates file operations to the Dimensions repository. File system cache: A holding area on the server that stores temporary files during check out, check in, and get copy

110 110 Chapter 8 Dimensions I-Net and WebDAV Server Installation operations. The cache also holds WebDAV resource properties. Tomcat: Servlet engine that enables WebDAV Server to run. It can be used standalone or in conjunction with any of the supported web servers. Web server: Enables information to be passed between WebDAV Server and the WebDAV client via HTTP. You can configure a supported web server to use in conjunction with the Tomcat servlet engine. WebDAV client: A WebDAV-compliant software tool that provides access to common versioning tasks. Before You Install System Requirements Before you install Dimensions I-Net and WebDAV Server, make sure that you meet the system requirements specified both in the Dimensions I-Net and main Dimensions README files. These specify the supported server operating systems and web servers, and the supported client operating systems and web browsers. Server Prerequisites Dimensions Server 7.2 (CD-1) is installed. You have the Installation CD-4 or there are copies of the tar files and installation script available. You are currently running from the root account. You have run the Dimensions login script:

111 Upgrading from Dimensions pcmslogin for C-shell. pcmsprofile for Bourne shell or Korn shell. User accounts already exist for the Dimensions and Oracle files. The home directories for the Dimensions tool-manager (default is pcms) and the Oracle account (default is oracle) exist. Upgrading from Dimensions 7.0 Dimensions I-Net and WebDAV Server require Dimensions Server x or 7.2 to be installed if you wish to take advantage of the Dimensions I-Net Querying and Change Document Attachment features introduced at Dimensions x. If you currently have Dimensions Server 7.0 or x installed, follow these general steps to upgrade to 7.2: 1 Upgrade Dimensions Server 7.0 or 7.1 to Install Dimensions I-Net and WebDAV Server following the instructions below. The installation program uninstalls any previous versions of these products. 3 Configure the web server you wish to use with Dimensions I-Net and WebDAV Server. See Configuring Apache Web Server on page 116 or Configuring iplanet and SunOne Web Servers on page 118.

112 112 Chapter 8 Dimensions I-Net and WebDAV Server Installation Installing Dimensions I-Net and WebDAV Server The installation program allows you to install both Dimensions I-Net and WebDAV Server. These components are installed within the same directory (DimINet) and use the same installation of the Tomcat servlet engine. You can install the components individually. However, the components will still use the same instance of Tomcat. To install Dimensions I-Net and WebDAV Server: 1 Make sure you are running from the root account. 2 Do one of the following: Copy the installation script and tar files to your system in a single temporary directory. The files include inet.tar, tomcat.tar, webdav.tar, and inet_install. Insert CD-4 into the CD-ROM drive. If the CD-ROM drive does not mount automatically, you must mount it before continuing. See Mounting the Dimensions CD-ROM on page 46 for instructions. 3 Change directory to one of the following: cd <temp dir> cd <CDROM mount>/inet/<os> where <os> is the directory corresponding to your operating system: solaris or linux. 4 Enter./inet_install 5 Select the components that you wish to install and press Enter. By default, both Dimensions I-Net and WebDAV Server are selected to be installed.

113 Installing Dimensions I-Net and WebDAV Server 113 NOTE If you are installing on Linux you will not be presented with these selections, as WebDav Server cannot be installed and Dimensions I-Net is the only option. 6 Press Enter at the prompt to confirm your selection. 7 Review the installation requirements and press Enter. 8 Press Enter to accept the installation medium (the CD-ROM or the temporary directory on your machine). 9 Press Enter to install the components under the Dimensions Root directory detected. This creates a DimINet directory into which all the files required to run the selected components will be copied. 10 Press Enter to accept the default configuration values, or modify the values to match your system setup: Dimensions Server Hostname: The name of the Dimensions server you are connecting to. By default, this is the name of the local machine. Oracle Database Hostname: The machine where the Oracle database resides. By default, this is the name of the local machine. Oracle Database SID: The database identifier for the database you are selecting. By default, this is the local Oracle SID. Tomcat Application Server HTTP PORT number: The Tomcat port number. The default is If you are adding a component, the port number shown is the current port number.

114 114 Chapter 8 Dimensions I-Net and WebDAV Server Installation NOTE Only one application can use a particular port. If another application (other than the WebDAV or I-Net component) or service is using the default port, then you must assign a different port number to Tomcat. 11 Check that your settings are correct and enter: Y to proceed with the installation using these settings. N to terminate the installation. Starting and Stopping Dimensions I-Net and WebDAV Server To start Dimensions I-Net and WebDAV Server, you start Tomcat, the servlet engine that is installed that enables both components to run. You can use Tomcat standalone and access it at the port number you specified during installation, or you can configure one of the supported web servers to work in conjunction with Tomcat. See Configuring Apache Web Server on page 116 and Configuring iplanet and SunOne Web Servers on page 118 for instructions. You must start Tomcat (along with any configured web servers) on the server machine before Dimensions I-Net can be accessed in a web browser, or WebDAV Server can be accessed through a WebDAV client. Once you have started Tomcat, it will continue to run until you shut it down manually or shut down the machine on which it is installed. For information on Tomcat, go to

115 Starting and Stopping Dimensions I-Net and WebDAV Server 115 NOTE You should start and stop Tomcat logged in as the user who owns the DimINet directory - normally the Tool Manager. If you run these tasks under other users, you may experience errors due to inconsistent file permissions. To start Tomcat: 1 Change directory to: cd <DimINet-Root>/jakarta-tomcat/bin where <DimINet-Root> is the path to your Dimensions I-Net/WebDAV Server installation. 2 Do one of the following: If C shell, enter: % source /<Dimensions Root>/pcmslogin If Bourne shell, enter: $. /<Dimensions-Root>/pcmsprofile where <Dimensions-Root> is the location of the Dimensions 7.2 Server installation. 3 Enter./startup.sh You can now install and access the Dimensions I-Net client in your web browser. See Installing the Dimensions I-Net Client on page 119 for instructions. You can also access Dimensions through a WebDAV client. See the WebDAV Server Implementation Guide for instructions on configuring WebDAV clients. To stop Tomcat: 1 Change directory to: cd <DimINet-Root>/jakarta-tomcat/bin 2 Enter./shutdown.sh

116 116 Chapter 8 Dimensions I-Net and WebDAV Server Installation NOTE When you stop Tomcat, both Dimensions I-Net and WebDAV Server will be unavailable. To run Tomcat from Dimensions command files: To start Tomcat: Uncomment the Tomcat statements in the pcms_startup command file located in $PCMS_ROOT/mmi. To stop Tomcat: Uncomment the Tomcat statements in the pcms_shutdown command file located in $PCMS_ROOT/mmi. Configuring Apache Web Server Perform these tasks to configure the Apache web server to work with both Dimensions I-Net and WebDAV Server: Install a web server adapter. Update the Apache httpd.conf file. Installing a Web Server Adapter Install the web server adapter (mod_jk.<ext>) to enable communication between Apache and Tomcat, where <ext> is the file extension corresponding to your operating system: so for Solaris and Linux. For information on the web server adapter, go to To install the web server adapter: 1 Change directory to: cd <DimINet-Root>/jakarta-tomcat/bin/<os>/<arch>

117 Configuring Apache Web Server 117 where <os> is the directory corresponding to your operating system: solaris or Linux; and <arch> corresponds to the machine architecture: sparc or i Copy the file mod_jk.<ext> to <Apache-Root>/libexec, where <Apache-Root> is the location of the Apache installation, and <ext> is the file extension corresponding to your operating system: so for Solaris and Linux. Updating the Apache httpd.conf File Update the Apache configuration file so Apache can load and initialize the web server adapter, as well as forward specific requests to Dimensions I-Net and WebDAV Server. The httpd.conf-generated file, which is generated during the installation, contains the entry that must be placed in the Apache configuration file. This entry already has the correct path inserted. To modify the httpd.conf file: 1 Log in as root. 2 Open <DimINet-Root>/jakarta-tomcat/conf/jk/ httpd.conf-generated in a text editor. 3 Cut and paste the following line to the end of the http.conf file located in <Apache-Root>/conf, where <Apache-Root> is the location of the Apache installation: include /<DimINet-Root>/jakarta-tomcat/conf/jk/pvcs_apache.conf 4 Save and close the file.

118 118 Chapter 8 Dimensions I-Net and WebDAV Server Installation Configuring iplanet and SunOne Web Servers To configure iplanet 4.x and SunOne 6 to work with both Dimensions I-Net and WebDAV Server, you must update the proper configuration file(s). There are configuration files generated during the installation that contain the entries that must be placed in the iplanet and SunOne configuration files. These entries already have the correct paths inserted. To update the iplanet 4.x configuration: 1 Open <DimINet-Root>/jakarta-tomcat/conf/jk/ obj.conf.iplanet4-generated in a text editor. 2 Follow the instructions in the file and transfer each section to your iplanet obj.conf file in <iplanet-root>/https- <server name>/config, where <iplanet-root> is the location of the iplanet installation and <server name> is the name of the machine running Dimensions I-Net and WebDAV Server. To update the SunOne 6 configuration: 1 In the directory <DimINet-Root>/jakarta-tomcat/conf/ jk, open the files obj.conf.sunone6-generated and magnus.conf.sunone6-generated in a text editor. 2 Follow the instructions in the files and transfer each section to your iplanet obj.conf file and magnus.conf files in <SunOne-Root>/https-<server name>/config, where <SunOne-Root> is the location of the SunOne installation and <server name> is the name of the machine running Dimensions I-Net and WebDAV Server. The entries in magnus.conf.sunone6-generated can be placed at the end of the magnus.conf file.

119 Installing the Dimensions I-Net Client 119 Installing the Dimensions I-Net Client Before you can connect to the Dimensions Server using Dimensions I-Net, you must download and install the Dimensions I-Net client applet. Follow these steps to copy the appropriate files from your server installation to each UNIX machine from which you wish to use Dimensions I-Net Client. To install the Dimensions I-Net client: 1 Log on as the user who originally installed Netscape Navigator. Since the Netscape installation is often shared, it may have been installed by a user with root access. 2 Change to the Client directory: cd <DimINet-Root>/client 3 Run the script: unix_client_inst <Nav-Root> where <Nav-Root> is the location where you installed Netscape Navigator. If the MOZILLA_HOME environment variable is set and points to the Netscape installation directory, then the <Nav-Root> parameter may be omitted. 4 Shut down and restart your browser. To start Dimensions I-Net client: 1 Start your web browser. 2 Open the URL of Dimensions I-Net. The URL of this page is where hostname is the name of the system hosting the Dimensions I-Net server and port is the web server port number. For further details on using the Dimensions I-Net client, please refer to the PVCS Dimensions I-Net User s Guide in conjunction with the Dimensions I-Net Online Help.

120 120 Chapter 8 Dimensions I-Net and WebDAV Server Installation Uninstalling Dimensions I-Net and WebDAV Server You can uninstall Dimensions I-Net and WebDAV Server by removing the installation directory. If you have both Dimensions I-Net and WebDAV Server installed, you must uninstall both components. To uninstall Dimensions I-Net and WebDAV Server: 1 Shut down the Tomcat web server (see Starting and Stopping Dimensions I-Net and WebDAV Server on page 114). 2 Shut down any other web server configured for Dimensions I- Net and WebDAV Server. See the web server s documentation for instructions on stopping the web server. 3 Delete the DimINet directory and its contents. 4 If you ve made any modifications for the web servers, undo those changes: For Apache, delete mod_jk.<ext> from <Apache-Root>/libexec (where <ext> is the file extension corresponding to your operating system: so for Solaris and Linux) and remove the line you added in <Apache-Root>/conf/httpd.conf. For iplanet or SunOne, remove the lines you added in <iplanet-root>/https-<server name>/config/ obj.conf.

121 121 A Guidelines for Estimating the RDBMS Database Size In this Appendix For this section Factors which affect the Size of the RDBMS Database See page 122

122 122 Appendix A Guidelines for Estimating the RDBMS Database Size Factors which affect the Size of the RDBMS Database There are many factors that affect the size of the RDBMS database and calculations of initial and eventual requirements must be made from the methods and practices of the users. Here we can only suggest factors that will have a bearing on the calculation. Each Dimensions base database will be allocated an initial 50Mb, though it may not require or use it all initially. Furthermore, Dimensions base databases can be expected to grow beyond 50Mb after some significant use. Each user registered using the Dimensions Create Dimensions User Database (CUSR) function or its Process Modeler equivalent form will require 500Kbytes of database space. However, a user registered using the Dimensions Register Users (UREG) function or its Process Modeler equivalent form will require negligible database space. Additional disk space will be required for Dimensions operating-system libraries to house items according to size and method of storage (i.e. whether or not delta libraries are being used for items). The number of Dimensions items and the number of revisions of each will generate a requirement that will depend on the number of states in the lifecycle and the quantity of information stored in the attributes of each revision. If the data stored is 10K per item revision, then 1,500 items with an average of five items will generate a database requirement of 75 + Mb (10K x 1500 x 5). NOTE The sizes of the items themselves are not relevant for the database size calculation, as items are held externally as operating system files.

123 Factors which affect the Size of the RDBMS Database 123 Change documents are held in the database and therefore there is a direct correlation between the eventual size (in characters) of the change documents and the database requirement. The number of states in the lifecycle, the number of attributes and the size of attribute values will also have a cumulative effect. The use of Dimensions Make, lifecycle images, items and change document templates must also be considered when calculating database size. It is highly recommended that you use the Dimensions SPAC command to keep regular track of space usage.

124 124 Appendix A Guidelines for Estimating the RDBMS Database Size

125 125 B Floating License Management In this Chapter For this section See page Multiple Vendors Using FLEXlm 126 Options File 127 License Administration Tools 128

126 126 Appendix B Floating License Management Multiple Vendors Using FLEXlm The license manager used by Dimensions is called FLEXlm. Where a site has multiple products that use FLEXlm there are a number of configuration options: Case 1: Independent licensing. In this case, Dimensions has its own license file and server processes (lmgrd and sqld). This is the configuration described in Licensing Dimensions Products with FLEXlm on page 90. Case 2: All products use the same license server node(s). In this case, each existing license file will contain: SERVER lines (up to a maximum of three) that are common to all the license files. Its own specific DAEMON, FEATURE and FEATURESET lines. A single combined license files can, therefore, be created by: Taking the SERVER lines from a single existing license file and placing them in the combined license file. Taking the specific DAEMON, FEATURE and FEATURESET lines from each existing license file and placing them in the combined license file. The combined license file can then become the default Dimensions license file $PCMS_ROOT/../license/license.dat. Alternatively, it can be moved to another location if desired (you must then set the PCMS_LICENSE environment variable accordingly) or multiple copies can be located at fixed locations as required by the various software vendors. There will be a single lmgrd process for all the vendors. Case 3: The products use different license server node(s). In this case, separate license files will be required, one for each distinct set of license servers.

127 Options File 127 NOTE Where several software vendors use a common subset of the license server nodes, the technique described in Case 2 above can be used to combine some of the license files. Options File You can customize your use of Dimensions via the daemon options file. This file allows you to reserve licenses for specified users or groups of users, and to allow or disallow use of Dimensions to certain people. RESERVE INCLUDE EXCLUDE GROUP NOLOG ensures that Dimensions will always be available to one or more users or on one or more host computer systems. allows you to specify a list of users who are allowed access to Dimensions. allows you to disallow certain people use of Dimensions. allows the specification of a group of users for use in the other commands. causes messages of the specified type to be filtered out of the daemon's log output. In order to use the daemon options capability, you must create a daemon options file and list its pathname as the fourth field on the DAEMON line for the sqld daemon. A daemon options file consists of lines in the following format: RESERVE number feature {USER HOST DISPLAY GROUP} name INCLUDE feature {USER HOST DISPLAY GROUP} name EXCLUDE feature {USER HOST DISPLAY GROUP} name GROUP name list_of_users NOLOG {IN OUT DENIED QUEUED}

128 128 Appendix B Floating License Management Lines beginning with a hash character ('#') in the options file are ignored, and can be used to comment the entries. For example, the following options file RESERVE 2 PCMS USER lee RESERVE 1 PCMS HOST terry EXCLUDE REPLICATOR HOST joe NOLOG QUEUED would: reserve two copies of PCMS for user lee; reserve one copy of PCMS for anyone on a computer with the hostname terry; not allow any users on the computer with a host name joe to use the feature REPLICATOR; and would cause QUEUED messages to be omitted from the log file. If this data were in file /usr/pvcs/license/local.options, then you would modify the license file DAEMON line as follows: DAEMON sqld./sqld /usr/pvcs/license/local.options License Administration Tools This section describes tools for administering your Dimensions licenses. In the command descriptions that follow, square brackets are placed around optional components of the command.

129 License Administration Tools 129 lmhostid The lmhostid utility reports the host id of a system. Usage is: lmhostid The output of this command looks as follows: lmhostid - Copyright Globetrotter Software, Inc. The FLEXlm host id of this machine is 69021c89 (See also, Host ID for Dimensions Licensing on page 43). lmcheck lmcheck displays the complete status of the license server. Usage is: lmcheck lmstat lmstat allows the user of Dimensions to monitor the status of all network licensing activities. lmstat allows your system administrator to monitor license operations including: which daemons are running users of individual features users of features served by a specific daemon.

130 130 Appendix B Floating License Management Usage is: lmstat -a Display everything -A List all active licenses -c license_file Use "license_file" as license file -f [license_name] List users of licenses -i [feature-name] List info about specified or all feature(s) -s [server_name] Display status of server node(s) -S [DAEMON] List all users of DAEMON s licenses -t value Set connection timeout to "value" lmdown The lmdown utility allows for the shutdown of all license daemons (both lmgrd and all vendor daemons) on all nodes. Usage is: lmdown -c $PCMS_LICENSE/license.dat Your system administrator should protect the execution of lmdown, since shutting down the license servers will cause the loss of licenses. lmremove The lmremove utility allows the system administrator to remove a single user's license from a specified feature. This could be required in the case where the licensed user was running the software on a node that subsequently crashed. This situation will sometimes cause the license to remain unusable. lmremove will allow the license to return to the pool of available licenses.

131 License Administration Tools 131 Usage is: lmremove -c $PCMS_LICENSE/license.dat feature user host display/handle lmremove removes all instances of "user" on node "host" from usage of "feature". "-c file" specifies the file to be used as the license file. The system administrator should protect the execution of lmremove since removing a user's license can be disruptive. The "display" or "handle" can be retrieved by use of lmstat. lmreread The lmreread utility causes the license daemon to re-read the license file and start any new vendor daemons that have been added. In addition, all pre-existing daemons will be signaled to re-read the license file for changes in feature licensing information. Usage is: lmreread -c $PCMS_LICENSE/license.dat NOTE The license file specified as "-c license_file" is the one read by lmreread, not by lmgrd; lmgrd re-reads the file it read originally. Additionally, lmreread cannot be used to change server node names or port numbers. Vendor daemons will not re-read their option files as a result of lmreread. lmcksum The lmcksum utility will perform a checksum on a license file. This is useful to verify any data entry errors for your location. lmcksum will print a line-by-line checksum for the file as well as

132 132 Appendix B Floating License Management an overall file checksum. lmcksum takes the '-k' switch to force the encryption key checksum to be case-sensitive. lmcksum will ignore all fields that do not enter into the encryption key computation; thus the server node name and port number, as well as the daemon pathname and options file names are not checksummed. In addition, lmcksum will treat non-case sensitive fields correctly (in general, lmcksum is not case sensitive). lmcksum takes an optional daemon name; if specified, only license file lines for the selected daemon are used to compute the checksums. By default, lmcksum operates on license.dat in the current directory. Specify '-c license_file' if you want to checksum another license file. Example output is: lmcksum - Copyright Globetrotter Software, Inc. lmcksum : Using license file /license.dat 3: SERVER acme 11a11b2 181: DAEMON sqld 121: FEATURE PCMS sqld permanent C2344AC VENDOR_STRING=A DIST_INFO= : FEATURE REPLICATOR sqld permanent 7 ACDF01FE : (overall file checksum) lmdiag The lmdiag utility allows you to diagnose problems when you cannot check out a license. Usage is: lmdiag [-c license_file] [-n] [feature]

133 License Administration Tools 133 where -c license_file Path to diagnose. -n Run in non-interactive mode, lmdiag will not prompt for any input nor will it give any extended connection diagnostics. feature Diagnose this feature only. If no feature is specified, lmdiag will operate on all features in the license file in your path. lmdiag will first print information about the license, then attempt to check out each license. If the checkout succeeds, lmdiag will indicate this. If the checkout fails, lmdiag will give you the reason for the failure. If the checkout fails because lmdiag cannot connect to the license server, then you have the option of running extended connection diagnostics. These extended diagnostics attempt to connect to each port on the license server node and determine if the port number in the license file is incorrect. lmdiag will indicate each port number that is currently listening, and if it is not an lmgrd process, lmdiag will state this as such. If lmdiag finds the vendor daemon for the feature being tested, then it will indicate the correct port number for the license file to correct the problem. lminstall The lminstall utility is designed primarily for typing in decimal format licenses to generate a readable format license file. Usage is: lminstall You will first be prompted for the name of the output license file. The default is today s date in yyyymmdd.lic format. The file should be moved to the Dimensions default license file directory.

134 134 Appendix B Floating License Management Otherwise, you can use $PCMS_LICENSE to specify the directory where the license files are located. Decimal format input is verified by checksummed-up entry of each line. To finish, type Q on a line by itself or enter two blank lines.

135 135 C UNIX Environment for a Different Character Set and Locale In this Appendix: For section See page Selecting a Suitable Environment 136

136 136 Appendix C UNIX Environment for a Different Character Set and Locale Selecting a Suitable Environment If your platform supports a different character set to US7ASCII with the "C" locale you will need to ensure that a suitable environment is set up for the user. To set up UNIX or Linux for 8-bit working you will require: stty -istrip cs8 -parenb This will permit characters such as åäëöüáéóúàèòù ÅÄËÜÁÉÓÚÀÈÒÙ to be used. For example to setup a user environment in Sweden you will require: If C shell: % setenv NLS_LANG swedish_sweden.we8dec % setenv LANGUAGE swedish_sweden.we8dec % setenv LC_ALL sv If Bourne shell: $ NLS_LANG=swedish_sweden.we8dec; export NLS_LANG $ LANGUAGE=swedish_sweden.we8dec; export LANGUAGE $ LC_ALL=sv; export LC_ALL CAUTION! It is required when creating the Oracle database to specify the character set you wish to use. It cannot be changed later in situ, except by doing a full Oracle system export, re-creating an empty database with the new character set and then performing a full Oracle system import. NOTE If you wish to use a character set that supports the Euro character, for example, WE8ISO8859P15, please refer to the README for important information concerning known issues when using such character sets.

137 137 D Dimensions Symbols In this Chapter For this section See page Introduction 138 User Database Assignment 139 Sending Mail to Dimensions Users 141 Editing Items 143 Editing Change Documents 148 Browsing Items and Change 153 Documents Paging Data 158 Printing Data 159 Deleting Unwanted Files 161 Showing Item Differences 161 Merging Item Revisions 163 Replication 165 Code Page Settings 166 Command Security 167 Secure Users Running User 168 Defined Reports Including SQL*Plus Statements

138 138 Appendix D Dimensions Symbols Introduction The script pcmslogin (C-shell) or pcmsprofile (Bourne-shell) located in directory $PCMS_ROOT sets a number of standard operating-system environment variable assignments and scripts for every user of that particular Dimensions installation. You are, on an all-user or a per-user basis, able to override a particular installation-wide assignment by making alternative local assignments as follows: For all users environments: via a custom pcmslogin or pcmsprofile script located in the directory $PCMS_ROOT/../custom. For your own user environment: via the.login or.profile login file or at the operating-system command prompt. These operating-system environment variables and scripts are generically referred to as Dimensions Symbols. Most Dimensions Symbols are supported on all the operating systems. Dimensions symbols and scripts set working environments or invoke tools in the following areas: User database assignment. Sending mail to Dimensions users. Editing data. Browsing data (usually by invoking an editor in read-only mode). Printing data files. Deleting unwanted files. Showing item differences. Merging item revisions. Replication.

139 User Database Assignment 139 By default Dimensions makes use of standard system tools or provides optional built-in tools. However, it is also possible to specify that third party tools are to be used instead e.g. installed proprietary packages for word-processing or desk-top publishing. This appendix also discusses several Dimensions Symbols that affect the functioning of Dimensions e.g. PCMS_REPORTDB. Some of these variables are only applicable when Dimensions is invoked from the command line. The graphical interfaces may have their own settings that override these, particularly invocations of editors and browsers. User Database Assignment PCMSDB Before invoking Dimensions, you must set the symbol PCMSDB to your user Dimensions database name (and optionally a password if created using /NOSECURE). You will have been notified of the identity of this symbol by when you were created as a Dimensions user by the Tool Manager. The default value is <user> where <user> is the operating-system account from which the pcmslogin /pcmsprofile procedure is executed. Access to databases hosted on remote nodes is controlled through the use of the environment symbol TWO_TASK. If this symbol is set, then Dimensions will connect to the remote database specified; else, it will assume that the database is on the same node that the user is logged on to.

140 140 Appendix D Dimensions Symbols PCMSDB should be set as follows: If C shell: % setenv PCMSDB userdbname/password (1) or % setenv PCMSDB userdbname (2) If Bourne shell: % PCMSDB=userdbname/password; export PCMSDB (1) or % PCMSDB=userdbname; export PCMSDB (2) TWO_TASK should be set as follows: If C shell: % setenv TWO_TASK <ora_service_name> % setenv PCMSDB userdbname/password (1) or % setenv PCMSDB userdbname (2) If Bourne shell: % TWO_TASK=<ora_service_name>; export TWO_TASK % PCMSDB=userdbname/password; export PCMSDB (1) or % PCMSDB=userdbname; export PCMSDB (2) In the above, <ora_service_name> is the Oracle NET8 Service Name; this is normally the same as the Oracle instance identifier <orasid> assigned to Dimensions on the node hosting the database. However, if there are other databases in the network with the same <orasid>, the <ora_service_name> is likely to be different. It can be determined by looking in /etc/tnsnames.ora or /var/opt/oracle/tnsnames.ora (Solaris only). 1. For a plain password. 2. For an encrypted password.

141 Sending Mail to Dimensions Users 141 Sending Mail to Dimensions Users The following UNIX Dimensions symbols are used to control PCMS_MAIL which is used to specify the actual mail tool Dimensions will use. PCMS_MAIL_SCRIPT which is used to specify a shell script that provides an interface to the mail tool specified by PCMS_MAIL. The use of these variables is described below. PCMS_MAIL The value of the PCMS_MAIL symbol specifies the name of the mail tool used to communicate information to users. Many Dimensions commands need to users when certain events have taken place, for example: When Dimensions products are created, the users who are Product Managers are notified via as to how they can start using their products. Whenever an item revision or change document is awaiting the attention of specific Dimensions users, as a result of a change in its lifecycle state, they are notified via to read their pending lists. Some Dimensions commands run batch scripts which on termination will users the outcome of the job. It should be noted that control of procedural time-scales and discipline remain with the project management. While Dimensions does provide report and query facilities to aid the management of a project, it does not chase outstanding actions.

142 142 Appendix D Dimensions Symbols Examples of mail tools include: mail automatic (BDS and HP-UX UNIX) mailx automatic (System V UNIX) mailtool interactive (OpenWindows) Default: UNIX (C shell): setenv PCMS_MAIL /usr/ucb/mail UNIX (Bourne shell): Syntax: PCMS_MAIL= /usr/ucb/mail ; export PCMS_MAIL /usr/ucb/mail -s <subject> -f <filename> <user list> PCMS_MAIL_SCRIPT This Dimensions symbol provides an interface to a user specified mail tool. The information to be ed is contained within the file passed down to the script. It is left to the script to delete the file at the end of processing. Default: UNIX (C shell): setenv PCMS_MAIL_SCRIPT $PCMS_MMI/pcms_mail.csh UNIX (Bourne shell): PCMS_MAIL_SCRIPT=$PCMS_MMI/pcms_mail.sh; \ export PCMS_MAIL_SCRIPT Syntax: $PCMS_MAIL_SCRIPT file -s subject user1 user2...

143 Editing Items 143 Editing Items The Dimensions Edit Item (EDI) function involves the dataprocessing of items while (in effect) they remain in the Dimensions item-library. Whichever editor tool is used, you must ensure that it saves the current file at or before exit, in order to make any alterations effective. Three different options are offered for choosing the editor tool. These options operate at different levels of sophistication to satisfy the complexity of your requirements. The option used depends on which of the Dimensions symbols PCMS_EDT or PCMS_EDT_SCRIPT, if any, is defined, and in the Motif GUI whether or not the built-in editor has been selected. Default Editors Command Line Interface If neither of these edit symbols is defined, the default for all item editing will be: Motif GUI The vi editor. To use the built-in editor, the Process Modeler Object Type Definitions Options Use inline editor when browsing and editing items from within Dimensions Motif Client will have to have been set up to associate the item type concerned with the built-in editor. In addition, the radio button Use Built In Editor in the Motif Client Control Panel Options menu must have been selected. If this is the case, the settings of the above edit symbols are irrelevant.

144 144 Appendix D Dimensions Symbols PCMS_EDT If only the PCMS_EDT symbol is defined, its value is the name of an editor tool that you wish to be invoked for every use of the Dimensions EDI function. You can redefine this symbol at any time, except from within a Dimensions spawned process. Default: UNIX (C shell): setenv PCMS_EDT vi UNIX (Bourne shell): PCMS_EDT= vi ; export PCMS_EDT Syntax: vi <filename> PCMS_EDT_SCRIPT If the PCMS_EDT_SCRIPT symbol is defined, its value is the name of a shell script file. A full specification of this shell script file, which is executed each time the EDI function is used, is given in Shell Script File for Editing Items on page 146. When this option is used, Dimensions ignores any value previously assigned to the PCMS_EDT symbol. Default (Motif Client): UNIX (C-shell): sateens PCMS_EDT_SCRIPT \ $PCMS_ROOT/xm_n/xpcms_edt_script

145 Editing Items 145 UNIX (Bourne-shell): PCMS_EDT_SCRIPT=$PCMS_ROOT/xm_n/xpcms_edt_script; \ export PCMS_EDT_SCRIPT Default (Command Line Interface): PCMS_EDT_SCRIPT is not set up automatically by the Dimensions login script. It needs to be set up manually as follows (but see Caution on page 146): UNIX (C-shell): setenv PCMS_EDT_SCRIPT $PCMS_MMI/pcms_edit_script UNIX (Bourne-shell): PCMS_EDT_SCRIPT=$PCMS_MMI/pcms_edit_script; \ export PCMS_EDT_SCRIPT Notes: 1 The script for Motif Client expects xterm to be in your path. 2 xm_n denotes the version of Motif Client (e.g. x2_7 would be version 2.7). 3 For Motif Client, the script assigned to PCMS_EDT_SCRIPT is also assigned by default to PCMS_CHD_EDT_SCRIPT. Miscellaneous There is, in effect, a fourth option for editing items: this is, instead of using the EDI function, to use the functions EI Extract Item (check out item) and later RI Return Item (check in item). While the item is checked out, you can process it independently in any way.

146 146 Appendix D Dimensions Symbols Shell Script File for Editing Items This enables the choice of an editor tool, and of how it is invoked, to depend on the product-id/item-type/format of the selected item revision. In the following description, the non- Motif Client script is described in further detail. However, it should be noted that exactly the same parameters are passed internally to the Motif Client shell script. A sample shell script file that invokes different editor tools depending on the item's format, is supplied in the directory specified by the UNIX environment variable PCMS_MMI. To use it, the assignment statements are as detailed in the previous section. Please note: both_edt_and_edit_occur as shown. CAUTION! Do not use the exact assignment statement until/unless you are satisfied that this shell script file will meet your requirements for invoking the appropriate editor tools to handle all various items. The actual processing required will vary considerably, according to what your requirements are at each installation of Dimensions. The parameters passed to the command script file are: as $1 as $2 as $3 as $4 as $5 as $6 as $7 <user-filename> I <item-spec> <product-id> <item-type> <format> <filename>

147 Editing Items 147 where <user-filename> The single letter I specifies the name of the (temporary) file which currently holds the item for the purposes of editing it. as the second parameter indicates that this is an item that is being edited. (See Shell Script File for Editing Change Documents on page 150, where the second parameter is the letter C.) <item-spec> comprises <product-id>, <item-type> and <format> <product-id>:<item-id>. <variant>-<item-type>;<revision> are elements of the item specification. For more detail, refer to the related document PVCS Dimensions Command-Line Reference Guide. <filename> specifies the name of the file which holds the item in the item-library. The purpose of the shell script file is to make use of passed parameters in executing the operating-system commands required for invoking the appropriate editor tool. The sample referred to above gives general guidance, but clearly there are limitless possibilities. When the Dimensions EDI function passes control to the shell script file, it surrounds each parameter with a pair of singlequotation/apostrophe (') characters in case the parameter contains embedded blank spaces. So a typical invocation (if the PCMS_EDT_SCRIPT assignment statement is as above) would be:

148 148 Appendix D Dimensions Symbols $PCMS_MMI/pcms_edit_script \ '/usr/smith/fs.h' I \ 'FS:ROUTE CONTROLLER.SRC;1' \ 'FS' 'SRC' 'C' 'fs.h' Editing Change Documents As with item operations, updating the contents of a change document will invoke an editor tool in which these changes can be made. Three different options are offered for choosing the editor tool. These options operate at different levels of sophistication to satisfy the complexity of your requirements. The option used depends on which of the Dimensions symbols PCMS_CHD_EDT or PCMS_CHD_EDT_SCRIPT, if any, is defined, and in the Motif GUI whether or not the built-in editor has been selected. Default Editors Command Line Interface If neither of these edit symbols is defined, the default for all change document editing will be: Motif GUI The vi editor. To use the built-in editor, the Process Modeler Object Type Definitions (Change Doc) Options use inline editor when browsing and editing change documents from within Dimensions Motif Client check box must be set and the radio button Use Built In Editor in the Motif Client Control Panel Options must have been selected. If this is the case, the settings of the above edit symbols is irrelevant.

149 Editing Change Documents 149 PCMS_CHD_EDT If only the PCMS_CHD_EDT symbol is defined, its value is the name of an editor tool that you wish to be invoked whenever a change document is edited. You can redefine this symbol at any time, except from within a Dimensions spawned process. Default: UNIX (C shell): setenv PCMS_CHD_EDT vi UNIX (Bourne shell): PCMS_CHD_EDT= vi ; export PCMS_CHD_EDT Syntax: vi <filename> PCMS_CHD_EDT_SCRIPT If the PCMS_CHD_EDT_SCRIPT symbol is defined, its value is the name of a shell script file. A full specification of this shell script file, which is executed each time a change document is edited, is given in Shell Script File for Editing Change Documents on page 150. When this option is used, Dimensions ignores any value assigned to the PCMS_CHD_EDT symbol. Default (Motif Client): UNIX (C-shell): setenv PCMS_CHD_EDT_SCRIPT \ $PCMS_ROOT/xm_n/xpcms_edt_script

150 150 Appendix D Dimensions Symbols UNIX (Bourne-shell): PCMS_CHD_EDT_SCRIPT=\ $PCMS_ROOT/xm_n/xpcms_edt_script; \ export PCMS_CHD_EDT_SCRIPT Default (Command Line Interface): PCMS_CHD_EDT_SCRIPT is not set up automatically by the Dimensions login script. It needs to be set up manually as follows (but see Caution on page 151): UNIX (C-shell): setenv PCMS_CHD_EDT_SCRIPT \ $PCMS_MMI/pcms_chd_edit_script UNIX (Bourne-shell): PCMS_CHD_EDT_SCRIPT=\ $PCMS_MMI/pcms_chd_edit_script; \ export PCMS_CHD_EDT_SCRIPT Notes: 1 The script for Motif Client expects xterm to be in your path. 2 xm_n denotes the version of Motif Client e.g. x2_7 would be version For Motif Client, the script assigned to PCMS_CHD_EDT_SCRIPT is also assigned by default to PCMS_EDT_SCRIPT. Shell Script File for Editing Change Documents This enables the choice of an editor, and how it is invoked, to depend on the product-id/type of the selected change document. In the following description, the non-motif Client script is described in further detail. However, it should be noted that

151 Editing Change Documents 151 exactly the same parameters are passed internally to the Motif Client shell script. A sample shell script file that invokes different editor tools depending on the change document's type, is supplied in the directory specified by the UNIX environment variable PCMS_MMI. To use it, the assignment statements are as detailed in the previous section. Please note: both_edt_and_edit_occur as shown. CAUTION! Do not use the exact assignment statement until/unless you are satisfied that this command script file will meet your requirements for invoking the appropriate editor tools to handle all various change document types. The actual processing required will vary considerably, according to what your requirements are at each installation of Dimensions. The parameters passed to the command script file are: as $1 as $2 as $3 as $4 as $5 <user-filename> C <chdoc-id> <product-id> <chdoc-type> where <user-filename> specifies the name of the (temporary) file which currently holds the relevant change document data to be edited. Note that on some occasions (such as "Edit Actions Description" for a saved change document) this will start as a zero-length file when control is passed to the editor.

152 152 Appendix D Dimensions Symbols Single letter C as the second parameter indicates that this is change document data that is being edited. When item data is to be edited (see previous section), the second parameter passed to the corresponding shell script file is the letter I. This allows for the possibility that it may be more convenient to set up a single shell script file to choose and invoke the appropriate editor tool for both items and change documents. In this case the symbols PCMS_EDT_SCRIPT and PCMS_CHD_EDT_SCRIPT need to be assigned the same value. <chdoc-id> is the identity of the change document. It has the format: <product-id>_<chdoc-type>_<sequencenumber> <product-id> and <chdoc-type> are elements of the change document specification. The purpose of the shell script file is to make use of passed parameters in executing the operating-system commands required for invoking the appropriate editor tool. The sample referred to above gives general guidance, but clearly there are limitless possibilities. When Dimensions passes control to the shell script file, it surrounds each parameter with a pair of singlequotation/apostrophe (') characters in case the parameter contains embedded blank spaces. So a typical invocation (if the PCMS_CHD_EDT_SCRIPT assignment statement is as above) would be:

153 Browsing Items and Change Documents 153 $PCMS_MMI/pcms_chd_edit_script \ '/usr/smith/act2.txt' C \ 'FS_CR_25' 'FS' 'CR' Browsing Items and Change Documents As well as supporting environment variables for accessing editing tools, Dimensions also supports environment variables for accessing browsing tools. The choice of browse tool is made using the values of Dimensions symbols in an exactly parallel manner to that used to choose the editor tool (see above), as is shown in the following table: Dimensions Symbol for Editor PCMS_EDT PCMS_EDT_SCRIPT PCMS_CHD_EDT PCMS_CHD_EDT_SCRIPT Equivalent Dimensions Symbol for Browse PCMS_BROWSE PCMS_BROWSE_SCRIPT PCMS_CHD_BROWSE PCMS_CHD_BROWSE_SCRIPT The tool used for browsing must always be invoked in a readonly mode, so that you cannot alter the viewed data. Any such alteration would be ineffective because Dimensions gives the tool access only to a temporary copy of the item revision or change document. Default Browsers The default tool used is as described above for editing items or change documents, except that the editor is invoked in readonly mode.

154 154 Appendix D Dimensions Symbols PCMS_BROWSE The default usage for the PCMS_BROWSE symbols works in the same manner as that for the edit symbol PCMS_EDT. PCMS_BROWSE is used only if PCMS_BROWSE_SCRIPT is undefined and the Motif Client built-in editor is not active. Default: UNIX (C shell): setenv PCMS_BROWSE vi -R UNIX (Bourne shell): PCMS_BROWSE= vi -R ; export PCMS_BROWSE Syntax: vi-r <filename> PCMS_BROWSE_SCRIPT If the PCMS_BROWSE_SCRIPT symbol is defined, its value is the name of a shell script file. A full specification of this shell script file is given in Shell Script for Browsing Items on page 155. When this option is used, Dimensions ignores any value previously assigned to the PCMS_BROWSE symbol. Default (Motif Client): UNIX (C-shell): setenv PCMS_BROWSE_SCRIPT \ $PCMS_ROOT/xm_n/xpcms_browse_script UNIX (Bourne-shell): PCMS_BROWSE_SCRIPT=\ $PCMS_ROOT/xm_n/xpcms_browse_script; \ export PCMS_BROWSE_SCRIPT

155 Browsing Items and Change Documents 155 Default (Command Line Interface): PCMS_BROWSE_SCRIPT is not set up automatically by the Dimensions login script. It needs to be set up manually as follows (but see Caution on page 155): UNIX (C-shell): setenv PCMS_BROWSE_SCRIPT \ $PCMS_MMI/pcms_browse_script UNIX (Bourne-shell): PCMS_BROWSE_SCRIPT=$PCMS_MMI/pcms_browse_script; \ export PCMS_BROWSE_SCRIPT Notes: 1 The script for Motif Client expects xterm to be in your path. 2 xm_n denotes the version of Motif Client (e.g. x2_7 would be version 2.7). 3 For Motif Client, the script assigned to PCMS_BROWSE_SCRIPT is also assigned by default to PCMS_CHD_BROWSE_SCRIPT. Shell Script for Browsing Items The parameters passed to the shell script file specified as the value of PCMS_BROWSE_SCRIPT are exactly the same as those passed to the one specified for PCMS_EDT_SCRIPT, and are fully described in Shell Script File for Editing Items on page 146. CAUTION! Do not use the exact assignment statements described until/unless you are satisfied that these shell script files will meet your requirements for invoking the appropriate browse tools to handle all various items. The actual processing required will vary considerably, according to what your requirements are at each installation of Dimensions.

156 156 Appendix D Dimensions Symbols PCMS_CHD_BROWSE The default usage for the PCMS_CHD_BROWSE symbols works in the same manner as that for the edit symbol PCMS_CHD_EDT. PCMS_CHD_BROWSE is used only if PCMS_CHD_BROWSE_SCRIPT is undefined and the Motif Client built-in editor is not active. Default: UNIX (C shell): setenv PCMS_CHD_BROWSE_EDT vi -R UNIX (Bourne shell): PCMS_CHD_BROWSE_EDT= vi -R ; \ export PCMS_CHD_BROWSE_EDT Syntax: vi -R <filename> PCMS_CHD_BROWSE_SCRIPT If the PCMS_CHD_BROWSE_SCRIPT symbol is defined, its value is the name of a shell script file. A full specification of this shell script file is given in Shell Script for Browsing Items on page 155. When this option is used, Dimensions ignores any value previously assigned to the PCMS_CHD_BROWSE symbol. Default (Motif Client): UNIX (C-shell): setenv PCMS_CHD_BROWSE_SCRIPT \ $PCMS_ROOT/xm_n/xpcms_browse_script

157 Browsing Items and Change Documents 157 UNIX (Bourne-shell): PCMS_CHD_BROWSE_SCRIPT=\ $PCMS_ROOT/xm_n/xpcms_browse_script; \ export PCMS_CHD_BROWSE_SCRIPT Default (Command Line Interfaces): PCMS_CHD_BROWSE_SCRIPT is not set up automatically by the Dimensions login script. It needs to be set up manually as follows (but see Caution on page 158): UNIX (C-shell): setenv PCMS_CHD_BROWSE_SCRIPT \ $PCMS_MMI/pcms_chd_browse_script UNIX (Bourne-shell): PCMS_CHD_BROWSE_SCRIPT=\ $PCMS_MMI/pcms_chd_browse_script; \ export PCMS_CHD_BROWSE_SCRIPT Notes: 1 The script for Motif Client expects xterm to be in your path. 2 xm_n denotes the version of Motif Client (e.g. x2_7 would be version 2.7). 3 For Motif Client, the script assigned to PCMS_CHD_BROWSE_SCRIPT is also assigned by default to PCMS_EDT_SCRIPT. Shell Script for Browsing Change Documents The parameters passed to the shell script file specified as the value of PCMS_CHD_BROWSE_SCRIPT are exactly the same as those passed to the one specified for PCMS_CHD_EDT_SCRIPT, and are fully described in Shell Script File for Editing Change Documents on page 150.

158 158 Appendix D Dimensions Symbols CAUTION! Do not use the exact assignment statements above until/unless you are satisfied that these shell script files will meet your requirements for invoking the appropriate browse tools to handle all various change documents. The actual processing required will vary considerably, according to what your requirements are at each installation of Dimensions. Paging Data The MORE environment variable provides an interface to a pager tool allowing files to be viewed page by page or line by line. Examples of Pagers are: more imagetool pageview -image viewer -PostScript viewer Default: UNIX (C shell): setenv MORE more UNIX (Bourne shell): MORE= more ; export MORE Syntax: more <filename>

159 Printing Data 159 Printing Data PCMS_PRINT This Dimensions symbol provides an interface to a print tool. When Dimensions commands require printing of various reports they call this interface. Examples of printer tools include: lpr, pr, printtool, printps and enscript Default: UNIX (C-shell): setenv PCMS_PRINT lpr -p UNIX (Bourne-shell): PCMS_PRINT= lpr -p ; export PCMS_PRINT Syntax: lpr -p <filename> NOTE If you prefer not to have Dimensions automatically print out reports, set the PCMS_PRINT symbol to echo. PCMS_CHD_PRINT This symbol is used to specify a printer tool specifically for change document operations. It is similar to PCMS_PRINT described above.

160 160 Appendix D Dimensions Symbols PCMS_CHD_PRINT_SCRIPT If the PCMS_CHD_PRINT_SCRIPT symbol is defined, its value is the name of a shell script file. A full specification of this shell script file is given in Shell Script for Printing Change Documents on page 160. When this option is used, Dimensions ignores any value previously assigned to the PCMS_CHD_PRINT symbol. Default (Command Line Interface): PCMS_CHD_PRINT_SCRIPT is not set up automatically by the Dimensions login script. It needs to be set up manually as follows (but see Caution on page 160): UNIX (C-shell): setenv PCMS_CHD_PRINT_SCRIPT \ $PCMS_MMI/pcms_chd_print_script UNIX (Bourne-shell): PCMS_CHD_PRINT_SCRIPT=\ $PCMS_MMI/pcms_chd_print_script; \ export PCMS_CHD_PRINT_SCRIPT Shell Script for Printing Change Documents The parameters passed to the shell script file specified as the value of PCMS_CHD_PRINT_SCRIPT are exactly the same as those passed to the one specified for PCMS_CHD_EDT_SCRIPT, and are fully described in Shell Script File for Editing Change Documents on page 150. CAUTION! Do not use the exact assignment statements described until/unless you are satisfied that these shell script files will meet your requirements for invoking the appropriate printer tools to

161 Deleting Unwanted Files 161 handle all various change documents. The actual processing required will vary considerably, according to what your requirements are at each installation of Dimensions. Deleting Unwanted Files For operations within Dimensions in which files are to be deleted, the tool specified by the PCMS_DELETE Dimensions symbol is used. The user can set this for safety reasons so that the files are not deleted but renamed into some suitable directory. Default: UNIX (C-shell): setenv PCMS_DELETE "rm -f" UNIX (Bourne-shell): PCMS_DELETE="rm -f"; export PCMS_DELETE Syntax: rm -f <filename> Showing Item Differences If the PCMS_DIFF symbol is set then it is used by the Dimensions DIFF command to display the differences between two Dimensions items. By default PCMS_DIFF is not set, and Dimensions DIFF will automatically call the script merge_tool_script located in the $PCMS_MMI directory with a DIFF parameter.

162 162 Appendix D Dimensions Symbols If PCMS_DIFF is set, it must be set to call a script that takes the show item difference arguments described below. The Motif Client graphical interface will display the diff <output file> if the symbol XPCMS_NO_DIFF_OUTPUT is not set. Default: NOT SET UNIX Environment C-shell: setenv PCMS_DIFF $PCMS_MMI/merge_tool_script Bourne-shell: PCMS_DIFF=$PCMS_MMI/merge_tool_script; \ export PCMS_DIFF Syntax 1: (Command generated if two items are compared: See also PCMS_MERGE_SCRIPT) $PCMS_MERGE_SCRIPT DIFF <product_id_1> (Specification of item 1 <item_id_1> <variant_1> <item_type_1> <revision_1> ) <product_id_2> (Specification of item 2 <item_id_2> <variant_2> <item_type_2> <revision_2> ) <item_filename_1> (Library filename of item 1) <item_filename_2> (Library filename of item 2) <item_data_file_1> (The text of item 1)

163 Merging Item Revisions 163 <item_data_file_2> (The text of item 2) <merge_output_file> (Output file if interactive tool is used) <listing_output_file> (Output file for batch style tools) Syntax 2: (Command generated if item is compared to user file: See also PCMS_MERGE_SCRIPT) $PCMS_MERGE_SCRIPT DIFF <product_id> (Specification of item <item_id> <variant> <item_type> <revision> ) <filename> (Library filename of item) <item_filename_2> (Library filename of item 2) <item_data_file> (The text of the item) <user_file> <merge_output_file> (User file) (Output file if interactive tool is used) <listing_output_file>(output file for batch style tools) Merging Item Revisions If the PCMS_MERGE_SCRIPT symbol is set then it is used by Dimensions to provide an interface to a merge tool script. This script is for merging two item revisions with a possible common ancestor and producing a newly merged item. By default PCMS_MERGE_SCRIPT is not set, and Dimensions will automatically call the script merge_tool_script located in the $PCMS_MMI directory with a MERGE parameter.

164 164 Appendix D Dimensions Symbols If PCMS_MERGE_SCRIPT is set, it must be set to call a script that takes the merge item revision arguments described below. Default: NOT SET UNIX Environment C-shell: setenv PCMS_DIFF $PCMS_MMI/merge_tool_script Bourne-shell: PCMS_DIFF=$PCMS_MMI/merge_tool_script; \ export PCMS_DIFF Syntax 1: (Common ancestor known): $PCMS_MERGE_SCRIPT MERGE <product_id> (Specification of item <item_id> <variant> <item_type> ) <library_filename> (Library filename) <revision_1> (Revisions to merge <revision_2> ) <merged_revision> (Output revision) <ancestor_revision> <data_file_1> (Common ancestor revision) (Data files for revisions to merge and ancestor <data_file_2> <ancestor_file> ) <merged_file> (Data file to produce containing merged text)

165 Replication 165 Syntax 2: (Common ancestor cannot be found): $PCMS_MERGE_SCRIPT MERGE <product_id> (Specification of item <item_id> <variant> <item_type> ) <library_filename> (Library filename) <revision_1> (Revisions to merge <revision_2> ) <merged_revision> (Output revision) <ancestor_revision>(common ancestor revision) <data_file_1> (Data files for revisions to merge <data_file_2> ) <merged_revision> <merged_file> (Output revision) (Data file to produce containing merged text) Replication For further information regarding replication, please refer to the related document PVCS Dimensions Replicator User s Guide. The following symbols are of importance to Replicator User s Guide. PCMS_REMOTE_FILE_AREA For the master DB site as well as all the subordinate DB sites, you can define the temporary work area that Replicator will use when sending and receiving items by setting the

166 166 Appendix D Dimensions Symbols PCMS_REMOTE_FILE_AREA symbol on each master and subordinate machine. Replicator will not run unless this variable is set. By default, this symbol is set to use /tmp. Code Page Settings PCMS_CODEPAGE PCMS_CODEPAGE specifies the directory that will contain the mapping tables to be used when translating between EBCDIC and ASCII. Pre-supplied tables will be installed here and any userdefined mapping tables need to be placed here also. CAUTION! Extreme caution must be used to ensure that userdefined tables do not overwrite the supplied tables. Example: PCMS_CODEPAGE /usr/pvcs/dimensions7_2/codepages Default: %PCMS_ROOT%/codepages PCMS_EBCDIC_CODEPAGES PCMS_EBCDIC_CODEPAGES defines which code pages are EBCDIC by specifying a list of the EBCDIC code set identifiers. This information is important as translations are only performed when moving items from ASCII environment to EBCDIC (or vice

167 Command Security 167 versa). It is not possible to detect automatically which code pages are EBCDIC or ASCII. Example: PCMS_EBCDIC_CODEPAGES 0037,0500 Default: If no code pages are defined, then they are all assumed to be ASCII. PCMS_DEFAULT_CODEPAGE PCMS_DEFAULT_CODEPAGE specifies a default code page to be used when working with connections for which a code page has not been defined. This effectively defines the code page for the system running the Dimensions data base server. Example: PCMS_DEFAULT_CODEPAGE Default: If not defined, then will be used. Command Security PCMS_FILE_ENCRYPTION One of the new features introduced at Dimensions release 7.0 was that all commands passed between the clients and the database server are encrypted. This enhances Dimensions security for all commands, but especially the new tertiary node login command (AUTH).

168 168 Appendix D Dimensions Symbols In addition to encrypting the commands, it is also possible to encrypt item contents as they are moved around the network. This can be particularly important in high security environments. However, because of the extra processing involved in encrypting/decrypting items, performance can be adversely affected. Therefore the capability to encrypt items during transfer is a configurable option that is set to off (no encryption) by default. Example: PCMS_FILE_ENCRYPTION on Default: PCMS_FILE_ENCRYPTION off Secure Users Running User Defined Reports Including SQL*Plus Statements If the auxiliary files in a Dimensions RUR shell script contain SQL*Plus statements, the script will fail if executed by a standard "secure" Dimensions user. This is because such a user does not have permission to access the internal Dimensions tables, and "connection" to these tables is a pre-requisite for executing SQL*Plus statements. To enable a secure user to run such RUR command scripts the Dimensions Published Views must be installed and the PCMS_REPORTDB symbol must be set to the PCMSDB of a Dimensions report user. For further details, please see PVCS Dimensions Reports Guide, Chapter 4 Setting Up User Defined Reports, section Execution of User Defined Reports Including SQL*Plus by Secure Dimensions Users.

169 169 Index A accessing the payroll demonstration product 104 Apache Web Server configuration 116 installing web server adapter 116 updating httpd.conf 117 B browse data 138 items and change documents 153 built-in editor 143, 148 C CD-1 components 18 CD-4 components I-Net 19 WebDAV 19 character set 33, 136 command script for browsing change documents 157 for browsing items 155 for editing change documents 150 for editing items 146 for printing change documents 160 configuring Apache Web Server 116 iplanet Web Server 118 contacting technical support 13 conventions, typographical 12 D default browser 153 default editor change documents Motif GUI 148 non-motif interfaces 148 items Motif GUI 143 non-motif interfaces 143 deleting unwanted files 138, 161 demo license 75 DFS node 28 Dimensions component binaries I-Net 19 server 18 WebDAV 19 Dimensions I-Net configuring for Apache Web Server 116 configuring for iplanet Web Server 118 installing 112 prerequisites 110 starting 115 stopping 115 uninstalling 120 upgrading 111 Dimensions I-Net client installing 119 starting 119

170 170 Index Dimensions Make on a multi-homed server 98 Dimensions networking 29 dimensions_listener 29 disk utilization 30 documentation set 11 E edit item H hard-copy documentation ordering 13 host requirements CPU and RAM 20 disk space 20 Dimensions 21 Oracle 21 PCMS_DATA tablespace 21 PCMS_RBS tablespace 21 PCMS_TEMP tablespace 21 redo logs 21 SYSTEM tablespace 21 FLEXlm version 24 Motif version 24 network software 23 operating system 22 Oracle software 22 shared memory parameters 23 SQL*Net version 24 swap space 23 httpd.conf 117 I installation default 28 summary of activities 26 installing a default non-interactive new installation 48 installing a standard interactive installation 51 installing Dimensions client installation database location 82 Dimensions directory 82 Dimensions files owner 82 Dimensions group owner 82 install administration components 81 installation media 81 Oracle directory 82 Oracle files owner 82 Oracle SID 83 RDBMS node name 83 service name 83 initiating option 1 73 option 2 74 new or upgrade server installation demo license 75 Dimensions directory 75 Dimensions files owner 75 Dimensions group owner 75 entry level process model 78 install in Oracle database 76 installation media 74 intermediate level process model 78 Oracle directory 76 Oracle SID 76 Oracle SYSTEM Password 77 PCMS_SYS database password 77 remote node name 76 select process model 77 service name 77 overview 70 installing Dimensions I-Net 112

171 Index 171 installing Dimensions I-Net client 119 installing Oracle initiating option 1 57 option 2 57 option 3 57 new client installation without database creation handling error conditions 67 installation media 65 Oracle directory 65 Oracle files owner 66 Oracle group owner 66 new installation with database creation database character set 61 database directory 59 first redo log size 60 handling error conditions 63 installation medium 58 Oracle directory 58 Oracle files owner 59 Oracle group owner 59 Oracle SID 58 PCMS_DATA size 60 proceed with installation 61 second redo log size 60 SYSTEM size 60 overview 54 pre-installation checks 56 installing WebDAV Server 112 iplanet Web Server updating obj.conf 118 item libraries impact changing format definitions 32 L lmcksum 131 lmdiag 132 lmdownh 130 lmhostid 129 lminstall 133 lmremove 130 lmreread 131 lmstat 129 creating the license.dat file 90 DAEMON line 91 demo license 92 Dimensions clients 94 FEATURE line 92 multiple vendors 126 options file 127 SERVER line 91 starting daemon 93 locale 33, 136 logging the installation 48 M memory and swapping 32 merge item revisions 138, 163 MORE 158 mounting Dimensions CD-1 Sun Sparc 47 N Network Administration Tool 29 NFS disk requirement 21 NFS networked disks 31 licensing Dimensions products 89 FLEXlm administration tools lmcheck 129

172 172 Index O online manuals ordering hard-copy manuals 13 optimizing Dimensions performance 29 ora_service_name 140 ordering hard-copy documentation 13 P paging data 158 payroll product 104 PCMS_BROWSE 154 PCMS_BROWSE_SCRIPT 154 PCMS_CHD_BROWSE 156 PCMS_CHD_BROWSE_SCRIPT 156 PCMS_CHD_EDT 149 PCMS_CHD_EDT_SCRIPT 149 PCMS_CHD_PRINT 159 PCMS_CHD_PRINT_SCRIPT 160 pcms_clientshutdown 97 pcms_clientstartup 96 PCMS_CODEPAGE 166 PCMS_DEFAULT_CODEPAGE 167 PCMS_DELETE 161 PCMS_DIFF 161 PCMS_EBCDIC_CODEPAGES 166 PCMS_EDT 144 PCMS_EDT_SCRIPT 144 PCMS_FILE_ENCRYPTION 167 PCMS_MAIL 141 PCMS_MAIL_SCRIPT 142 PCMS_MERGE_SCRIPT 161, 163 PCMS_MMI 146, 151 PCMS_PRINT 159 PCMS_REMOTE_FILE_AREA 165 pcms_reply.txt 28 PCMS_REPORTDB 168 pcms_shutdown 95 pcms_startup 95 PCMSDB 139 pcmslogin 94 pcmsprofile 95 port number, for Tomcat 113 post-installation access to Dimensions files 97 Dimensions command files pcms_clientshutdown 97 pcms_clientstartup 96 pcms_shutdown 95 pcms_startup 95 pcmslogin 94 pcmsprofile 95 Dimensions Make on a multi-homed server 98 FLEXlm licensing 90 creating the license.dat file 90 DAEMON line 91 demo license 92 Dimensions clients 94 FEATURE line 92 SERVER line 91 starting daemon 93 licensing Dimensions products 89 re-booting Oracle and Dimensions 99 setting up access to Dimensions 86 standalone process model installer 101 pre-installation changing default init.ora file 42 configuring kernel for shared memory and semaphores 41 creating operating system user accounts pcms and oracle 37 deciding which process model to install 36 existing user reuse of own generic process model 45 FLEXlm license details 44 general checks upgradable versions 56 identifying host-id for license request 43 operating system patches 40 pre-requisites for installing Dimensions separately from Oracle 45

173 Index 173 reinstalling Dimensions 7.2 on Solaris or Linux 43 prerequisites Dimensions I-Net 110 WebDAV Server 110 print data 138, 159 printed manuals ordering 13 process model entry level 36 intermediate level 36 other 36 R RDBMS size factors 122 re-booting Oracle and Dimensions 99 S secure Dimensions users RUR including SQL*Plus statements 168 sending mail 138, 141 set up environment command script for browsing change documents 157 for browsing items 155 for editing change documents 150 for editing items 146 for printing change documents 160 MORE 158 ora_service_name 140 PCMS_BROWSE 154 PCMS_BROWSE_SCRIPT 154 PCMS_CHD_BROWSE 156 PCMS_CHD_BROWSE_SCRIPT 156 PCMS_CHD_EDT 149 PCMS_CHD_EDT_SCRIPT 149 PCMS_CHD_PRINT 159 PCMS_CHD_PRINT_SCRIPT 160 PCMS_CODEPAGE 166 PCMS_DEFAULT_CODEPAGE 167 PCMS_DELETE 161 PCMS_DIFF 161 PCMS_EBCDIC_CODEPAGES 166 PCMS_EDT 144 PCMS_EDT_SCRIPT 144 PCMS_FILE_ENCRYPTION 167 PCMS_MAIL 141 PCMS_MAIL_SCRIPT 142 PCMS_MERGE_SCRIPT 161, 163 PCMS_MMI 146, 151 PCMS_PRINT 159 PCMS_REMOTE_FILE_AREA 165 PCMS_REPORTDB 168 PCMSDB 139 TWO_TASK 139 XPCMS_NO_DIFF_OUTPUT 162, 164 setting up access to Dimensions 86 sever node 28 show item differences 138, 161 standalone process model installer 101 starting Dimensions I-Net client 119 starting the installation 48 SupportNet Online 14 T technical support contacting 13 contacting by 14 contacting by fax 15 contacting by mail 16 Tomcat description 114 port number 113 starting and stopping 114 TWO_TASK 139 typographical conventions 12

174 174 Index U upgrading Dimensions I-Net 111 WebDAV Server 111 using your own Oracle software 22 V very large file restriction 33 W web server adapter 116 web servers configuring Apache 116 configuring iplanet 118 WebDAV Server components 109 configuring for Apache Web Server 116 configuring for iplanet Web Server 118 installing 112 prerequisites 110 starting 115 stopping 115 uninstalling 120 upgrading 111 X XPCMS_NO_DIFF_OUTPUT 162, 164