Q & A On Elastic Search With Classic Message Store
Last updated on JULY 04, 2018
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
Are there more details on the restricted Searchengine option ?
Question # 2:
Are there any details about appropriate sizing and elastic search instance for classic store search ? For example, would 1:1 with the size of all idx be appropriate ? Is having the Storesource Option elasticsearch.storesource enabled good, and will this drive more disk space consumption.
Question # 3:
Are there specific details on how the classic store acts as a "client" for Elastic search, in terms of how records are inserted and queried for ?
Question # 4:
Are there other items that are appropriate to provide for a successful test deployment ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms