Inventory and compliance

The inventory for an environment lists the component versions that are intended to be deployed to that environment. Compliance shows whether the environment actually contains those component versions.

The inventory and compliance for an environment are updated each time that you run an application process or deploy a snapshot to the environment. For example, assume that you run an application process that deploys two component versions to an environment. Regardless of whether the application process completes successfully, the environment inventory shows that the two component versions are deployed. The compliance shows how many of the components installed successfully. In this way, the inventory shows the intended state of a resource or environment, while the compliance shows how closely the resource or environment matches the intended state.

The environment inventory and compliance track components, not snapshots or applications. For example, if you successfully deploy a snapshot with two component versions, the inventory is 2 components and the compliance is 2 components. If you successfully deploy a different snapshot with versions of two different components, the inventory is 4 components and the compliance is 4 components. In this way, the server counts component versions for inventory and compliance, not the versions in a snapshot or applications.

The inventory provides complete visibility into the different versions of your applications, which can be tracked back to the original artifacts imported into IBM® UrbanCode Deploy. There are different views of the current inventory, depending on where in IBM UrbanCode Deploy you are. Inventory information is available on the individual components, for every application environment, and for each agent resource.

Feedback