My organization uses ESB heavily for the services our application expose and consume. Application don't interact with each other but through ESB services. Services can be atomic, composite, or simply pass through.
I'm struggling to find a way to model this effectively in LeanIX. There is no "Service" factsheet type and this doesn't fit entirely as an "Application" expect it does have consuming and exposing interfaces. If I do not model this as "Application", it won't be recognized in the data flow diagram.
I think services developed using this architecture pattern (SOA on ESB) is quite common in the industry and I would like to understand how is this done by others and if there is any best practices to model this in LeanIX.