Anybody using Pro Clolud Server to integrate multiple EA repositories?

[Paolo F Cantoni]

Paolo,

What if each element was in its own package?
In that case, you would be able to share individual components between different models.

Have you considered this approach?

I know it's a bit unorthodox, but it might just work.

Geert

You jest, surely, Geert!    The administrative overhead would be worse than writing our own synchroniser (and on going).  We're talking several hundred to several thousand shareable items in tens of thousands of items in an enterprise repository.  As the overseer said, in "Cool hand Luke", "Id cayn't be durn".

Paolo

[Geert Bellekens]

I don't really see the overhead.

Surely your version control system can handle thousands of files.

Putting each element into it's own package, and adding that package to version control can be automated with a little script (I have some examples if you want).

I'm guessing EA won't have an issue with this either.
And if you only version control the lowest package level, you could import a random selection of elements into any given repository.

Or is it the dependency management that you are afraid of?
The fact that you need to import all dependencies of an element into a repository as well if you want to be able to update an element in that repository and not loose any relations in the process?

I can imagine that being a challenge regardless of the chosen solution.

Geert

[Paolo F Cantoni]

I don't really see the overhead.

Surely your version control system can handle thousands of files.

Putting each element into its own package, and adding that package to version control can be automated with a little script (I have some examples if you want).

I'm guessing EA won't have an issue with this either.
And if you only version control the lowest package level, you could import a random selection of elements into any given repository.

Or is it the dependency management that you are afraid of?
The fact that you need to import all dependencies of an element into a repository as well if you want to be able to update an element in that repository and not lose any relations in the process?

I can imagine that being a challenge regardless of the chosen solution.

Geert

(my emphasis)
Yes, Geert, I see the emphasised issue as the essential problem.

We're currently looking at a model for the design of this process.  If the model shows it might be feasible, we'll have a look at possibly implementing.

As Eve has said, we need to clearly enunciate our requirements and constraints.  This we are also modelling to clarify our thinking (about ANY solution) and guide our design.

For example, I don't think we'll need to import ALL dependencies, but only the relevant ones (that is only those in the target repository - we hope.  But the detailed analysis will reveal if that's the case.  Nevertheless, it doesn't reduce the complexity much.

I agree one item per package is not (really) a performance issue for EA, but it is a significant human loading issue.

Anyway, we'll plug-on with the modelling to see what we think is necessary.

Paolo

[Ian Mitchell]

I guess you already looked into the Reusable Asset Server? I thought that yours was the use case it was designed for? Or are you more about partitioning the rep into bits ?

[Paolo F Cantoni]

I guess you already looked into the Reusable Asset Server? I thought that yours was the use case it was designed for? Or are you more about partitioning the rep into bits?

Hi Ian,

I thought RAS was a unidirectional mechanism, you could only edit in the remote repository and once imported into the local repository can only be compared with the remote version.

That's not my use case.  My use case is element based, not package based,  I guess my use case IS more about partitioning the repository (but not on a package basis).

More formally, it's about creating a distributed "virtual" repository where some elements are shared between a number of physical repositories.

We're still working our way through formalising the requirements in a model using Requirements, Constraints, BPMN diagrams etc (as time and resources permit )

Paolo