Installation Guide. Sybase PowerDesigner Windows

Transcription

1 Installation Guide Sybase PowerDesigner 12.5 Windows

2 Part number: DC Last modified: April 2007 Copyright Sybase, Inc. and its subsidiaries. All rights reserved. Information in this manual may change without notice and does not represent a commitment on the part of Sybase, Inc. and its subsidiaries. Sybase, Inc. provides the software described in this manual under a Sybase License Agreement. The software may be used only in accordance with the terms of the agreement. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc. and its subsidiaries. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS for the DOD and as set forth in FAR (a)-(d) for civilian agencies. Sybase, SYBASE (logo), ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture, Adaptive Server, Adaptive Server Anywhere, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, Adaptive Server Enterprise Replication, Adaptive Server Everywhere, Advantage Database Server, Afaria, Answers Anywhere, AppModeler, APT Workbench, APT-Build, APT-Edit, APT-Execute, APT-Translator, APT-Library, ASEP, Avaki, Avaki (Arrow Design), Avaki Data Grid, AvantGo, Backup Server, BayCam, Bit-Wise, BizTracker, Certified PowerBuilder Developer, Certified SYBASE Professional, Certified SYBASE Professional Logo, ClearConnect, Client-Library, Client Services, CodeBank, Column Design, ComponentPack, Connection Manager, Convoy/DM, Copernicus, CSP, Data Pipeline, Data Workbench, DataArchitect, Database Analyzer, DataExpress, DataServer, DataWindow, DataWindow.NET, DB-Library, dbqueue, Dejima, Dejima Direct, Developers Workbench, DirectConnect Anywhere, DirectConnect, Distribution Director, Dynamic Mobility Model, e-adk, E-Anywhere, e-biz Integrator, E-Whatever, EC Gateway, ECMAP, ECRTP, efulfillment Accelerator, EII Plus, Electronic Case Management, Embedded SQL, EMS, Enterprise Application Studio, Enterprise Client/Server, Enterprise Connect, Enterprise Data Studio, Enterprise Manager, Enterprise Portal (logo), Enterprise SQL Server Manager, Enterprise Work Architecture, Enterprise Work Designer, Enterprise Work Modeler, eprocurement Accelerator, eremote, Everything Works Better When Everything Works Together, EWA, ExtendedAssist, Extended Systems, ExtendedView, Financial Fusion, Financial Fusion (and design), Financial Fusion Server, Formula One, Fusion Powered e-finance, Fusion Powered Financial Destinations, Fusion Powered STP, Gateway Manager, GeoPoint, GlobalFIX, ianywhere, ianywhere Solutions, ImpactNow, Industry Warehouse Studio, InfoMaker, Information Anywhere, Information Everywhere, InformationConnect, InphoMatch, InstaHelp, Intelligent Self-Care, InternetBuilder, iremote, iscript, Jaguar CTS, jconnect for JDBC, KnowledgeBase, Logical Memory Manager, lrlite, M2M Anywhere, Mach Desktop, Mail Anywhere Studio, Mainframe Connect, Maintenance Express, Manage Anywhere Studio, MAP, M-Business Anywhere, M-Business Channel, M-Business Network, M-Business Suite, MDI Access Server, MDI Database Gateway, media.splash, Message Anywhere Server, MetaWorks, MethodSet, mfolio, Mirror Activator, ML Query, MobiCATS, Mobil 365, Mobileway, MySupport, Net-Gateway, Net-Library, New Era of Networks, Next Generation Learning, Next Generation Learning Studio, O DEVICE, OASiS, OASiS logo, ObjectConnect, ObjectCycle, OmniConnect, OmniQ, OmniSQL Access Module, OmniSQL Toolkit, OneBridge, Open Biz, Open Business Interchange, Open Client, Open ClientConnect, Open Client/Server, Open Client/Server Interfaces, Open Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++, Partnerships that Work, PB-Gen, PC APT Execute, PC DB-Net, PC Net Library, Pharma Anywhere, PhysicalArchitect, Pocket PowerBuilder, PocketBuilder, Power++, Power Through Knowledge, power.stop, PowerAMC, PowerBuilder, PowerBuilder Foundation Class Library, PowerDesigner, PowerDimensions, PowerDynamo, Powering the New Economy, PowerScript, PowerSite, PowerSocket, Powersoft, PowerStage, PowerStudio, PowerTips, Powersoft Portfolio, Powersoft Professional, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst, Pylon, Pylon Anywhere, Pylon Application Server, Pylon Conduit, Pylon PIM Server, Pylon Pro, QAnywhere, Rapport, Relational Beans, RepConnector, Report Workbench, Report-Execute, Replication Agent, Replication Driver, Replication Server, Replication Server Manager, Replication Toolkit, Resource Manager, RFID Anywhere, RW-DisplayLib, RW-Library, SAFE, SAFE/PRO, Sales Anywhere, Search Anywhere, SDF, Search Anywhere, Secure SQL Server, Secure SQL Toolset, Security Guardian, ShareSpool, Sharelink SKILS, smart.partners, smart.parts, smart.script, SOA Anywhere Trademark,SQL Advantage, SQL Anywhere, SQL Anywhere Studio, SQL Code Checker, SQL Debug, SQL Edit, SQL Edit/TPU, SQL Everywhere, SQL Modeler, SQL Remote, SQL Server, SQL Server Manager, SQL SMART, SQL Toolset, SQL Server/CFT, SQL Server/DBM, SQL Server SNMP SubAgent, SQL Station, SQLJ, Stage III Engineering, Startup.Com, STEP, SupportNow, S.W.I.F.T. Message Format Libraries, Sybase 365, Sybase Central, Sybase Client/Server Interfaces, Sybase Development Framework, Sybase Financial Server, Sybase Gateways, Sybase IQ, Sybase Learning Connection, Sybase MPP, SyberLearning LIVE, Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase Synergy Program, Sybase Virtual Server Architecture, Sybase User Workbench, SybaseWare, Syber Financial, SyberAssist, SybFlex, SybMD, SyBooks, System 10, System 11, System XI (logo), SystemTools, Tabular Data Stream, The Enterprise Client/Server Company, The Extensible Software Platform, The Future Is Wide Open, The Learning Connection, The Model For Client/Server Solutions, The Online Information Center, The Power of One, TotalFix, TradeForce, Transact-SQL, Translation Toolkit, Turning Imagination Into Reality, UltraLite, UltraLite.NET, UNIBOM, Unilib, Uninull, Unisep, Unistring, URK Runtime Kit for UniCode, Unwired Accelerator, Unwired Orchestrator,Viafone, Viewer, VisualWriter, VQL, WarehouseArchitect, Warehouse Control Center, Warehouse Studio, Warehouse WORKS, Watcom, Watcom SQL, Watcom SQL Server, Web Deployment Kit, Web.PB, Web.SQL, WebSights, WebViewer, WorkGroup SQL Server, XA-Library, XA-Server, XcelleNet, XP Server, XTNDConnect, and XTNDACCESS are trademarks of Sybase, Inc. or its subsidiaries. All other trademarks are the property of their respective owners. ii

