7 docs tagged with "type system"

When customizing Deploy, it is recommended that you start by extending configuration item (CI) types and writing rules.

Deploy's type system allows you to customize any configuration item (CI) type by adding, hiding, or changing its properties. These properties become a part of the CI type and can be specified in the deployment package (DAR file) and shown in the Deploy GUI.

You can define new configuration item (CI) types in Deploy. When you specify a new type, its base (a concrete Java class or another synthetic type), and its namespace, the new type will become available in Deploy. The new CI type can now be a part of deployment packages and created in the Repository browser. Each of the three categories of CIs (deployables, deployeds, and containers) can be defined this way.

In Deploy, you can define methods on configuration items (CIs). Each method can be executed on an instance of a CI via the GUI or CLI. Methods are used to implement control tasks, as actions on CIs to control the middleware. An example is starting or stopping a server.

This topic will explain how to create an enum kind property fully in synthetic.xml. In previous versions of the product(s) you needed to have a compiled Java Enum class on the classpath to define the values of the enumeration. Now you can add the following properties to the synthetic.xml file of your plugins / extensions:

The Apache Tomcat plugin for Deploy is designed to be extended through Deploy's plugin API type system. For more information about this plugin, see Apache Tomcat plugin.

Deploy stores all of its information in the repository. The Explorer gives you access to the configuration items (CIs) in the repository and allows you to edit them manually.