You can index data located in back-end systems in real time for Search and Operational Analytics.
Note
The back-end system must also support real-time indexing.
From the administration cockpit, you launch an administration UI that you can use to control and monitor real-time indexing.
You can define the time after which the daemon process interrupts its work if it does not receive any more data from the back-end system. If the back-end system transfers new data again, the daemon process restarts its work and triggers the system to index new or changed data.
Note
In the case of DataSource-based connectors, note the information in the section Performing Real-Time Indexing for DataSource-Based Connectors.
In the administration cockpit, you have activated real-time indexing for a connector:
Choose a connector and then choose Real-Time Indexing
flag.
You have entered an extraction user in Customizing in the SAP system:
In the SAP system, launch customizing by choosing transaction SPRO
. Choose the node . Enter the extraction user in this customizing activity.
Once you have selected the connectors for real-time indexing, a daemon process starts automatically to perform real-time indexing on the back-end system.
You can execute the following tasks for real-time indexing:
Manually stop or restart the daemon process.
Change the time interval for the maximum idle time.
Monitor the status of the daemon process.
Monitor indexing.
Display the job log.
Launch the administration cockpit.
Choose
.Stop the daemon process on the back-end system.
Note
You should stop the process only for support purposes or debugging.
Start the daemon process after completion of your support or debugging tasks.
Choose OK
to close the window or choose Cancel
to leave the screen without saving your changes.
If you want to change the predefined default value for the idle time, specify in the Maximum Idle Time
parameter the time in seconds after which the daemon process is to interrupt its work. Choose Apply
to confirm your entry.
In the upper screen area, the system displays the status of the daemon process.
Process Status |
Description |
---|---|
|
The process is starting. |
|
The process is restarting automatically after a stop. |
|
The process is running. |
|
The process is processing the last package and will stop afterwards. |
|
The process was suspended. |
|
The process pauses and continues once the idle time has expired. |
|
The process has not been started because there are no connectors in the system that support the type of indexing. |
|
There is a temporary error in the communication between the systems; note the error message. |
|
There is a technical error; note the error message. |
|
There is an error in the communication between the systems. The back-end system could not be reached. |
|
This type of indexing is not supported by the system. |
|
The system is in debug mode. The process is not running and indexing is not taking place. |
Table Indexing Changes in <System>
contains all connectors, their extraction status, and the queue size. The queue size specifies the number of objects that contain changes. You can choose the Refresh
link to display the current status and the updated queue size.
In the lower area of the window, you can see the job log. This displays all status changes and error messages that have occurred since the system was started.