Questions about using a shared repository

[Mabb]

Hi Everyone,

I've searched user manuals and messages posted here and have not been able to get my head around how things work when you're using a shared repository.  I thought I understood it, but now that we've set one up, I am lost.

We have created an Oracle repository and transferred several models to the repository successfully.

Now I want to transfer all the older models that we've previously saved on our network file system into the repository so that parts of these models can be re-used in new models.

While the documentation says lots about creating a repository and transferring a model, there is nothing about how one uses this resource once its set up.  If I've missed this, please point me to the right place as I'd be most grateful!

Here are my questions:

How does one find a particular model, package, artefact etc within the repository?  We've transferred 3 models to the repository, but every time I connect, the same model loads.  I can't find anywhere to pull out the others.

How do you work with multiple models?  Our DBA seems to think, after checking out the repository using his Oracle tools, that you can't have multiple models within a single Oracle schema.  Is this correct?  

I'm confused about the "Connection Name".  What is its purpose?  Is this specific to the model/project?  Is it specific to the user?  It appears in the recent models list, so I assumed it would load a specific model, but you don't nominate a name when you tranfer the model.  Is it the model name, ie model.eap?

As I said above, I can find no documentation on the day-to-day use of a repository, how it works and how a team might share models and parts of models.  What am I missing?

thanks in advance


Felicity

[thomaskilian]

Felicity,
I'll try to give some short quick answers:

How does one find a particular model, package, artefact etc within the repository?  We've transferred 3 models to the repository, but every time I connect, the same model loads.  I can't find anywhere to pull out the others.

There is one model per repository. You could store multiple models in one repository by using different root nodes, but this is not recommended. So you have to build multiple repositories.

How do you work with multiple models?  Our DBA seems to think, after checking out the repository using his Oracle tools, that you can't have multiple models within a single Oracle schema.  Is this correct?  
 

You need to use multiple Schemas (see above) in order to store multiple repositories.

I'm confused about the "Connection Name".  What is its purpose?  Is this specific to the model/project?  Is it specific to the user?  It appears in the recent models list, so I assumed it would load a specific model, but you don't nominate a name when you tranfer the model.  Is it the model name, ie model.eap?

It's more or less related to the model/repository. Using EAP files (which are simply Access databases) they are related to the filename. Else you have a relation to the ODBC connection.

As I said above, I can find no documentation on the day-to-day use of a repository, how it works and how a team might share models and parts of models.  What am I missing?

In short: practice You need some time to get used to working with EA, but once you are you'll find it a m
irreplaceable tool.

[Mabb]

Thanks Thomas, I can see now how we might work with the separate repository although I must say I don't think this is the nicest way to implement the feature but that's a subject for another forum after we've worked with it for a while :-)

I do find the documentation frustrating at times.  Good documentation should cover the use of the product in context and the EA User Manual falls short in this regard in my opinion.  

It's so frustrating having to teach yourself through trial and error!  And we just don't have time to do that so consequently, I know we're not using the product to its full advantage for our organisation :-(

I do hope that the ICONIX training comes to Melbourne!

[thomaskilian]

I ordered the ICONIX training CD and it was very helpfull for me (especially in the beginning).  I can understand very well your frustration about this trial and error process. OTOH I think there is no "kings way" since EA can be used for many, many purposes. Each of them differ in the way you use the tool. It's certainly impossible to actually write a "complete" documentation that fits your purpose. EA documentation is already a 1000 pages. I never read it, just used it to look up some details.  Be brave