Components

Required Roles n/a
Required Rights
(by category)
Applications
Perspective  Configuration Management
Access  DROPS Server Artifacts →  Applications →  Application editor → z/OS Components tab

Components are unique, functional subdivisions of applications used to structure releases created when artifacts are imported into the artifact repository. Components should group an application's artifacts by the intended deployment target because every artifact in a component will be deployed to the same infrastructure item.

A component can only belong to one application but an application can have many components. They are used to manage import strategies and are the parent entity for imported artifacts in the artifact repository's hierarchy. Artifacts that belong to a component can come from different sources which means that a component can contain multiple import strategies, which each provide DROPS access to the artifacts to import.

During the deployment process, the contents of components (artifacts) are deployed to target systems following the same directory structure defined in the artifact repository. The structure inside the component node is defined in each import strategy.

Example

Your application is a software product that uses a web-based interface to connect to a server. Both the website and the server are required for the application to work correctly. The server is located in New York but the website's source HTML files and the .css style sheet must be hosted in Paris. The application should contain two components - one for each destination.