Topology service reference

Use this introduction to the Netcool Agile Service Manager services to understand the most important topology service concepts and functions.

You can access the Swagger documentation for the topology service at the following location: https://<your host>/1.0/topology/swagger

Remember: IBM Netcool Agile Service Manager is cloud-born, and built on secure, robust and proven technologies. It is designed to be flexible and can be extended as needed using plug-in components and micro-services to cater for highly specific environments.
Refresher:
It is important that you are familiar with the following important terms introduced in the Glossary, as they will be used and expanded on in this reference section:
resource
A resource is a node in an interconnected topology, sometimes also referred to as a vertex, or simply a node. It can be anything in a user-specific topology that has been designated as such, for example a hardware or virtual device, a location, a user, or an application.
edge
An edge is a relationship between resources, also simply referred to as the 'link' between resources.
Edges have a label, which allocates them to a family of edges with specific behavior and governs how they are displayed in the UI, and an edgeType, which defines the relationship in real terms.
tenant
A tenant is represented by a globally unique identifier, its tenant ID.
The default tenant ID is: cfd95b7e-3bc7-4006-a4a8-a73a79c71255
provider
A provider is usually a single data source within the scope of a tenant.
Note: A provider's uniqueId property for a resource is unique only within the scope of a provider.
status
Status is a property of one or more resources, and a single resource can have different types of status.
Each status can be in one of three states: 'open', 'clear' or 'closed'.
The severity can be one of the following: 'clear', 'information', 'indeterminate', 'warning', 'minor', 'major' or 'critical'.
The status of a resource can be derived from events, in the case of the resource having been retrieved via the status service, or it can be supplied when resources are posted to the topology service.
Additional: For more information on how topologies are displayed in the UI, you can take a look at the topology viewer screen reference topic:User interface reference