# Together 4.2 Readme

WHAT'S NEW | OS PLATFORMS | JVM & SYSTEM REQUIREMENTS | VERSION 2.X USERS | INSTALLATION & STARTUP | KNOWN PROBLEMS | ADDITIONAL NOTES
|  | JVM Information System requirements |  | Latest On-line Info Windows NT Launching Help Installation support |  |

## What's New

Release 4.2 adds number of new e-commerce features, improves and enhances some existing features, and fixes a number of bugs . For more information, see What's New. If you would like to review features introduced in recent releses, please see Version History.

## Supported operating platforms*

Together has been tested on Linux, Sun Solaris (SPARC), and Microsoft Windows (95/98/NT/2000). Together may run on other platforms that support Java(tm), but TogetherSoft supports the product only when running on one of the above operating systems with a recommended Java Virtual Machine (JVM).

## Java Virtual Machine and Together system requirements

The information in this file and related linked files is current as of date of release. Releases of new JVM builds or third party integrations may necessitate changes to information about system requirements or JVM recommendations between releases of Together.

TogetherSoft posts details on system requirements and virtual machine recommendations on the Worldwide Web. For the latest system requirements and virtual machine recommendations for all supported platforms, please visit: www.togethersoft.com/together/requirements/. At the time of release the following information is current:

### JVM Information

Together 4.2 installs the Java(TM) 2 SDK, Standard Edition, Version 1.3.0 on Windows platforms. Together runs by default on this JVM.

Other operating systems require that you obtain the necessary JDK. You can obtain these as separate downloads from various sources on the Web. For requirements information please see sysrequire.html. Information in that file is current as of release date. Note that virtual machine or JDK recommendations can change between Together releases if new versions become available. The most current information on VMs and system requirements is posted on www.togethersoft.com.

### Together system requirements

For Together system requirements-- recommended processors, RAM, disk space, etc. please see sysrequire.html. Information in that file is current as of release date. Changes that may occur between releases are posted to www.togethersoft.com/together/requirements/

## Attention Together 2.x Users

If you are upgrading from Together version 2.x please see Important Information for 2.x Upgrades.

## Installation & Startup Information

Together installation is designed to be easy and straightforward. For Windows installation, an executable installation program guides you through the process, and the Together.exe launcher is written to the bin directory of the installation.

Installation archives for other operating systems are provided in tar.gz and JAR archives containing the entire Together directory structure. You extract the archive into a directory on your computer. A launcher file Together.sh is extracted to the bin directory of the installation. You should review the command line and comments in the Together.sh file to see how your environment variables need to be set so that you can execute Together.sh to launch Together.

Note about JAR installation archive
Because jar archival doesn't save permissions of the archived files, a script for setting permissions is provided in the installation. After unjarring the installation archive, do the following to complete installation:

1. Change directory to the newly created "Together-4.2" directory
2. Run the setpermissions script with the "sh setpermissions.sh" command.

Windows NT installation
When installing Together on Windows NT, make sure you are logged on to the machine with Administrator privileges.

Server installation
If you want to do a server based installation, please install on a local drive first and review the installation topic in Together Help.

On-line Installation & startup notes
Installation Help for all supported platforms is on-line at www.togethersoft.com/readme/. You'll also find information on how to start Together on each of the supported operating systems.

### Launching Together Help

Together on-line Help is implemented under JavaHelp 1.1. After installation, you can either run Help from Together's Help menu when Together is running, or launch it with specially provided command files when Together is not running.

- Help launcher for Windows: %TOGETHER_HOME%/bin/win32/help.bat
- Help launcher for UNIX: %TOGETHER_HOME%/bin/unix/showhelp.sh

### Where to get installation support

Support is provided by TogetherSoft and an international network of Together Exclusive Distributors. If you need installation support, you may contact the Together support center most convenient for you. For complete up-to-date contact information, please visit www.togethersoft.com/support/.

## Known problems

