Book a Demo

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 - crequena

Pages: [1]
1
General Board / Re: Export XMI limitations
« on: February 15, 2019, 03:58:19 am »
Hi,

We had some performance issues when performing a model transfer from remote repositories, specifically with MSSQL databases.
Hence, I have developed an open-source library to perform model imports and exports without using EA's API.

If you know how to use a Java library, you could give it a try: https://krequena.github.io/eamodeltransfer/.


2
So relying in the t_uSysTables table could have some issue in some models.

Well, maybe a solution for my library could be working as it currently does (transferring all the well-known standard tables) and then copying any extra table present in t_uSysTables as an option.

Seems feasible for you, Paolo?

3
I guess we could create a fork in the project to allow other tables to be copied?  Better still add a special table in the main repository telling which other tables should be copied.  That way, there's no need to fork, the project is self-extending.

Thoughts?
Paolo
That table already exists. It's called usysTables
That's what the standard project transfer feature uses.

Geert

I didn't know about this feature, and seems more than necessary to develop it.

Paolo, feel free to open a ticket in the project repository ;)

4
Hi Paolo,

Thanks for the questions.

Yes, it is a database copy done table by table, but only with the standard EA (t_...) tables.
Other tables present in the database are not copied.

Regards,

crequena

5
Hi,

I have found this issue in the past, as well as some limitations on EA's API.


Since a solution was needed asap, I have developed a Java library that performs Project Transfer operations externally, at database level.
It is published in GitHub: https://github.com/krequena/eamodeltransfer.
The general documentation is here: https://krequena.github.io/eamodeltransfer/

The main advantages of this library are:
  • No COM dependencies are needed.
  • No GUI session is required (useful for headless servers).
  • Works in 64-bit JVM.
  • Can be automated with no restrictions.
  • *-to-DBMS operations are supported.

I have to publish some examples yet, but it is already usable.


Kind regards,

6
Dears,

We are having the very same issue: EA Automation just skips the Password parameter.
In our case, this happens both from a Java application and in PowerShell with EA 14.

The username (easervice in this case) goes though the API and is displayed in the model authentication popup... Which obviously lacks the password.

I think this screenshot may provide some clarification of this OpenFile2 method bug:


Regards,
crequena

7
General Board / Re: EAP-to-DBMS model transfer
« on: June 14, 2018, 11:56:17 pm »
Thank all for your replies.

8
General Board / Re: EAP-to-DBMS model transfer
« on: June 01, 2018, 12:36:03 am »
Hi,

It's a SQLServer db.

Invoking the ProjectTransfer method from eap to dbms file just returns "false" and does nothing with the database.
Also, nothing gets logged.

It's not working neither from Java nor PowerShell:

$ea = New-Object -ComObject "EA.Repository" -Strict
$project = $ea.GetProjectInterface()
$project.ProjectTransfer("....eap", "DBType=1;Connect=Provider=SQLOLEDB.1;Persist Security Info=True;User ID=...;Password=...;Initial Catalog=...;Data Source=...", "D:\....DBMS.log")
$ea.Exit()


9
General Board / EAP-to-DBMS model transfer
« on: May 31, 2018, 08:32:26 pm »
Hi,

I see there is no automation to perform an EAP-to-DBMS operation.
http://www.sparxsystems.com/enterprise_architect_user_guide/14.0/automation/project_2.html

Does anyone know any alternative to do this without using EA's GUI?

Thanks.

10
Bugs and Issues / Re: Cloud Services logging bug
« on: May 23, 2018, 05:15:33 pm »
Hi,

Thanks for your replies.

Cloud Services requires that the password is saved in the DSN: https://www.sparxsystems.de/fileadmin/user_upload/pdfs/Cloudservice/Enterprise_Architect_Cloud_Services_setup.pdf (page 12 and following).

The DSN is then logged fully.
Using Windows Authentication could be a workaround in this case, but not with other databases.

Regards.

11
Bugs and Issues / Cloud Services logging bug
« on: May 23, 2018, 01:10:20 am »
Hi,

The Cloud Services product is logging passwords as plain text in the server logs.

Code: [Select]
2018-05-22 16:37:20 [INFO]: Added database manager - ConnectionStr:  'Provider=SQLOLEDB.1;Password=1234;Persist Security Info=True;User ID=user;Initial Catalog=db;Data Source=ds;DMAlias=db;'

This is a bug similar to Twitter's: https://www.bleepingcomputer.com/news/security/twitter-admits-recording-plaintext-passwords-in-internal-logs-just-like-github/

Will you release a new Cloud Services version correcting this?

Regards.

Pages: [1]