Page History
...
| Excerpt | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
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 value of the content source name. Starting in Aspire 4.0, the database names will be prefixed with "as-" to avoid possible conflicts of name.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<!-- noSql database provider for the 4.0 connector framework -->
<noSQLConnectionProvider sslEnabled="false" sslInvalidHostNameAllowed="false">
<implementation>com.accenture.aspire:aspire-mongodb-provider</implementation>
<servers>mongodb-host1:27017,mongodb-host2:27017,mongodb-host3:27017,mongodb-host4:27017</servers>
</noSQLConnecitonProvider>noSQLConnectionProvider> |
Using TLS/SSL
If you need to connect to a MongoDB configured to Use TLS/SSL you need to set the following attributes into the noSQLConnectionProvider tag:
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<!-- noSql database provider for the 4.0 connector framework -->
<noSQLConnectionProvider sslEnabled="false" sslInvalidHostNameAllowed="false">
<implementation>com.accenture.aspire:aspire-mongodb-provider</implementation>
<servers>mongodb-host:27017</servers>
<maxRetries>5</maxRetries>
</noSQLConnecitonProvider>noSQLConnectionProvider> |
MongoDB Authentication
Aspire 4.0 supports authenticating to MongoDB using X.509 or SCRAM. Based on the requirement will be necessary modify the settings.xml file.
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<!-- noSql database provider for the 3.0 connector framework -->
<noSQLConnectionProvider sslEnabled="false" sslInvalidHostNameAllowed="false">
<implementation>com.accenture.aspire:aspire-mongodb-provider</implementation>
<servers>mongodb-host:27017</servers>
<authentication>
<scram>
<username>aspireUser</username>
<source>admin</source>
<password>encrypted:302B58140B6ED1FBEBDC33A9263EF742</password>
</scram>
</authentication>
</noSQLConnecitonProvider>noSQLConnectionProvider> |
MongoDB provider will verify the supplied user credentials against:
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<!-- noSql database provider for the 4.0 connector framework -->
<noSQLConnectionProvider sslEnabled="true" sslInvalidHostNameAllowed="false">
<implementation>com.accenture.aspire:aspire-mongodb-provider</implementation>
<servers>mongodb-host:27017</servers>
<x509username>CN=user,OU=OrgUnit,O=myOrg</x509username>
</noSQLConnecitonProvider>noSQLConnectionProvider> |
If you don't know what to use into the <x509username> field execute the following command using the x509 client certificate:
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<!-- noSql database provider for the 4.0 connector framework -->
<noSQLConnectionProvider sslEnabled="false" sslInvalidHostNameAllowed="false">
<implementation>com.accenture.aspire:aspire-mongodb-provider</implementation>
<servers>mongodb-host:27017</servers>
<encryptFields>
<field>_id</field> <!-- Encrypts all the IDs -->
<field>url</field> <!-- Encrypts the url fields -->
<field>fetchUrl</field>
<field>parentId</field>
</encryptFields>
</noSQLConnecitonProvider>noSQLConnectionProvider> |
Overview
Content Tools