...
Aspire will create one MongoDB database for each content source configured. When the content source is deleted, the database will be dropped. The database name will the taken from the normalised normalized value of the content source name. Starting in Aspire 3.2, the database names will be prefixed with "aspire-" to avoid possible conflicts of name. If you wish to change the prefix, add a "namespace" to the configuration:
...
After importing it into a truststore you need to add it into the Aspire startup script, read Crawling via HTTPs for more instructions on how to add the truststore into the startup script.
The Provider will automatically retry the operations in case they couldn't be completed because of connections errors. The maximum retries to execute is configurable using the "maxRetries" option. By default (if nothing is provided), it will not retry operations at all.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- noSql database provider for the 3.2 connector framework -->
<noSQLConnectionProvider sslEnabled="false" sslInvalidHostNameAllowed="false">
<namespace>myNamespace</namespace>
<implementation>com.searchtechnologies.aspire:aspire-mongodb-provider</implementation>
<servers>mongodb-host:27017</servers>
<maxRetries>5</maxRetries>
</noSQLConnecitonProvider> |
Aspire 3.2 supports authenticating to MongoDB using X.509. Based on the requirement will be necessary modify the settings.xml file.
Aspire 3.2 only supports authenticating to MongoDB using X.509.
...
Code Block |
---|
$ openssl pkcs12 -export -out client.pkcs12 -in client.pem Enter Export Password: <your-password-here> $ keytool -import keystoreimportkeystore -srckeystore client.pkcs12 -srcstoretype PKCS12 -destkeystore client.jks -deststoretype JKS Enter destination keystore password: Re-enter new password: <your-password-here> Enter source keystore password: <your-password-here> Entry for alias 1 successfully imported. Import command completed: 1 entries successfully imported, 0 entries failed or cancelled |
...