FAQ
Frequently asked Questions
*		 Together
GENERAL PERFORMANCE   TROUBLESHOOTING USING TOGETHER   QUESTIONS LIST
 
In this document you can find answers to a number of questions that first-time users of Together may encounter. You can find additional information specific to Together 2.x at http://www.togetherj.com/tj-faq.htm. Each topic in this document contains one or more keywords in [ brackets ] that relate to the subject of the question. While not comprehensive, if you use your browser's search/find function you may be able to locate information more quickly. For a complete list of all questions covered here, click the Contents link above.

 General information

What product download options are available and what should I know about them?

DOWNLOAD: Together (NT/95 INSTALLER) 

  • Together plus Sun's JRE (version 1.1.6) for NT/95 (10 MB) 
  • Together plus Microsoft's JVM (build 2924) for NT/95 (12 MB) 
  • Together only (7 MB) 
DOWNLOAD: Together (PURE-JAVA INSTALLER) 
  • Together only (5.5 MB). Here, the installer itself is pure Java. It requires that you install any Java VM before you run the installer. There are two variants of this download: 
    • packed in Zip format (principally for OS/2 users) and 
    • packed in tar format (mainly for UNIX users). 
For the latest information, visit the Object International website's download page. 

DOWNLOAD VMs directly from manufactures: 


[ Download ] [ options ] [ versions ] [ platforms ]

What should I know about Virtual Machines? 

If you have Together/J 1.0, Together/J 2.0, or Together 2.x you need to install a Java virtual machine (VM) or Java Development Kit (JDK). To see what VMs are currently supported, see readme.html. Here are some things you should know about specific VMs and/or JDKs: Microsoft's, IBM's, Sun Solaris', and Linux ports.

Microsoft ® JVM:

Microsoft ® VM for Java is distributed separately or as a part of Internet Explorer 4 or within SDK for Java. However, you need to update your version of MS JVM to version 5.00.2924. (Build 2339 is also acceptable). 
Normally, you can check the version of your MS VM by invoking jview in command shell: 
  1. start command shell (command.com for 95 or cmd.exe for NT)
  2. type jview and press Enter
  3. check the version. It should be Version 5.00.2924

    4. Here's an example of console output: 
    C:\users\default>jview 
    Microsoft (R) Command-line Loader for Java  Version 5.00.2924 
    Copyright (C) Microsoft Corp 1996-1998. All rights reserved. 
  4. if your version differs, you should run MS VM installer (MSJaVX86.EXE) included in Together plus Microsoft's VM. This file automatically starts in the end of Together installation.
Note that, if you work in NT, Service Pack 3 for Windows NT 4.0 must be installed before installation of Microsoft Virtual Machine for Java. To obtain Service Pack 3 for Windows NT 4.0, refer to 
http://www.microsoft.com/support/winnt/nt4sp3.asp. 

Some configurations created from different or improper installations may mix jview and Java itself of different builds. You can follow the more complex procedure to make sure which build of Java is actually invoked when you start any Java application, e.g. Together: 

  1. start regedit (Registry editor)
  2. find the key: HKEY_CLASSES_ROOT\MSJava\CLSID
  3. invoke editor for the (Default) value and copy to Clipboard the data of the Class identifier, e.g. {08B0E5C0-4FCB-11CF-AAA5-00401C608501}
  4. now find the key with the copied value: invoke Edit | Find, paste to Find what, check Keys only 
  5. expand the found key, select the subkey InprocServer32 and look for its (Default) value - it should be a library that actually executes Java; usually it would be msjava.dll in Windows system folder, e.g. C:\WINDOWS\System\msjava.dll or D:\WINNT\System32\msjava.dll
  6. now find this file in Windows explorer and invoke the Properties dialog
  7. click the Version tab and see the "File version" field

Microsoft ® JVM and Windows 98:

Microsoft ® Windows 98 is distributed with Internet Explorer 4 and Java VM already built-in into the system. The version of JVM usually is greater than one used in Windows 95 or NT. So you don't need to upgrade JVM with the supplied installer. 
However, Together has been tested in Windows 98 with the build 2424 of JVM. Make sure that you have the appropriate build. Refer to the previous paragraph for the information on how to know the build number. 

