|
by Steve Hughes
Before you utilize the full potential, power, and design tools of Designer/2000, you must install the product. Because Designer/2000 is a client/server product, you need to perform some tasks on the client (often an IBM PC or compatible) and perform
server-specific tasks on the server (possibly a Windows NT server, a Dec Alpha, or other platform supporting Oracle).
One of the most popular platforms on which to run the client side of Designer/2000 is Microsoft Windows. In this chapter, you'll learn how to install Designer/2000 for Microsoft Windows. As of this writing, Designer/2000 is at release 1.1. Enhancements
over release 1.0 include remarkable increases in speed, some taming of previous "untamed enhancements" (some people call them bugs), and minor enhancements to the software.
The following table indicates where components of Designer/2000 reside.
Client
|
Server
|
|
Repository Administrator
|
Remote database
|
|
Forms Generator
|
Designer/2000 Repository
|
|
Process Modeller
|
Application Program Interface
|
|
Report Generator
|
|
|
Server Generator
|
|
|
System Designer
|
|
|
System Modeller
|
|
For Designer/2000 to execute properly, certain minimum system requirements must be met. The following list explains the minimum system requirements for the client and server side of Designer/2000 version 1.1. Remember, these are the minimum
requirements. Often, when manufacturers state the minimum requirements they state the base minimum for the product to function. And even though the product will function under the minimum requirements, additional horsepower, such as a speedy hard disk,
additional processing power (Pentium-level processor), plenty of RAM, and a finely tuned Oracle server will make the software run much more efficiently.
For the client side of your installation, the following is a list of the minimum requirements:
- IBM PC, or 100 percent compatible, with at least 486/25 processing power.
- CD-ROM drive that can be assigned to a logical drive letter, often D: or E:.
- Available disk space of 350 MB if all options are installed, 300 MB for a typical installation. Also, at least 40 MB of swap space. (Use a permanent swap file when you allocate this space.)
- RAM requirements: a hefty 16 MB available, with a recommendation of 32.
 Acquire as much RAM as possible; try to match or better the 32 MB. Additional RAM, especially above the 16MB minimum, will gain the most increase in performance within Designer/2000, with the exception of
installing a faster processor.
- At least 400 KB of conventional RAM (memory below 640 KB) available before starting Windows.
- Microsoft Windows, version 3.1, or higher, in enhanced mode.
Although Designer/2000 has not been specifically engineered for Windows 95, it seems to run well under the new operating system.
- MS-DOS, version 5.0 or greater.
- SQL*Net, version 1.1 or 2.0 for Windows, both of which are supplied on the Designer/2000 CD-ROM. If you are planning to use SQL*Plus, it must be version 3.1.3.5.5 or 3.1.3.7.2C; the latest version will be included on the Designer/2000 CD-ROM.
On the server side of the installation, the following list is a list of minimum requirements:
- Oracle 7 Server, with the procedural option installed. Ask your Oracle database administrator (DBA) if all procedural option packages have been installed on the server.
- A minimum of 35 MB in the system tablespace is needed for the repository PL/SQL packages, procedures, and views that comprise Designer/2000.
Remember, 35 MB is the minimum. In actuality, if sufficient disk space is available, allocate at least 65 MB of additional space to the SYSTEM tablespace. Also, try to make sure the available SYSTEM tablespace is
fairly contiguous.
- If you plan to utilize the legacy driven approach to information systems, using the reverse engineering tools, you must configure the Oracle server with distributed options.
Although the Designer/2000 product has been tested thoroughly by Oracle, as well as numerous current users of Designer/2000, always protect your current system be performing a complete backup of your machine. During the installation process, entries
will be made to your WIN.INI file. The installation process might include coordination with your DBA to ensure all data on the Oracle server has also been backed up. If any problems occur after the installation, you will be able to return your system to
its original state before the installation if you have backed it up.
Which Oracle CASE product you have already installed on your client impacts how you begin to install Designer/2000. The following scenarios will help you determine which steps to perform to upgrade to Designer/2000.
Here, a functional Oracle CASE version 5.1 resides on the client PC. To upgrade to Designer/2000, remove CASE 5.1 from the client PC, and proceed to Client Installation. On the server side, you will need to upgrade the repository.
A previous, early version of Designer/2000 resides on the client. To upgrade to the current release of Designer/2000, uninstall the old version and proceed to Client Installation. On the server side, you will need to upgrade the server repository.
Although a previous version of Designer/2000 exists on the client, you will not have to uninstall it before upgrading to the latest release of Designer/2000. Proceed to Client Installation, which will overwrite the current version of Designer/2000. On
the server side, you will need to upgrade the server repository.
To install the client side of Designer/2000, a Windows-based product developed by Oracle called Oracle Installer is utilized. This installation program is located on the CD-ROM and performs the following steps during installation of Designer/2000:
- Creates the Oracle home directory (usually ORAWIN), and appropriate subdirectories.
- Copies installation-specific files to the appropriate subdirectory.
- Creates a Designer/2000 program group.
- Installs selected components of Designer/2000.
- Installs Designer/2000, on-line documentation, and appropriate icons within the Designer/2000 program group.
Before you start Oracle Installer, make sure that no other Windows tasks are currently running.
 When you make sure that no other Windows tasks are currently running, you also should disable all screen savers and incoming/outgoing fax management software because the installation process can be a
