IDM on-prem connection issues Http redirects are not supported.

hcmoller
hcmoller Member, Infor Partner Posts: 3
in Document Management

When trying to connect using 3rd party product, or StreamServe adapter using IONAPI file i get this error:

Http redirects are not supported. Make sure you are connecting to the correct port.

Anyone who knows how to solve this?

Regards
Hans

Tagged:

Answers

  • Brandon Watson
    Brandon Watson Member, Infor Partner Posts: 52

    Hello Hans - There is a KB article out there for that error, do any of these help you? Also, what version of jdk are you running? I believe the utilities jar requires oracle java jdk 8.

    https://customerportal.infor.com/csmcore?id=kb_article_view&sysparm_article=KB2054564

    Resolution : As a workaround in importing large documents,
1. Use utilities.bat to increase the java memory size (from 1024 ++)
2. run smaller batches (say 130 -150 folders at a time)
3. log out and login in utilities tool every time you finish batch importing to somehow decrease the java memory usage.

  • hcmoller
    hcmoller Member, Infor Partner Posts: 3

    Hi Brandon

    I've seen the KB and it's not related to the java since i can connect to IDM PRD environment but not IDM TST environment from the same application. If it were the java or java memory size, then it should fail for both.

  • Brandon Watson
    Brandon Watson Member, Infor Partner Posts: 52

    And you are talking about on-prem InforOS? Are they both the same version? How are you logging in, with IONAPI file or saml? Do you get an error after logging in or when trying to run?

  • hcmoller
    hcmoller Member, Infor Partner Posts: 3
    https://community.developer.infor.com/discussion/comment/364#Comment_364

    Yes, it's on-prem.
    Same version.
    Login using IONAPI.
    Error happens when trying to login.

  • Brandon Watson
    Brandon Watson Member, Infor Partner Posts: 52

    I would think it has something to do with the properties file or the ION API file. Did you download the utilities jar from prd itself? Did you use a service account with proper credentials and access? The last thing to check may be the Doc Type Filter differences between prd and tst to ensure the security role for the service account has proper access.

Categories