# Maintaining Omnitive Search Server

## Overview on Maintaining Omnitive Search Server

In order to maintain the Omnitive Search Server, you can:\
1\. Reingest when the index is not in sync and not recoverable\
2\. Upgrade Omnitive Search packages with updated modules.

### 1. Data Re-indexing

The search uses one search index. In some rare cases, an index might not in sync and not recoverable. So, the data from the repository needs to be loaded again, this is called ingest.\
\
**To re-index the data:**\
\
1\. Clean inactive index, then launch the clean index script found in Taigerfolder,platform,Search-resources,elasticsearch,scripts,win. The script to execute will depending on the index version we need to clean.

![](https://3100524483-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbAG_FtZ7y_VPVF4kik%2F-Mei7Ftsb9zv0iksSL9u%2F-McxSA6DRMdRDLnWM31y%2F30.png?alt=media\&token=e61b8117-5e02-4257-aa76-30641455cc0e)

2\. Change the connector configuration to inactive index.

![](https://3100524483-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbAG_FtZ7y_VPVF4kik%2F-Mei7Ftsb9zv0iksSL9u%2F-McxSpWC54C6oY33xSY-%2F29.png?alt=media\&token=59dee45e-ed67-46d1-b088-b8ddc5a26664)

3\. Start the ingest process. 

![](https://3100524483-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbAG_FtZ7y_VPVF4kik%2F-Mei7Ftsb9zv0iksSL9u%2F-McrULDY6P4fkHK4F3cQ%2F42.png?alt=media\&token=7afb418b-415b-458a-a729-1c5c49ef381d)

4\. Switch Search index to the Search Configuration page.

![](https://3100524483-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbAG_FtZ7y_VPVF4kik%2F-Mei7Ftsb9zv0iksSL9u%2F-McxT51WavD8xiKkZHMT%2F28.png?alt=media\&token=7de0fe78-4f8f-4264-aeba-b4d35af4077a)

### **2. Upgrading Omnitive Search Packages**

1\. Create a deployment folder in the following path:\
\- Path: Taigerfolder\
\- Folder name:  deployment-YYYYMMDD\
            Inside it, create a folder name ROLLBACK

2\. Shutdown Tomcat Server using Services

![](https://3100524483-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MbAG_FtZ7y_VPVF4kik%2F-Mei7Ftsb9zv0iksSL9u%2F-McrVTHwzUZtlATn99-P%2F37.png?alt=media\&token=69051f4b-1e1c-452c-b080-ebd726c4590a)

3\. Upload deployment packages to application server at Taiger,installers,Search-Installers,search-packages 

4\. Extract isearch-resources.zip

5\. Move last deployment (war package) to the ROLLBACK folder\
\- Move Taiger,platform,isearch-resources to ROLLBACK\
\- Move Taiger,platform,\<tomcat>,webapps,\*.war to ROLLBACK

6\. Clean Tomcat deployment folder to remove the isearch folders.

7\. Copy new ware deployment packages to the Tomcat deployment directory.

> **copy isearch-resources dir Taiger,platform**\
> **copy \*.war Taiger,platform,\<tomcat folder>,webapps**

8\. Restart Tomcat server using Services.msc.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://taiger.gitbook.io/omnitive-search/additional-information/archive/search-administration/maintaining-taiger-search-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.