3 Contents About This Manual v 1 Installing PowerDesigner 1 Installation Options Installing PowerDesigner in Standalone Mode Setting up a License Server Installing PowerDesigner in Administrative Mode Installing PowerDesigner in Silent Mode Installing the Repository 25 Repository Installation Options Installing SQL Anywhere Installing the Repository Proxy Index 41 iii

4 iv

5 About This Manual Subject This book describes the installation procedures for: All modules in the PowerDesigner product line Sybase SQL Anywhere client and authenticated server to use with the PowerDesigner repository. If you already have SQL Anywhere, install of current version is not mandatory The PowerDesigner repository proxy Audience This book assumes that you are an experienced Windows user. PowerDesigner modules The combination of modules installed differs for each product in the PowerDesigner line. The example used in this installation guide is for a given combination, however, the installation process is the same for all PowerDesigner products. v

6 vi

7 CHAPTER 1 Installing PowerDesigner About this chapter This chapter describes how to install PowerDesigner. Contents Topic: page Installation Options 2 Installing PowerDesigner in Standalone Mode 4 Setting up a License Server 13 Installing PowerDesigner in Administrative Mode 19 Installing PowerDesigner in Silent Mode 22 1

8 Installation Options Installation Options This section explains the system requirements and various install options of PowerDesigner. PowerDesigner has the following minimum system requirements: Microsoft Windows XP, Microsoft Windows Server 2003, or Microsoft Windows Vista Pentium 500 MHz 256 MB RAM SVGA or higher-resolution graphics adapter and compatible color monitor (800x600) CD-ROM drive Up to 500MB for installation of all the core modules that make up the Studio Enterprise Edition. You can choose among the following installation modes: Standalone mode - is the typical install scenario, where PowerDesigner is installed directly on each client machine (see Installing PowerDesigner in Standalone Mode on page 4). Administrative mode - installs PowerDesigner for use from a network machine (see Installing PowerDesigner in Administrative Mode on page 19). Silent mode allows you to deploy PowerDesigner on a large number of machines, using exactly the same setup options (see Installing PowerDesigner in Silent Mode on page 22). Depending on which version of PowerDesigner you have purchased, you will be able to install one or more of the following modules: Requirements Model (RQM) Business Process Model (BPM) Conceptual Data Model (CDM) Physical Data Model (PDM) Information Liquidity Model (ILM) 2

9 Chapter 1. Installing PowerDesigner Object-Oriented Model (OOM) XML Model (XSM) Repository Free Model (provided with all PowerDesigner configurations) Reports (provided with all PowerDesigner configurations) In addition to the standalone version, you can also install PowerDesigner plug-ins for use in the Eclipse and Visual Studio 2005 IDEs. 3

10 Installing PowerDesigner in Standalone Mode Installing PowerDesigner in Standalone Mode Standalone mode is the standard method for installing PowerDesigner on one or more individual workstations. For mass installations and network installation, see Installing PowerDesigner in Silent Mode on page 22 and Installing PowerDesigner in Administrative Mode on page 19. Non-Administrators Non-Administrator users may receive a warning message during installation. Setup requires write access on certain directories and on the registry that a non-administrator user may not have. Setup can go on despite this message. To install PowerDesigner in standalone mode 1. Insert the PowerDesigner CD-ROM in your drive. If setup does not automatically start, then double-click the SETUP.EXE file in the setup directory of the CD-ROM. 2. Click the Install PowerDesigner 12.5 button to open the welcome page, and then click Next to go to the license selection page: 3. Select one of the following license types, and then click Next to go to the license agreement page. Trial version is a full-featured version, valid for an evaluation period of 15 days, that allows you to perform any design task. Contact Sybase if you require a limited extension. 4

