x

A candidate message flowing through iWay Service Manager (iSM) and iWay Enterprise Index passes through the following sequence of events:

1. Service Manager receives the message.
2. Message flows through Service Manager.
3. Message arrives at the Index Filter. The Index Filter determines whether the message should be indexed for content and security. If it should, the Index Filter sends the message to the search appliance with redisplay URI.
4. Message continues through the flow and completes normally.

x

A search executed through iWay Enterprise Index passes through the following sequence of events:

1. Inquirer brings up the search page (for example, Google) from the search appliance, as shown in the following image.

   

2. The search appliance searches indexed messages, selecting candidates, as shown in the following image.

   

3. For every candidate that contains a secure marker, the search appliance requests identification from the user, a standard 401 HTTP response, as shown in the following image.

   

4. Secure candidates and user credentials are sent to the iSM via a dedicated link, as shown in the following image.

   

5. iSM passes the candidate and its associated credentials to the Security Exit and the Security Exit determines whether it can be shown to the user, as shown in the following image.

   

6. Results of the security exit are sent back to the search appliance, as shown in the following image.

   

7. The search appliance presents the filtered results to the user, as shown in the following image.

   

8. User selects a candidate and the search appliance posts the choice to the iSM via the stored URI, as shown in the following image.

   

9. Post triggers an IEI render agent or workflow to call the recapture and format agent, which recovers the information from the log and formats it appropriately, as shown in the following image.

   

10. System returns the result to the user, as shown in the following image.