11 docs tagged with "discovery"

You can define control tasks on configuration items (CIs) to execute actions from the Deploy GUI or CLI. Control tasks specify a list of steps to be executed in order.

You can use the discovery feature to import an existing infrastructure topology into the Deploy repository as configuration items (CIs).

This topic covers using the discovery feature to automatically create an accurate model of your infrastructure in Deploy. During discovery, Deploy scans your middleware environment and creates configuration items (CIs) in the repository. Discovery is part of the Deploy plugin suite, and the exact discovery functionality available depends on the middleware platforms that are present in your environment.

Deploy does not allow the creation or discovery of multiple CIs with the same name, and considers them as duplicates. However, Websphere allows the creation of such resources with the same name, as long as they are of different types.

The Kubernetes plugin supports discovery of k8s.Master and k8s.Namespace CIs from a Kubeconfig file. To discover,

This topic describes how the Generic plugin supports discovery in any subtype of generic.Container, generic.NestedContainer, or generic.AbstractDeployed.

This topic explains about Discovery in the IBM WebSphere AS plugin.

This topic describes how to use the JBoss Application Server plugin to discover properties of a running JBoss server after specifying the JBoss server home location and the host on which the JBoss server is running.

This topic explains how to use the Deploy WebLogic (WLS) plugin to discover middleware containers on a server running Oracle WebLogic after specifying the host and domain.

This topic covers tasks in Deploy, which are activities with steps for deploying, updating, or managing applications that can be scheduled, recovered, and manually archived post-execution.

This topic describes how to manage deployments and resources using JBoss Domain or jbossdm plugin.