The following operating systems are tested and supported: 

• Windows NT 4 SP6a
• Windows 2000 Professional, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
• Windows 2000 Server, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
• Windows 2000 Advanced Server, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
• Windows XP Professional, Service Pack 1 and Service Pack 2 Release Candidate 2

Notes:

• IBM Rational v2003.06.13 products do not officially support Windows XP Professional, SP2, and the information in this document is based on testing done with a Windows XP SP2 release candidate. The production release of Windows XP SP2 was not available for final testing at the time this document was finalized. Contact IBM Rational Software Support to obtain the latest information on Windows XP SP2 support. You can also check the latest version of this document in the IBM Publications Center at www.ibm.com/shop/publications/order. Search for "GI11-4685-03".
• Windows NT is not a supported operating system for Visual Studio .NET 2003.

Rational XDE supports data modeling for the ANSI SQL 92 standard and the following database management systems (DBMS):

• IBM DB2 UDB 5.2, 6.1, 7.0, and 8.0
• IBM DB2 UDB zSeries 5.x, 6.x, and 7.x
• IBM DB2 UDB iSeries v5 r2
• Oracle 7.3, 8.x, and 9i for Windows NT
• Microsoft SQL Server 6.5, 7.0, and 2000
• Sybase Adaptive Server 12.x

Category

ID

Description

The online Help for freezing a model incorrectly states an expected setting. In steps 3 and 4 of the "Freezing Include Models" topic, you are told to look for the text unitPolicy ="1". Instead, you will normally see unitPolicy="0" when opening a .mdx file.

When upgrading from Rational XDE Version 2003.06.12 to 2003.06.13, code template CLR callouts do not operate.

Workaround: Following an upgrade, CalloutCLRManager.dll must be reregistered manually using the regasm.exe utility.

To register using the command line:

1. Change the directory to <install-location>\Rational\XDE\Addins\codetemplates\assemblies.
2. Enter the following on one line, where drive is the drive where the MS .NET Framework is located and version-number is the Framework version number, such as 1.0.3705:
   <drive>:\Windows\Microsoft.NET\Framework\v<version-number>\RegAsm.exe CalloutCLRManager.dll

When working in a team development environment, unsynchronized items can result if one user accesses a solution using Rational XDE Version 2003.06.12, and a second user accesses the solution using version 2003.06.13 of XDE. The synchronization problem can happen if the version 2003.06.12 user fails to synchronize the solution before closing the solution, and the second user opens the solution from the 2003.06.13 version of XDE to work on the same model elements.

Workaround: Use one of the following workarounds:

• Synchronize a solution before closing it and delivering changes to your configuration-management solution. This is a best practice and helps prevent many synchronization issues.
• Before you begin to make additional modifications in a solution, run the Reset Synchronizer command to ensure that all prior changes in code and model are synchronized:
  1. After rebasing your project, open the shared solution.
  2. Right-click the solution or project node in the Solution Explorer, or right-click the model
     root in the Model Explorer, and then click Reset Synchronizer.

When you publish a model, upon first opening the model you may see the following error message, "Page cannot be displayed."

Workaround: The Web publishing facility cannot access the contents of a model unless the Model Explorer in XDE can access them. For example, constraints that are not visible in the Model Explorer will not be published. The filter settings for the Model Explorer determine what is visible.

To modify filter settings for the Model Explorer:

1. On the Window menu, click Preferences.
2. Expand Rational XDE, click Model Explorer, and then click the Filter Settings button. The Model Explorer Filter Settings dialog box is displayed.
3. In the Display the following elements list, select all the model elements you want to appear in the Model Explorer. Any elements you do not select will be hidden when publishing.
4. Click OK.

Category

ID

Description

If you rename a model element or add a diagram to a saved and checked-in model, the dialog box that appears has buttons only for Checkout, Edit, and Help. The dialog box does not have a Cancel button.