Issue | Description
Editor pane keyboard shortcuts work only after speedmenu access | The Editor pane's keyboard shortcuts do not work until the pane's right-click menu has been invoked one time. We chose not to allow this minor defect to delay delivery of other important functionality our customers have urgently asked for in this release. We apologize for any inconvenience. This problem will be fixed in the next release (scheduled for early Q1/01).
Problems with running Together under Linux with some locales | Different locale settings which have no support in the JVM may exhibit problems. For example, if you start Together under Linux and have an environment variable set: LC_*=ru_RU.KOI8-R, then Together will crash (under Sun vm1.3) or will work, but often throw exceptions (IBM vm1.3). The workaround is to unset the locale variables. (LC_*).
Diagram Printing Problems under Windows 98/95 | Printing of very large diagrams (diagram of java.awt for example) does not work under Windows 95/98. As a workaround, you can break up the content and print several smaller diagrams. Large diagram printing under Windows NT and Windows 2000 has been tested and no problems have been found. When Together is running under JDK 1.2.2 on Win98/95, diagram printing (to printer, not to file) causes an exception window "This program has performed an illegal operation and will be shut down". Workaround: To get diagram printing to work, it is necessary to print something from the Editor pane first. Diagram printing then works for the rest of the session. The problem cited in #1 above is still pertinent
Assembly diagram doesn't reference Home/Remote interfaces for JSP test client | A new feature of v.4.2 is optional generation of a JSP client (for testing a running EJB) during EJB deployment. (See What's New for details.) For this release, it is preferable to initiate the deployment process from a Class diagram rather than an Assembly diagram if you plan to generate the JSP test client because the deployment engine does not spot the Home and Remote interfaces of the EJB implementation class in the Assembly diagram. (This will be fixed in the next release.) Workaround: It is still possible to use an Assembly diagram as basis for deployment. But in order for JSP client generation to work, you will need to explicitly add shortcuts for the EJB's Home and Remote interfaces to the diagram, since these are not automatically referenced when you add the EJB implementation class to the diagram.
Unexpected Breakpoint Behavior | When using the Debugger with the HotSpot VM (which is how Together is configured by default when it uses JRE 1.3), there are some differences in behavior from the standard 1.2 VM. For example, the HotSpot VM doesn't support the synchronization monitors, fields' breakpoints, and so on. Thus, you may see seemingly strange behavior when stepping through and into code (remember, Hotspot may be doing some optimizations under the covers). To get the breakpoints to work as you expect, go to your Debugger config options (Options | Default: Debugger: Arguments and parameters: Application: VM options) and enter -classic in the VM options field. For Applet debugging, do the same for Options | Default: Debugger: Arguments and parameters: Appliet: VM options Note:This value can also be entered directly in the VM options field of the Arguments and Parameters dialog, invoked by the Run in Debugger menu/shortcut command.
### VM crashes when Debugger gets empty this variable | It has been reported that the Debugger can crash the VM (both the JDK1.2 version and the JDK 1.3 Classic). Investigation shows that such crash can occur when you attempt to get the value of a this variable of type String which has a value of "" (i.e. empty string). This is Sun's bug, and one which we do not attempt to get around. That is why the HotSpot VM is preferable to be used by default.
Full-text search in Help does not work under JDK 1.3 | This is a known problem documented by Sun: full-text search in JavaHelp does not work under JDK 1.3. It does work under JDK 1.2x. Until this problem is fixed by Sun, TogetherSoft will provide a searchable version of Together Help in an alternative format at the Together Community website (www.togethercommunity.com).

### Additional notes

#### Changed Inspector behavior

In property inspectors, changes are applied when you press Enter (dialog remains open), when you press Ctrl+Enter (dialog closes), when you exit the edited property field, or when the open inspector dialog loses focus.

If you have changes pending in any field and you click the dialog's Close button (x), pending changes are not saved. This is a change in behavior from previous version 4.1.

#### Early-release support for HP-UX

