Reconfiguring OS Entreprise Search

Hi,

I think that i have made a mistake during OS installation(12.0.37) while configuring Entreprise Search screen : i entered the FQDN of "M3 Entreprise Search". I thought, that OS will "call" the M3 Entreprise Search software.

It looks that it was a mistake because now i have an error in MESSchedulerService : it is unable to reach the address https://"M3 Entreprise Search":9200.

And at the same time, the templates supposed to be available at that url are located actually in the OS server.

Is it possible to change that address from the OS grid ?

Probably it is possible. But until now, i didn't found where.

Regards.

Find more posts tagged with

Installation

Accepted answers

Brandon Watson

Hello - The Infor_OS_Farm.dbo.ServiceConfigurationDetail has the elastic links used for Infor OS. You could try to change all of the endpoint and URLS to inforos.farmname.com:9200. I do not recall seeing it in the Grid, nor any other SQL table really. After making the change, you will want to reboot the SQL server then the Infor OS Server(s).

You may want to look at the elasticsearch.yml file(s) to make sure they are set properly as well.

After the reboot, you will need to load the Elastic indices for Infor OS, via the three templates found in KB 1934131. You will need the admin password, found in the above SQL table, and Postman to do PUT API call, to put the templates.

unknown

Hi Brandon,

It worked finally.

OS Entreprise Search seems to be correctly configured now. No more errors on the grid.

And, i can list the API suites in « Create data service », in APPBUILDER repository which was impossible before because of ES misconfiguration.

I did as you told me :

1) Correcting ES endpoint in table « [Infor_OS_Farm].dbo.ServiceConfigurationDetail ».

2) Reinstalling « Infor ION API Service » (KB1934131).

Thank you very much.

All comments

Brandon Watson

unknown

Hi Brandon,

Thank you for your help.

I went to table "Infor_OS_Farm.dbo.ServiceConfigurationDetail" and i changed all the endpoints.

I restarted SQLSERVER services and all OS hosts.

But, i got a new error message : " 1. 2020-01-24 17:30:02,583 +0100Z {} ERROR ServiceWebApp com.infor.search.schedulerjobs.jobrunner.monitor.CaptureMain: Cannot obtain Jest client to healthdata endpoint for cluster https://es.gdeinfor2.com:9200"

It seems that the old endpoint is still stored somewhere else.

Brandon Watson

How is the health of the Infor OS ES cluster? es.gdeinfor2.com:9200/.../health. Anything in the ES logs (<DRIVE>:Program FilesInforOSServicesEnterpriseSearchlogs).

unknown

• In https://[M3 ES].gdeinfor2.com:9200/_cluster/health : Page unreachable.

• In https://[INFOROS].gdeinfor2.com:9200/_cluster/health :

with Chrome, impossible to access to the webpage. With IExplorer, a login page is displayed.

When i enter the admin credentials used for the OS installation, it is not accepted. The page also displays « The server reports that it is from Search Guard ».

At another hand, the browser displays a certificate issue even after having installed the certificate issued by search.informingle.com.

In (<DRIVE>:Program FilesInforOSServicesEnterpriseSearchlogs) :

Log « elasticsearch-service-x64-stdout.2020-01-21 » :

[2020-01-27T12:02:00,161][WARN ][c.f.s.c.PrivilegesEvaluator] ionapigateway does not exist in cluster metadata

[2020-01-27T12:02:00,177][WARN ][c.f.s.c.PrivilegesEvaluator] event does not exist in cluster metadata

[2020-01-27T12:02:00,180][WARN ][c.f.s.c.PrivilegesEvaluator] message does not exist in cluster metadata

[2020-01-27T12:02:00,186][WARN ][c.f.s.c.PrivilegesEvaluator] statistics does not exist in cluster metadata

Copyright © 2025 Infor. All rights reserved.