If you click the Checkout button, and then click the Cancel button in the next dialog box, the in-memory changes are kept rather than being rolled back.

Workaround: If you want to add a diagram to a saved and checked-in model, you need to explicitly check out the storage unit of the diagram. The checkout must be done before making any changes to the model. If you did not check out the model, you can recover by closing the model without saving the changes.

Rational XDE customers who have installed recent ClearCase v2002.05.00 Windows patches (for example, patch 24 and 26) will start receiving prompts to reinstall the XDE/ClearCase Type Manager Installer. This is due to the ClearCase patch overwriting the XDE bindings in ClearCase control files that steer compare and merge operations to the XDE compare/merge facility.

Workaround: Uninstall and then perform a reinstall of the XDE/ClearCase Type Manager Installer on the server and on the client. This will have to be repeated after every ClearCase patch install. Monitor future ClearCase patches for fixes for this issue.

• IRXEPatCTCalloutData
  • IRXECodeTemplatesExpansionData
  • IRXEPatCalloutData
    • IRXEPatVetoableCalloutData
      • IRXEPatternsOnArgumentValueCalloutData
      • IRXEPatternsOnBindCalloutData
      • IRXEPatternsOptionalElementCalloutData
      • IRXEPatternsWizardCleanUpCalloutData
      • IRXEPatternsWizardStartUpCalloutData
      • IRXEPatternsExpansionLocationCalloutData
    • IRXEPatAbortableCalloutData
      • IRXEPatExpansionCalloutData
        • IRXEPatternsPreExpandCalloutData
        • IRXEPatternsPostExpandCalloutData
      • IRXEPatternsPreApplyCalloutData
      • IRXEPatternsPostApplyCalloutData
      • IRXEPatternsErrorCalloutData
      • IRXEPatternsPostMappingCalloutData
      • IRXEPatternsCollectionCalloutData
    • IRXEPatElementCalloutData
      • IRXEPatternsMergeCalloutData
      • IRXEPatternsMatchCalloutData
      • IRXEPatternsScriptletCalloutData

• IRXEPatApplicationMap
• IRXEPatExpansionMap
• IRXEPatCTCalloutUser
• IRXECodeTemplatesExpansion
• IRXEPatternsCallout
• RXEPatCTArgumentTypes
• RXEPatApplicationEvents
• RXEPatNextOptions
• RXEPatElementMergeBehaviors

When upgrading from a previous 2003 version of an IBM Rational product using the 2003.06.12 CDs, the following message may continue to display with Disk 1 in the CD drive: “Please insert the disk: Disk 1”

This happens when the original installation was performed using a designated release area created through the "Enterprise Deployment" install option, or for a product that was downloaded from the Web.

Workaround: Read the related technical note. Go to www.ibm.com/software/rational/support/ and search for the text "upgrade insert disk 1.”

The default font used on the drawing surface is not suitable for all languages (especially Asian languages).

Workaround: Users should change the default font face in the Options dialog box (on the Tools menu) by expanding Rational XDE and Appearance, and then clicking General. Choose a font that supports your character set. Also, select Default for new models in the Settings for list to ensure that the change applies to all new models.

An English-language error message appears when starting the Rational Unified Process, or RUP, and RUP's Extended Help, if you have not installed the Sun Java Runtime Environment (JRE) plug-in, version 1.4.1, for your Web browser. For a workaround, see defect 245756 under "General XDE."

Publishing a model to a folder that has double-byte characters in the name causes the tree control to fail in the published model.

Workaround: Replace the default Sun Java Runtime Environment (JRE) version 1.3x with version 1.4.1_01.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.0\ToolsOptionsPages

On a standard Visual Studio .NET installation with XDE installed, the number of Options pages exceeds the aforementioned limit. Therefore, the following two Rational XDE pages in the Options dialog box for Visual C++ settings may not be displayed:

