Hi Tony,

Those links are very informative. Thaks a lot for your help.

I have one question about the queues. I have not find any queue related to indexing. If we have indexing running in a separate server, when and how the messages are sent to it.

How are messages are handed over to indexing. Is it storage service that queues messages to Indexing server? is it done before storing the message or after storing the message? As far as I understand, I think the storage service sends the messages to indexing service then it creates the SAVESET ID, indexes the content and then sends back to storage service. Then storage service archives the message and updates the voultstore database. is my understanding correct?

We have EV8.0 in our environment. Once again thanks for your reply.

Indexing doesn't use Message Queuing as it can go directly to the savesets on disk. The storage service sets flags in the database that the indexing process checks to see if there are updates pending

As Nick said, the item is stored and then it is Indexed. 

One thing you wrote I have a question about, you say "If we have indexing running in a separate server"  Can you clarify what you mean there?

Hi Tony and Nick,

Thanks for your replies. "Indexing running on separate server" I mean, Indexing running in a  different server than the storage server.
I am not really sure if we can configure indexing and Storage services in separate servers.

Please confirm if we can configure these roles in separate servers. If this configuration is possible, how message will flow from Storage to Indexing.

Query2: Also I have read in one of the articles, I think its in EV6, where its mentioned that indexing is done before message is stored. Is it chaged in EV8.