On this page:


Step 1. Launch Aspire and open the Content Source Management Page

Launch Aspire (if it's not already running). See:

Step 2. Add a new Content Source

For this step please follow the step from the Configuration Tutorial of the connector of you choice, please refer to Connector list.



Step 3. Add a new Publish to HTTP Client to the Workflow

To add a HTTP Client application drag from the HTTP Client rule from the Workflow Library and drop to the Workflow Tree where you want to add it.
This will automatically open the Publish to HTTP Client window for the configuration of the application.

Step 3a. Specify Application Information

 In the Publish to HTTP Client window, specify the connection information to publish to the .

  1. Service Url: The service endpoint url
  2. Response Tag: Enter the name of the tag that will be used to store the service response.

  3. Accepted Response Codes: Enter , separated codes that are accepted for the service response.
  4. Request Content Type: Select the type of the content that will be send to the service
    1. Json: The request body is in json format.
      1. Json Builder Path: The path of the json builder file.
    2. Xml: The request body is in xml format.
      1. Xsl Path: The path of the xsl file.
    3. Binary: The request body is in binary format.
      1. Field Name: The name of the field in the request that will contain the binary.
      2. Specify Mime Type Field: Check to specify the XPath of the field that contains the mime type of the binary content. If not application/octet-stream will be used as default
        1. Mime Type Field: The field that contains the mime type of the binary content.
      3. Specify File Name Field: Check to specify the XPath of the field that contains the file name of the binary content.
        1. File Name Field: The field that contains the file name of the binary content.
  5. Request Headers: The headers that will send to the service.
    1. Header Name: The name of the header
    2. Sensitive Value: Check if the header contains sensitive data like a password
    3. Header Value: The value of the header
  6. Response Content Type: The format of the service response.
    1. Json: Select if the response is in Json format.
    2. Xml: Select if the response is in Xml format.
    3. Plain: Select if the response should be added a plain text.
  7. Process Deletes: Check to process deleted documents.
  8. Connection Timeout: Time in seconds before the connection gives a timeout.
  9. Connection Retries: Number of attempts before the connection fails.
  10. Retry wait time: Time in milliseconds to wait before each retry.
  11. Use Connection Throttling: Check to enable connection throttling.
  12. Throttle Rate in Millis: The throttle rate in milliseconds.
  13. Connections Rate: The number of connection to allow in the the specified throttle rate

Once you've clicked Add, it will take a moment for Aspire to download all of the necessary components (the Jar files) from the Maven repository and load them into Aspire. Once that's done, the publisher will appear in the Workflow Tree.

For details on using the Workflow section, please refer to the Workflow introduction.