Working with pattern plug-ins
Plug-ins provide the constituent parts of a pattern and the underlying implementation so that the pattern is deployable in the cloud. Pattern types, the containers of solution-specific and topology-specific resources that are required for different types of patterns, are collections of plug-ins. Virtual system patterns are based on the IBM® Virtual System Pattern Type. Virtual application patterns can be based on several different pattern types.
About this task
Plug-ins contribute components, links, and policies that are available in the Pattern Builder. They are grouped into pattern types. When you create a pattern, the first step is choosing the pattern type. This choice determines the options and the user experience in the Pattern Builder. In the Pattern Builder, you can select from the components, links, and policies that the plug-ins in the pattern type provide. The plug-in that contributes a component or link completely determines its semantics and operation. Components, links, and policies are the most user-visible capabilities a plug-in can contribute, but a plug-in developer must also include other capabilities. Plug-ins are responsible for the implementation of components and links when a pattern is deployed, and maintenance through the entire lifecycle of the instance. A plug-in must contribute appropriate lifecycle scripts to manage the instance through its various lifecycle events.
A pattern type is a collection of plug-ins that are designed for a specific type of pattern and used as the foundation of the pattern. For example, a database virtual application pattern uses the IBM Cloud Pak System Software. When a user selects a pattern type in the Pattern Builder, the design experience is determined by the associated plug-ins.
For more information about working with plug-ins, see the Related tasks section.