Show Posts
1
General Board / EA Corporate Deployment question
« on: February 23, 2009, 11:47:47 am »
Hi All
This is my first post on this forum. Please bear with me as I am new to EA.
I am planning to introduce EA into our organisation so investigating an ideal deployment option. After some initial research I have found that the following deployment may be ideal for us:
1. One Repository - Multiple Projects: My understanding is that in this deployment we will be creating a single EA Project and creating multiple root nodes for each Business Project. I think this will enable us to reuse components across projects.
2. A Central DBMS Repository: I can not understand the benefit of having this if we also use Version Control.
3. Version Control using Subversion: For security, sharing and history.
Please note that I have NOT yet set up EA this way so I am not sure how this will work. Please can you answer the following questions:
Q1. Why do we need a DBMS Repository when we can check-out files using Subversion? DBMS Repository seems to contain the same data which is also available through Subversion. Subversion maintains the master copy. Users can check-out to create local copy and make changes to the local copy and check-in. I am very confused about the purpose of DBMS Repository.
Q2. If we use the deployment described above what will be the steps for an EA user to open the project and make changes and save changes?
Q3. How can we enable security such that a user can only modify contents of the project he / she is working on.
Q4. Upto 20 users will be using EA every day. Most of them will be on local network. All of us work on more than one project at any time and we wish to encourage sharing on contents across projects. Please can you suggest if any other type of deployment will be suitable?
This is my first post on this forum. Please bear with me as I am new to EA.
I am planning to introduce EA into our organisation so investigating an ideal deployment option. After some initial research I have found that the following deployment may be ideal for us:
1. One Repository - Multiple Projects: My understanding is that in this deployment we will be creating a single EA Project and creating multiple root nodes for each Business Project. I think this will enable us to reuse components across projects.
2. A Central DBMS Repository: I can not understand the benefit of having this if we also use Version Control.
3. Version Control using Subversion: For security, sharing and history.
Please note that I have NOT yet set up EA this way so I am not sure how this will work. Please can you answer the following questions:
Q1. Why do we need a DBMS Repository when we can check-out files using Subversion? DBMS Repository seems to contain the same data which is also available through Subversion. Subversion maintains the master copy. Users can check-out to create local copy and make changes to the local copy and check-in. I am very confused about the purpose of DBMS Repository.
Q2. If we use the deployment described above what will be the steps for an EA user to open the project and make changes and save changes?
Q3. How can we enable security such that a user can only modify contents of the project he / she is working on.
Q4. Upto 20 users will be using EA every day. Most of them will be on local network. All of us work on more than one project at any time and we wish to encourage sharing on contents across projects. Please can you suggest if any other type of deployment will be suitable?