Topics

1

Automation Interface, Add-Ins and Tools / Alias and notes not safed in toolbox profile (EA 14)

« on: October 24, 2018, 12:29:36 am »

In my toolbox profile I wrote the following into my diagram notes:
Alias=Activity;Notes=The toolbox for the activity diagram;

But when I save this toolbox profile with EA 14 (Design > Diagram > Edit > Advanced > Safe as Profile...), EA doesn't save the alias and notes into the xml file.
Is this a bug in EA 14, or am I doing something wrong?

2

Automation Interface, Add-Ins and Tools / Stereotype from Action metaclass with 'Atomic' as default notation kind

« on: October 23, 2018, 11:14:29 pm »

In which property of the Stereotype or Metaclass could you configure the default notation kind for an action?

3

General Board / Auto creation of a composition with ArchiMate

« on: October 11, 2018, 10:55:23 pm »

Does EA has a feature that automatically creates a composition if you drag an ArchiMate element into another ArchiMate element?
E.g. a business process into a business proces.

Thanks,

Matthias

4

Automation Interface, Add-Ins and Tools / UML Elements for MDG Toolbox

« on: October 08, 2018, 06:05:08 pm »

I want to fill my Toolbox with some UML elements. The standard UML elements are listed below, and I can add them to the toolbox by adding them as an attribute
to the stereotype.

e.g. UML::Actor for an Actor.

But what can I use to represent a 'Use' or an 'Include' association on a use case diagram? Is there a list available of ALL (not just UML) elements and relationships that I can add to the toolbox?

Connector names for Toolbox Page definitions
•   Abstraction
•   Aggregation (Aggregate)
•   Assembly
•   Association (Associate)
•   AssociationClass (Association Class)
•   CallFromRecursion (Call)
•   CommunicationPath (Communication Path)
•   Composition (Compose)
•   Connector
•   ControlFlow (Control Flow)
•   Delegate
•   Dependency
•   Deployment
•   Extension
•   Generalization (Generalize or Inheritance)
•   InformationFlow (Information Flow)
•   InterruptFlow (Interrupt Flow)
•   Invokes
•   Manifest
•   Message
•   Nesting
•   NoteLink (Note Link)
•   ObjectFlow (Object Flow)
•   Occurrence
•   PackageImport (Package Import)
•   PackageMerge (Package Merge)
•   Precedes
•   ProfileApplication (Application)
•   Realization (Realize or Implements)
•   Recursion
•   Redefinition
•   Representation
•   Represents
•   RoleBinding (Role Binding)
•   SelfMessage (Self-Message)
•   Substitution
•   TagValAssociation (Tagged Value)
•   TemplateBinding (Template Binding)
•   TraceLink (Trace)
•   Transition
•   UCExtend (Extend)
•   UCInclude (Include)
•   Usage
•   UseCaseLink (Use)


