Version 6.2

Updated November 2, 2003

Table of Contents

1.0 System Requirements
    1.1 Operating Systems
    1.2 IDE Platforms
    1.3 Hardware and Storage
    1.4 JDK
2.0 Installation and Startup
3.0 Licensing
4.0 Updating from a Previous Version
5.0 Known Issues and Limitations
6.0 Finding Out More
    6.1 Getting Started Guide
    6.2 Online Help
    6.3 On the Web
7.0 Getting Help

1.0 System Requirements

1.1 Operating Systems

• Windows 2000 (Service Pack 2 or higher)
• Windows XP Professional

1.2 IDE Platforms

1.3 Hardware and Storage

1.4 JDK/JRE

Back to contents.

2.0 Installation and Startup

Important:

• Do not install Together 6.2 over (in the same folder as) an older version of Together. Also, if you have other Together editions installed (such as Borland^® Together^® Edition for Websphere^® Studio or Borland^® Together^® Edition for Eclipse) do not install Borland^® Together^® Edition for SAP Netweaver^™ Developer Studio over (in the same folder as) the other versions. For related information, see Updating from a Previous Version.
• If the installer offers you a choice of any JDK other than 1.3.1, you should not accept it. Together supports jdk 1.3.1.
  

These instructions assume that you already have SAP NetWeaver™ Developer Studio 2.0.0 (SAP) or Eclipse installed.

1. If you have not done so, visit http://www.borland.com/company/contact/where_to_buy.html for information on purchasing and downloading Together.

2. Launch the executable file, either from an installation CD or the location to which you downloaded the web-based file.

3. If downloaded, double-click on the file to begin installation.

4. InstallAnywhere opens. Click Next as prompted.

5. Click the radio button to indicate acceptance of the license agreement. Click Next.

6. Enter the path and folder name where Together should be installed, or click Choose to browse. Click Next. If the directory does not exist, it will be created.

7. Enter the path to your SAP NetWeaver™ Developer Studio 2.0.0 directory, or click Choose to browse.

8. Select a Java Virtual Machine. The installer detects JVMs on your machine, or you may click Choose Another to locate one manually. Click Next.

9. Choose a location for your Together startup icons. If you select "In a new Program Group" or "Other" you may accept the default or enter any name you wish. This is the name that will appear in your Start menu. Click Next.

10. If your preferences are acceptable, click Install.

11. As you specify, Together will either start automatically or you can navigate to it according the install preferences you selected. (If you accepted the defaults, Together appears as an option on your Start > Programs menu.) Click Next.

12. When InstallAnywhere finishes, click Done.

13. For licensing questions, refer to Licensing below.

Back to contents.

3.0 Licensing

5.0 Known Issues and Limitations

New issues and workarounds may be identified after release. For the latest list, please visit http://info.borland.com/techpubs/together/.

1. Except for Singleton and Proxy, the Patterns Recognizer does not recognize Gang of Four (GoF) patterns unless they were created using the Together Apply Pattern wizard.

2. If you are using SDK/JDK 1.4, you need to specify a location for document generation other than the default (or remove any spaces from the default destination). If not, the documentation will not open in the default browser.

3. When applying a recognized pattern in a diagram, the diagram elements can become overcrowded. As a solution, consider manual diagram layout.

4. In the document generation output, the index link in the navigation bar of the javadoc frame displays only java elements, not other diagram elements. To see all elements, use the navigation applet in the Project frame.

5. XMI issues:
   

   •	Rational Rose cannot import swimlanes from XMI. When activity diagrams with swimlane elements are exported from Together using XMI, the elements do not appear in swimlanes in Rational Rose.
   •	When importing from Rational Rose, diagrams in a use case may not import correctly. In a recent test, for instance, the diagrams in the use case "manage order" in Rose's sample "order system" were missing when the project was imported to Together. In an earlier test, they came into Together as empty sequence diagrams in the "com" package. Import of the "Overview of type libraries"component diagram in order system produced similar results; the diagram was empty.
   •	If you use the XMI feature to import UML 1.4 (OMG), you should view the imported elements first in the UML Navigator (as opposed to the UML Explorer) by turning off the filter "Hide design elements." You can access filters by clicking the down arrow on the title bar of the UML Navigator. You can then include the imported elements in a diagram manually using the shortcut feature in the Diagram View (New > Shortcut on the context menu). Note that the elements can successfully be imported using other supported XMI formats: XMI for UML 1.3 (Unisys Extension), XMI for UML 1.3 (Unisys Extension, Recommended for TCC) and XMI for UML 1.3 (Unisys Extension, Recommended for Rose).

6. If you close projects in the Navigator view, then switch to the UML Navigator view and export a project for UML documentation, you may receive an exception error. This is an Eclipse issue. To work around, ignore the exception and continue.

7. If you mistakenly launch a second instance of Together, an error message displays. Multiple instances cannot be launched. You can, however, use Window > New Window to open a new workbench window.

8. In the HTML-based output of document generation, you can navigate between documentation for elements by clicking on their SVG graphics in the diagram frame. However, if an element did not completely fit on its diagram before document generation, it will not be possible to navigate to its documentation in this way. Also, zooming in and out may cause SVG images to go partially out of view or seem to disappear. Adjust the view as required. The behavior of SVG images (such as those in the output of document generation) is defined by the SVG viewer, which is not a Together product.