11 Chapter 1. Installing PowerDesigner Local standalone license is installed on and locked to a particular machine. Click next to go to the license key page, where you must load a valid license file (see Obtaining a license key file on page 10). Served standalone license is provided by one or more SySAM license servers, and is locked to a particular machine. Click Next to go to the license server page, where you must enter the name of your license server. Served floating license is provided by one or more SySAM license servers, which manage the allocation and recuperation of licenses 5

12 Installing PowerDesigner in Standalone Mode among a pool of users. Click Next to go to the license server page, where you must enter the name of your license server. For more information about PowerDesigner licensing, see the Managing PowerDesigner Licenses chapter in the General Features Guide. 4. [for served licenses] Click Next to go to the package selection page, where you can select which package to install. The list displays all the packages that are available on the server but it does not necessarily reflect the availability of a license for a particular package: 5. Click Next to go to the License Agreement page. Select the location where you are installing the software, read the License Agreement, and then click the I Agree radio button to accept the terms of the agreement. If you click I Do Not Agree, you cannot proceed with the Setup program and you have to cancel install. Printing the License Agreement You can print the License Agreement from the Setup\Licenses directory on the product CD. 6. Click Next to go to the directory selection page, where setup suggests a directory in which to install PowerDesigner files. You can specify an alternate directory by clicking the Browse button. For major versions, this directory is different from the directories for previous major versions of PowerDesigner. We recommend that you do 6

13 Chapter 1. Installing PowerDesigner not install a new major version of PowerDesigner in a directory that holds a previous version. 7. Click Next to go to the component selection page, which lists the products and features that are available to install. Each node can be expanded in order to let you select or deselect sub-features: 8. Select or clear check boxes to add or remove products or features and click Next. If you have Microsoft Visual Studio 2005 and Team Foundation installed 7

14 Installing PowerDesigner in Standalone Mode on your computer, you can select the Visual Studio 2005 plug-in and its feature Team Foundation for installation. Modify install When modifying an install, if you deselect a check box, the feature will be removed (see Uninstalling PowerDesigner and Installation Maintenance on page 11). If you selected the Eclipse 3 plug-in in the list of components, the Eclipse directory selection page is displayed. Click the Browse button to specify a directory containing a valid Eclipse 3.1 or higher installation. Upgrading the Eclipse plugin If you had manually installed the Eclipse plug-in in PowerDesigner version 10 or 11 and want to upgrade to version 12.x you have to remove the plug-in manually. To do so, open the Eclipse directory, and remove any PowerDesigner-related folder under the \configuration, \features, and \workspace\.metadata\.plugins folders. 9. Click Next to go to the Program Folders page. You can select the default folder, or select or create another: 8

15 Chapter 1. Installing PowerDesigner 10. Click Next to go to the Current Settings page, which lists all your selections. Select the Keep PowerDesigner Settings check box to retain any settings from a previous version of PowerDesigner. 11. Click Next to begin the install. Setup begins copying files to the destination directory. 12. Wait for the setup complete page to appear and click Finish. Depending on your working environment, Setup may ask you to reboot your machine. 9

16 Installing PowerDesigner in Standalone Mode Obtaining a license key file Readme.html The Readme.html file contains important release information. You can open it using a text editor from the /PowerDesigner directory by default. You must have a license key file to install PowerDesigner. License files can be downloaded on the Sybase Product Download Center site (SPDC) at When you purchase PowerDesigner from Sybase, you receive an with an URL, your login, and your password for the SPDC. When you purchase PowerDesigner from a Sybase reseller, you receive a certificate with a Web key registration number and a download URL. Host ID Before accessing the download site, make sure you know your license configuration, the host ID and the name of the computer that will receive the license key file. You can find the host ID and the computer name in the Installation program, these details are automatically calculated and displayed in the third page of the installation where you are asked to load or copy a license file to proceed. For Windows platforms, if your machine does not have a network adapter an alternate Hostid of type Disk Serial Number is supported. To get this host id, use the lmutil lmhostid -vsn command or get the disk s volume serial number by executing DIR C:, remove - from the value and prefix DISK_SERIAL_NUM= to the serial number to get the host id. Each host ID type has valid formats that will be checked when generating a license. Make sure the value entered matches these valid formats. Ethernet addresses are 12 character hex values consisting of digits 0 through 9 and characters A through F. They may be entered in any of the following formats: 12AB34CD56EF 12-AB-34-CD-56-EF 12:AB:34:CD:56:EF Host Ids are 8 character hex values consisting of digits 0 through 9 and characters A through F. They may be entered in the following formats: 12AB34CD 12AB-34CD 10

