Restricting DB access to sub-models

[PhilK]

Hi all,

We have a requirement to map out our technical landscape, which is maintained by several teams.  Our overview starts with a high-level package model which then drills down into the individual deployment models.

As a single eap file this works well, but what I'd like to do is break this up so the environment teams can manage the deployment models associated with their areas whilst still maintaining the overall high-level view.

This is the structure at a high-level:

OVERVIEW PAGE:
              Application 1:
                            Deployment Model 1
              Application 2:
                            Deployment Model 1
                            Deployment Model 2
              Application 3:
                            Deployment Model 1
              Application 4:
                            Deployment Model 1
                            Deployment Model 2

For example is it possible, preferably from a stored model in a DB, to allow access to the Application 2's models for certain users?

[Geert Bellekens]

With "Access" I'm guessing you mean write access?

In that case there are two options
- Integrate version control and control the different application in different version control locations. You can then manage the security in the VC.
- Use group locks to define who is allowed to modify a specific application.

I would recommend the VC option since that is a lot better in judging what exactly should be locked, and what not.


Geert

[beginner]

Create a trigger that check the parent chain for individual element.

Or use EA's security.

b.

[PhilK]

Thanks for the feedback - the possible solutions you've suggested are where I'm weakest on EA so I'll dive into the help and focus on these areas.