Using Custom Source Configuration Types

You can select the custom source configuration types in the Source Config Type drop-down when you are creating or configuring a component.

Following are some things to expect when using an external source configuration type, whether or not it is custom.

• If you attempt to delete a source configuration type that is packaged in a jar with multiple custom source configuration types, you'll receive a warning message that this will delete all of the custom source configuration types that packaged with this one. If you choose to delete, the source configuration type jar is physically deleted from the profile location.
• If a new version of a custom source configuration type is loaded that has additional required fields, you are notified about the missing required fields when you view or edit a component that is configured with that source configuration type.
• If a component is configured with a custom source configuration type that is missing, the component page has an alert message that says to reconfigure the component. This can happen if:
  • Someone deletes the source configuration type
  • The Deployment Automation server starts without loading the custom source configuration type, due to an error loading the jar file or jar files missing from the profile location
• Importing versions works the same as for built-in source configuration types. See Importing Component Versions.
  Tip: You must select Copy to CodeStation if you want the versions to be imported into the Deployment Automation version file system. This is the preferred setting, as it enables you to track the inventory of your versions in environments.