17 Chapter 1. Installing PowerDesigner Manual fonts installation Note: For some platforms, host IDs can also be entered in decimal formats, in this case prefix the host id with a # sign. Example: # Disk Serial Number is always entered with a DISK_SERIAL_NUM= prefix. For example: DISK_SERIAL_NUM=3e2e17fd If setup fails to define default fonts, you can do it manually. You should perform the following modifications: 1. Select the Fonts page in the General Options dialog box and define fonts for UI, Code and RTF Editor. 2. Create a new report, select Report Change Font and define new fonts. 3. Verify that the following registry key does not exist: HKEY_CURRENT_USER\Software\Sybase\PowerDesigner 12\DisplayPreferences\Font Name. 4. Create a registry key named Font Name (with the following string values: Name, Size, Style) for all symbols in the following registry key: HKEY_LOCAL_MACHINE\Software\Sybase\PowerDesigner 12\DisplayPreferences\Font Name. Uninstalling PowerDesigner and Installation Maintenance After installing PowerDesigner on your machine, you access installation maintenance when you select Control Panel Add/Remove Programs or when you restart installation. The maintenance dialog box does not let you modify the type of license installed on your machine, you can only use it to add or remove components in the current PowerDesigner installation. 11

18 Installing PowerDesigner in Standalone Mode This mode allows you to perform the following: Modify the current installation in order to remove or add program features on your current install. Select or clear components in the components page. Repair the current installation. This option allows you to reinstall the same PowerDesigner configuration as previously installed on your machine. You need to have the software CD or access to the network drive where installation files are copied to repair your current installation. Remove the current installation and clean up your registry. You do not need the software CD or access to the network drive in this case. Note that user files are not removed. 12

19 Chapter 1. Installing PowerDesigner Setting up a License Server You need a license server when you have selected to install a standalone served or a floating served license. The license server allows you to share and control licenses within a pool of users. The license server controls license availability and allows you to use licenses as needed; in floating mobile mode the server also allows you to borrow and return licenses. The license server also blocks use when all licenses are being used. However, it is possible to exceed the total number of purchased licenses by a 10% overdraft. This is to let your organization operate temporarily out of compliance in order to maintain day to day operations while obtaining new licenses and also to help you measure the new licenses needed to achieve compliance. The license server program is available on the PowerDesigner CD-ROM. License server and PowerDesigner application Do not install a license server and PowerDesigner on the same workstation. Served licenses limitation If you are using a standalone served or a mobile floating license and you work disconnected from the server, and if your workstation hosts other products that also use Flexlm served licenses, you may have problems for returning your license to the server. Installing a license server Prerequisites Diagnostic programs If a Flexlm license server (SYSAM) is already installed, PowerDesigner license server will be installed on the same server, otherwise a PowerDesigner license server is installed. A Flexlm license server installed with PowerDesigner version 11 does not have the same service name as a server for version 12.x and cannot read version 12.x license files. If you no longer use the version 11 license server, we recommend that you remove it. You need a license file to install the license server (see Obtaining a license key file on page 10). For more information about SySAM, see Lmutil.exe and lmtools.exe located in the \\SYSAM-2_0\Bin folder are programs provided to help you diagnose problems you may encounter when installing the Flexlm license server. 13

20 Setting up a License Server For example, the following command can be used to find the user(s) who have currently borrowed the license(s): lmutil lmstat -a -c <port>@<host> where <port> and <host> are license server information. For more information about Flexlm and additional examples of these programs, see sybase.help.doc.ase_15.0.flexnet/html/title.htm. To install a license server 1. Click the Install Licenses Server button to open the Sybase Software Asset Management for PowerDesigner wizard: 2. Click Next to display the license agreement page. Read the License Agreement and click the I Agree radio button to accept the terms of the agreement. If you click I Do Not Agree, the installation will be cancelled. 3. Click Next to display the license file definition page. 4. Click the Load button if you already have a license file and browse to the folder where your license file is located. The content of the license file is automatically displayed in the License key box. or Download a license file from SPDC and copy the file content into the License Key box. 14

21 Chapter 1. Installing PowerDesigner 5. Click Next. The destination folder page is displayed if no other Flexlm license server (SYSAM) is detected. If another Flexlm license server exists on the current machine, the destination folder page is skipped. 6. Click Next to accept the suggested destination folder. or Click Browse, select a different destination folder, and click Next. 15

22 Setting up a License Server The start copying files page is displayed: 7. Click Next to accept the current settings and start copying files. The copy starts. A progress box is displayed and Setup copies files to the destination directory. The InstallShield Wizard Complete page is displayed. If no other Flexlm server existed on the current machine you can choose to start the license server as a service. 16

23 Chapter 1. Installing PowerDesigner If the PowerDesigner license server was installed on an existing license server, you can choose to reread licenses in order to refresh the server license file. 8. Click Finish. Managing the license server You can manage the license server from a specific interface. To manage the license server 1. Double-click lmtools.exe in the \\SYSAM-2_0\Bin folder. The LMTOOLS dialog box is displayed to let you manage Flexlm servers. 2. Select SYSAM in the list of servers to configure using services. 3. Click the Start/Stop/Reread tab to display the Flexlm licenses Services installed on the server machine. 4. Click the Reread License File button to force the server to read again the file sybpdes.lic and update license number. 5. Select File Exit to close the LMTOOLS dialog box. 6. Start PowerDesigner. For more information about SySAM, you can look at the following Web address For more information about Flexlm, you can look at the following Web address help.doc.ase_15.0.flexnet/html/title.htm. 17

