To include a classification attribute or relationship attribute in your custom asset type, make sure that the corresponding taxonomy exists before you begin creating the custom asset type. To add a classification attribute or relationship attribute to the custom asset type, you must specify the taxonomy with which the attribute is associated. You cannot do this unless the taxonomy already exists in CentraSite.Consider using classification attributes and relationship attributes instead of ordinary String attributes whenever possible. Among other benefits, these attribute types enable users to more easily discover assets and understand the relationships that an asset has with other objects in the registry.In general, use a classification attribute or an enumerated String attribute instead of an ordinary String attribute when you want the attribute to be more functional.Instead of defining multiple asset types to represent variants of the same basic type, consider creating one basic type and using a classification attribute to differentiate them. For example, instead of creating separate asset types for different kinds of Web services (for example, business services, technical services, security services), use the one basic Web service asset type and use a classification attribute to classify its variations.When you are creating a custom asset type, think about the design/change-time polices that you may want to apply to assets of that type. If you need to apply different policies to different sub-sets of the asset type, use a classification attribute to differentiate the sub-sets.If you do not want users to be able to assign ad hoc classifiers and associations to instances of a particular type of asset, omit the Classifications and Associations profiles from that asset's type.To provide different views of an asset to different users or groups, divide the attributes among profiles in a way that enables you to use profile permissions to selectively show or hide the appropriate set of attributes to different users or groups.
To add a custom asset typeField | Description | |
Name | Type a name for the new asset type. Specify a name that your users will recognize and understand. For example, use BPEL Process Document, not bpdoc. The name you assign to the asset type can contain any character, including spaces. | |
Description | Optional. Type a short description for the new asset type. This description appears when a user displays the list of types in the Asset Types page. | |
Options | Specify the options that are required to be set specific to the type. The available options are: | |
Enable lifecycle management | Allow a lifecycle model to be applied to instances of this type. | |
Enable reports | Allow reports to be generated against instances of this type. | |
Enable versioning | Allow users to generate versions of instances of this type. Note: When this option is not selected, CentraSite disables the New Version action from instances of this type. | |
Policies can be applied | Allow user-defined design/change-time policies to be created and enforced for instances of this type. Note: When this option is not selected, CentraSite does not apply any user-defined design/change-time polices to instances of this type, even in cases where the policy is designed to execute against all asset types. Note: This option does not apply to system policies. CentraSite will apply system policies to instances of this type, irrespective of the option. | |
Require consumer registration | Require users to register an application when they submit consumer registration requests for instances of this type. | |
Top level type | Allow users to create instances of this type from scratch. When this option is selected, users are allowed to create instances of this type using the Create New Asset page in CentraSite Business UI. Generally, you will not select this option for types that are constituents of other assets. For example, the Operation type is used to represent an operation that belongs to a Web service. Operations are derived automatically from the service WSDL. They are not intended to be manually defined by users. Therefore, the Operation type is not designated as a top level type. | |
Visible in asset browse | Allow instances of this type to be displayed in the Browse list. When this option is selected, CentraSite includes the type in the Choose Asset Types box (go to Browse > Additional Search Criteria > Asset Types > Choose). When this option is not selected, CentraSite omits the type from the Choose Asset Types box so users cannot browse for instances of this type. Including a type in the Choose Asset Types box enables users to define queries that select on that specific type. | |
Visible in search | Allow users to define a type-ahead Search for instances of this particular type. When this option is selected, CentraSite includes the type in the Scopes box next to the Search text box). When this option is not selected, CentraSite omits the type from the Scopes box so users cannot search for instances of this type. | |