time-consuming process that should not be interrupted once it is initiated.
Once Windows is running, insert the CD-ROM into the available CD-ROM drive.
In the following examples, [CD-ROM Drive Letter] refers to the drive letter associated with your CD-ROM drive. This is often drive D: or E:. Substitute the proper drive letter whenever you encounter [CD-ROM Drive
Letter].
With the CD-ROM properly inserted in the CD-ROM driver, start the installation process by selecting File | Run from the Windows Program Manager. When prompted to enter the command line to execute, enter the following:
[CD-Rom Drive Letter]:INSTALLORAINST.EXE
Alternatively, you can use the Windows File Manager to view the contents of the CD-ROM and execute the preceding program.
The remaining steps of installing the Designer/2000 client portion are numbered in the order they should be processed.
- After the installation loads into memory and performs a few initialization steps, the first screen of the Oracle Installer will appear. This window enables you to select the language to be used during the installation process (see Figure 23.1).
Figure 23.1. The Language selection menu.
- Next, you will be prompted for some license information, as well as the Oracle Home directory. Enter the name of your company, and move to the Oracle Home directory field. Change the value displayed or accept the default, C:ORAWIN (see Figure 23.2).
Figure 23.2. License information and the Oracle Home directory.
 Take a minute to jot down the Oracle Home directory because it is a very important piece of information. This location is where all information concerning Designer/2000 and all subsequent Oracle Products are
installed.
- If the Oracle Home directory, specified in the previous step, is not part of your PATH statement, the Oracle Installer will ask you if your AUTOEXEC.BAT file should be modified to include the Oracle Home path. Unless you intend on adding the path
yourself, let Oracle Installer add Oracle Home to your PATH statement in the AUTOEXEC.BAT file by selecting the Yes button (see Figure 23.3).
If you select Yes in step 3, you will need to reboot your computer before the changes will take effect.
Figure 23.3. The Oracle Installer asking if the Oracle Home subdirectory should be added to the PATH statement in your AUTOEXEC.BAT.
- Designer/2000 can be installed one of three ways. Each method of installation requires different amounts of disk space, and takes more or less installation time, depending on the number of components selected to install (see Figure
23.4).
Figure 23.4. The three methods of installing Designer/2000.
As the name implies, a complete install will install all components of Designer/2000, including the option to install SQL*Net products. The Oracle Installer is pretty smart. If the user has an older version of SQL*Net, it will ask if he wants to
upgrade. Also, a custom install or complete install asks about SQL*Net. To perform a complete installation, select Complete Install. The following lists the components for a Complete Install.
- SQL*Net installation. Select the version of SQL*Net you plan to run by selecting the appropriate version (see Figure 23.5). If you do not make a selection for SQL*Net at this point, you can install SQL*Net later by performing a custom
installation/deinstallation.
Figure 23.5. Available SQL*Net options that can be installed during a custom installation.
- If you chose to install SQL*Net in step 1, you will then be presented with a list of SQL*Net products to install (see Figure 23.6). Select the proper SQL*Net option.
Figure 23.6. List of available SQL*Net products available for installation.
- The actual install process will begin after you select OK. If you have a previous version of Designer/2000, you might be prompted on whether to rename the old files (previous versions of a new file), or simply overwrite them. Always select the option
to rename the previous files if sufficient disk space is available. See Figure 23.7, which appears right before the installation process begins.
Figure 23.7. The Oracle Installer screen before the actual Designer/2000 installation begins.
- Certain Oracle files, called executables, are stored in a special area, as defined by [Oracle Home]BIN. Each additional component of Designer/2000 should have its own specific subdirectory. This enables patches and upgrades to be implemented more
easily. You will next be prompted to enter the location where the common Designer/2000 files should reside (see Figure 23.8).
Figure 23.8. Prompt for the location of the Designer/2000 files.
- Because Oracle applications being developed in Designer/2000 can take advantage of OLE2, some of your Windows system files might need to be updated. You will be prompted as to whether or not you want Oracle Installer to update these files (see Figure
23.9). You should not encounter any problems when you upgrade to newer versions of these files. Select Yes to continue.
 You cannot remove these files by using the Deinstall utility. Once they are installed, you will have to manually remove them.