24 Setting up a License Server Using SAMreport Sybase.opt SAMreport is a report generator that helps you report the usage of licenses on the server. SAMreport produces license usage reports based on license usage activity recorded in the FLEXnet report logs and on selected criteria including product and feature name, user, date and time, display or host. The SAMreport install program and the Flexnet Licensing End User Guide documentation are provided on the PowerDesigner CD under the \samreport folder. To use SAMreport, make sure you create a file sybase.opt in the server license file folder. This file should contain a line for accessing the report log: REPORTLOG [+] report_log_path 18

25 Chapter 1. Installing PowerDesigner Installing PowerDesigner in Administrative Mode System administrators can install PowerDesigner on a server and have client machines run the application from this central install. The client machines do not install any files but their registry is modified in order to be able to access PowerDesigner from the specified location. With this type of administrative mode install, there is only one instance of PowerDesigner to deploy and upgrade. You can install any type of PowerDesigner license and specify any combination of installation options on each client machine. Creating the administrative install on the server The first part of the administrative install consists in copying the PowerDesigner files to a server. You are not required to enter any product key or select any feature to install. All PowerDesigner setup files are decompressed and copied to the server, but the server registry and system files will not be affected. To copy the files to the server 1. Insert the CD-ROM in the drive to automatically launch the setup program. The initial setup dialog box is displayed. Click the Administrative Installation button. or Select Start Run, type the PowerDesigner setup.exe path followed by /a in the Run dialog box and click OK. The welcome page is displayed: 19

26 Installing PowerDesigner in Administrative Mode 2. Click Next to display the network location page: 3. Specify the network location where you want to copy the product files, and then click Install. The setup status page displays a progress box while the files are copied to the destination directory. When this process is complete, the Complete page opens. 4. Click Finish to exit the InstallShield Wizard. 20

27 Chapter 1. Installing PowerDesigner Installing client machines Once you have created the administrative install on the server, you can set up the client machines. The client install modifies the registry of the client machine in order to be able to reference the files located on the server, but does not copy any file onto the client machine. Consequently no space is required on the client machine. To install a client machine 1. On the client machine, open Windows Explorer, connect to the network location where you have created the administrative install and double-click the Setup.exe file. The welcome page is displayed. Upgrading an administrative install 2. Click Next to open the license selection page, select a license type, and then click Next again. 3. Define the appropriate installation parameters on the following pages, and then click Finish to begin the install. Depending on your working environment, Setup may ask you to reboot your machine. For detailed information about license types and other setup parameters, see Installing PowerDesigner in Standalone Mode on page 4. If you want to pass the administrative install command to an upgrade package downloaded from the web, you have to use the following syntax: <name of the executable file.exe> -a <argument> pdupgrade.exe -a /a Where -a is used to specify that command </a> is targeted to the executable file within the downloaded package pdupgrade.exe. 21

28 Installing PowerDesigner in Silent Mode Installing PowerDesigner in Silent Mode Installation log If you need to deploy PowerDesigner on a large number of machines and wish to reuse exactly the same setup options and destination folder for each machine, you can use the silent install mode. Silent install runs without user input, by using a response file (called setup.iss) that specifies all the required installation options. The silent installation mode does not provide any information about the installation itself. You can open the setup.log file in the directory containing the setup.exe file to have a report about the silent install. The last section of this file called ResponseResult contains a line ResultCode=X, which indicates whether the installation is successful. If X=0, installation was successful. CD or network location You can perform a silent install from the product CD or from a network location where the PowerDesigner installation files have been copied. To perform silent installs 1. To create a setup.iss response file, select Start Run to open the Windows Run dialog box and enter the following command: <PD-inst-dir>\setup\setup.exe /r /f1 <path>\setup.iss Complete the installation parameters as required and then click Finish to create the setup.iss file at <path>. For example, the following: G:\setup\setup.exe /r /f1"setup.iss" References a network drive G:, mapped to a location where the PowerDesigner files have been copied, and creates setup.iss in the setup directory for easy access. 1. Proceed to install the client machine with the following command: <PD-inst-dir>\setup\setup.exe /s /f1 <path>\setup.iss. Each new silent install will replace the content of the setup.log file located in the Installation drive. Use the /f2 parameter to define a local directory where the setup.log file will be stored on each client machine: G:\setup\setup.exe /s /f2 c:\temp\setup.log 22

29 Chapter 1. Installing PowerDesigner Silent installation of administrative mode From a client machine, map a drive to the server where the PowerDesigner files are copied. The drive letter must be the same as that on the server. For example, if your PowerDesigner files are located on drive R:\admin\setup.- exe, you must use the R drive on each client machine to access installation files. Uninstalling PowerDesigner in Silent mode A silent uninstall works in a similar fashion to the silent install, but requires that you locate the InstallShield PowerDesigner maintenance file. For PowerDesigner v12.x this file is located, by default, at: C:\Program Files\InstallShield Installation Information\ {DA53ABD DA-A6DD-287A48F74D37}\setup.exe Locating non-standard InstallShield maintenance files It may be that your maintenance file is not found in the standard location. You can always retrieve its location file from the following registry key: HKEY_LOCAL_- MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DA53ABD DA-A6DD-287A48F74D37} To perform silent uninstalls 1. To create an uninstall.iss response file, select Start Run to open the Windows Run dialog box to invoke the installshield maintenance file with the following options: <path-to>\setup.exe /r /f1 <path>\uninstall.iss Complete the installation parameters as required and then click Finish to create the uninstall.iss file at <path>. For example, the following: C:\Program Files\InstallShield Installation Information\ setup.exe /r /f1"c:\temp\uninstall.iss" Uses the standard maintenance file, and creates uninstall.iss in a temp directory. 1. Proceed to uninstall the client machine with the following command: <path-to>\setup.exe /s /f1 <path>\uninstall.iss 23