• Rational XDE\Round-Trip Engineering\Visual C++ Settings\Visual C++ Initial File Settings
• Rational XDE\Round-Trip Engineering\Visual C++ Settings\Visual C++ Containers

As a result, it is not possible to configure the settings on the affected pages.

Workarounds:

• Manually remove some of the registry entries for pages that are not used.
• Upgrade to Visual Studio .NET 2003.
• Microsoft may include a fix in a future service pack for Visual Studio .NET 2002. Check the MSDN download site for the availability of service packs for VS .NET 2002.

If you create a project with Rational XDE models in Visual Studio .NET 2002, and then subsequently upgrade the IDE to Visual Studio .NET 2003, upon reopening the project, the Miscellaneous Files project in the Solution Explorer may appear to have duplicate versions of each referenced assembly model. This condition occurs after you reinstall XDE in Visual Studio .NET 2003, open up the project, and then synchronize the project or open the model.

The apparently duplicate models are actually separate versions. After the upgrade to the new IDE version, both Visual Studio 2002 and 2003 versions of each referenced assembly model are shown under the Miscellaneous Files project in the Solution Explorer. Although the references to assembly models point correctly to the Visual Studio .NET 2003 versions (vs7rte\vsnet\Models\v1.1\*.mdx), the display of the apparent duplicate assembly models may be confusing. However, this condition does not affect synchronization or cause actual problems of any kind.

Workaround:

To remove unused duplicate reference models from the project:

1. Open your project in Visual Studio .NET 2003.
2. In the Solution Explorer, select a reference model file in the Miscellaneous Files project.
3. In the Properties window, view the File Path property.
4. For those reference models that reside in the ..\vs7rte\vsnet\Models\v1.0 directory, right-click the model, and then click Remove.
5. Repeat steps 2 through 4 for each duplicate reference model.
6. Close the solution (save as needed) and exit Visual Studio .NET.
   When you open VS .NET the next time, you should not have this issue.

Note: This procedure removes the model files as project items from the Miscellaneous Files project, but it does not delete them from the file system. If you remove a correct model by mistake, the model will be recreated in the project at the next synchronization.

Visual Studio .NET 2003 (devenv.exe) may hang indefinitely when using Visual C++ support in Rational XDE 2003.06.12. This can happen when running on:

• Windows 2000 Professional SP2, SP3, or SP4
• Windows 2000 Server SP2, SP3, or SP4

Workaround: If this problem occurs under this set of conditions, you must reboot the computer by turning it off and back on. This issue with the Windows 2000 kernel is Microsoft support case SRX031219604116. For the related Knowledge Base (KB) article and to learn about any hotfix, see article number 837443 at http://support.microsoft.com/?id=837443. IBM Rational customers can also contact Microsoft support directly for the hotfix, at the toll-free phone number(s) listed on http://support.microsoft.com, by simply referencing the KB article number (837443) for this problem.

Error messages may appear during synchronization if you have reverted from the Rational XDE version 2003.06.12 Service Release to an earlier version of XDE.

Workaround: Use the following procedure as a guide when synchronizing.

1. Create a C# Class Library project.
2. To synchronize, click the Synchronize button on the toolbar.
   The Unknown RAS File Type dialog box opens.
3. Type .mdx and click OK.
   The RTE.ModelMonitor.UpgradeProfile dialog box opens.
4. Click OK.
   The synchronization completes.
5. Delete the rte.prx profile located in the default directory. Typically, this is
   C:\Documents and Settings\user\Application Data\Rational\XDE\Profiles.

The next time you synchronize, the correct profile is applied.

If you are using Rational XDE with Microsoft Visual Studio .NET 2003, you may see the following error message after using the Visual C++ Round-Trip Engineering feature in a solution containing a Managed C++ Windows Form project and adding a new form to the project:

"The designer could not be shown for this file because none of the classes within it can be designed."

