Resources

A resource is a logical deployment target that typically resolves to an agent.

A resource can represent an agent, agent pool, component, or an organizational entity that is used to group other resources. A component-type resource can point directly to the agent or agent pool that deploys it, or point to another resource in a hierarchical chain of resources. If a resource is part of a hierarchy, it delegates its automation, if any, up the chain until it finds an agent.

A group-type resource can represent any logical collection of resources. In the following illustration, the top-level resource, myCompanyEast, represents a data center that contains the Development subresource (which represents an environment). In this instance, myCompanyEast does not point to any higher-level resource. The resource tomcat represents a component, and delegates its automation up the chain until it reaches the tph1 resource, which represents an agent. In order for an agent to be invoked, at least one resource must be defined for it.

Resources are created on the Resources page, which displays resources in a hierarchical tree structure. By displaying all resources across all environments, the Resources page provides a single place to see your entire infrastructure.

The hierarchical structure is used wherever resources are used and not just on the Resources page, such as when assigning resources to environments. The hierarchical model is especially effective when several logical deployment targets reside on the same machine. In the accompanying illustration, the resources tomcat and tomcat-e represent servers on the same machine where the agent tph1 is located. Both can be individually targeted for deployment.

Selecting a resource selects every resource below it, if any, in the hierarchy; for example, deleting or moving the tph1 resource deletes or moves the tomcat and tomcat-e resources as well.

Whether you need one or multiple resources per environment is determined by your current infrastructure, deployment procedures, and other requirements. Many IBM® UrbanCode Deploy users have significant differences among environments. Whatever your structure, the Resources page displays the entire infrastructure across all environments.

If you are using IBM WebSphere® Application Server, you can import information from cells as resources; see Importing resources from WebSphere Application Server.


Feedback