30

31 CHAPTER 2 Installing the Repository About this chapter This chapter explains how to set up the PowerDesigner repository server and client, and also the optional repository proxy. Contents Topic: page Repository Installation Options 26 Installing SQL Anywhere 27 Installing the Repository Proxy 35 25

32 Repository Installation Options Repository Installation Options The PowerDesigner repository can be used to store your PowerDesigner models and other files relating to your design projects. An authenticated copy of Sybase SQL Anywhere is provided with the PowerDesigner repository module for use as the repository database server. This chapter provides instructions on installing SQL Anywhere, along with the repository proxy. Alternatively, you can host a repository database (with, or without the proxy) using any of the following supported databases via an ODBC connection: Oracle 7 and higher IBM DB2 Common Server and DB2 for OS/390 Sybase Adaptive Server Enterprise Sybase SQL Anywhere Informix 2000 Microsoft SQL Server 7 and higher In addition, the following databases are supported via a native connection: Oracle 7 and higher Microsoft SQL Server 2000 and higher For information about setting up a repository, see the Getting Started with the Repository chapter in Working with the Repository. 26

33 Chapter 2. Installing the Repository Installing SQL Anywhere The PowerDesigner repository is delivered with an authenticated version of Sybase SQL Anywhere, which can only be used to store your PowerDesigner model repository. PowerDesigner Trial version The trial version of PowerDesigner is supplied with a lighter version of SQL Anywhere, for which the setup may be slightly different. Installing SQL Anywhere on your repository server To install the SQL Anywhere authenticated server 1. Insert the software CD-ROM in the drive, and click the Install SQL Anywhere button. Choose your setup language, and then click Next to open the SQL Anywhere InstallShield wizard 2. Click Next to go to the License Agreement page. Select your country or region, review and accept the license terms, and then click Next to go to the Choose Location page. 3. Accept the default install location or select one using the Browse button, and then click Next to go to the Choose Samples Location page. 4. Accept the default install location or select one using the Browse button, and then click Next to go to the Select Components page: 27

34 Installing SQL Anywhere 5. Accept the default components, and click Next to go to the Server License page: 6. Enter your total number of PowerDesigner licenses in the Licensed Units field, verify that the Networked Seat (per-seat) model radio button is selected, and then click Next to go to the Select Program Folder page. 7. Accept the default or enter a new folder name, and click Next to go to the Start Copying Files page, which summarizes your installation option choices: 28

35 Chapter 2. Installing the Repository Authenticating databases 8. Click Next to start the install. A status bar is displayed showing progress. 9. When the installation of the main program files is complete, you will be invited to install documentation. Accept the default options and click Next to continue. 10. When the documentation installation is complete, the Setup Complete page opens, inviting you to view the ReadMe and online resources. Make your choices and then click Finish to open the InstallShield Wizard Complete page. 11. Select the Yes radio button and click Finish to restart your computer and complete the installation. For information about setting up a repository, see the Getting Started with the Repository chapter in Working with the Repository. Authenticate any new database Authenticate existing database You must create a database to store the repository tables in the server. When you install the authenticated version of SQL Anywhere, existing databases and new databases cannot be used with the authenticated server because these databases are not authenticated. You have to perform the following actions to be able to use a database with the authenticated server. If you want to automatically authenticate any new database, you have to copy the contents of the script authdb.sql delivered with the repository under \Tools, into the file saopts.sql under \Script in the SQL Anywhere directory, on the server machine. The authentication string included in this file will let you use any new database with the repository as soon as you create it. When you install the authenticated version of SQL Anywhere, you cannot use existing databases with the repository since they are not authenticated. However, you can authenticate these databases by executing the script authdb.sql delivered with the repository under \Tools. This will let you use the repository with any existing database. To execute the authdb.sql script on an existing database 1. Start Interactive SQL (dbisql.exe). 2. Type dba in the User ID box. 3. Type sql in the Password box. 29

36 Installing SQL Anywhere Creating a database 4. Enter the data source name in the ODBC Data Source Name box. 5. Select the Database tab and click the Browse button. 6. Double-click the existing database in the file selection window, the file path should appear in the Database File box. 7. Click OK. The Interactive SQL window is displayed. 8. Open the script authdb.sql and execute it. 9. Close Interactive SQL. This should stop the server. Your database is now authenticated and you can start it to use it with the repository. The following procedure explains how to create a database for the repository on your repository server. 30

