Viewing dependent assets

The Dependent Assets view shows which assets are used by each service, whether they are in the same project or a different one. You can also directly go to the integration where an asset is used from this view.

About this task

Dependent asset in packages refers to the components or resources that a package relies on to function properly. These packages can include the following files:

Other packages - A package might depend on services or utilities that are provided by another package. You can define these dependencies explicitly in the package settings.
Connections - If your package uses services such as JDBC or SAP, it needs properly configured and accessible adapter connections to function correctly.
Shared resources - The resources include schemas, document types, or shared services that are used across multiple packages.
External libraries - External JAR files or libraries that the package is dependent to function.
Configuration files - Some packages might require specific configuration files such as .cfg or .xml to be present and correctly set up.

Procedure

From the navigation pane, go to Projects and select a project.
Click Packages.
The Packages page is displayed listing packages that are already added to the project.
Click the package that you want to update.
The Package Information tab is displayed.
In the Assets tab, click the asset name that is displayed under Name.
The Dependent Assets are displayed on the right side of the page.
View all the dependent assets that are there in your projects.
Optional: To view the usage of assets, you can filter the assets based on the following types:

Flow services

Displays assets that are categorized on the service type, for example, Flow services.

Others

Displays assets of other types such as document types, adapter connections, or Java™ services.
In Usage Information, click the asset name.
The integration in which the asset is used appears in a new page.