The form fails to open up in the designer and the message appears in both the designer form and the task list. This error happens most frequently on Windows 2000 and is the result of an "out of memory" problem.

Workaround: To free up contiguous memory:

1. Close the solution (first use Save All as appropriate).
2. Close Visual Studio .NET.
3. Start Visual Studio .NET
4. Open the solution. The form opens correctly.

If you filter out a particular element type (such as Text), hot spots that have no associated links may be created in the published model.

Workaround: Remove all filters before publishing a model.

Workaround: If you want to publish a model to the Web, specify only absolute paths for all linked files.

To specify an absolute path for a linked external file, do the following:

1. In the Model Explorer, right-click the model element to which you want to link an external file, and then click Add UML > URL.
2. In the URL Input Dialog dialog box, clear the Use relative path representation for all file references check box.
3. Click Browse, browse to and select the file that you want to link to the model element, and then click Open.
4. Click OK in the URL Input Dialog dialog box.

Use the following steps to increase the JVM size setting within the Registry:

1. Close Rational XDE and Microsoft Visual Studio .NET.
2. Open the Run tool available from the Start menu.
3. Type regedit in the Run window, and then click OK.
4. Navigate to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\RationalSoftware\RJCB\JVMs\XdeJavascriptJvm.
5. Locate the JvmOptions string value.
6. Change the "-Xmx256m" JVMOptions string value to a bigger size, such as "-Xmx448m".

Note: The actual size of the JVM should be smaller than the physical RAM size of the computer, and must be multiple increments of 1K (or 1024 bytes).

When you export a Rational XDE model using the XML Metadata Interchange (XMI) file format, the following harmless error messages may appear if the ClassicRose profile is applied to the model you are trying to export and the model contains XDE-created realization and abstraction relationships:

• Tagged value "ClassicRose::Visibility" not found for element "xx_Abstraction"
• Tagged value "ClassicRose::Friend" not found for element "xx_Abstraction"
• Tagged value "ClassicRose::MultiplicityTo" not found for element "xx_Abstraction"
• Tagged value "ClassicRose::MultiplicityFrom" not found for element "xx_Abstraction"

The error messages appear because there is no UML:Realization metaclass in UML/XMI. On XMI export, Rational XDE realizations and abstractions stereotyped as "Realize" are exported as UML:Abstraction stereotyped as "Realize". On XMI import back into Rational XDE, all abstractions with “Realize” stereotypes become realization relationships in XDE.

If you upgrade your Microsoft Windows 2000 Terminal Server to Service Pack 4 (SP4) from SP3 and then try to use the Rational XDE version 2003.06.12 Service Release, you may experience a package load failure.

Then, on exiting Microsoft Visual Studio .NET, you may get an application error:

The instruction at "0x791bad3a" referenced memory at :0x00000050". The memory could not be "read".

This behavior happens when the following conditions are met:

• You log on to the Terminal Server as a limited user (a user without administrator rights).
• The Terminal Server is running Windows 2000 SP4 and has the .NET Framework 1.0 SP2 or earlier installed.
• You have not installed the .NET Framework 1.1 or later on the Terminal Server.

Workaround: This is a known Microsoft issue. Please refer to http://support.microsoft.com/default.aspx?kbid=823485.
To work around this problem, install the Microsoft .NET Framework 1.1 on the Windows 2000 SP4-based Terminal Server.

When you export a Rational XDE model to the Unisys 1.3.5 file format, multiple state and final state actions (such as do, exit, and entry) are not exported. When you import the Unisys 1.3.5 file back into XDE, only one action (a do action) is imported. All actions (UninterpretedActions) should export and import correctly.

Workaround: Remove multiple actions that reside within an activity model element before exporting a model in the Unisys 1.3.5 format.

Workaround: Add one event per transition when you want to associate multiple events with a transition.

Workaround: Change the duplicate attribute "body=" to "language=" in the exported XMI file.

Associating one constraint with multiple model elements causes XDE to hang during an XMI import.

