Workspace Setup for Self-Built Software Discovery

🚧

Early Adopter Release

This feature is currently in early adopter release and may not be available to all customers.

Introduction

Before setting up microservice discovery, provision the self-built software discovery feature in your SAP LeanIX workspace. Provisioning extends the meta model by adding the microservice fact sheet subtype, along with essential fields and relations. This enables discovered microservices to be added as fact sheets and linked to relevant business applications, and responsible teams. For more details, see Meta Model Extension.

Provisioning and Configuration

To provision the self-built software discovery feature, do the following:

1. In the administration area, open the Self-Built Software Discovery section.
2. Click Provision.

📘

Note

Provisioning is done only once. If you tinker with any of the newly created relations and fields or delete them, you need to manually bring them back into your meta model. For details on relations and fields, see Meta Model Extension.

Customizing Relations

In SAP LeanIX, the customer owns the meta model. Depending on your needs, you have the option to choose a different relation between the microservice subtype and the teams or business application subtypes that you have created in the meta-model.

Incoming manifests base connections on the configured relation to link the microservice with the team and business application subtypes when references to teams or applications are present in the manifest. To learn more, see Manifest File and Schema. Also, the SBOM explorer uses these relations to fetch and show the associated teams and business applications.

🚧

Caution

Before adjusting relation settings, carefully consider potential implications and proceed with caution. Relations that were created earlier are not automatically updated unless the corresponding fact sheets are updated through the manifest file.

To adjust relation settings, click Edit next to Provisioned Relationships, select the custom relations from the relevant drop-down lists for the teams and business application subtypes, then save the changes.

Enabling Tech Stack Discovery

You can enable the detection and creation of IT components underneath the discovered microservices by selecting the Enable Tech Stack discovery via the SBOM check box.

Technologies derived from SBOM data are matched against a curated reference catalog to detect and automatically create IT components. To learn more, see Tech Stack Discovery from SBOMs.

Meta Model Extension

SAP LeanIX Technology Risk and Compliance extends the meta model by adding the microservice fact sheet subtype, along with additional fields and relations that offer more context about each microservice. The meta model extension as part of SAP LeanIX Technology Risk and Compliance includes the following:

• Microservice fact sheet subtype to capture microservices as application subtype.
• Relation between microservice and business application fact sheet subtypes to indicate which business application uses a specific microservice.
• Relation between microservice and team fact sheet subtypes to capture which team uses a specific microservice.
• Other fields that provide more context about discovered microservices:
  • Repository Status: indicates if the underlying git repository is active or inactive
  • Repository Visibility: indicates if the underlying git repository is internal, public, or private
  • Repository URL: the URL of the underlying git repository
  • Technology Discovery ID: holds the external ID that uniquely identifies the microservice from an external source (e.g., GitHub).
  • Is SBOM attached: to indicate whether an SBOM is linked to the fact sheet. The number of SBOM components linked to the fact sheet is shown on the right side pane of the fact sheet.
  • Type: the type of microservice to help differentiate the different nuances, for example, UI (micro frontend), Backend, Data (ML/AI service), etc.
  • SBOM URL: the URL to the SBOM explorer for the particular microservice.

📘

Note

All relations and fields mentioned above are conditional attributes and are visible only in respective subtypes. To learn more, see Fact Sheet Subtype Management.

🚧

Caution

The fields mentioned above are essential for the functioning of features and should not be deleted. However, you can perform other actions, such as changing their positions on the fact sheet or hiding them, without any issues.