Cayenne Software, Inc. ObjectTeam 7.1.1 Read Me First Notes Introduction This document contains system requirements and last-minute information about the installation of ObjectTeam. Please read this document prior to installation! For instructions on how to install the ObjectTeam software, refer to the CD insert. For an overview of all platforms and third-party products for which ObjectTeam is certified, refer to the ObjectTeam Certification Matrix. For an overview of all new or changed features, refer to the ObjectTeam What's New list. Contents * Before You Start * Upgrading * Problems and Workarounds Before you start It is strongly recommended that you back up your ObjectTeam 6.1.1 installation before installing this software. It is also recommended that you back up a copy of your Windows registry. For details on this topic, refer to the ObjectTeam Installation Guide for Microsoft Windows. Note that this version cannot run simultaneously with previous releases on a single server due registry/service conflicts. Please note that if you have installed a beta version of ObjectTeam 7.1.1, you must uninstall it and related products. Upgrading If you are upgrading from a previous version of ObjectTeam, be sure to read the chapter "Upgrading From a Previous Release" in the ObjectTeam Installation Guide. This chapter contains important notes on compatibility between 7.1.1 and previous versions. Important notes include: * For PC platform o Requires Windows NT 4.0 or Windows 95 (no support on Windows NT 3.51) o Upgrade from SQL Anywhere 5.0.03 to SQL Anywhere Authenticated Edition 5.5.02 * For Unix platforms o Requires Sun Solaris 2.5.1 (no support on Solaris 2.4) o Requires HP/UX 10.20 (no support for HP/UX 10.01). o Requires Oracle 7.3.x RDBMS for Oracle-based repositories o Requires Informix 7.2 RDBMS for Informix-based repositories * All platforms o Requires repository and environment data conversion o Configuring ObjectTeam modules The Known Problems section below also contains important issues regarding upgrades. Known Problems and Workarounds DynaText does not work under CDE (UNIX) Problem: DynaText 2.3 does not support CDE for any UNIX platform. For those using CDE, the following workarounds however may work. Workaround 1: Add the following Xresource: *XmTextField*FontList: 8x13 to your Xdefaults and then merge that file in using xrdb -merge. Workaround 2: Set the variable XNLSPATH to point to /usr/lib/X11 and set the variable XKEYSYMDB to point to the dtext/tmp/XKeysymDB file. For example: setenv XNLSPATH /usr/lib/X11/nls setenv XKEYSYMDB /usr/dtext/tmp/XKeysymDB Cannot overwrite old FLEXlm installation (MS Windows) Problem: When upgrading FLEXlm, the setup cannot overwrite the cayenne.exe file because the existing FLEXlm license service has a lock on it. Workaround: The Installation Guide for Microsoft Windows explains that you should stop the FLEXlm service before upgrading the FLEXlm software. This is insufficient, since even when stopped, the license service retains a lock on the cayenne.exe file. After stopping it, you must also remove it using the FLEXlm control panel. Select Start | Settings | Control Panel and double-click on the FLEXlm license manager. Click on the Setup tab, and enter the name of the existing license service (e.g., Cayenne License Manager). (NOTE: Due to a bug in the control panel, the name does not appear in the pop up list.) Click in one of the other fields, and the details should appear automatically. Click Remove to remove this service. You can now run the FLEXlm setup program from the ObjectTeam 7.1.1 CD. ObjectTeam installation directory and ADA code generators (MS Windows) Problem: The ADA code generators will not work when an ObjectTeam installation directory is chosen containing spaces in the directory path. Workaround: Do not install ObjectTeam in a location containing spaces in the directory path if you intend to use the ADA code generators. E.g., use the default ObjectTeam installation directory: C:\Cayenne\Tools TCP/IP setup requirements (Windows 95 standalone) Problem: During the creation of the repository or starting the ObjectTeam Browser, error messages appear like: 115024 Cannot obtain corporate id for 'corporate' 120051 Name request for Corporate service 'corporate95' not involked 120020 Operation implementation unavailable 120033 Error accessing the implementation repository 120014 Request for 'ot_broker' at host 'xx' timed out after 60000 milliseconds Workaround: ObjectTeam 7.1.1 has some special requirements for a correct TCP/IP setup, depending on your hardware configuration. For the latest information, please refer to our technical note TAN#3632 on our On Line support web pages. Under Solution to Problems, select ObjectTeam as product, enter the words 'Windows95 standalone' as keywords and click on Find. Incorrect default in Create New Repository dialog box on UNIX Master server Problem: When you create a new repository in the Corporate Management tool, the Create New Repository dialog box prompts you to enter a value for the User Environment Root directory. This is the directory to which files are written when users generate files, such as code files or documents, from ObjectTeam. If you leave this field empty, it is automatically set to the value you fill in for the location of the repository directory (by default /usr/cayenne/repos). However, this directory is not writable for users other than ObjectTeam administrator. Workaround: Do not leave the User Environment Root field empty. Instead, enter either a file system path part or an absolute path. This works as follows: * If you enter a path part, then files are generated to a directory of that name in each user's home directory. For example, suppose you enter the value ot_files for User Environment Root. If the user smith creates an external file abc.tcl in the system core_sys, in the implementation phase, in the smith_conf configuration, in the project my_proj, the file would be written in the file system to: ~smith/ot_files/my_proj/smith_conf/implementation/core_sys/abc.tcl * If you enter an absolute path, then when a user generates files from ObjectTeam, they will be written to that location. For example, suppose you set the User Environment Root to /user/ot_files. In the same example as above, the file would be generated in: /user/ot_files/my_proj/smith_conf/implementation/core_sys/abc.tcl Note that in this case the directory specified by the absolute path (e.g, /user/ot_files) must be accessible and writable for all users. Note for heterogeneous environments: If you are installing a client/server ObjectTeam installation where the server is running UNIX and all clients are running Windows NT or Windows 95, the absolute path must be a Windows style path, e.g. C:\ot_files. Upgrade from 6.1.1 Master server (UNIX and Windows): File System Path Part property incorrectly set Problem: After upgrading from ObjectTeam 6.1.1, the File System Path part for your corporate object (and possibly other levels such as Project or Configuration) will still be pointing to your old user environment directory. When users generate files, they will be written to the old location. Workaround: After upgrading, in the ObjectTeam browser, select the Corporate and select File->Edit Properties. Select File System Path Part and enter a value. If users have set this property for any other levels in the corporate hierarchy, they should also reset it. For details on how to set this variable, see the previous problem description. No slave server configuration possible on Windows NT Problem: It is not possible to upgrade to, or install, a slave server configuration on Windows NT. This is due to a bug in the dbserver program. Workaround: Do not install a slave server configuration on Windows NT. Install a normal client - master server configuration instead.