Workaround: Only associate one constraint with one model element.

The Rational Unified Process, or RUP, and RUP's Extended Help, will not work if you have not installed the Sun Java Runtime Environment (JRE) plug-in, version 1.4.1, for your Web browser. In addition, the related error message appears in English and is not localized.

Workaround: Install Sun JRE 1.4.1.

To install the JRE plug-in, do one of the following:

• If you have installed RUP from a CD, you can execute the JRE plug-in installer from the Rational common directory:
  [INSTALLDIR]\common\rwp\JRE_plugins\j2re-1_4_1-windows-i586-i.exe
  where [INSTALLDIR] is the installed Rational products directory. For example,
  C:\Program Files\Rational.
• Download and install the JRE from the Sun Java Web site, using this link:
  http://java.sun.com/products/archive/j2se/1.4.1/index.html

For other options, please contact your organization's technical support staff.

When finished installing, restart RUP or Extended Help.

Category

ID

Description

513643

When working with XDE, two users may create storage units with the same name in their versions of the same directory. When the users attempt to check in or deliver their work and a merge is triggered, ClearCase will prompt the user to choose between the two storage units and XDE Compare/Merge will independently ask the user to choose between the two model elements associated with those storage units. In this situation, it is important that you choose consistently. That is, if you choose one user's storage unit, then you should also choose that user's model element associated with that storage unit. For example, suppose both users created class1 as a separate unit in a file named class1.clx in their versions of the same directory. The ClearCase directory merge will ask which of the two class1.clx files should be present in the merged directory and XDE Compare/Merge will ask which of the two class1 model elements to present in the merged model. If the user chooses the first user's class1.clx file during the ClearCase directory merge, then the user should also choose that user's class1 model element during the XDE Compare/Merge session.

Note that if the model element names differ but the storage units are the same, a similar situation arises but the behavior differs. For example, both users might initially create class1 in storage units class1.clx in their versions of the same directory. Then, the first user renames the class1 model element to be myclass. The storage unit retains the name class1.clx. However, in this case XDE Compare/Merge will allow both model elements class1 and myclass into the merge result model even though the ClearCase directory merge will permit only one class1.clx to reside in the directory. The resulting model will be unable to locate the missing storage unit. To recover from this, you should rename the missing class1.clx file to some other name and then locate this renamed file using the Browse to Unit command on the shortcut menu for the model element that is missing its unit. Perform the rename using the ClearCase Explorer or at a cleartool command line so that the history of the renamed file (which includes the file with its original name) is preserved.

It is possible for newer versions of a model to be loaded during a rebase, update, or deliver operation; therefore, we recommend that the user do the following when performing one of these operations:

1. Save any unsaved changes.
2. Perform the operation (rebase, update, or deliver).
3. In the Model Explorer, click the Reload All button.

If you have no existing data model, the Class to Table Transformation dialog box does not open when you use the Class to Table command on the Transform menu.

Publishing a model to a folder that has double-byte characters in the name causes the tree control to fail in the published model.

When uninstalling Rational XDE version 2003.06.12, two DLLs may be removed that are required but not reinstalled if you install another version of XDE, including version 2003.06.00.

When working in a team development environment, unsynchronized items can result if one user accesses a solution using Rational XDE Version 2003.06.12, and a second user accesses the solution using version 2003.06.13 of XDE. The synchronization problem can happen if the version 2003.06.12 user fails to synchronize the solution before closing the solution, and the second user opens the solution from the 2003.06.13 version of XDE to work on the same model elements.

For generalization, dependencies and realizations, the methods/properties to access the end elements return the opposite end. Specifically:

• IRXEGeneralization.SuperElement returns SubElement
• IRXEGeneralization.SubElement returns SuperElement
• IRXEDependency.SupplierElement returns ClientElement
• IRXEDependency.ClientElement returns SupplierElement
• IRXERealization.SpecificationElement returns ImplementationElement
• IRXERealization.ImplementationElement returns SpecificationElement

