Introduction | System Requirements | Installation | Start Working with Cameo DataHub | Troubleshooting | More information and support
Cameo DataHub consists of DataHub Server and DataHub Plugin. DataHub enables you to import, export, synchronize, and make data references in the following formats: CSV files, MagicDraw UML/ SysML/UPDM(DoDAF and MODAF) elements, Cameo Requirements+ requirements, DOORS objects, and RequisitePro requirements.
DataHub reads data from a repository in CSV format. DataHub Plugin is available for MagicDraw, Cameo Requirements+, and two third-party tools:
MagicDraw (MagicDraw
Cameo Requirements+ (Cameo Requirements+
RequisitePro (IBM® Rational® RequisitePro® 7.0)
DOORS (IBM® Rational® DOORS® 8.0, 8.1, 8.2, 8.3, 9.0, 9.1, 9.2, 9.3, 9.4, and 9.5)
| Resource | Minimum | Recommended |
| CPU | PentiumTM 4, 1.6 GHz or higher. | CoreTM i3, 2.5 GHz or higher |
| RAM | 2 GB | 3 GB RAM recommended; higher memory capacity
generally improves responsiveness. 4 GB RAM is recommended for very large projects. |
| Disk Space | 400 MB | 400 MB or more |
| Video Mode | 800 * 600 | 1280 * 1024 |
| Operating Systems | All support Java compatible JVM 1.6. Windows XP, Vista, Windows 7, Windows 8, Linux, and Mac OS X Lion and Mavericks (most testing procedures and debugging were performed on these platforms). |
|
| UI Application | MagicDraw 18.0, or Cameo Requirements+ 4.1 SP3 | |
| Java Virtual Machine (JVM) | JDK 1.6 | JDK 1.7.0_55 for Windows and
Linux JDK 1.7.0_25 for Mac OSX |
All Mac OS X come with a Java Virtual Machine by default.
After installing and configuring Cameo DataHub, there are 3 simple steps to start working with DataHub: starting DataHub Server, starting each driver, and connecting other tools to DataHub Server.
| Known Issues | Description | Solution |
| DH-8255 DataHub Console is not started when calling from Requirements+ application. |
Working with
DataHub 64-bit, DataHub Console will not be started when calling from
Requirements application. It seems that a 64-bit Java DLL cannot be loaded within 32-bit Java used by Requirements+ application. |
|
| DH-7565 No change found on attribute changes after the synchronization for hierarchy changes from other side. |
Two nodes are synchronized.
When source node is moved, and at the same time target node is edited. If the synchronization is made on source (moved node), moved will be applied. But later at the target side (edited node), they synchronization will not found the update. | If moving and updating are made on each side of relation, in order to capture both changes, synchronization has to be made on the the side that contain updating. |
| DH-6712 Teamwork project Data Source will be disconnected if multiple user connect to DataHub with the same project and other commit new content into Teamwork Server. | When multiple user are working with the same Teamwork project, DataHub will work only with the Data Source that own the current version of project in order to avoid the synchronization with the data that is not updated. | If Data Source of Teamwork project is disconnected due to the commit from others, update the Teamwork project and connect the Data Source again. |
| DH-6680 After migrated relations from DataHub version 4.1 and 17.0.1 to version 17.0.2 and performed Check Node Changes command, the "Modify" status are displayed in the Change Summary dialog. | This case can happen to only Trace relations that have been migrated from the DataHub version 4.1 and 17.0.1 to version 17.0.2. After performed Check Node Changes command, the non-updated Trace relations are displayed as "Modify" change type both of "Trace" and "Suspect" status in the Change Summary dialog. If select to synchronize data, all of the Trace relations are set to "Suspect" status although there have no any changes. Thus, the migrated all of Trace relations will be set to "Suspect" after perform data synchronization. |
To avoid the ambiguous changes of the migrated Trace relations, the user should
do as follows: 1. Before migrating data, the synchronization should be performed and all of the relations status should be the "Synchronized" for the data sync relations or the "Trace" status for the Trace relations. 2. The DataHub server and all of the agents should be stopped. 3. Perform data migration in the DataHub console. 4. Perform data synchronization at the migrated DataSource then all the Trace status will be set to "Suspect". 5. Clear all the "Suspect" status. |
| DH-6226 DataHub does not support
multiple extended types that have the same names. |
To extend an element type, the user can apply additional stereotypes. This stereotypes may contain the same names if they are stored in different packages, but DataHub cannot identify those extended types with the same names. Therefore, only one type will be available. | To avoid this problem, the user should not create a custom stereotype with the same name. |
| DH-6157 There are some cases that
the same DataSource may be shown twice. |
This case can happen to Shared DataSources. If the DOORS Server or Teamwork Server is logged on with different host identifiers such as 127.0.0.1 and localhost, DataHub will assume that they are using different DataSources when two or more users work on the same DataSource. | To avoid this problem, the user should log on to the DOORS Server or Teamwork Server by using the same host identifier. |
| DH-5824 DataHub menu in Rational DOORS and RequisitePro do not
work if Rational DOORS and RequisitePro are running with 64bit
JVM. |
On Windows7 64bit, Rational DOORS and RequisitePro may run using 64bit JVM. DataHub menu will not work on both applications if they are using 64bit JVM. | Download and install 32bit JVM. (see http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u31-download-1501634.html) |
| DH-5089 Drag and Drop for exporting multiple items into MagicDraw diagram is sometime not exported. | Exporting nodes from DataHub Explorer into MagicDraw diagram, if multiple nodes are selected for export, it can happen sometime that only single node is exported. This case was found only on Mac OSX. | During the multiple select, while clicking on the last node, please hold the mouse click. Then drag and drop for export. Do not leave the last mouse press and clicking again. |
| DH-3457 DataHub Report cannot handle large amount of data. |
Due to the memory constraint, in order to handle large amount of data, more JVM memory has to be set. |
With approximate data over 2000 elements, additional memory configuration is need. MagicDraw:
DataHub Console:
DataHub Server:
RequisitePro:
Note: The maximum memory setting depends on not only the amount of RAM in the system but also the current memory utilization. So, two systems with the same RAM may allow difference value of the Xmx parameter. |
| Items in the third-party tools will not automatically refresh in Cameo DataHub Browser |
The display of original items from third-party tools and items in DataHub Browser will depend on the changes manually made in the third-party tools. |
Reload items in DataHub manually after changing them in third-party tools. |
| All relationships from Cameo Requirements+ will be copied to MagicDraw if the relationships' source and target items are selected |
All relationships from Cameo Requirements+ will be copied to MagicDraw if the relationships' source and target items are selected even though the export recursive items option is not chosen. |
Remove the relationships manually from MagicDraw Containment Tree. |
| DataHub cannot detect read-only data mode from a RequisitePro Project |
The read-only data mode in DataHub will not be enabled if user try to change to read-only mode by reopen the project with Read Only option without closing the current opened project. |
1. Close the project. |
| RequisitePro data cannot be automatically updated using Cameo DataHub |
Cameo DataHub cannot automatically update RequisitePro data. |
Refresh RequisitePro data to update it |
| Applications running on Java 1.5 on Ubuntu might not work on some machines. |
The application window is displayed as a blank page. |
This is a Java 1.5 problem on Linux (Ubuntu). To avoid this problem,
insert the following line at the end of the filename: /etc/bash.bashrc
|
| Need to use the edit function in the schema map to map newly added attributes. |
When a user adds a new attribute to the type. DataHub will not acknowledge the changes in the type. |
Manually map the newly added attribute using the edit function in the schema map. |
|
Limitations |
Description |
Synchronization |
|
|
DH-8271 DataHub does not recognize the link that Client or Supplier has changed. |
DataHub does not recognize the link that Client or Supplier has changed. The synchronization will mark that link as deleted. |
Cameo DataHub Plugin in MagicDraw |
|
|
Cameo DataHub use the physical path + .mdzip filename as the ID for MD Datasource |
The MD Datasource use "physical path + .mdzip filename" as the ID. If associated MD project file was deleted from the file system and the new MD project file was created using the same filename and location, the DataHub project that used to associate to that MD project will try to connect to the newly created MD project but elements that used to be associated will no longer be in sync anymore. As a result of no element is detected to sync, DataHub will treat as all elements are deleted and will remove all associated elements as well. |
| Cameo DataHub Plugin in RequisitePro | |
| Login to RequsitiePro is required before connecting from DataHub | DataHub cannot connect to RequisitePro if the project is not yet open in RequisitePro Application. |
| RequisitePro Security Enabled Projects is not detected. | DataHub cannot detect read-only permission on the data from RequisitePro Security Enabled Projects. So, DataHub will be able to Read, Write, Create, and Delete over the project even it was opened as Read Only. |
|
Cameo DataHub Plugin in
DOORS |
|
| DataHub does not support Unicode characters | DataHub does not support Unicode characters used in DOORS objects. |
| Operation Failed due to Invalid DOORS Access Rights | The Operation Failed dialog will appear when creating DOORS objects or synchronizing as they are not allowed to be updated. |
| DataHub does not support OLE enabled objects | DataHub does not allow to edit any DOORS object that contains OLEs |
| Auto Synchronization does not support OLE enabled Objects | For SyncAuto, the status of DOORS Object that contains OLEs will change to PendingUpdate. |
| Text Style in DOORS object's attributes will be lost after data sync | The updated data from DataHub does not contain the text style, so it will be lost. |
The main source of information on Cameo DataHub is on http://www.magicdraw.com/cameodatahub.
New features
For information on Cameo DataHub new features, see New and Noteworthy at: http://www.magicdraw.com/newandnoteworthy/cameo_datahub.
You can also send us an e-mail. We provide professional e-mail support for registered Software assurance customers:
support@magicdraw.com for product related questions (installation, usage, bugs, etc.)
sales@magicdraw.com for academic, site discounts, sales, and marketing related questions.
contact@magicdraw.com for other issues.
Documentation