SLM Search Indexing and Index Rebuild Guide
SLM search indexing organizes application data in advance so Safety Lifecycle Manager can return relevant information efficiently when users perform searches. Rather than analyzing every piece of SLM data individually for each search, the application retrieves matching keywords from prepared index tables.
SLM indexes information according to object ID, type and field. Administrators can also rebuild indexes through the System module when required, with the rebuild performed as a background task.
This guide explains how SLM search indexing works, the three index types used by the application, how administrators rebuild an index and how SLM keeps indexed information current when objects are edited.
How SLM Search Indexing Works
SLM search indexing prepares application information so that it can be searched efficiently. During the indexing process, SLM organizes information in advance rather than requiring every piece of application data to be analyzed individually whenever a user performs a search.
SLM indexes data according to:
- Object ID
- Type
- Field
When a user performs a search, the SLM data search engine retrieves relevant keywords from the index tables. This provides a more streamlined search process than examining all available SLM data individually for each query.
The indexing function forms part of the wider SLM application environment described in the SLM On-Premise Hardware and Software Requirements guide.
Three Types of Search Index in SLM
SLM uses three types of search index. Although they apply to different categories of application information, the transcript explains that all three function in the same way.
The three indexes cover:
- Objects
- Action items
- SLM documents
Separating these index categories allows SLM to maintain searchable information for the different types of data used within the application while applying the same underlying indexing approach.
SLM search indexing therefore extends beyond the main application objects. Action-item information and SLM documents also have dedicated indexes used by the application’s search functionality.
Why SLM Uses Prebuilt Index Tables
The purpose of the index is to organize searchable information before a user submits a query. Without this indexing process, a search would need to analyze the underlying application data individually to identify relevant information.
Instead, SLM can retrieve keywords from its index tables when a search is performed. This reduces the amount of data that needs to be examined during the individual search operation and supports quicker response times.
The index should therefore be understood as a prepared representation of searchable SLM information rather than the underlying application data itself.
This distinction is useful for administrators because maintaining the index and maintaining the source application data are related but separate processes. SLM provides mechanisms both for rebuilding index information and for updating it following changes to objects.
Rebuilding an SLM Search Index
Administrators can rebuild SLM search indexing through the System module. The rebuild process allows the administrator to select the relevant data type before creating the indexing task.
The workflow demonstrated in the training is:
- Navigate to the applicable indexing function within the System module.
- Select the data type that needs to be rebuilt.
- Select Rebuild Index.
- SLM creates a background task to index the objects belonging to the selected data type.
For example, the training selects the Site data type and initiates a rebuild. SLM then creates a background task responsible for indexing the Site objects.
Because the work is performed as a background task, administrators can review the resulting task through SLM’s background-processing functionality.
Monitoring Index Rebuild Background Tasks
After an administrator starts an index rebuild, the indexing operation is created as a background task.
The training demonstrates reviewing this activity through the Background Queue monitor, where the newly created indexing task can be seen after the rebuild has been initiated.
This relationship between indexing and background processing is important when administering the search function. Starting the rebuild does not mean that the complete index has necessarily been regenerated immediately; instead, the requested indexing work is placed into the background-processing workflow.
Administrators working with these processes should also review the SLM Background Task Manager guide for additional information about background task processing.
How SLM Search Indexing Stays Current
SLM search indexing is not maintained only through manual rebuilds. SLM also updates index information when indexed application data changes.
Whenever an object is edited, the application triggers a background task to update the index tables with the latest data for that object. This helps keep the searchable index synchronized with changes made within SLM.
The two mechanisms therefore serve related purposes:
- An administrator can initiate a rebuild for a selected data type.
- SLM can trigger an index update when an individual object is edited.
Both operations use background processing, allowing indexing work to be handled without requiring the user performing a normal search to rebuild or analyze the underlying application information.
Search Indexes and Application Performance
The SLM search indexing process is designed to support quick response times by organizing information before searches are performed.
When a user submits a query, the search engine can work with keywords stored within the index tables rather than analyzing each individual piece of SLM data during the request.
For administrators, this makes the health and currency of the index relevant to the application’s search functionality. The available rebuild process provides an administrative mechanism for regenerating indexed information for a selected data type, while automatic background updates help maintain indexes following object edits.
This page describes the SLM-specific indexing behaviour demonstrated in the training. For general technical background on how search indexes reduce the amount of data that must be examined during queries, Microsoft’s SQL Server indexes documentation provides a useful overview of indexing concepts. SLM’s own search-index implementation and administration should continue to follow the SLM-specific processes described here.
Managing Search Indexes as an SLM Administrator
SLM search indexing is primarily an application administration function rather than traditional public website search engine optimization.
Administrators should understand which of the three SLM index categories is relevant to the information being investigated and whether the requirement involves rebuilding a selected data type or reviewing an automatically generated background update.
If a rebuild has been initiated, the Background Queue monitor provides visibility into the background task created to perform the indexing work.
If an object has recently been edited, SLM automatically triggers background processing to update the corresponding index information with the latest object data.
These functions allow administrators to maintain the searchable representation of SLM objects, action items and documents while SLM continues to use prepared index information to support efficient application searches.
