I'm struggling with the DM Rhapsody client extension.  Specifically, I'm unable to move a Rhapsody model to an actively managed DM project (as described in this other forum thread).  Given that the issue has apparently stumped IBM, I'd like some guidance on what my alternative plan of action should be.  Would you suggest I:

a) Create a new DM project that is managed externally and import the model via a .zip file upload, then convert the project to an actively managed one and have the Rhapsody client extension connect up to that one.  I'm not opposed to doing that if it would work.  But I don't know if such a thing would work; I don't know if the Rhapsody client extension can be used to attach to a project that already has a model in it, or if the the client extension needs to perform the initial move of the model to the server in order to attain its initial synchronization.

b) Go down the route of using an externally managed project and doing periodic imports.  I've shied away from this approach thus far because it seems like its more complex than an actively managed project.  But I'm willing to consider it if I can't get the actively managed project to work.

Note that what I'm trying to do is get a Rhapsody model up in DM so I can link it to elements of an RM project.  The most I've been able to do thus far is a .zip import of a model to an externally managed DM project.  But that approach appears to be a one shot import (I've tried making changes to the model and then re-uploading the .zip file, but that appears not to accept any of the model changes and just keeps the old one).  I wouldn't mind periodically importing a zip file manually, but I need to be able to update a model without erasing what's already been done.

Please advise me on what my next step(s) should be, as right now I'm completely stalled in my tracks.

Thanks,
Joe Gariano