Navigation:  Additional procedures > Troubleshooting >

Index server

 Top  Previous  Top  Next

The objective of the index server is to extract data from records and files in SE Suite to index them. These indexes are used in some system search screens, in addition to the general search. This service works in parallel with the system; when starting SE Suite, the index service is also started. See below the steps to verify whether the service is being executed:

 

1.Execute the following command:

# ps ax | grep java

 

2.Locate the Java service which the following file is running: "SESUITE_HOME/tools/se-fts-indexer-server/se-fts-indexer-server.jar".

 

 

In some situations, this service may not work adequately. See below a list of possible causes and their solutions:

 

hmtoggle_arrow1Port blocked in the FIREWALL

1.Open the SESUITE_HOME/tools/se-fts-indexer-server/conf/config.properties file for editing and verify the indexer.server.port parameter port. Example:

#Port used by the index server

indexer.server.port=31712

 

2.Check whether there is a firewall configuration blocking the port of the 'indexer.server.port' parameter. After unblocking the port, it will be necessary to restart the system and check whether the index service is being executed.

 

hmtoggle_arrow1Port being used in another service

1.Open the SESUITE_HOME/tools/se-fts-indexer-server/conf/config.properties file for editing and verify the indexer.server.port parameter port. Example:

#Port used by the index server

indexer.server.port=31712

 

2.Check whether there is another service using the port of the indexer.server.port parameter. If affirmative, select an available port.

 

hmtoggle_arrow1Problem with the Oracle database

Check for the following error in the SE Suite logs:

'java.lang.UnsatisfiedLinkError'

 

If existent, it will be necessary to perform the following procedure:

 

1.Access the SE Configurator directory:

# cd /usr/local/se/tools/configurator

 

2.Execute the following command to update and reconfigure the data of the connection with the database:

# bash run.sh