37 Chapter 2. Installing the Repository To create a database using Sybase SQL Anywhere 1. Navigate to the SQL Anywhere 10 program group and open Sybase Central or run the SCJVIEW.EXE executable in the Sybase Central directory. 2. In the Sybase Central window right-hand Plug-ins tab, double-click the SQL Anywhere 10 item to access its tools and features: 3. Click on the Tools button, and select Create Database from the list to open the Create Database Wizard. 4. Click Next to go to the Select a Location page. The Create a database on this computer is automatically selected. Click Next to go to the Specify a Database File page: 31

38 Installing SQL Anywhere 5. Click Next to go to the Specify the Transaction Log File page: 6. Make sure the check box Maintain the Following Transaction Log File is selected, accept or specify an alternate log file name and location, and then click Next. 7. Continue clicking Next and accepting the default settings until you arrive at the Specify DBA User and Password page: 32

39 Chapter 2. Installing the Repository 8. By default, the database is created with a super-user called DBA, and with a password sql. Select these defaults or provide your own parameters (being sure to remember them for later), and then click Next to go to the Connect to the Database page. 9. Click Finish to create the database. A message box displays the progress and informs you when the creation is complete. Installing the SQL Anywhere client on client machines You must install the SQL Anywhere client on all machines that will access the repository database on the server. To install the SQL Anywhere client 1. Insert the software CD-ROM in the drive, and click the Install SQL Anywhere button. 2. Click Next to go to the License Agreement page. Select your country or region, review and accept the license terms, and then click Next to go to the Choose Location page. 3. Accept the default install location or select one using the Browse button, and then click Next to go to the Choose Samples Location page. 4. Accept the default install location or select one using the Browse button, and then click Next to go to the Select Components page: 33

40 Installing SQL Anywhere 5. Deselect all components except Network Database Client (inside SQL Anywhere), and then click Next to go to the Select Program Folder page. 6. Accept the default or enter a new folder name, and click Next to go to the Start Copying Files page, which summarizes your installation option choices. 7. Click Next to start the install. A status bar is displayed showing progress. 8. When the installation is complete, the Setup Complete page opens, inviting you to view the ReadMe and online resources. Make your choices and then click Finish to open the InstallShield Wizard Complete page. 9. Select the Yes radio button and click Finish to restart your computer and complete the installation. For information about connecting to a repository, see the Getting Started with the Repository chapter in Working with the Repository. 34

41 Chapter 2. Installing the Repository Installing the Repository Proxy The Repository is as a client-server application, in which the Client issues SQL statements via an ODBC connection to be executed on the database server. While such a system provides acceptable performance on a Local Area Network (LAN), it may be less effective on a Wide Area Network (WAN). SQL statements require several network packets, each of which must go back and forth before the next one is issued. While a LAN connection typically has a ping time of less than 10ms; a WAN connection (passing through the Internet via a Virtual Private Network (VPN) connection) has a typical ping of over 100ms. The PowerDesigner repository proxy is intended to run on either the repository server (if it is a Windows machine) or on the same LAN. Clients connect to it from elsewhere in the WAN using a dedicated protocol, and it can pool client requests, and provides a metadata cache, all of which reduce network communication and improve client response times. Before you set up the repository proxy, you must install the repository (see Installing SQL Anywhere on page 27). Next you should choose whether to install the repository proxy on the repository server, or on another windows machine on the same LAN, and then accomplish the following steps: Creating an ODBC system data source on the proxy server on page 35 on the proxy server Installing the repository proxy on the proxy server on page 36 Configuring the repository proxy on page 39 After installation is complete, you can set up client machines to connect to the repository via the proxy. See the Getting Started with the Repository chapter in Working with the Repository. Creating an ODBC system data source on the proxy server The ODBC data source defines the connection between the proxy and the repository database. You must create a system (and not a user) data source for the proxy to communicate with the repository. 35

42 Installing the Repository Proxy To define a system data source 1. Select Start Settings Control Panel Administrative Tools Data Sources (ODBC) to open the ODBC Data Source Administrator window. 2. Click the System DSN tab, and then click the Add button. 3. Select the driver corresponding to your DBMS. 4. Click Finish. The configuration box is displayed. Generally, you will have to declare the data source name together with the name of the server where the database is installed. You may also be prompted to type the name of the user that will connect to the database and a password. 5. Test the connection if applicable and then save the new DSN by clicking OK to return to the System DSN page, where your new data source is displayed in the list. 6. Click OK to close the ODBC Data Source Administrator window. Installing the repository proxy on the proxy server The repository administrator is generally responsible for installing the repository proxy. We recommend that you install the repository proxy on the same computer as the database or at least on the same LAN. 36

43 Chapter 2. Installing the Repository To install the repository proxy 1. Insert the PowerDesigner software CD-ROM in the drive, and then click the Install PowerDesigner Repository Proxy button. The Repository Proxy installation program opens to the Welcome page. 2. Click Next to go to the license agreement page, and select the location where you are installing the software. Read the License Agreement and click the I Agree radio button to accept the terms of the agreement. If you click I Do Not Agree, you cannot proceed with the Setup program and you will have to cancel the install. Printing the License Agreement You can print the License Agreement from the Setup\Licenses directory on the product CD. 3. Click Next to go to the directory selection page. Setup suggests a location in which to install the Proxy, which you can change by clicking the Browse button. 37