Element names for Toolbox Page definitions
•   Action
•   ActionPin
•   Activity
•   ActivityFinal (Final)
•   ActivityInitial (Initial)
•   ActivityParameter
•   ActivityPartition (Partition)
•   ActivityRegion (Region)
•   Actor
•   Artifact
•   AssociationElement (Association)
•   Boundary (for Use Cases)
•   CentralBufferNode (Central Buffer Node)
•   Change
•   Choice
•   Class
•   Collaboration
•   CollaborationOccurrence (Collaboration Use)
•   Comment (Note)
•   Component
•   Constraint
•   Datastore
•   Decision
•   DeploymentSpecification (Deployment Specification)
•   Device
•   DiagramLegend (Diagram Legend)
•   DiagramNotes (Diagram Notes)
•   DocumentArtifact (Document Artifact or Document)
•   Entity (Information)
•   EntityObject (Entity)
•   EntryPoint (Entry)
•   Enumeration
•   ExceptionHandler (Exception)
•   ExecutionEnvironment (Execution Environment)
•   ExpansionRegion
•   ExitPoint (Exit)
•   Feature
•   FinalState (Final)
•   FlowFinalNode (Flow Final)
•   ForkJoinH (Fork/Join - Horizontal)
•   ForkJoinV (Fork/Join - Vertical)
•   Gate (Diagram Gate)
•   GUIElement (UI Control)
•   HistoryState (History)
•   Hyperlink
•   InformationItem (Information Item)
•   InitialState (Initial)
•   InteractionFragment (Fragment)
•   InteractionState (State/Continuation)
•   Interface
•   InterruptibleActivityRegion
•   Issue
•   Junction
•   Lifeline
•   MergeNode (Merge)
•   MessageEndPoint (Endpoint or Message Endpoint)
•   MessageLabel (Message Label)
•   Metaclass
•   Node
•   Object
•   ObjectBoundary (Boundary)
•   ObjectControl (Control)
•   ObjectEntity (Entity)
•   Package
•   PackagingComponent
•   Part
•   Port
•   Primitive
•   PrimitiveType
•   Process
•   Profile
•   ProvidedInterface (Expose Interface)
•   ReceiveEvent (Receive)
•   Requirement
•   RobustBoundary (Boundary)
•   RobustControl (Control)
•   RobustEntity (Entity)
•   Screen
•   SendEvent (Send)
•   SequenceBoundary (Boundary)
•   SequenceControl (Control)
•   SequenceEntity (Entity)
•   Signal
•   State
•   StateMachine (StateMachine)
•   StateTimeLine (State Lifeline)
•   Stereotype
•   StructuredActivity (Structured Activity)
•   SynchState (Synch)
•   Table
•   Terminate
•   TestCase (Test Case)
•   Text
•   UseCase (Use Case)
•   UMLBoundary (Boundary)
•   ValueTimeLine (Value Lifeline)

5

General Board / Versioning with composed components

« on: June 22, 2018, 05:15:28 pm »

We model our integration architecture and API's with ArchiMate symbols. An API (ArchiMate_ApplicationService) is composed of some components (ArchiMate_ApplicationComponent)

- API (ArchiMate_ApplicationService)

• Gateway (ArchiMate_ApplicationComponent)
• Java Code (ArchiMate_ApplicationComponent)
• Integration  (ArchiMate_ApplicationService)
• AS400 Service  (ArchiMate_ApplicationService)
• RPG Routine  (ArchiMate_ApplicationComponent)

Suppose there is a new version of the ESB Admissibility service that impacts the whole Admissibility API so we need to deploy a new version of that API. In the Admissibility API v2.0, we will use the new ESB Admissibility v2.0, but for all the other components we reuse the v1.0 versions. A big remark is that we will stil use the Admissibility API v1.0 besides the Admissibility API v2.0 for some implementations.

The v1.0 components that we will reuse in the Admissibility API v2.0, can't be duplicated in EA as parts of the two versions of the Admissibility API, and that's a big problem...
For example the Admissibility GW v1.0 must be a part of Admissibility API v1.0 and Admissibility API v2.0, how can we handle this?

6

Automation Interface, Add-Ins and Tools / EAI Patterns

« on: May 31, 2018, 07:37:22 pm »

Does anyone know if there's an MDG available to model EAI patterns?

7

General Board / How to model an API architecture

« on: April 11, 2018, 10:04:25 pm »

I search some examples of the modelling of an API architecture in EA. Starting from the canonical/logical data model, over inner API's to consumer API's and the front-end.

The intention is to describe a layered design:

- Front-end (HTML5 /JS)
- Consumer API
- Consumer Java code
- Inner API
- Inner Java code
- ESB
- Legacy System
- Database

The data model is located between the ESB and the Inner Java Code, because the ESB will translate the legacy data to the new data model that will be accessed through the API's. For each attribute we have to keep track of the source attribute, in order to create a mapping table afterwards.

8

Uml Process / AS400/RPG to Java API migration

« on: April 07, 2018, 05:34:54 pm »

In our company we have a monolithic as400 system with a DB2 database. The long term plan is to migrate everything to a new service oriented Java API platform.