The methods IRXEReference.Resolve() and IRXEReference.getRefModel() always return Null. A call to resolve() will resolve a reference, if possible, but it will still return Null.

Visual Trace does not support tracing ASP.NET applications on the Microsoft .NET Framework version 1.1.

If you are using an installation of Rational XDE that was installed by another user, you may be prompted to install additional components when you attempt to publish a model. The suggested installation is unnecessary; you should click Cancel. Publishing will then proceed normally.

If you allow the process to finish by not clicking Cancel, a second dialog box appears that suggests a restart. You should click No. If you click OK, XDE restarts and the published model is incomplete.

In a published model, displays that rely on a relationship with a MessageEnd object fail. These failures include:

• A sender/receiver table.
• Sequence elements in a sequence diagram that contains a reference between an operation and a message.

The cross-model reference adornment is not displayed in the correct position in the print preview or when you paste the shape into other applications such as text editors.

When you open a saved model that initiates specific internal processes to open a diagram, the model appears in the unsaved or modified state (with an asterisk next to the model name in the Model Explorer), even if you made no modifications to the model. You can safely save or discard the changes without data loss.

When you work with subunits, it is recommended that you save your work by using the Save All command on the File menu. If you use the Save command (or Ctrl+S), your work may not be saved consistently.

For example, you may change one subunit, which results in changes in two other subunits. If you save only the first subunit and not the two others, the files saved on disk will be inconsistent with one another. If, instead, you use the File > Save All command, all three changed files will be saved to disk and the files on disk will be consistent with one another.

You are prompted to check out the file if you open a diagram within a source-controlled model and page breaks must be updated due to prior changes in the diagram elements. However, clicking Cancel does not dismiss the dialog box. (This happens if the Prompt for check out setting is selected on the Source Control, General page of the Options dialog box.)

Users who have installed Rational XDE Developer Plus on Windows NT may find that saving a blank model assigns a Rational RequisitePro applied profile to the model.

When you import a model file from Rational Rose into Rational XDE, classes that have stereotypes may become very large in the diagram window.

Category

ID

Description

The online Help for Data Modeling states that you can assign a domain to an attribute in a logical data model. This functionality is not supported.

Rational XDE reverse engineers Microsoft Visual Studio .NET Web projects into a new model file with no contents from the source project.

This issue was fixed by changing the Rational XDE HTML parser to be case-insensitive when looking for HTML tags. If the parser is unable to parse a file, it reports the error and continues with the next file instead of aborting the synchronization. Writing of aspx, asmx, and ascx files is now more robust on both VS.NET 7.0 and 7.1.

A reverse-engineered class is added to code within a code template expansion, leading to unexpected behavior. If a class has a code template bound to it, then a nested class, field, or operation added to that class in the model may get generated within the code template expansion in code during synchronization. This added item is deleted during code template expansion upon the next synchronization.

XDE code templates bound to classes causes data loss. The binding of a code template to a class while at the same time modifying a model element in the class (for example, adding a parameter to an operation) causes the class to be deleted upon synchronization.

If you are using Microsoft Visual Studio .NET 2003 and are a member of the the Debugger Users group in Windows, the list of classes you select for monitoring by Visual Trace wil not be retained once you close the Class Selection Wizard.

Visual Trace is not always able to differentiate between applications launched by a user and other processes started as a result of an IDE action. This can result in Visual Trace attempting to trace processes unintentionally and displaying the following warning: "Visual Trace supports only tracing one application at a time. Please stop all other applications being traced and restart the application."

The following defect is now associated with solution 187450534. Please refer to this number when calling technical support for additional information.

Visual Trace uses a socket to connect to the application being traced. If a connection cannot be established, the following warning is displayed: "Visual Trace could not establish a socket connection with target."

Category

ID

Description