Version 4.2 includes early release support for the HP-UX operating system. This means that most functionality that works on other platforms works on HP-UX, but further testing is still necessary. Please be aware that TogetherSoft has not officially announced support for this OS, and you should use Together on HP-UX at your own discretion and risk. TogetherSoft welcomes your feedback about the performance of Together under HP-UX.

#### Debugger config option setting for HP-UX users

Options | Default : Debugger: Arguments and Parameters: Application:VM Options, and
Options | Default : Debugger: Arguments and Parameters: Applet:VM Options

In this field type -classic for classic debug mode. Otherwise, the debugger does not function properly under HP-UX.

#### Dropped module

The module "WLE CORBA Wizard" for development of CORBA application for BEA Weblogic Enterprise was added to the installation of version 4.1. This module has been dropped from the 4.2 installation due to a number of issues that could not be resolved by release date.

#### Inspector customization is backward compatible to version 3.0

In version 4.0, the implementation of the Inspector moved from configuration properties to the Open API and customizations of the inspector.config file from version 3.x did not appear in the new Inspector in version 4.0. Backward compatibility was added to release 4.1. Documentation and an example of how to activate config-based Inspector customizations is provided in %TOGETHER_HOME%/inspector.config .

#### Java SDK Location

You must specify the location of the recommended Java version (JDK/JRE) for your operating system in Options | Tools: JDK Home. If the SDK is not present in the expected location, Together's integrated project make will fail.

For Windows users who download the full installation of Together, this is not an issue... the installer configures the required location. Those who download the Windows installer minus SDK/JRE, and users of non-Win32 operating systems should check for the correct setting of this configuration option before using make.

#### New include directives for C++ headers

Include files for VC are added to the installation:

%TGH%/lib/pi_vc_stl.inc
%TGH%/lib/pi_vc_stdlib.inc

They contain set of #include directives for certain Microsoft Visual C++ headers.

pi_vc_stl.inc: 13 headers related only VC's STL (according to MSDN)
pi_vc_stdlib.inc: complete VC's Standard c++ library (according to MSDN)

The installation also contains include files

%TGH%/lib/pi_bcpp_stl.inc
%TGH%/lib/pi_bcpp_stdlib.inc
%TGH%/lib/pi_bcb_stdlib.inc

that store the sets of #include directives for Borland C++ and Borland C++ Builder headers.

With appropriately modified preinclude.inc files, these provide the possibility to make defines and symbols from Visual C++ STL, Standard C++ Library, or Borland C++ libraries available in a Together model.

To include this support, you should add the folder with the relevant headers to the Search/Classpath (File | Project Properties - Advanced) in a Together project. Then define the wrapped Together macros

TS_PREINCLUDE_VC_STL
TS_PREINCLUDE_VC_STDLIB
TS_PREINCLUDE_BCPP_STL
TS_PREINCLUDE_BCPP_STDLIB
TS_PREINCLUDE_BCB_STDLIB

respectively, using Options | [level] - Source Code page - C++ -

#### Recommended PVCS version

Together has problems when using PVCS 6.5 as SCC provider for version control. PVCS VM 6.6 has demonstrated no problems working with Together and is recommended for those planning to integrate PCVS for version control.

#### CVS version control integration notes

1. This note applies only if you use CVS Client-Server for version control. The version of jcvs used by Together's version control integration module appears not to read Entries.log files. These files are created by command-line cvs at checkout time and seem to be merged in regular Entries after update. Thus, to ensure there are no Entries.log files in your working directory, you need to run cvs update from project root after checking out sources. This problem only occurs on a freshly checked out source tree, not if it was updated at least once. Thus, it cannot be remedied using only Together... run update on your freshly checked-out sources before using Together's CVS integration.
2. If a source tree was checked out using a cvs client version later than version 1.10, the Together CVS system does not work. This is because the format of internal CVS files has changed. Version 1.10.x is not an official release and thus is not yet supported in Together. Only version 1.10 of the cvs client is compatible with Together.