Page History
Installation Process
Install the Group Expansion Manager service
Content source management page
1. Using the settings button on the right hand side of the screen to load the Services console.
Settings menu
2. This will return you to the following screen:
Services management page
3. Select Add service and then the Aspire Transaction Manager
Select Aspire Transaction Manager
4. The service will now load the configuration screen. This may take a moment if the connection to the internet is slow. Once the service has been downloaded, you will see the following:
Service configuration
5. Enter a name for your Aspire Transaction Manager or leave it as default
6. Click the Service tab at the top of the screen or use the arrow at the right of the screen to move to the service configuration screen. You will now see the service configuration.
Fields Description:
- Servlet name
- Specifies the name for the HTTP servlet to be created for the group expansion requests coming from the the search engines or search application. The default is "transaction" so the requests have to be made against "localhost:50505/transaction/subscription/fetchTransactions/indexed/publisher?batchSize=100&startId=79990bd7a7a43bc4f0d4ab03ebd6dd74"
- Specifies the name for the HTTP servlet to be created for the group expansion requests coming from the the search engines or search application. The default is "transaction" so the requests have to be made against "localhost:50505/transaction/subscription/fetchTransactions/indexed/publisher?batchSize=100&startId=79990bd7a7a43bc4f0d4ab03ebd6dd74"
- ElasticSearch Host
- The service will bind to this hostname.
- The service will bind to this hostname.
- ElasticSearch Port
- The service will bind to this port.
- The service will bind to this port.
- Cache
- Check this option if cache should be enabled. SharePoint can heavily load data. Define here elastic search indexes which should be preloaded and cached at the initialization of service.
- Check this option if cache should be enabled. SharePoint can heavily load data. Define here elastic search indexes which should be preloaded and cached at the initialization of service.
- Incremental configuration of cache elasticsearch indexes
- Elastic Search Index Name - Specify index name to be cached at initialization.
- Elastic Search Index results size - Specify size of results to be cached.
- Cache results size
- Default cache size for new elasticsearch index, which will be automatically setup, when http request will be sent with new elasticsearch index, which is not defined above.
- Cache size
- Maximum number of elasticsearch indexes, what will be cached.
- Cache expiration
- Cache expiration in seconds.
Click on Save and Done.
Overview
Content Tools