9. When you copy a package in a referenced project from the UML Navigator to your project, the contents of the package will not be copied. It will be copied, however, if using the UML Explorer view.
   

10. Refactoring does not occur for elements whose names remain the defaults assigned to them upon their creation (Class1, Attribute1, etc.). Elements must be renamed to a non-default name for refactoring to take place . To enable refactoring of elements upon creation, select the last option in the Source code groupbox in the Java preferences dialog (navigation: Window > Preferences > Modeling > Java).
    

11. When adding shortcuts to elements containing subelements, the shortcuts lose their view properties (such as background color, foreground color, and 3D look). Also, when adding a shortcut of a Node element containing two Component subelements onto another diagram, the Component subelements overlap. You will need to manually expand the Node element, and move the top Component to reveal the other Component subelement.

12. Currently, only source classifiers can be used as pattern participants. Compiled classifiers cannot. This applies to library elements as well.

13. You can view, but should not edit design diagram files in the editor view. (These files are automatically created/updated by Together and visible in the UML Explorer when the filter is off.) If edited and saved in this manner, the diagram can be lost.

14. The Undo and Redo commands do not work in the UML Explorer.

15. When running QA or generating documentation including a QA report for large projects, you may receive an OutOfMemory error. If this happens, restart Together.

16. After generating documentation for a large project, the results may not display correctly in Internet Explorer unless the Sun Java plugin is turned off.

17. When the option, Save resources automatically on changes in the diagram, is off (Windows > Preferences > Modeling > Java), exceptions will occur when you rename a property using the in-place editor, and the accessors are not changed. Exceptions also occur when you use the in-place editor to add parameters to a method. Be sure to manually save before using the in-place editor.

18. Though the Hyperlink command is available, Hyperlink > Edit does not function for all items listed in the UML Navigator. Both menu commands are available, however, in the context menu commands of the Diagram view.

19. Links to class shortcuts disappear when renaming the container package.

20. To avoid possible corruption, do not place .jar files containing com.borland.sanctuary in the JVM_HOME/lib/ext folder before registering Together.

21. Note that when adding a class by pattern to a class diagram (as opposed to a package diagram) the new classes/interfaces appear on the package diagram, not the class diagram.

22. When using cut/paste to move a package with shortcuts to other classes, the shortcuts may disappear. Instead, use drag and drop.

23. You can copy and paste within the UML Explorer. However, note that there is a clipboard for Java elements and a separate clipboard for all subelements on diagram elements. Thus, you cannot past non-Java elements in the UML Explorer.

24. There is no Class by Pattern button in the Diagram View for EJB diagrams. Instead, use the Diagram View context menu. Similarly, the Link by Pattern action is only possible for existing links, and should also be done using the context menu.

25. If you have used other Together products, you may expect package element names to turn from black to blue once hyperlinked. Due to the unique nature of the SAP NetWeaver(tm) Developer Studio 2.0.0 IDE, this does not occur with Together packages.

26. The SAP NetWeaver(tm) Developer Studio 2.0.0 IDE and Together each has a different default location for its workspace. Consider this when synchronizing project work. If you have used the SAP NetWeaver(tm) Developer Studio 2.0.0 IDE and its default (or your own) workspace to create projects before installing Together, Together will not find your earlier work when it first opens. To correct this, close and launch SAP NetWeaver(tm) Developer Studio 2.0.0 as you did prior to installing Together.

27. You may encounter exceptions when using the Properties view to create a hyperlink to an element if the model changes while browsing for the element.

28. You cannot create class/interface library shortcuts using the Add Linked context command of the Diagram View. Instead, use New > Shortcuts.

29. When first generating documents using a new workspace, you may encounter two undefined elements on the second page of the Wizard. You should ignore these elements. They will not appear during subsequent document generation attempts.
    
    Back to contents.

6.0 Finding Out More

6.1 Getting Started Guide

You can find this tutorial covering most of the major features in Together in the docs directory of your installation: $Together$/docs/GettingStarted.pdf.

Back to contents.

6.2 Online Help

Together provides online help through the Together help browser. From the menubar, select Help > Help Contents. When the help browser opens, click Borland^® Together^® Edition for SAP NetWeaver(TM) Developer Studio User Guide. Expand the nodes to see the different help sections.

Back to contents.

6.3 Documents on Our Website

The latest version of this readme file, the Borland^® Together^® Edition for SAP NetWeaver(TM) Developer Studio Getting Started Guide, and other documentation are available on our website: http://info.borland.com/techpubs/together/.

Back to contents.

7.0 Getting Help

E-mail questions or comments to together-support@borland.com. Visit Borland at www.borland.com.

Back to contents.

This product includes software developed by the Eclipse Project (http://www.eclipse.org).

Copyright © 2002-2003 TogetherSoft Corporation, a wholly owned subsidiary of Borland Software Corporation. All rights reserved. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. SAP NetWeaver is a trademark of SAP AG. All other marks are the property of their respective owners. IBM and WebSphere are trademarks of IBM Corp. in the United States, other countries, or both.