Version Control While Accessing Model Via Citrix

[kotrick]

We are using Oracle Database for Architecture Model which is  located in Frankfurt

Its difficult to access this model for Users from different location's as its very slow. We use Citrix Server to make the Model Access Faster from different location.

Recently Version Control was introduced in model to maintain history using SCC Integration

Issue:
Currently we are not able to use Version Control via Citrix as we get error's when multiple user's connect to same citrix server to perform check-in check-out operations

So we are in a situation were we cannot use Version Control via Citrix. And to access model directly remotely its very slow so user's cannot perform check-in check-out operations Locally without Citrix and with version controlled model.

Can you provide any suggestion to solve the problem above?How can we make model access faster irrespective of database location so that user's use version control locally OR How to make Version Control working for multiple user's via Citrix?

Thank You

[Guillaume]

Hi,

Have you looked at installing the Cloud Service and enabling EA security to manage your user locks?
Sparx Cloud Service includes the WAN Optimizer which aims at improving performances with the DB (e.g. Oracle).
It also simplifies the clients' configuration as a url replaces the ODBC configuration.

Citrix Server is only useful if you don't want to install EA on each user's PC and need an optimised/central way of managing your licences (if you have floating ones).

I would suggest dropping Version Control as it quickly lead to slow access for users. The only advantage of Version Control compared with the EA Security is to provide an Undo Checkout (there are workaround to achieve this).
Version control is not great at maintaining history since controlled packages often change during the model life; hence data can move from a controlled XML file to another which can make it difficult use when needed.
There are options to keep history of your models: baselines, scheduled tasks to run an XMI export of your models, DB backup, audit logs...

[Geert Bellekens]

Version control is actually possible, even if multiple users connect to the same server.
We use TFS for version control on Remote Apps, and that poses no problems at all. You only have to make sure that the workspace mapping has a unique path for each user and the workspaces are named uniquely for each user.
We use our username as name for the workspace, and map it to a location on our personal network drive.

This even works when having a pool of servers with a load balancer. The only thing you need to do when logging on to a different server is tell TFS your computer has changed its name using the command:
tf workspaces /updateComputerName:[OldComuterName] /s:[UrlToTFS]

Geert