Hello friends
What is the best way to map banks in an Application architecture in LeanIX? Which factsheet is the most appropriate one keeping in mind that there will be interfaces to these banks?
Regards, Akash
Solved
Mapping banks in an Application Architecture
Best answer by Graham Howe
I created a single application for each type of external partner I’m integrating with, for example Bank, Customer, 3PL etc. Then I added three fields to the Interface fact sheet:
Exposure - single select with options of Internal, External Application and External Partner
Partner Name - text field where the name of the partner can be stored
Partner Type - single select where I also record the types of partner as 3PL, Customer, Bank etc
This means I have minimal additional ‘Applications’ created but can still report on interfaces based upon external partners.
Hello friends
What is the best way to map banks in an Application architecture in LeanIX? Which factsheet is the most appropriate one keeping in mind that there will be interfaces to these banks?
Regards, Akash
Hi Akash, are you referring to banks as financial institution? sorry if is an obvious question.
+1Hallo
when we send data via Interfaces to our Banks we see it as an service, so we define this type of external endpoint as Application, Category Microservice without Business Caoability assigned (so it does not count vs your license). You can additionally define the bank as an user group, too and add it to the Microservice.
Best regards,
Carsten
I created a single application for each type of external partner I’m integrating with, for example Bank, Customer, 3PL etc. Then I added three fields to the Interface fact sheet:
Exposure - single select with options of Internal, External Application and External Partner
Partner Name - text field where the name of the partner can be stored
Partner Type - single select where I also record the types of partner as 3PL, Customer, Bank etc
This means I have minimal additional ‘Applications’ created but can still report on interfaces based upon external partners.
We created a new fact sheet ‘External App’ as it is not part of the landscape we own and are responsible for. So we don't want them in all kind of reports. But indeed to make the interface visible between our Applications and those of external parties we created this Fact sheet type with just a small set of fields.
We don't use subtypes to identify the external partner yet. Could be an easy add-on if needed in the future. (Bank, Government, Partner etc...)
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.