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

Pages: [1] 2
Even though the MDG for office has been 'updated' recently, the systems requirements do not go much beyond Server 2008.  Can Sparx update the sys reqs and testing to state whether it is supported on (in my particular case we are using RDSH onto a Server 2019 environment) modern platforms?

It is known (and may well be related) that the expression of MDG models including ArchiMate are not properly described through WebEA, which appears to revert to the base element that has been profiled/stereotyped as part of the MDG.  One of our principal problems however is that creating a relationship matrix profile in the EA client showing say capability realizing another capability will cause the app to generate the requisite image for webEA to show the axes, but will not create the arrows in the grid.  It works for other relationships that we have looked at (association being the simplest).

Has anyone else seen this behaviour?  Is there a workaround/fix?

Raising it as a bug in the appropriate place also.

PCS Suggestions and Requests / WebEA access to model Glossary
« on: May 15, 2020, 08:27:53 pm »
There is no mechanism at present to expose the Glossary through webEA as it is presented inside the full tool.  The context based browser also reduces the chance that there is a glossary package at the top level which can be accessed wherever in the models context the user happens to be.
It is suggested that one of two things is looked at (there will be other and probably better ideas, I am sure):
  • Create a 'button' that shows the glossary on the web page - tabbed for initial letters, rather than a huge list
  • Some web development done to allow the same tool-tipping revelation of glossary linked words on mouse over or hyperlinking to a glossary entry definition

I imagine that it will already be in a backlog somewhere, however we are looking at publishing architecture to a wide audience with a mixed degree of capability, so simpler (in their view) is better.


This had me scratching my head as well.  The current version of the user guide still describes the previous route to find DD's.  That will have to be changed clearly.


  I expected much of what you say, however the point I am getting at is that the change is not on the actual EA client, but rather on one of the MDG plugins.  If the new installer is the only vehicle for these plugins to be updated (when they are largely separate [admittedly they have to be assured to work]) then the cadence of delivery and close adherence to standards (which is a great point in Sparx favour) is diminished.

Sadly I don't know the internal structures and working practices of Sparx, so I don't know if the MDG work is carried on in parallel, feeds into the main EA deployment streams etc.  Hence the question.

While I am immediately interested in the Archimate case, the general approach is of wider interest I think for the whole community.

Apologies if I have missed any previous post outlining this.

kind regards.

 As you will be aware, 5th November 2019 saw the release of the Archimate 3.1 Standard.  There are a couple of relationship changes and the introduction of a new element in the Strategy Layer -the View Point.  All well and good.  Bearing in mind that most of the MDG plugins are bundled into the same installer now, I have a couple of questions:

  • Why is the new Archimate plugin not available yet for EA?  It has been HOURS for crying out loud :)
  • What is the process for getting it in the future - a download of the plugin to replace what is already in the install path, a full download of a new EA version/release, etc?
  • Who is responsible for creating the new version of this or any other addin that is shipped with the install binaries?

Of course I realise that this will take some time to address - there are other things happening, the correct team/supplier has to be engaged, do the work, deliver, pass QA, be scheduled for integration, etc etc.  Is there a commonly deployed pattern to deal with this sort of activity, as I am sure it comes up a fair amount, with the number of standards that EA conforms or complies with?

p.s.  If it does require a new EA release, please, please, please try to resist the attraction of changing the menus again!  Nothing more embarrassing when trying to extol the virtues of the application to new users in a new environment when I cant find the commands because it is a newer or older installation.  You guys are crazy :D

in the process of migrating our services and when recreating the database connection managers, I get SSL errors when trying to use the ODBC for SQL Server drivers (most recent possible, with SQL Server 2017 SSMS on a SQL Server 2016 Std platform).  I can use the native SQL client to set up the connection, however when I try to save the manager settings, i get an invalid connection string error.  I can manually change the string then to the old style SQLOLEDB and it lets me save (and doesn't flag as '(old)').

Can anyone explain what is happening under the hood?  I am at a loss really.  Ideally we would use the webconfig client (less logging onto the servers themselves), however this behaviour seems a bit inconsistent.

any ideas appreciated.

that would do it:)

I will get the upgrade installed as part of our server move.

as always, very many thanks!

kind regards

Clumsy title, however...

we have Prolaborate looking at various models and in all of the repositories when we click on a diagram navigation element to open the diagram it references, the system does a fetch, opens the requested diagram, pauses for a couple of seconds, then reloads the previous (launching) diagram.  This happens in Firefox and Chrome, but not on MS Edge.  IE of course doesn't play well at all.

Has anyone else come across this, and if so is there a simple fix, rather than bugging the support team with a ticket :).

Did you solve the Prolab diagram bouncing, and if so, how?



 indeed we will be reordering the model structure across a number of repositories and merging them into one project so that we can run analysis, generate reports etc.

Many thanks for the reply - it is the way that we will set things up.

kind regards

I have been tearing my hair out, but expect that there is a simple solution to this.  I have a multipart document representing a software design description that I am pulling out of a (rather messy) EA model.  for one of the sections, the engineer wants to have a specific diagram, with its notes and descriptions of all of the objects on it as a section of the document.

i can pull the diagram (or shallow copy) into a specific folder and target a model document against it.  Leaving it in place (with other diagrams) means that the generator will return all of the diagrams in that package.  I would rather use either the QBF or custom SQL query to generate this.

What am I missing?

there is work in line to harmonise the model structures such that everyone is representing the same 'stuff' in the same way (please dont ask...) as well as striking the balance between ease of navigation for non-modellers and document generation and modellers thought patterns, however to get over the current hump I have a series of structures of model documents, templates, fragments (duct tape, string and hope) pulling it together; except this 'pull a single diagram' into a fragment and report on it.

any advice appreciated!

Running some structured specs and trying to extract the test cases into a suite.  This creates the base test case object and a diagram however it only places the basic path object onto the diagram.  There is no generated alternate or exception path objects created in the tree or placed on the diagram.

Have tried this on cloud models (IIS web served with SQLServer 2016 SP1, client on Win10, EA version 14.1 build 1427) and local eapx files- same result.

Has this been seen before, or is there a reasonable workaround?  Looking to get our test teams to start the processes here and port to RQM, rather than just straight into RQM.

The EA Backroom boys have pointed out that there is a bug in Jazz 6.0.3 which prevents the correct enumeration of folders etc.  We upgraded our test rigs to 6.0.6 and everything works fine.

Thanks guys!

Has anyone got this to work yet?
we have set up a test using the trial version with all servers on the same LAN and domain.  I can see the Jazz connection through the specialise function, however it only lets me navigate to teh repository, then the project, before throwing an error (External Data (Jazz - DoorsNG): Failed to transform menu level 2 list XML).

I have a ticket in with the boys down under, however I am hoping that there is something obvious that I am missing.

Windows domain, Jazz 6.0.3, cloud and DB on same box, server 2016, client EA 14 ultimate.  Default installs all around.

Any ideas?

kind regards

General Board / Re: Migration from Rhapsdody to EA
« on: June 06, 2018, 08:16:04 pm »
This is an issue we are seeing as well.  Importing via the rpy file omits the diagrams completely.  Importing through XMI creates multiple DAORecordset [3022] errors, creates duplicate named packages with different contents and only imports sequence and a few activity diagrams.  No sysML diagrams (BDD or iBD) coming across.  have tried stripping GUID's etc as well of course.
It is a weird one, and something that I have worked around before  I just cannot recall what we did.

any advice from the EA Druids would be appreciated :)

Pages: [1] 2