LeanIX EAM Discovery
Out-of-the box integration with LeanIX Enterprise Architecture Management
Introduction
The LeanIX EAM integration with the EAM workspace will allow you to:
- Bring in Business Applications from EAM to VSM to understand your business applications top to bottom including their software/runtime/cloud footprint in detail
- Provide further business context around the software artifacts to drive holistic insights within VSM
Setup
The LeanIX discovery integration will fetch relevant Fact Sheet data from your EAM workspace and automatically create Fact Sheets. Those will be kept up-to-date by running this integration on a schedule.
The LeanIX integration needs to be set up on your VSM workspace.
Activating the integration
Please reach out to your CSE/M to have the integration fully enabled in your workspace.
Configuration
In your LeanIX VSM workspace, go to Administration > VSM Integrations and follow the instructions to set up the EAM integration.
Configuring the EAM integration
Sync Logging
Open "Sync Logging" tab to get understand the progress of your current integration run. Sync Logging also provides information on previous integration runs
Scheduling your integration
To run the integration on a schedule - you can specify the schedule via the schedule parameter during the integration setup.
The recommendation is to run this integration once a day.
Scheduling options
Imported data
The connector is suggested to be set on a daily schedule but can be adjusted to individual needs. The table below states the information that is synchronized across the workspaces:
| EAM | VSM |
|---|---|
| Application fact sheet and backlink to VSM | Product fact sheet and backlink to EAM |
| Subscriptions of type Accountable and Responsible on Application fact sheet | Subscription of type Responsible and role EAM Application Owner on Product fact sheet. Note: For now both Responsible & Accountable subscription roles from EAM are registered as Responsible on the Product Fact Sheet. This is to be changed in the near future to maintain consistency with the EAM subscription roles. |
| Application fact sheet parent child relation | Product fact sheet parent child relation |
The table below states what information is removed/ deleted from the VSM workspace when it's counterpart in EAM is deleted
| EAM | VSM |
|---|---|
| Application fact sheet is archived | Corresponding Product fact sheet is archived |
Leveraging the full power of the two integrations (EAM & VSM)
Setting this integration up along with the VSM integration (in EAM) will allow the system to automatically link your applications in EAM to their discovered software artifacts (brought in by the VSM integration as IT Components, subtype Microservices ). Hence, this will allow for an automatic link between applications and IT components, subtype Microservices in EAM.
Requirement: you need to link Products in VSM to their respective Software Artifacts in VSM
Securing Data Reliance
Within the integration(s) between workspaces a leading system is defined for each Fact Sheet type and even individual attribute. This ensures data between workspaces is always in sync and does not need to be manually tracked or followed up. However, to bring this even further and make sourcing clearer for end users you can define as "read only" in LeanIX Self-Config in the respective workspace - this avoids user confusing completely as edits can only be made in the source workspace. Note: for some fields read-only is not a possible self-config option, here it might make sense to employ the auth model to prevent changes. Alternatively, the help texts of the fields could help to sharpen the user's awareness that these fields are exclusively sourced from EAM.
Updated about 1 year ago