# Writing Components ## Component Types The first step in writing a custom component is to choose what type of component you need. The component types are broken down by basic function. Almost all components you write will be one of the first three (which are document transformers). When creating a new component, choose the most specific type that meets your needs. | Type | Description | | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `DocumentModifyingTransformer` | A document transformer that can do anything to the document passed to it. It can delete, modify, and add fields to the document. This transformer type also allows you to choose to drop the document. | | `FieldValueCreatingTransformer` | A document transformer that creates new fields in the document based on existing fields. | | `FieldValueModifyingTransformer` | A document transformer that modifies existing fields in the document. This transformer type also allows you to choose to drop the document. | | `MultiOutputDocumentTransformer` | An advanced document transformer that allows you to modify an existing "parent" document and to generate new "child" documents based on it. The new documents will then flow through the system independent of the "parent" document. | | `QueryTransformer` | A transformer that can modify queries before they are processed by the search engine. | | `ResponseTransformer` | A transformer that can modify the resposnse to queries after they are processed by the search engine but before the response is returned to the user. | | `BaseRoutingComponent` | An advanced component that can change the workflow that will be used for a system message. | | `MessageHandlingWorkflowStage` | An advanced catch-all component that operates on raw system messages, doing whatever it likes to them. | ## The Mix-In Interfaces Once you have chosen a component type, you can also add a number of mix-in interfaces to the component. These allow you to indicate additional capabilities or requirements to the platform for your component. ### Lifecycle | Name | Description | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Startable` | Provides a hook for the component to do initialization after its properties have been set before it does any processing. | | `Stoppable` | Provides a hook for the component to clean up resources before system shutdown. | | `AfterAllLocalInstancesStarted` | Provides a hook for the component to do initialization after all instances of this component have been started (`Startable.startComponent()` has been called). | | `AfterLocalNodeStartup` | Provides a hook for the component to do initialization after all components in the system have been started. | ### Component Configuration | Name | Description | | -------------------------- | ----------- | | `HasBackoffLocaleProperty` | | | `HasCaseModeProperty` | | | `HasFieldMappingProperty` | | | `HasFieldsProperty` | | | `HasInputListProperty` | | | `HasInputProperty` | | | `HasOverwriteProperty` | | | `HasQueryLanguageProperty` | | | `HasSchemaNameProperty` | | | `HasTokenizerProperty` | | ### Miscellaneous | Name | Description | | ----------------------------- | ------------------------------------------------------------------------------------------------- | | `AieLoggerAware` | No longer recommended. Use [slf4j APIs](https://www.slf4j.org/api/org/slf4j/Logger.html) instead | | `ComponentNameAware` | | | `ProvidesProcessingFeedback` | | | `QualifiedComponentNameAware` | | | `SchemaUtilAware` | | | `SystemEventPublisherAware` | | ### Annotations | Name | Description | | ------------------------------------ | ----------- | | `MultiOutputDocumentTransformerMode` | | | `SingleInstancePerCluster` | | | `SingleInstancePerNamedComponent` | | | `SingleInstancePerNode` | | | `ThreadSafe` | | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://attivio.gitbook.io/sdk/release-4.4/components/components-writing.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.