This section provides the following configuration options:
- Seedlist Path - Path to the ATOM-formatted Seedlist. Example: /seedlist/myserver in http://connections.example.com/blogs/seedlist/myserver.
- Separate MIME types per section By default, all connections documents will enter conversion with the same MIME type. Enabling separate MIME types will cause each section to have its own MIME type. This makes conversion-time modifications to just one section's documents considerably easier and higher performing. The IBM Connections Unifying Converter must be present in the conversion chain in order for documents to be renamed to application/vxml+unnormalized.