OS/2 Warp 4 and IBM® JVM:


Solaris JDK:


Linux ports of JDK:

  • Recommended:

    • JDK 1.1.5 v7 or 1.1.6 v5 ported by Randy Chapman and Steve Byrne. 
     
  • NOT fully compatible with Together and can cause problems:

    • JDK 1.1.4 and 1.1.6 ported by Sergey Nikitin 
    JDK 1.1.6 v1 ported by Randy Chapman and Steve Byrne. 
     
  • JIT compilers:

    • TYA since 0.7 by Albrecht Kleine. Available via http://www.blackdown.org, Linux-Java Tools page. It works with JDK 1.1.5 v7. Earlier versions are not acceptable. 

    Visit the Java Linux project site at http://www.blackdown.org/java-linux.html


[ Virtual Machines ] [ VM ] [ platforms ]

"Installation failed" message using pure Java installer? 

You logged in without Administrative privileges. This is known issue of InstallShield Java Edition: 
"Installation failed" message appears after installation on Windows NT systems when end user is not logged on as an administrator. 
When installing on Windows NT, InstallShield Java Edition uses an .INF file to enter uninstall information into the end user's registry. If the end user is not logged on as an administrator, Windows NT displays an error message which states that the installation has failed. This message appears because the end user does not have access to the registry key that needs to be modified with uninstallation information. 

I now run the Sun VM. I hear Microsoft's is faster, but what happens to my apps if I install MS JVM?

Together runs ALMOST 2.5 TIMES FASTER with Microsoft's VM, compared with running on Sun's VM. If you have a need for speed, choose this VM. Your Java apps will run as before unless you yourself choose to configure them to run with the MS VM. 

  • Observe that "java" invokes the Sun VM. In contrast, "jview" invokes the MS VM. You control which VM you use for each of your Java apps.
  • MS VM does not affect the class path.
  • MS Internet Explorer automatically installs a version of the MS VM.
[ Virtual Machines ] [ Sun ] [ MS ] [ speed ]
What documentation is provided with Together ?

Together provides on-line documentation in HTML format. You can use your Web browser to view and print documentation files. The default path for these files is: $TOGETHER_HOME$/help/ and subfolders below. The main documentation subfolders are: 

Getting Started:
The Getting Started book includes a features summary, conventions and terminology, and an introduction to basic concepts. It explains the basics of using Together tools and features. Recommended first reading if you are new to Together. Begin with ./help/GettingStarted/index.html (Table of Contents file).  Now it includes the Fast-track tutorial GS_Tutorial.html to help you get up and running fast. 

HowTo:
A page of task-oriented headings with links to the appropriate topics in the Together on-line documentation. See ./help/HowTo/index.html. 

User's Guide:
Covers specific information for creating and working with the various diagrams supported in Together. Also includes User's Reference, which provides a complete reference for Together menus, toolbars and main dialog boxes. Begin with ./help/UserGuide/index.html (Table of Contents file). 

There is also an example project: Families. This is a visual example of what you can achieve using Together. It provides a ready-made project that includes several of the most common UML diagrams. Open ./help/Families/families.html. 

For a complete Table of Contents for all on-line documentation, see ./help/index.html. 

References:
In addition to User Reference with complete links to Together components, menus, dialogs, etc., refer to programming documentation located in ./doc directory and its subdirectories. There are documentation on Script API, several scripts, and more. 
 

Known problems, etc.

Refer to problems.txt for the list of known problems, limitations, workarounds and helpful tips. 

[ Documentation ] [ Help ] [ information ]

Where can I get product information and support?

This varies depending upon where you are located. For the most up to date information refer to addresses mentioned in Getting Help of the readme.html file. 

[ Support ] [ Help ] [ information ]

 Performance tuning

Problem: excessive hard drive accesses 

Here are several things you can check: 

  1. Check the include path and additional directories. Deep path names like "C:" will slow things down.
  2. Look at the memory used while parsing; if it goes close to the maximum, then try to increase the swapping file size (set the minimum swap file size to something like 100-150M).
  3. Try running Together with jre.exe (Sun JVM). It provides options to specify the Java heap size. Change the maximum heap size (-mx32m) to some larger amount  (e.g. -mx60m or -mx100m, depending upon how much virtual memory is available).
