Book a Demo

Author Topic: Software AG  (Read 5653 times)

chrisneedshelp

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Software AG
« on: September 21, 2015, 11:37:44 pm »
Hi all, new to this.
Looking at getting EA 12, but need a way of getting from a component diagram to the flow in Software AG, its a very specific XML and was hoping it possible?
chris

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Software AG
« Reply #1 on: September 22, 2015, 12:48:59 am »
Probably not out-of-the-box. Most likely you will be able to import it via a script as I did with ARIS some time ago.

(OT: Is it still something with Adabas/Natural?)

q.

chrisneedshelp

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Software AG
« Reply #2 on: September 22, 2015, 01:28:43 am »
We are using the WebMethods integration server. Do you know if something similar would be possible?
If so, would you be able to send me your script to work from?
thanks

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Software AG
« Reply #3 on: September 22, 2015, 05:09:13 am »
I have no idea of that. Unfortunately I can't send the script since it was written for a customer. It would not help much anyway since most, most likely this format is as compatible with ARIS as Windows software is with Mac.

q.

Rodrigo Nascimento

  • EA User
  • **
  • Posts: 33
  • Karma: +3/-0
    • View Profile
Re: Software AG
« Reply #4 on: September 24, 2015, 12:22:16 am »
Hi Chris,

Essentially, webMethods Integration Server's flow language is a visual language to specify the integration logic for a integration service. I can't see any reason for customising Sparx EA to generate this very specific type of (and proprietary) code. Technically it is possible, but you need to recreate all the development functionalities from WM Designer into Sparx EA, including the visual tools like Mapping.

Even if you heavily customise Sparx EA to generate WM Flow language code (XML), you can't guarantee that the next WM version will not change its behaviour, breaking all the work you've done in Sparx.

The approach that I usually use with my clients is to do all the integration architecture and design models in EA and  produce service contract artefacts (i.e. XSDs and WSDLs) that can be imported into WM, and then implementing the integration logic using WM Designer (Flow language).

Hope it helps.

Regards,
Rodrigo
Please check my blog for more EA related articles!

http://connection.rnascimento.com