 |
 |
 |
 |
Installation and Licensing Please refer to the Rose for UNIX/Linux Installation Guide that is provided as your primary guide for installing and setting up licensing for this product.
If you encounter any problems while installing or licensing the Rose product, please check here first to see if it is a known problem. If a problem is not yet documented, please contact Rational Technical Support so we can investigate it, provide you with a workaround, and track the problem for future action.
This chapter contains the following sections:
- General Install Information
- Pre-Installation Information
- System Requirements
- Hardware/Software Patch Requirements
- Configuring Window Manager So Pop-Up Windows Will Remain On Top of their Parent Windows
- Running Multi-threaded GUI Applications on Multi-processor Solaris 2.6 Computers
- MainWin Runtime Components
- Installing and Utilizing Fonts Compatible on Both PC and UNIX/Linux Displays
- Licensing Information
General Install InformationAs a precaution, always make back ups of any Rose model files that you will be accessing with this software.
This product includes FLEXlm, a licensing product from Globetrotter, Inc. A startup license key that allows you to start using your product immediately is shipped with this product. You must obtain a separate permanent license from Rational in order to continue using this product beyond this startup key expiration date. Please refer to the licensing section of the Installation Guide for detailed instructions on obtaining and installing permanent licenses. Also, see Licensing Information for any last minute licensing notes.
Note: Rose 98i, 2000e, 2001,2001a, and 2002 for UNIX licenses are valid for this release. You will not need to utilize the startup licenses or obtain new permanent licenses if you are already utilizing Rose 98i, 2000e, 2001, or 2001a for UNIX licenses.
Pre-Installation Information
You may want to back up your Registry prior to running the installation program. Specifically, we recommend you make backups of the following files:
- You should always have a backup of all your model files. These can include files that end with .mdl,.cat,.ptl, .red, and .sub.
- Custom property files, which can include files that end with .pty and .prp
Note: There is no need to save .pty files that ship with Rose since these will be re-installed.
- Custom script files, which can include files that end with .ebs and .ebx
Note: There is no need to save .ebs or .ebx files that ship with Rose, since these will be re-installed.
- Path Maps (For Rose 98i, 2000e, 2001, and 2001a path map variables are saved in the registry.)
Follow these steps to back up path maps:
- 1 Run regedit and navigate to HKEY_CURRENT_USER\Software\Rational Software\Rose\Virtual Path Map
- 2 Click Registry > Export Registry File...
Follow these steps to restore path maps:
- 1 Run regedit and navigate to HKEY_CURRENT_USER\Software\Rational Software\Rose\Virtual Path Map
- 2 Click Registry > Import Registry File... and import the file you exported.
System Requirements
Before installing this software, please verify that your system meets the minimum system requirements listed below. If the requirements are not met, the product may not install and/or operate correctly.
Note: All platforms may not be available at this time. Contact Rational technical support for platform availability information.
The following table contains the hardware requirements for installation and use of this product. Note that the recommended amount of memory is only the suggested minimum amount. Additional memory may improve performance. Your memory requirements will also be larger if you are constructing large models.
The next table contains the software requirements for installation and use of this product. Note that this is also only a suggested amount of swap space. Your requirements may be larger if you expect to construct very large models. If all of your models are small, you may need less than the amount shown.
Hardware/Software Patch Requirements
Please see "Operating System Runtime and/or Patch Requirements" in the Installation Guide for system patch requirements.
When installing and running Rose for UNIX/Linux for the first time, you will be alerted if hardware or software patches are necessary. If running on a Solaris or HP-UX server, Rose for UNIX/Linux will attempt to automatically determine if patches are necessary on your server and/or Solaris display, and will advise accordingly.
You may also run the following anytime to determine if your computer requires operating system patches to run Rose for UNIX/Linux.
- SUN Solaris Server (computer running Rose for UNIX/Linux)
- SUN Solaris Display (computer displaying Rose for UNIX/Linux)
Check that the DISPLAY environment variable is set to your display, and then:
- HP-UX, IBM, or SGI Server
Running and Displaying on SGI IRIX - Hang Can Occur
This issue typically occurs when running on an SGI IRIX multi-processor machine and displaying to any SGI machine. If you encounter a Rose Hang, under these circumstances, install the patched "libX11.so" library in your Rose release as described below.
If you encounter any problems, after installing this patch contact Rational Technical Support.
- 1 Make sure your Rose process is no longer running. (Use ps to determine if the process is running, and "kill -TERM [pid]" if it is necessary to kill the process.)
- 2 As the owner of these files, cd rational_dir/releases/rose.I.J.K/install/patches/mips_irix_n32
- 3 cp libX11.so rational_dir/releases/rose.I.J.K/mips_irix_n32/lib/.
- 4 Run rose_cleanup.
- 5 Run rose.
Configuring Window Manager So Pop-Up Windows Will Remain On Top of their Parent Windows
Configure your Window Manager such that pop-up windows will remain on top of their parent windows, in compliance with the Windows API. Under X11, Window Managers may implement different strategies for maintaining the Z-order of pop-up windows.
In order to keep pop-ups on top, if possible:
- For MWM - Motif Window Manager
There is no specific configuration to keep pop-up (transient) windows on top. Pop-up windows are kept on top by default.
- For DTWM - Desk Top Window Manager (shipped with CDE)
Depending on your system's configuration, the default behavior of dtwm may not keep pop-up (transient) windows on top of their owner.
For example, it may be that the window stacking behavior for dialogs is specific, such as "Dtwm*secondariesOnTop = False". In such a case, here are some possible solutions for keeping the pop-ups on top:
- a
Change Dtwm*secondariesOnTop to True in the system-wide dtwm configuration file. On Solaris, the dtwm configuration file is located at /usr/dt/app-defaults/C/Dtwm. On platforms other than Solaris, the path to the dtwm configuration file may be different.- b
Add- c
Be more specific with the program name, and add, for example:- For OLWM -- Open Look Window Manager
Running Multi-threaded GUI Applications on Multi-processor Solaris 2.6 Computers
If Rose for UNIX/Linux hangs when running on a multi-processor Solaris 2.6 computer, verify that the Solaris 2.6 server and display (if applicable) includes the Sun Solaris XSun Patch 105633-32 or higher. This patch includes a fix for Sun Defect 4233280, Sun SO#3918581 (multi-threaded applications crash/hang on 2.6 multiprocessor computers). To check for this patch, run
on both the server running Rose and the display (if display Solaris 2.6).
When installing or running the application for the first time, Rose will advise if this patch is installed or required.
Displaying on Ultrabook, Using PGX Graphics Card
A CDE crash may occur when displaying Rose for UNIX/Linux on a Ultrabook using a PGX Graphics Card, if SUN Solaris patch 105362-26 is installed.
If using a PGX Graphics Card, we recommend that SUN Solaris patch 105362-20 be installed as this is the latest version tested and determined to be compatible with this release.
If you encounter the CDE crash, uninstall patch 105362-26 and if possible install "105362-20". If SUN Solaris patch "105362-20" is not installed, the following may occur:
- GUI Hanging Issues
- Paint Problems (i.e. black/white regions may appear in menus, dialog boxes, toolbars, etc.)
If you uninstall patch 105362-26 and encounter any of the issues described above, contact Rational Technical Support if patch 105362-20 is not available.
Running Rose for UNIX/Linux on HP-UX 11.00 with HP-UX OS Patch PHSS_21493
Rose for UNIX/Linux requires HP-UX OS Patch PHSS_17327 (X/Motif 2.1 Dev Kit Mar99 Periodic Patch). This Patch requires PHSS_17326 (X/Motif2.1 Runtime Mar99 Periodic Patch). PHSS_17326 has been superseded by HP-UX OS Patch PHSS_23823.
It is important to use PHSS_23823 as Rose for UNIX/Linux will not start (display) if an earlier version of this patch is installed (i.e. PHSS_21493).
If it is necessary to have a Motif Xlib runtime patch prior to PHSS_23823 and you encounter this issue, refer to the following instructions to workaround this problem:
- 1 Make sure your Rose process is no longer running. (Use ps to determine if the process is running, and "kill -TERM [pid]" if it is necessary to kill the process.)
- 2 As the owner of these files,
- 3 cp libX11.3 rational_dir/releases/rose.I.J.K/hppa_hpux/hp11/lib/.
- 4 chmod 555 rational_dir/releases/rose.I.J.K/hppa_hpux/hp11/lib/libX11.3
- 5 Run rose_cleanup.
- 6 Run rose.
MainWin Runtime Components
When Rose for UNIX/Linux runs for the first time, an $MWUSER_DIRECTORY directory is created which includes MainWin files and directories. Rose is created utilizing MainWin (developed by Mainsoft) and requires specific MainWin components to operate correctly. $MWUSER_DIRECTORY may be set to serve as the windows directory. For example, $MWUSER_DIRECTORY may be set to $HOME/.windows. If $MWUSER_DIRECTORY is not set, the default location will be $HOME/windows.
Within the $MWUSER_DIRECTORY directory, you will find the following type of files and directories:
- mwfc-* - Font caches, are created incrementally over the duration of the application process; activating when a user chooses a new font. The font cache is built each time Rose for UNIX/Linux is run on a new X server, or if the server's font path is changed. Each font cache file has a unique name:
mwfc-xxxx (where xxxx is dependent on the specific display used)
This file can be removed if it is suspected of interfering with font operations. If removed, it will be regenerated the next time Rose is invoked.
When Rose for UNIX/Linux is invoked by the user on the same X server, the application can quickly look up the font cache file and select the closest X font available.
- registry directory - This directory includes a binary "registry" file which is created the first time the user runs Rose for UNIX/Linux (for each version of the Operating System). For example, a "registry.5.6" registry is created for a user running the release on a SUN Solaris 2.6 computer. The registry stores Rose for UNIX/Linux configuration and initialization data.
The registry directory also includes rose_reg_check, an ascii file which includes the version of Rose for UNIX/Linux and it's associated add-ins. This file is created the first time a user runs Rose for UNIX/Linux.
A specific registry file may be utilized by setting the following environment variable:
- help - This directory includes files that get created and stored every time the user runs help and creates the help keyword database.
- win.ini file - This is a default configuration file. It includes such information as print device/port settings.
Rational Rose for UNIX/Linux includes "mw" directory
Rational uses MainWin (by Mainsoft) to rehost Rose for UNIX/Linux platforms. Specific MainWin runtime components are included in Rose. Below is a description of the type of MainWin files included in Rose for UNIX/Linux under the rational_dir/rel*/rose*/mw directory.
- afm directory - Includes support fonts.
- bin directory - Includes programs which perform such functions as determining hardware configuration, removing unreleased X resources, showing X resources, and converting old registries to new.
- bin-<os>_optimized directory - Includes binaries designed to register libraries and controls, provides registry browser and support, and type library browser, and font server.
- fonts directory - Includes release fonts and font files compatible on both PC and UNIX/Linux displays. See Installing and Utilizing Fonts Compatible on Both PC and UNIX/Linux Displays .
- fontserver.cfg file - Font configuration file used by font server.
- helpfile directory - Includes help files provide by Mainsoft.
- lib directory - Includes scripts to order library paths correctly, and to setup MainWin configuration.
- lib-<arch>_<os> directory - Includes an nls directory which holds *.nls (Nation Language Support) files that are used upon application startup. It also includes mwperl (an executable called upon by the MainWin scripts).
- lib-<os> directory - Includes files to manage the font cache, provide support for type library browser and registry browser.
- lib-<os>_optimized directory - Includes MainWin support libraries and resources.
- system directory - Includes default binary registry and system MainWin registry files.
- setmw* and setup* files - These files provide appropriate MainWin environment settings.
- win.ini is the default Windows configuration file (which gets copied in $MWUSER_DIRECTORY the first time Rose is run).
Installing and Utilizing Fonts Compatible on Both PC and UNIX/Linux DisplaysRose for UNIX/Linux now includes the following release fonts which are compatible and may be used on both the PC and UNIX/Linux displays:
- MS Sans Serif
- Arial
- Times New Roman
- Courier New
- Tahoma
As it now is possible to display these same fonts on UNIX/Linux and the PC - models, etc. created on the PC (using these fonts) should display easily and accurately in Rose for UNIX/Linux on PC and UNIX/Linux displays. Furthermore, utilization of these fonts will provide the following additional enhancements:
- Improved dialog scaling on all platforms
- Resolves defects when these PC fonts were not always available on UNIX/Linux displays. Previously, a model created on the PC would utilize an Arial font (not available on UNIX/Linux). Opening the same model on a UNIX/Linux display could produce unpredictable results when the font would map to "Application".
- Resolves defects when users were creating/sharing models to be displayed on PC and UNIX/Linux displays. Display difficulties could occur when models created or edited on PC display (i.e. using eXceed) were then opened on a UNIX/Linux display.
Font files (in *.pcf - portable compiled format), are now included in the rational_dir/releases/rose.I.J.K/mw/fonts directory of your release. This directory also includes the following fonts* files:
- fonts.dir - The X11 fonts dir file.
- fonts.mwd - MainWin fonts dir file. This file is accessed by this release and contains, for each font, the WIN32 metrics, the X11 fontname, a mask stating whether it is a "stock" font, and a "used on unix" flag.
A fontserver.cfg file is included in the rational_dir/releases/rose.I.J.K/mw directory. This file is used when starting the font server to provide the new fonts to the Rose application. A font server (xfs) is also provided in the rational_dir/releases/rose.I.J.K/mw/bin_<os>_optimized directory.
Making The Release Fonts Available on Your $DISPLAY
Prior to running Rose for UNIX/Linux for the first time, run rational_dir/releases/rose.I.J.K/bin/rose_cleanup. Upon starting Rose for UNIX/Linux, you will notice some new messages in relation to the availability of the new fonts. Rose will attempt to determine if the new fonts are available for your $DISPLAY, by running the new Rose for UNIX/Linux rose_fonts utility.
UNIX/Linux DISPLAY with visibility to Rose fonts
rose_fonts will make the fonts available to your DISPLAY by including the path to rational_dir/releases/rose.I.J.K/mw/fonts/ in your DISPLAY's font path.
DISPLAY other than UNIX/Linux (i.e. PC using eXceed) or UNIX/Linux DISPLAY without visibility to Rose fonts
In this case, fonts must be made available by using a font server and including the font server in the DISPLAY's font path.
rose_fonts will determine if a font server is providing access to the Rose fonts, as described below:
- Determines if a font server is already running (on the server used to run Rose). There may already be a font server running on the designated font server's port# 7100. On SUN systems 2.5.1 and above it is likely that a font server is already running and defined in the /etc/services file, as "xfs" or "fs". The existing font server's default fontserver.cfg file will not include a path to the Rose fonts (unless it has been configured to do so).
- If a font server is running, rose_fonts determines whether the existing font server is already providing access to the rose_fonts (i.e. it determines if the fontserver.cfg includes the path to the Rose fonts provided in the release).
- If a font server is not running, rose_fonts attempts to start a font server "xfs".
- If a font server is running and does provide access to the Rose fonts, rose_fonts adds the font server to the DISPLAY's font path.
If Necessary To Configure Existing Font Server
If a font server is running on the Rose server and it is not already providing access to the Rose fonts, contact your System Administrator to perform this setup or refer to the man pages for xfs(1). The following advises how to configure an existing font server on SUN Solaris.
Note: Configuring an existing font server to provide access to the Rose fonts may produce less than optimal font results, based on the font paths included in the fontserver.cfg's catalogue setting. This is due to a potential Rose 2000e for UNIX/Linux font mapping issue that is currently under investigation. If you elect to continue with the following instructions, and you encounter poor font results please notify Rational Technical Support and remove the Rose font support from your fontserver.cfg file.
If you elect not to add the Rose font support (as described next) or elect to remove the Rose font support from an existing font server Rose will continue to operate correctly, however the font enhancements listed in Installing and Utilizing Fonts Compatible on Both PC and UNIX/Linux Displays will not be available and you may encounter the following defects:
Adding Rose fonts to Existing Font Server on SUN Solaris
To add Rose font support to an existing font server on SUN (it may be necessary to su to root to perform these actions):
- Edit the default fontserver.cfg file "/usr/openwin/lib/X11/fontserver.cfg" to add the location of the Rose fonts in the "catalogue" path (being careful not to add or remove extra spaces).
A catalogue path may appear as:
/usr/openwin/lib/X11/fonts/F3bitmaps/,/usr/openwin/lib/X11/fonts/Type1/
Add the Rose font path, by prepending the path to the catalogue path.
rational_dir/releases/rose.I.J.K/mw/fonts/,/usr/openwin/lib/X11/fonts/F3bitmaps/,...
- Use ps to determine the process ID of the "fs" or "xfs" process, and then stop (kill) the "fs" or "xfs" process, if running.
- Set the DISPLAY font path to include the path to the existing font server by running:
- Determine if the Rose fonts are available and restart font server:
Rose (upon starting) should indicate that the Rose fonts are now available.
Upon performing this setup, it will be important to update the fontserver.cfg file if Rose is uninstalled or moved to a different location (path changes).
Starting a Font Server
If a font server is not running (on the server running Rose), rose_fonts will start a font server provided in the release, if necessary. This is necessary if the DISPLAY is not a UNIX/Linux display, or if the display does not have direct visibility to the fonts provided in the Rose release.
X Font Commands Utilized by rose_fonts
The following commands are typically located in one of the following directories: /usr/openwin/bin, /usr/bin/X11, /usr/X11R6/bin, /usr/openwin/lib/X11, or /usr/openwin/include/X11. The font server "xfs" is provided in your release in rational_dir/releases/rose.I.J.K/mw/bin-$arch_optimized.
To Start a Font Server
xfs -config rational_dir/releases/rose.I.J.K/mw/fontserver.cfg -port 7100
To Set the Font Path
xset +fp rational_dir/releases/rose.I.J.K/mw/fonts/ (direct path to fonts in release)
xset +fp tcp/$host:7100 (font server path)
To Determine if Rose Fonts Available
xlsfonts may hang if a font path includes a path to a font server which is not running. rose_fonts will not let xlsfonts run for longer than a specified period of time (typically 30 seconds), to safeguard against this event. If an xlsfonts hang occurs, rose_fonts will provide status with recommendations.
rose_fonts Overview
In summary, rose_fonts will provide the Rose fonts to your DISPLAY by either setting the font path to point to the fonts in the release (UNIX/Linux display with visibility to the fonts), or by setting the font path to a running font server if the font server is providing access to the Rose fonts. rose_fonts will use "xset" to set the font path, "xfs" to start a font server (if necessary) and "xlsfonts" to determine if the Rose fonts are available after the setup has been performed. If a font server is already running and does not already provide support for the Rose fonts, manual setup is necessary (i.e. see Adding Rose fonts to Existing Font Server on SUN Solaris ) to complete the Rose font setup. In this case, manual set up is required as it is often necessary to su to root to perform this action. rose_fonts will provide messages describing the current status each time Rose is started.
Contact Rational Technical Support if you should have any questions or encounter any difficulties accessing or utilizing the new Rose fonts.
If Rose Fonts Not Available
There may be occasions when the Rose fonts will not be available. rose_fonts will alert you if, when starting Rose, if the Rose fonts are not available. If this occurs, Rose will continue operate correctly, however the font enhancements listed in Installing and Utilizing Fonts Compatible on Both PC and UNIX/Linux Displays will not be available and you may encounter the following defects:
To Eliminate Output from "rose_fonts" When Running Rose
Each time that you start Rose, rose_fonts determines whether the Rose Fonts are available, attempting to make the fonts available when necessary. Each time Rose is started, rose_fonts displays messages advising current Rose Font status. In order to eliminate output from rose_fonts, set the following environment variable prior to running Rose.
Setting this environment variable will allow rose_fonts to run, but will refrain from printing Rose Font status messages.
Licensing InformationThere are three license types supported by Rose for UNIX/Linux:
- Startup - This is a time-locked temporary license to allow you to use the software until you receive a production key.
- Node-locked - This allows you to run the software on a single node (computer).
- Floating - This is server-based licensing, where a client logs onto a license server to be assigned a key.
For a full description of license types, installation and usage, please consult the Rational Rose for UNIX/Linux Installation Guide.
The software you receive includes a temporary startup license. You must install the software and follow the steps detailed in the Installation Guide to acquire node-locked or floating license for your product. For users who are upgrading from Rose 98i for UNIX/Linux or after, you may use your existing license key to run Rose for UNIX/Linux.
| Rational Software Corporation
http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2002, Rational Software Corporation. All rights reserved. |
| |
|
|
|