Figure 23.9. The prompt denoting additional system support files might be required.
- Your next prompt is for the location of SQL*Plus (see Figure 23.10). This is where the SQL*Plus files, and future versions of SQL*Plus, will reside. Change the value displayed, or accept the default.
Figure 23.10. The prompt for the location of the SQL*Plus files.
- The next prompt will determine where the Developer/2000 Forms runtime files are to be located (see Figure 23.11). Change the value displayed, or accept the default.
Figure 23.11. The prompt for the location of the Developer/2000 Forms runtime files.
- In this step, you will resolve the location of the Developer/2000 Reports runtime files (see Figure 23.12). Change the value displayed, or accept the default.
Figure 23.12. The prompt for the location of the Developer/2000 Reports runtime files.
- Next, define the location of the Designer/2000 Repository Administrator files (see Figure 23.13). Change the value displayed, or accept the default.
Figure 23.13. Select the location of the Designer/2000 Repository Administrator files.
- A single client should be assigned to initiate and configure the Oracle Repository on the Oracle server (see Figure 23.14). If this client PC is going to be designated as such, select Yes. Make the appropriate selection, and continue.
If the client is selected, an additional 10 MB of disk space will be needed for additional files.
Figure 23.14. The selection menu for determining if this client is assigned to configure the Oracle Repository on the Oracle server.
- Next, specify where the Designer/2000 Systems Designer files will reside (see Figure 23.15). Change the value displayed, or accept the default
Figure 23.15. Selection for the destination of the Designer/2000 Systems Designer files.
- After step 11, you are asked where the Designer/2000 Reports Generator files should dwell (see Figure 23.16). Change the value displayed, or accept the default.
Figure 23.16. Selection for the location of the Designer/2000 Reports Generator files.
- Next, you determine the location of the Designer/2000 Server Generator files (see Figure 23.17). Change the value displayed, or accept the default.
Figure 23.17. The location of the Designer/2000 Server Generator files.
- Subsequently, the Oracle Installer prompts you for the location of the Designer/2000 Forms Generator files (see Figure 23.18). Change the value displayed, or accept the default.
Figure 23.18. The prompt for the location of the Designer/2000 Forms Generator files.
- In the next-to-last prompt for the location of a Designer/2000 component, define the location of the Designer/2000 Process Modeller files (see Figure 23.19). Change the value displayed, or accept the default.
Figure 23.19. The location of the Designer/2000 Process Modeller files.
- The final prompt defines the location of the Designer/2000 Systems Modeller files (see Figure 23.20). Change the value displayed, or accept the default.
Figure 23.20. The location of the Designer/2000 Systems Modeller files.
- Oracle Installer will now show you all the products you have selected for installation (see Figure 23.21). All of the selected components will now be copied to their selected destination.
Figure 23.21. Version information associated with each component selected for installation.
Take a minute to write down the information displayed, especially the version numbers associated with each component. If you ever need to call Oracle support, they will need this information in order to serve you
better and assist you with any problems you might encounter.
- Oracle Installer now lists any additional files it has determined it needs to install (see Figure 23.22). Once again, take a minute and record this information for future reference. Once you have captured this information, continue the installation
process.
Figure 23.22. Additional files Oracle Installer has determined it needs to install.
Oracle Installer will now compute the disk space requirements and make sure sufficient space is available on the destination drive. After space requirements have been met, the actual components will be copied to the destination drive. Oracle Installer
will display a progress indicator and update the progress while files are being copied. Once the progress indicator reaches 100 percent, the installation of Designer/2000 for the client is complete. Proceed to the section titled "Server
Installation" to complete the necessary steps on the Designer/2000 server.
When installing Designer/2000, most sites select default installation. The main difference between a custom installation (described previously) and a default installation is your ability to change the location of the Designer/2000 files. This process
copies a default configuration, complete with default file locations. The following are the steps involved:
- SQL*Net installation. Select the version of SQL*Net you plan to run by selecting the appropriate version (refer to Figure 23.6). If you do not make a selection for SQL*Net now, you can install SQL*Net later by performing a custom
installation/deinstallation.
- If you chose to install SQL*Net in step 1, you will be presented with a list of SQL*Net products to install (refer to Figure 23.7). Select the proper SQL*Net option.
- Because Oracle applications being developed in Designer/2000 can take advantage of OLE2, some of your Windows system files might need to be updated. You will be prompted as to whether or not you want Oracle Installer to update these files (refer to
Figure 23.8). You should not encounter any problems when you upgrade to newer versions of these files. Select Yes to continue.
You cannot remove these files by using the Deinstall utility. Once they are installed, you will have to manually remove them.
- Oracle Installer will now show you all the products you have selected for installation (refer to Figure 23.22). All of the selected components will now be copied to their selected destination.
Take a minute to write down the information displayed, especially the version numbers associated with each component. If you ever need to call Oracle support, they will need this information in order to serve you
better and assist you with any problems you might encounter.
- Any additional files Oracle Installer has determined need to be installed will now be listed (refer to Figure 23.23). Once again, take a minute and record this information for future reference.
Oracle Installer will now compute the disk space requirements and make sure sufficient space is available on the destination drive. After space requirements have been met, the actual components will be copied to the destination drive. Oracle Installer
will display a progress indicator and update the progress while files are being copied. Once the progress indicator reaches 100 percent, the installation of Designer/2000 for the client is complete. Please proceed to the section titled "Server
Installation" to complete the necessary steps on the Designer/2000 server.
During a complete install, you can install or deinstall a list of selectable Designer/2000 components. A window to the left indicates components that can be installed, and a window on the right indicates components of Designer/2000 that can be
deinstalled.
Installing Designer/2000 on a client is a fairly simple process. Using the Oracle Installer is an intuitive process; it automatically determines which components of Designer/2000 are dependent upon others and gathers necessary information quickly and
easily.
Once you have installed the client portion of Designer/2000, a series of steps are necessary to set up the server side of Designer/2000. The series of steps performed in this section must be performed by an Oracle DBA who has specific privileges to the
system areas of your Oracle server.
Designer/2000 needs the Oracle Server procedural option to be installed. Your DBA can do this by executing the CATPROC script.
During this setup process, you will create additional tablespaces on your Oracle server and allocate space to these tablespaces. You will also create a repository owner, who is granted special Oracle system privileges needed by Designer/2000. You will
also confirm that your Oracle server meets the minimum requirements in several areas, including SYSTEM tablespace, SGA shared pool size, and other parameters. The following are the steps involved:
- Start the server process by creating a new tablespace and an accompanying tablespace for the Designer/2000 indexes.
Do not install the Designer/2000 tables in the SYSTEM tablespace. Designer/2000 enables you to specify another tablespace, so please do. Keep your SYSTEM tablespace as clean and clutter free as possible.
It is recommended that the tablespace be called DES2, and the tablespace for the indexes be called DES2_I. The size of these tablespaces should be 13 MB and 11 MB, respectively. As the Oracle DBA, don't forget to assign quota limits (or an unlimited
quota) to these newly created tablespaces.
- Large rollback segments are a necessity for proper use of Designer/2000. Although most rollback segments within an Oracle installation are often the same size, you might need to increase their size if you are receiving errors because of the size of
insufficient rollback segments. Designer 2000 does not commit the changes made to the Oracle instance frequently, so it requires large rollback segments. These large rollback segments are only needed during the installation of Designer/2000. Once it's
successfully installed, you can alter the size of the rollback segments.
You can create a very large, single rollback segment. Take all other rollback segments offline, and the installation process will be forced to use the large rollback segment. Once successfully installed, you can
drop the large rollback segment and return your system to its normal state.
- In addition to adding data in the previously created DES and DES_I tablespaces, the installation process will add data to the SYSTEM tablespace. Designer/2000 will need a minimum of 35 MB of additional space in the SYSTEM tablespace. Although this is
the minimum, experience has shown that typically about 60 MB of space is needed. If possible, the space available should be as contiguous as possible. Fragmentation within the SYSTEM tablespace can lead to extremely poor performance.
- Create a repository owner/user for the installation process. Define the DES tablespace as the default and temporary tablespace. Also, allow this user an unlimited quota on DES and DES_I tablespaces. You will need to assign special system privileges to
this user. These are as follows:
CREATE SESSION
ALTER SESSION
CREATE TABLE
CREATE VIEW
CREATE SEQUENCE
CREATE PROCEDURE
CREATE TRIGGER
CREATE CLUSTER
CREATE SYNONYM
CREATE ANY SYNONYM
DROP ANY SYNONYM
CREATE DATABASE LINK
CREATE ROLE
CREATE SNAPSHOT
- Create a role, possibly called DES2000_OWNER, that contains the privileges listed in step 4. A script is available for performing these actions, and is located in [Oracle home]REPADM10UTL. This SQL script, CKROROLE.SQL, can be run from the SYS (not
the SYSTEM) account. Once the role has been created, the DBA can assign the created role to the owner.
Some parameters within the Oracle server INIT.ORA file might need modification. The parameters that might need to be modified, and their minimum values (or required values) are
Parameter Minimum/Proper Setting
shared_pool_size 18000000
db_block_buffers 1000
open_cursors 200
processes 20
global_names False
- Remember, these are minimum settings. If your Oracle instance contains larger values than those references here, no changes are necessary. If changes are made to any of the preceding parameters, you must shut down your Oracle database, and then
restart your database for the new parameters to take effect.
- During the installation process, the Import utility is needed. For the Import utility to function properly, your ORACLE.INI must contain a LOCAL parameter setting. This specifies which Oracle server and database to connect to. The connect string, if a
TCP/IP connection is being used, might resemble the following:
LOCAL=t:server:database
where server is the name of the Oracle server, and database is the name of the database to which to connect. Use an ASCII text editor to add this LOCAL parameter to your ORACLE.INI file.
- You are now ready to start the Repository Administration Utility and install a new repository instance. From Windows, open the Designer/2000 program group if it is not already open. Start the process by double-clicking the Repository Administration
Utility. A connection prompt will appear, asking for a user name and password. These were set up by your DBA, probably as OWNER1. Enter the information, and select Connect to continue.
- Select the proper tablespaces where the Designer/2000 repository information will reside. Your DBA has probably defined these tablespaces as DES for the table tablespace, and DES_I for the indexes tablespace.
- To make sure enough system resources are available and the proper system privileges have assigned, select the Pre-Check button to ensure an error-free installation.
The installation process can often take several hours to complete. Always run the Pre-Check process to ensure the proper steps have been completed before the Designer/2000 repository has been installed.
- Begin the long installation process by selecting Execute. Be patient during the installation process. At two separate times during the install, the Import function will be summoned. After each import of data, you will be required to close the import
message box once the import is complete. Simply select Close once it becomes available for selection.
Move the mouse occasionally because the mouse icon is not properly updated from an hour glass to a normal mouse pointer once the import utility has completed its task.
Remember, the process might take some time to complete, based on the quickness with which your server can process information. Don't be alarmed if the process seems to have locked up your computer. Give the process at least six to seven hours to process
before concluding that the computer has locked. Before rebooting the client, contact your DBA, and ask if any activity is being performed on the server. If activity is detected, do not reboot—things are still running.
Once the installation processes have completed, the Designer/2000 is ready for use.
The installation process is a somewhat lengthy process. If at all possible, you might want to schedule the installation for a weekend. Also, don't forget to have complete backups of both the client and server data before you install Designer/2000.
|
