Use > Create Designs > View Component Types > Create a Component Type

Create a Component Type

For more information about component types, see Components (Sequenced Designs).

To create a component type

  1. In the left pane of the Sequenced Components area, select the component palette in which you want to create a component type.
  2. Click Create Component Type.
  3. Provide the following information and then click Create.
Item Description
Base Component Type

Select the component palette from which you want to select a base component type, and then select a base component type from which the new component type will inherit properties and constraints. Component types are not required to have a Base Component Type. The lists display only component palettes and component types that are compatible with (that is, they do not create circular dependencies with) the palette in which you are creating the component type.

This field cannot be modified after a base component type has been selected.
Name A name for the component type. The component type name must be unique within a component palette. No white space is permitted; all letters are changed to upper case for this value. This field cannot be modified after a component type has been created.
Display Name The name that displays for the component type.
Description The description you provide for the component type.
Image An image that displays for the component type. Click Change Image. Choose the image you want, and click Select. Click Upload to add your own image. Supported file extensions include .jpg, .jpeg, .gif, and .png. The recommended image size is 256 by 256 pixels, and the image will be scaled to the appropriate size. The images are stored in the %CSA_HOME%\jboss-as\standalone\deployments\csa.war\images\library folder of the Codar server.
Default Settings

Select the following items as needed. These items specify the initial default values for service components:

  • Consumer Visible - Select this box to specify that, by default, the service component is visible in the Marketplace Portal. Deselect it to specify that the service component will not be visible.

    Properties and lifecycle actions that have been configured as consumer visible will only display in the Marketplace Portal if the associated service component itself is configured to be visible. The visibility of a service component does not affect visibility of its child service components, and it is not necessary for a parent of a service component to be visible for the child component to be visible in the Marketplace Portal.

    • Note Marketplace Portal is available only when the CSA license is applied.

  • Pattern - Select this box to mark the service component as a pattern by default. This indicates that the service component will not be automatically processed by the lifecycle engine. When you create a pattern service component, you must also create a Clone Pattern action in the parent service component. If the Clone Pattern action is not created in the parent service component, a validation error is displayed in the designer. For example, the out-of-the-box component type, Server, is typically marked as a pattern, and its parent service component, Server Group, includes the Clone Pattern action.

    • You can identify a service component that is marked as a pattern because its icon appears with a grid-like background, as shown below.

 

Send Help Center feedback