Problem: excessive time “drilling down” (navigating) a hierarchy of packages 

Better way: navigate down through the project's tree in the Navigation pane and right-click on the desired diagram to Browse (i.e. open) it. You don't have to create browser windows for all the directories along the way. When you navigate down, select "Browse" rather than "Browse in new window." (If you forget to do that simply close the windows that remained open as you worked you way down.) The diagram update time is significantly faster this way. 

Tips for really big projects:

  • For a directory with lots of files, partition those files into subdirectories and then drill down into the subdirectory you are interested in. If you cannot add subdirectories, add a new package. Then bring both physical and logical content into the new package and then work with only this package open.
  • Open just one package, closing all others, and import logical content using the diagram speed menu's Import command rather than importing by Ctrl-drag-drop.

Troubleshooting

 
Together ran out of memory

Large projects require a lot of memory in fact. Working with Sun VM you can control a memory allocation. Together.bat file (in installation's bin directory) contains by default the keys (-ms/-mx) that tell Java Machine to immediately allocate a large, 32MB heap. This provides benefit in performance in comparison with allocating-on-demand. 
Here is the beginning of the command that invokes jre: 

    jre -ms32m -mx32m -cp %TOGETHER_HOME%\classes;...
However, if you experience a luck of memory, excessive hard drive access (swapping), system messages "Your system is running low of virtual memory", or simply wish to optimize Together for memory size, you can reduce the numbers at -ms/-mx parameters or even delete -ms parameter. 

Other hand, you can increase these parameters for better performance on large projects. You should an appropriate powerful computer; otherwise the effect may be negative. 

Note: we know of no such options for the Microsoft VM. 

See also: Excessive hard drive accesses
[ Sun VM ] [ memory ]

I used the pure Java installer under NT/95.  I don't see Together on my Start menu... how do I start the program?

Run the Together.exe file found in the bin directory under your Together installation. Moreover, you can simply drag-and-drop the Together.exe file icon to the Start button on the Windows Task bar to create a program item. 

[ Windows ][ NT ][ Installation ][ Install ][ start ]

In Windows, images are displayed in the wrong palette.

You are working in 256-colors mode, switch to the High or True color mode. In Control Panel, open Display. On the Settings tab in Color Palette, choose pallete with number of colors more than 256. 

[ Windows ][ color  ][ 256 ][ High Color][ palette ]


I'm having trouble printing.

Printing problems can stem from any number of things unrelated to a particular application program. One problem frequently reported by Together users stems from the page size set in the system printer being set to a different size than that specified in Together's print options. Make sure the correct page size is set in both the system printer properties and in the Print tab of the Global Options dialog. If you override Global print options in individual diagrams, make sure the correct page size is set in both the system printer properties and in the Print tab of the Diagram Options dialog. 

There are known printing problems with the Sun JVM version 1.1.5 and 1.1.6 under Windows. If you are running this version, consider reverting to version 1.1.4 until Sun Microsystems reports these problems fixed. 
The same problems occurs with the MS JVM build 2829 (SDK 3.0) and build 2924 (SDK 3.1). 
Together offers workaround for printing in Windows 95 and NT. Uncomment the following property: 

print.dpi=72 
in the ./lib/config.properties file, then call Edit | Reload Options, if Together is running. Also read the next question. 

[ Virtual Machines ] [ Sun ] [ Printing ]


I can't do any configuration. The documented config.properties files is missing and Reload Options... command in the Edit menu is always disabled.

You probably have a limited edition. User-configurable system properties are disabled in some kinds of editions (e.g. freely downloaded) and the config.properties file is not installed. 

If you've got a full commercial edition, try running Together again. If your config.properties was missing for some reason, Together generates a new one with default configurations. 

[ Properties ] [ Configuration ] [ Customizing ]

The commands on my Help menu don't work under Solaris. 

There is a file called 'associations' in Together's bin directory. This file specifies the path to the web browser used to display Help. The default setting is  'netscape'. If you don't run Netscape Navigator, or it is not in your search path, the Help menu commands are not invoked unless you point the associations file to your browser. 

[ Help ] [ Solaris ] [ Browser ]

Together crashes when I run a tool launch command under Linux . 

Specific to Linux port of JDK 1.1.4 only: If you create a tool (Edit | Global Options | Tools) and check the Use oistart and Wait for Update options, then start that tool and try to select Edit | Global options, Together crashes because of unexpected xlib reply. This is a problem in the Linux port of JDK 1.1.4. Workaround: Do not use it. 

[ Linux ] [ Tool ] 

Scrollbars jitter under JDK 1.1.6 and Sun Solaris

JDK 1.1.6 Production Release has an error in working with scrollbars under Solaris. 
Workaround: use patches to java.awt classes supplied with Together since build 361. You can:

  • Prepend classpath with ./lib/awt.zip. Note this library should be specified on the classpath before the standard Java classes.
  • Use the alternative starter ./bin/tg116.sh, which already contains the necessary modifications in classpath.
These files are available in any UNIX-system installation.

[ JDK 1.1.6 ] [ Solaris ] [ Scrollbar ] 

Using Together

Why my changes in the Text editor do not propagate to other related places?
I rename a class in the Text editor, switch to diagram and see that constructors have the old class name.
I rename a class in the Text editor and it lost incoming links.
I change C++ operation's declaration in the Text editor, switch to diagram and notice that the linkage with operation's definition is lost.
This is because the Text editor in Together is only an auxiliary tool. It serves either small changes or implementations. 
The update in the mentioned cases is one-way, from the source code to the diagrams. A user is fully responsible for the correctness and synchronization of changes made in the Text editor. 
For careful update and propagating changes all over the model, we recommend to use diagram or inspector. 
Also recommended to make sure that all the diagrams deep in the package tree are opened. To do it, call Tools | Scan all diagrams from the main menu. 

[ Editing ] [ Text editor ] [ Update ] [ Propagate ]


Why can't I enter Attribute/Operation declarations in-place as they display?

With in-place editing of Attribute and Operation names, you have a choice:

  • you can enter only the name (as you would in the name property in the Inspector)
  • you can enter the full declaration for the attribute or operation.
For the latter, Together requires that the in-place entry be full correct syntax for the target language of the project.

For example, in a Java project you you might see an attribute displayed on a Class icon like so:   +attr1:int 

When you click to activate the in-place editor, the editable text displays as: attr1
You can enter either attr2 or public string attr2;  but not +attr2:string

[ Editing ] [ Properties] [ Attribute ] [ Operation ]


Why can't I import classes from <default> directory for another Together project?
I want to import classes from other Together projects but encounter the following problem: 
I want to import classes from c:\samples\project1; 
I include c:\samples\project1 in source/class path; 
No files appear in the Import dialog, since only packages are listed there (no root directory for ANOTHER project, only <default> for current one). It's possible to see the desired files in the Import dialog by shortening source/class path of the project  to c:\samples. However, then you'll see a  project1 item in the listbox of the Import dialog, and see classes you want to import, but the classes won't be imported since they have no package statement. 

This is because of importing classes with Package statements is inconsistent with the path to file relative to the source/class path. 
[ Import ] [ Default ] [ Package ] [ Project ]


How can I reach operation's definition in C++ projects?

Together knows about operations' and static attributes' definitions, if they are available in the current project. It loads the corresponding definition source code into the Text editor, if you Shift-click the item. In addition, if you Shift-click the class that has already at least one operation with definition, the corresponding source file will be loaded into the editor.
Some C++ projects have the structure that source (definiton) files and header files are stored in separate directories. To make sure that source files will be parsed in Together, include the directories with source files into C++ Additional directories option of the C++ Project Properties dialog.
Note that if you rename an operation or change its declaration in the Text editor, you should repeat  the same changes for its definition; otherwise Together loses the reference from declaration to definition. It's recommended to make changes using the inspector or diagram; changes made there are applied to both declaration and definition. 

[ C++ ] [ Defintion ] [ Navigation ] 

Contents

General Information Performance Tuning Troubleshooting Using Together


 
GO TO TOP  HOW TO  USERS GUIDE HELP CONTENTS
© 1997-98