Community
Participate
Working Groups
Papyrus must provide a tool to import Rhapsody models into Papyrus. This tool must be able to convert semantic model (uml) and graphic model (.notation). This tool must be able to manage referenced libraries This tool must be able to manage stereotype applications This tool must be able to manage uml diagram.
Hello Vincent. Found this buzilla on the page https://wiki.eclipse.org/Papyrus/Oxygen_Work_Description/NewFeature/ImportRhapsody What is the progress of this work? (based on the RSA importer, I guess) Does the plugins work on Neon.1 ? Regards/Toni
I'm especially interested in how you import "applied profiles" and "Rhapsody stereotypes" in users models, in the case where the stereotype packages and user model packages are in the same Rhapsody model.
Hello Toni, we are working on the SysML Model and Diagram from Rhapsody import (bug 496176). So we are able to import SysML Parametric Diagram, Internal Block Diagram and Block Definition Diagram. The set of managed elements will be described in the documentation (coming soon). We manage SysML Stereotype application and we map Rhapsody Type on UML primitives Types and Papyrus Designer C types library.
Thanks Vincent. I'm interested in import of plain Rhapsody models with user-defined "Rhapsody stereotypes" applied, in typical Rhapsody-proposed-ways, where some of them can be Rhapsody SysML stereotypes. The Oxygen Work Description lists this particular bugzilla 496175 to be part of the Oxygen release, so this bugzilla is what I'm interested in. I guess that Rhapsody SysML model elements can have additional user-defined stereotypes applied too. Since "Rhapsody stereotypes", which also may contain UML1-style tags, are defined at the level of the user model itself (M1), and such tagged values can also be added directly to model elements, without stereotypes, there seem to be a great freedom in the way users can create their models in Rhapsody. A semantic model in Rhapsody may contain Rhapsody UML elements and Rhapsody stereotypes, and tagged values, where some of then happen to be Rhapsody stereotypes located in the SysML stereotype package. I'm currently downloading the latest Oxygen M3 nighly plus this Rhapsody import feature, just for doing some initial testing.
How can I install the latest Papyrus Rhapsody Plugins from an nightly update site? /Toni
I have just installed the Oxygen M3 Modeling Package plus all other MDD + collaboration tooling used by different Papyrus users the past years. For new non-RSARTE users, I'm now interested in installing+updating the "Papyrus Rhapsody Plugins" in the same way via nightly builds, the plugins that are listed here: https://wiki.eclipse.org/Papyrus/Oxygen_Work_Description/NewFeature/ImportRhapsody Right now, I only want to do some initial testing, just to be able show proof of concept for a huge base of Rhapsody users. :) So... I need a workable nightly update site for "extras", just like we have for the RSARTE import feature. I hope to be able to "update" to the latest "Papyrus Rhapsody Plugins" this weekend, to start working on some initial proof of concept demo's. /Toni
Hi Toni, nothing is officially released concerning the Rhapsody Import Tool. This tool will be available the 16th of December as extra plugins of Papyrus, in the nightly build of the Oxygen branch. Regards, /Vincent Lorenzo
I was hoping to start some early testing now. :(
Hi Vincent. I like to do some early testing a.s.a.p of the Rhapsody import plugins. On this page https://wiki.eclipse.org/Papyrus/Oxygen_Work_Description/NewFeature/ImportRhapsody You (CEA) say that: All Papyrus Rhapsody plugins are stored in the Papyrus git, in this path : extraplugins/migration/rhapsody Problem: The Papyrus git seem to have moved around a bit the past years, after this wiki was created: https://wiki.eclipse.org/Papyrus_Developer_Guide Question: Where is the current Papyrus git located now, where the extraplugins/migration/rhapsody path can be found, and those Rhapsody plugins? Regards/Toni
Hello Toni, the given path is correct in the documentation, but it required to be on the branch dedicated to the rhapsody import. Since 5 minutes ago, all the developement and the documentation have been pushed on the Papyrus git repository, so it will be available after the next Papyrus nightly build. The feature is provided as Papyrus extraplugin, but requires to have Rhapsody installed on your computer. The documentation is available on the git repository in plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc. Updating your Papyrus installation will allow you to get this documentation in the Eclipse Help Contents. This documentation will indicate your the supported Rhapsody concepts and their mapping. It is a SysML Import and not yet a full UML import framework.
Hello, we are heavily using Rhapsody in our projects and now i'm verifying other modeling tools for small projects. So i'm new to Papyrus :) I've tried to import a small Rhapsody model and see this error: ... Could not find the file <...>\S7PCpuInfra\uml_models\S7PCpuInfra_rpy/$RHP_INFRA/development/uml_models/RhapsodyUnits_rpy/CPU1500Profile.sbs referenced by an Element at line 457 of file <...>\S7PCpuInfra\uml_models\S7PCpuInfra.rpy ... It looks like environment variables (here $RHP_INFRA) are not supported. We are using them in all models to have smaller spitted models that reference (read only) each other in bigger projects. I've set all the variables in one batch file before starting eclipse / papyrus, may be i'm missing something? Thanks and Regards, Andre
Hello all. Importing Rhapsody models (or EA models) should be as easy as importing the IBM RSA models and profiles, all financed by Ericsson. Most of the work has aready been done. :) Regards/Toni
It looks like environment variables (here $RHP_INFRA) are not supported... i will try to remove them and use relative pathes for the first tests...
