Starting Indexing of Connectors
To make the objects in the connectors available in the search, you have to start or schedule indexing for the new connectors in the following cases:
- In the SAP HANA-based variant: You are using connectors that do not provide database support.
- In the TREX/BWA-based variant: You have to start or schedule indexing for all connectors.
In these cases, indexing runs either as full indexing or as delta indexing. This depends on whether or not the underlying model supports delta transfers, and the settings your define for indexing.
If you have already created the connectors automatically in ABAP Task Manager using the Task Manager task list SAP_ESH_CREATE_INDEX_SC, you do not have to perform this task. The task list contains the creation of the connectors and their indexing.
You have created connectors manually.
You are in the administration cockpit.
Choose the connectors that you want to schedule indexing for and then choose
Actions 
Schedule Indexing 
.
Below Object Type, select one or more search and analysis models.
NoteThe entry screen allows you to make settings for more than one model at the same time.
To trigger indexing immediately, select the Start Immediately flag. Alternatively, you can schedule indexing for a later time. To do this, specify a start time.
If you want to do a full indexing run, choose the Mode for Full Indexing.
When you select a mode, you decide whether the existing index is retained during full indexing and updated row by row or completely emptied and then refilled.
If you do not choose a mode, the system performs delta indexing if possible; otherwise it performs full indexing. In the case of delta indexing, during the first run, the system performs full indexing for a prepared connector with an empty index and then delta indexing directly afterwards. During the subsequent runs, delta indexing is performed each time.
NoteNote the following information for the indexing of connectors for delta-compatible DataSources:
For the first indexing run, two requests are created: a request for full indexing and a request for the subsequent delta. For the delta indexings of the subsequent runs, one delta request is created for each run. You can display the requests in the delta queue monitor.
More information: Monitoring Delta Queues
Optional: Define whether or not Real-Time Indexing is to be used.
For more information about setting up and monitoring real-time indexing, see Controlling Real-Time Indexing.
Optional: If you want to perform indexing regularly, for example, for delta-compatible models, enter a recurrence period.
ExampleIf you specify tomorrow's date at 01:00:00 and one day as the recurrence period, the system performs the indexing run from the next night onwards, every subsequent night at one o'clock.
Choose OK to activate the indexing schedule.
In transaction RZ11, you must assign the value auth/new_buffering to the 4 profile parameter so that changes in user data are available without delay and can be subsequently indexed. Then schedule object USER_AUTHORITY for delta indexing. Note that real-time indexing is not possible for this object. However, you can schedule indexing by using the administration cockpit (action: Index User Authorization).
If you want to index documents that contain hidden text, note the additional information in SAP Note 604635 
.
In you have to reset indexing of connectors during troubleshooting, proceed as follows:
Schedule a one-off indexing run, for which you choose the Delete Index Content option as the Mode for Full Indexing. This empties the index entirely and builds it again.
To ensure that periodic delta indexing is performed rather than periodic full indexing, you then schedule the indexing periodically again and without choosing the Full Indexing Mode.