Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Eve

Pages: [1] 2 3 ... 457
Suggestions and Requests / Re: Make searches diacritic insensitive
« on: December 13, 2019, 02:18:42 pm »
Searches use the collation settings for the database. If you want this behavior you should just need to change your collation in sql server.

I just tested to copy the EA 15.1 B Archimate3.xml file to the Archimate3.xml file on a computer with EA 14.1 and it worked :).
So now even the PC with EA 14.1 have Archimate 3.1 capability :)
I think you'll lose all quicklinkers and connector rules though.

The thing is the ArchiMate MDG I've built doesn't have is restrictions on relationships as it was just too time consuming to do. Plus it wasn't until ArchiMate V3.01 that they actually sorted out the relationships properly. I've lost track on how many hours I've put into creating and modifying it over the years but a guess is probably in the order of 80 or 90 hours.
Pro-tip. Look in the built-in ArchiMate 3 technology from 15+ for the RelationshipTable. You'll need to change the keys in the first two lines to match your stereotype names, but I'd estimate you could get it going in half an hour.

The ArchiMate MDG with Sparx EA V15.1 is probably better now the only thing is that people often want to add custom tag values to the ArchiMate elements. For example Application Component often needs extra tag values like Product Owner, Commissioned Date, Retired Date etc.
Which I would recommend adding as a redefines stereotype within your own profile. Then set the technology containing your own definition as active.

I tested the EA 15.1 Beta Archimate 3.1 but I dont like ValueStream symbol as it does not suport streatching out with nice looking arrows as Archis implementation does.
I see what you mean. If we don't decide to change it, you can use a redefines like above to replace the shape script. Were you expecting something like the following? (It's defaulting to non-rectangle notation to make it easier to see the behavior. If you swap that condition to check against "1" it will be rectangle notation by default)
Code: [Select]
shape main

In that case I'd double check the provided credentials. Can you log in as that user explicitly? May also be worth checking the security settings of the model.

Any certification for that?
I don't think that anyone offers certification for using a database feature.

Seriously, do a search for Oracle or SQL server row level security. That will give you a very good idea of what is happening and why it's better security than anything EA can do on the client side.

Across the EA15 presentations videos I see that I could make multiple root nodes in a project and limit their visibility so users can't even see the root node.
Would this feature help me acheive my goals ?
No. This feature is not related to the row level security function. Consider it more as a convenience for your users who don't want to see things in those root nodes. They can still access the information if they try a little.

I would not trust this mechanism to meet any information security requirements without having done a proper analysis in the context of the proposed deployment.
By all means, review it. Row level security is not our term. What we have done is applied the techniques described by Oracle and Microsoft to the Enterprise Architect data model, allowing useful portions of the database to be restricted. The good news is you only need to do your analysis on the EA portion of the technology. The DB side is well documented.

Row-level security has been introduced to help address this, but there is no public documentation that goes into any detail beyond the fact that row-level security is applied only to 24 "critical" tables (out of the 94 tables in EA's database schema). However, the documentation does state explicitly that "only models hosted by a Pro Cloud Server are able to make use of this feature", so for client users the old access model still applies.
The changes all happen directly within your database, which as far as I'm concerned means that they are quite open. As Geert states, the security is within the database. The PCS offers an added redirection so that users don't have direct DB access, but even if they could connect using the credentials the cloud is using, they couldn't access the data they aren't meant to see.

Since the EA client's security model is trivial to bypass, the only way to achieve meaningful security is to use the security features of the underlying database. This means that the project (which is essentially the same as a database) is the smallest unit at which security protections can be applied.
Which is what row level security is doing.

That's as may be, but there are several industries where security is the business, or is at least integral to it. In those, convenience of use takes a backseat to security, and in those, EA has to be set up the way I've described.
Maybe you should actually investigate the features within EA and PCS before you make such a blanket statement.

General Board / Re: EA and PostgreSQL x64
« on: December 06, 2019, 09:20:11 am »
Do they still have a 32 bit driver to connect to the 64 bit database? If so, that's your answer.

General Board / Re: Foreign Keys removing themselves when I save
« on: December 05, 2019, 08:41:42 am »
Finding yourself in 2011 must have been a hell of a surprise.
It was the first time around.

Bugs and Issues / Re: C++ include guards
« on: December 04, 2019, 08:43:52 am »
It's stored in each eap(x) file or database.

Bugs and Issues / Re: C++ include guards
« on: December 03, 2019, 04:58:03 pm »
I just tried a generation with the default templates and it generated:

Code: [Select]
#if !defined(EA_20DC1767_DEDE_46a2_A251_3EDA957EA5AB__INCLUDED_)
#define EA_20DC1767_DEDE_46a2_A251_3EDA957EA5AB__INCLUDED_

I don't get a warning for identifiers with double underscore within the name, but if your compiler is it's coming from line 18 in the C++ File template.

The http(s) security prompt comes directly from Windows. The exact appearance will vary depending on Windows version.

Generally you should see the server name and model name listed. In my test environment it also uses a title of 'Windows Security' and explicitly states that the request is coming from 'EA.exe'.

The EA project security prompt will not provide any of those things. It should have a title 'Login to EA Repository'.

If you want to use the File Impl for your language, you'll need to create an MDG technology that specifies ImplementationExtension in the code options.


Bugs and Issues / Re: php7 methods with returnType not imported in classes
« on: December 02, 2019, 09:28:52 am »
Changing the code generation templates won't change the import behavior at all. Neither will setting required or active, but required could prevent other people from accessing your model.

The behavior with perspectives was not intentional, and I believe it has been corrected in the latest builds. So the easiest approach is updating to the latest build.

In the perspectives menu, select manage perspectives. On the second page create a new perspective and select the php7 technology. Save it and you're done. As long as you are in 'All' or your new technology when first importing PHP in an EA session it should take effect.

No scripting (or even compiled) language is going to make much of a difference unless you're doing some serious crunching in your code. The big time costs are associated with the DB access itself.

Pages: [1] 2 3 ... 457