Infor OS update Issue with ION API Service

Hello.

 

We have a customer who have faced the issue with updating Infor os without stopped the ION Api Service.

 

Now the Service is corrupt. 

We try to remove and re-install with the Service with nssm64.exe.

Now the Service is running again but we have the issue that ION API cannot load the API definition under "API Metadata".

 

The error "Failed to fetch https://xxx.xxx.com:7443/ionapi/metadata/v1/swaggerDoc?tenantId=infor" accours.

Trying to open the URL results in connection refused.

 

Have anybody an idea to fix the corrupt service problem or why we can load the metadata?

Everything works great before this update issue?

 

thx a lot for any response! 

Parents Reply Children
  • I will take advantage of the thread as it is open already, hope you don't mind.

    Brandon - in a documentation that I've got in the past regarding pushing templates to Elastic search it was said that we should check the availability going to http://<hostname>:9200/_template, and later on checking http://<hostname>/_cluster/settings and then sending new templates using PUT request. For me it worked in 12.0.30 but not in 12.0.32/37. Seems to me that port 9200 uses SSL protocol now (and I would say that also because in elasticsearch.yaml there are lines describing certificates, etc). And if I go to https://<hostname>/_cluster/settings, it asks for username and password (if I use a browser that can go beyond non trusted certificate that this service uses, does anyone know, what it expects for user/pass). I had a session with Infor Support and they desperately tried to go to http address and see that it does not work there and ending up, that installation is fault and I should reinstall the whole Infor OS.. But the fact is that this address on http does not work the way they tried even on fresh installations of 12.0.32 or 12.0.37 (I have tried that at other customer, that didn't went through upgrade process).
  • Tilen - I added this to my doc in .32. They added searchguard to secure elastic, for Infor OS, over HTTPS. In the Farm.ServiceConfigurationDetail table you will find 3 records that have admin for the ConfigValue. The next record will have the password. Use that admin/password combo to get logged in. if you are using Postman, use Basic Auth for the Authorization.

    3) Check gateway template is in correct version (use the URL for the environment you are working with to replace the hostname here): inforbcxi01.inforbc.com:9200/.../ionapigateway , we can see template as empty or in some cases template is present and it will be in older version (i.e type value with String)
    a. May need to use basic auth for Infor OS 12.0.32+
    i. Infor_OS_Farm.dbo.ServiceConfigurationDetail – admin – next record password
  • Hi, thank you very much. This is very valuable information. Finally found that templates in 12.0.32 and they are wrong, using string type instead of type keyword..
  • I would be careful about the IONAPIGATEWAY. All of my .32/.37 customers have string in this template, and are working. If you need a copy of my .32/.37 template, for this, let me know.
  • Hi, yes, if it is available, please send it to me. I have checked two systems and it seems "misconfigured" 12.0.32 seems to have the same ionapigateway json as "working" 12.0.37. I didn't compare the rest templates. I have seen that gateway_tracing is replaced with another one in 12.0.37.
  • Hi Brandon and Tilen.

    After hours of trying to fix the issue we have found a lot of other missconfigurations.
    This circumstances brings us to the only right decision... a fresh install of OS on a new server.

    Do you Guys know that there are possibilities to make config backups an restores on an new server?
    We dont find any migration documentation or something to guide us in an reinstall or migration scenario?

    Tilen, i hope you have success with you issue and Brandon... thx a lot for you guidance in this case!!!
  • Hi,
    what other misconfigurations did you find?
    What we did in the past (at several clients):
    - stop the Infor Search service (elastic search) and ION API Gateway service
    - uninstall ION API Gateway service via "sc delete"
    - take the appropriate versions, do what it says in KB 2024641 and 1934131
    - install it manually, register it and start it
    - check, what is going on with templates (this is where Brandon helped me, as it is not working anymore as it is described in KB 2024641 and 1934131) -look at the table FarmDB/ServiceConfigDetails for admin's password, use that to log into https://<servername>:9200.
    - I think we ran setup with both switches -v"RENEWGRIDOAUTHKEYS=true" and -v"UPDATECERTIFICATES=true", most probably several times

    My problem after all the procedure above was finally fixed. It was actually related to the fact that ServiceConfigDetails table had some records with wrong server address (server.name.name1.local instead of server.name-name1.local). You can check that also.

    Regarding the restore onto a new server.. I don't think you can take much of the existing with you. For ION content you can export it and import it in the new environment,. but you are losing the history. For IDM you can copy to new share and do a backup and restore of the IDM database.. I haven't done this so I wouldn't know if it is really possible. User management content could also be exported to some extent. Anything else you would overwrite with the backup I think you are risking ending up in an even worse situation (but that is my opinion, Infor support might think of some solution). That is why I try to avoid reinstalling at all costs :(.
  • Hello - Your best chance is to fix the broken parts. If that cannot happen, you can export almost everything out of the "old" farm, for the new farm. The mingle dashboard and BOD history are about the only two things you cannot. If you are on 12.0.37, I believe you can export all users mingle data, but have not confirmed. If you have to worry about IDM, just the JAR file from the Utilities download. You can export all documents to a share, then run the JAR for your new farm and import.

    I have had to do three, uninstall/reinstalls lately. Sometimes it is the only path, but pretty much all data is exportable.