Limit "Export" functionality

[K N]

Hi

I have a DBMS repository setup.

Is there a way that I can limit the Export functionality without enabling the user security?
in other words, I dont want to enable security but want to limit few functions. Can this be done through the DB itself?

Thanks
KN

[qwerty]

Well, what is this else as security? IOW: turn on security. Or maybe you find a hacker to patch EA.exe so it has no export menu.

q.

[K N]

I know you would have found this a stupid question. But because I didn't wanted to have user security enabled as there are many users (will have to create that many user ids and passwords)...so thought whether there was any solution at database level.

[qwerty]

No. The XMI export is a function within EA. It accesses the database like any editing of element as necessary during modeling. The DB does not know which EA function is retrieving data. The only "work around" would be to path EA.exe - I would in no way recommend such an approach. Either you tell you users to be friendly and not to use export (you might tell them a scary story that it would corrupt their modeling work) or you need to turn on security.

Btw: usually the users are all stored in AD. You can turn on windoze synch import the legal users and assign them a group with limited access.

q.

[Eve]

One idea would be to give everyone the same login details that include only the permissions you want. The main thing I can think that you would lose from that is the author for everyone would be identical.

Of course, if this question is because you don't trust your users not to steal secrets you have bigger problems that preventing xmi export won't solve.

Having said that, if I really had to do what you're asking. I would choose a db that is open source then configure it to fail when EA runs a query (matching a pattern) that is only run during xmi export. The XMI export would then presumably fail.

[qwerty]

Having said that, if I really had to do what you're asking. I would choose a db that is open source then configure it to fail when EA runs a query (matching a pattern) that is only run during xmi export. The XMI export would then presumably fail.

Would you really recommend that? I think it's quite unsafe to rely on such a pattern. In the end the XMI export is based on the same DB layer as the modeling components of EA (I would expect!!!). Else what what would such a pattern be?

q.

[Eve]

No, I would certainly not recommend it. But if management insisted I make it happen despite my advice to the contrary I would try that.

I don't know exactly what I'd be looking for. It could be one query I believe to be distinct or a series of queries that occurred in a particular order. It wouldn't be pretty, but I believe I could make it work.