The HTTP Listener Connector can be configured using the Aspire Admin UI. It requires the following entities to be created:

• Connection
• Connector
• Seed

Below are the examples of how to create the Connection and the Seed. For the General Connector Configuration, please refer to this page.

Create Connection

1. On the Aspire Admin UI, go to the connections tab
2. All existing connection connections will be listlisted. Click on the new button button
3. Enter the new connection description. 
4. Select HTTP listener from the Type list.
5. General
   1. Accept posted content: Check if you want sent XML, JSON data or file by web form.
      1. Select Multipart form data option:
         1. disable: → sent POST request with XML, JSON body
         2. stream: → sent file by web form, will be streamed to Job.
         3. file: → sent file by web form, the file will be stored in on disc and only the path will be sent to Job.
            1. Upload directory name: path to directory where file will be stored.
   2. Transform response: Check if you want data to be transformed.
      1. Transform file: path to XSLT template file.
   3. Saxon Processor: Select if you want to use the Saxon processor.
   4. HTTP Headers: Headers which will be added to HTTP response.
   5. Max size file in MB: Restrict size of file which will be uploaded.
   6. Debug out file: specifies debug output file for XSL transformation.
6. Policies
   1. Throttle Policy: Select the throttle policy that applies to this connection object.
   2. Routing Policies: Select the routing policies that this connection will use.
      
   3. Delete Policy: Select the delete policy that applies to this connection object.

Create Connector

For the creation of the Connector object using the Admin UI, check please refer to this page.

Create Seed

1. On the Aspire Admin UI, go to the connections tab
2. All existing seeds will be listlisted. Click on the new button
3. Enter the new seed description. 
4. Select HTTP listener from the Type list.
5. Endpoint name: choose the name of the endpoint.
6. Connector: The ID of the connector to be used with this seed. The connector type must match the seed type.
7. Connection: The ID of the connection to be used with this seed. The connection type must match the seed type.
8. Workflow: The IDs of the workflows that will be executed for the documents crawled.
9. Tag: The tags of the seed, these can be used to filter the seed.
10. Policies
    1. Throttle Policy: Select the throttle policy that applies to this connection object.
    2. Routing Policies: Select the routing policies that this connection will use.