The architectural plan is to expose the necessary RPG Routines as SOAP Web Services (1 on 1), and then transform them to REST services with the help of IBM Integration Bus. The REST services must already be based on the new data model. On top of the IIB layer we will create a Java API layer (with API Connect above) to provide data to the consumer applications. In fact, we will do SOA/API.

The problem is that the whole project approach is bottom-up, we do not have any contact with the business, only with the AS400 analyst/developers (dinosaurs  .

One of the steps in the whole plan is to create use cases, use cases that will be used to create the granularity for the API's. So, my question is, what is the best approach to create use cases, bottom up, from AS400 RPG routines?

9

Automation Interface, Add-Ins and Tools / Generate data model subset + JSON

« on: December 22, 2017, 02:19:03 am »

With the Message Composer from Geert Bellekens it's possible to create a subset from the canonical data model.
But if you want to generate JSON files you have to run the Schema Composer and create a new schema from that subset.

Is there a solution to do this in a simple way: create subset + generate json file?

Thanks

10

General Board / Associations & the Schema Composer

« on: May 11, 2017, 11:58:08 pm »

I create e schema in EA13 and add some classes without to that schema, logically there are no associations visible in the schema composer.
But now, when I add the associations afterwards to my class diagram, the associations are still not visible in the schema composer. Next step, I remove the classes from my schema composer and add them again in the hope that the associations will be visible, unfortunately still no associations visible in the schema composer.

What next? I create a new schema and add my classes, now, the associations are visible.

Is it normal that you need to create a new schema to get some changes on your class diagram visible in the schema composer?

11

Automation Interface, Add-Ins and Tools / Set diagram page orientation with script

« on: May 10, 2017, 10:58:11 pm »

The following code creates a class diagram under the BIGroup element, this part works. But when I try to set the orientation of that class diagriam to landscape, it seems not working. When I debug it by showing a message box with the orientation, he gives me an 'L'.

Code: [Select]

function EA_OnPostNewElement(Info)
    dim elementID
    elementID = Info.Get("ElementID")
dim BIGroup
set BIGroup = Repository.GetElementByID(elementID)
dim classDiagram 'as EA.Diagram
set classDiagram = BIGroup.Diagrams.AddNew("LDM-BI Entities Overview", "Class")
classDiagram.Orientation = "L"
classDiagram.Update()
BIGroup.Diagrams.Refresh()
end function

12

Automation Interface, Add-Ins and Tools / Broadcast Event for dragging Attribute to Object

« on: May 02, 2017, 08:31:49 pm »

Which Broadcast Event occurs when an attribute is dragged from the project browser to an element (f.e. a class)? I tried with the EA_OnPostNewAttribute(Repository, Info) event but no results...

Thanks,

13

Automation Interface, Add-Ins and Tools / Value of 'Direction' in the database

« on: April 05, 2017, 08:04:30 pm »

On the label of a connector you can choose the direction so that a litle black arrow appears. Now I want to query that value, but I can't find  that value in the DB.

14

Automation Interface, Add-Ins and Tools / Hide stereotype notation

« on: March 25, 2017, 01:44:29 am »

When you create an mdg with uml profiles, and you don't use shapescripts, how can you prevent that the stereotype appears on your diagram?

15

Automation Interface, Add-Ins and Tools / VBScript - Remove duplicate elements from arraylist

« on: March 10, 2017, 04:26:06 am »

Is it possible to remove duplicate elements from an arraylist?
I tried with some functions but no success.

Code: [Select]

'returns an ArrayList without duplicates
function removeDuplicates(arraylist)

dim result
set result = CreateObject("System.Collections.ArrayList")

dim element as EA.Element
for each element in arrayList
dim b
b = contains(arraylist, element)

'if contains then
'
'else
'
'end if


next
set removeDuplicates = result
end function

Code: [Select]

'returns boolean
function contains(arraylist, element)
set contains = false
dim res as EA.Element
for each res in arrayList
if res.ElementID = element.ElementID then
set contains = true
exit for
end if
next


end function