corporate usage

[Gobo]

Hi,
I move my project from Master-Replicas usage to Database usage (corporate edition). And  now work is possible ONLY while connection with database is active. Its ok for those working only from office (database is on a corporate server). But for designers working outside (on customer side or at home) master-replicas working model was better - there are no way to connect to corporate server from outside. In addition: working mean changing, not only read-only access.

Does anyone have such experiences? Is it possible to compromise advantages of those two usage models?

Greatfull for any help
Gobo

[thomaskilian]

Gobo,
I haven't tried since there is no need for me to have replicas. But you could make a local copy of the replica (tools/data management/transfer) to an EAP-file. With that you can walk around and bring it back to the master DB later.

[Gobo]

Tomas,
Right, I can transfer project to EAP-File and in this way take it off-line
But, is it safe for read only. After modification in file, how to synchonize them with DB?? Transfering to DB ALWAYS replace current DB content. Keep in mind that others designers could change model simultanously with off-line changes.
How to solve that??

Gobo
PS.: we change model usage because off growing number of designers. In group of 6-10 replication is ok. Above that it takes time to synchonize replicas, locking problems and simultauosly access make work more difficult.

[thomaskilian]

Well, the last time I was working in a big context I was using Rose   There we assigned single packages to independent designers. They could do inside their packages what ever they wanted (more or less). One person was responsible for integration work. That meant: integrate the single packages and make global changes.

Unfortunately I'm working on my own right here so I have no need for replication. But most of the problems you have could probably be solved by organizing access to packages (if to take a blind man's advice to an one eyed).

[Bruno.Cossi]

Gobo,

you could export the package to XML file and have the person import it into their own model. After they are done with the changes, they could export it and import back to the main model. Would that help?

Bruno

[jaimeglz]

Hi Gobo:

Bruno is right: the best way to make changes off-line and then merge these changes back is by package export and import. Just make sure you assign the packages that are going to be modified to particular owners (you don't want two or three modelers modifying the same package off-line). Try package control (right-click on the package -> Package control -> Configure...) Also, make sure that each modeler changes ONLY the package under her/his control: if they add or delete elements outside their package(s), things can get quite messy.

Cheers,

Jaime  

[Gobo]

Thanks,
I preceed some tests and assume that XML export/import work fine. So, probably it is the best (and only, so far) practise for sharing model in corporation and taking it offline in the same time.
So, steps are as follow:
(model is stored in database)
1. Lock package (with subelements)
2. Transfer to EAP file or export package to XML
3. Proceed offline modifications
4. Import locked package from XML
5. Unlock package

That, resolves my problem
Gobo