44 Installing the Repository Proxy 4. Click Next to go to the Current Settings page which shows your choices: 5. Click Next to accept the current settings and start copying files. The copy starts. A progress box is displayed and Setup copies files to the destination directory. When the setup is complete, the following page appears with two checkboxes selected by default, to let you start the proxy service and launch the configuration tool. 38

45 Chapter 2. Installing the Repository 6. Click Finish to exit setup. Configuring the repository proxy The Repository Proxy Configuration dialog box opens to let you configure the repository proxy (see Configuring the repository proxy on page 39). The Repository Proxy Configuration dialog box allows you to configure the repository proxy. This configuration phase simplifies the client connection to the repository. When connecting to a repository, the client only has to select a proxy repository definition in which the name of the proxy server, its port number and the instance of the proxy are specified. The Repository Proxy Configuration dialog box can be divided into two main parts: The Instances group box (on the left part), in which you enter all the parameters to create a new instance. You can also delete instances. All other group boxes (on the right part), such as Connection, Log file or Cache allow you to parameter the Proxy itself. These group boxes are generally defined once for all instances You have to enter the following parameters in the Repository Proxy Configuration dialog box: 39

46 Installing the Repository Proxy Groupbox Parameter Description Instances New Delete An instance gathers the connection information between the proxy and the database server. Click the New button to create an instance of the proxy for the repository database. Each time you create an instance while the repository proxy is already running, you must stop it and restart it again for the instance to be taken into account. You can also select an instance in the Instances box and click the delete button to delete an instance. Connection Log file Name Data source User Password Port Log operations Including success Name of the instance selected in the Instances box. Name of the system ODBC data source that specifies the database to use to connect to the server. Note that user data source cannot be used by the proxy server Name of the user ID with which you log on to the database on the proxy server. Password for the connection to the database on the proxy server. Connection port of the server on which the proxy is installed and which allows the client to communicate with the server using TCP/IP protocol. The default port number is Select the Log operations check box, if you want to generate a log file. Select the Including success checkbox to display success in the log file. Cache Directory Path to the folder where you want to save the cache. You can click the Question Mark button to browse for a folder. Max size Maximum value for the cache size. The default value is 300MB. Now that configuration is complete, you can set up client machines to connect to the repository via the proxy. See the Getting Started with the Repository chapter in Working with the Repository. 40

47 Index A administrative mode 2 administrative install 19 client 19 client license 21 copy files on server 19 install client machines 21 server 19 authdb.sql 29 authenticate existing database 29 new database 29 C client install 21 SQL Anywhere 33 computer name 10 copy files on server 19 create system data source 35 create database 29, 30 D database authenticate 29 create 29, 30 existing 29 new 29 diagnostic program 13 disk space 19 E Eclipse plug-in 8 F floating served license impossible to return 13 limitation 13 font general options 11 report 11 symbol 11 G general options font 11 H hard disk space 2 host ID 10 I install administrative mode 2, 19 authenticated server 27 BPM 2 CDM 2 client machine 21 copy files on server 19 Eclipse plug-in 8 font problem 11 free model 2 ILM 2 license server 13 maintenance 11 maintenance mode 2 modes 2 network location 20 non-administrator user 4 OOM 2 PDM 2 PowerDesigner 4 report 2 repository 2, 26 repository proxy 35, 36 RQM 2 SAMreport 18 silent 22 silent mode 2 SQL Anywhere 27 41

48 Index L standalone mode 2 upgrade administrative version 21 Visual Studio 2005 plug-in 8 XSM 2 license agreement 6, 37 print 6, 37 license file 10 license server install 13 installation 13 license file 13 manage licenses on server 17 reread 16 SAMreport 18 start 16 LMTOOLS 13, 17 LMUTIL 13, 17 M maintenance license 11 mode 2 modify 11 remove 11 repair 11 modify install 11 N network location 20 non-administrator user 4 O ODBC SQL Anywhere 33 ODBC system data source 35 P PowerDesigner current setting 9 install 4 module 2 README 9 requirement 2 what to install 2 proxy cache 39 configure 39 connection 39 instance 39 log file 39 R RAM PowerDesigner 2 readme.html 9 remove install 11 repair install 11 report font 11 report log 18 repository create ODBC system data source 35 install 26, 27, 35 repository proxy cache 39 configure 39 connection 39 install 36 instance 39 log file 39 requirement PowerDesigner 2 system 2 reread license file 17 reread license server 16 response file 22 return floating served license 13 standalone served license 13 S SAMreport 18 report log 18 sybase.opt 18 saopts.sql 29 SCVIEW.EXE 29 served license SAMreport 18 server check disk space 19 copy files 19 42

49 Index install 27 install license server 13 manage licenses 17 SQL Anywhere 27 settings PowerDesigner 9 setup.iss 22 setup.log 22 silent mode 2 silent install 22 response file 22 setup.iss 22 setup.log 22 standalone local 22 SPDC 10 SQL Anywhere authenticated server 27 client 33 create database 29 install 27 network authenticated server 27 ODBC 33 repository 27 standalone mode 2 standalone local license license file 10 silent installation 22 standalone served license impossible to return 13 limitation 13 start license server 16 Sybase Central 29 Sybase Product Download Center 10 sybase.opt 18 symbol font 11 U upgrade administrative install 21 V Visual Studio 2005 plug-in 8 43