Help Needed with Integration Issues in OpenText

Thomas Elis

Hi everyone,

I’m facing integration issues with OpenText Intelligent Viewing and Content Server. Despite following the setup instructions, I'm running into authentication and authorization problems.

Here’s what I’ve tried so far:

1. Checked user permissions and roles.
2. Confirmed the service account setup.
3. Reviewed configuration files.
4. Verified server time synchronization.
5. Examined various logs for errors.
6. Checked network and firewall settings.
7. Tried using both HTTP and HTTPS.

Has anyone experienced similar issues or have suggestions for troubleshooting? Any advice or steps to resolve this would be greatly appreciated!

Thanks!

appuq

Have you contacted support?

this is a good link https://forums.opentext.com/forums/developer/discussion/comment/966244#Comment_966244

In reality, if the OTDS server and OTIV are mismatched expect problems—some rudimentary checks from my experience.

1. I Install OTDS to the Version that OTIV likes
2. make sure the OTDS database is created and all that jazz
3. make sure OTCS and OTDS work and the license is applied
4. Create a simple user called "lab.demo" because OTIV will not work for super user(otadmin@otds.admin=Admin)
5. Install rabbitMQ allowing defaults and you can monitor as guest/guest as possible only on that machine.
6. In the OTIV installer edit the properties and put otadmin@otds.admin and its password this allows the OTIV installer to create several OAUTH clients in OTDS.
7. I verified if the OAUTH clients like iv-cs, and iv-publisher all have come to OTCS in its users and groups, The theory is each OAUTH client needs a representation in OTCS(not enough it just exists in OTDS)
8. Start OTIV starting with Configuration, Asset, Publisher, and Publication monitor configuration logs and see if they contacted database. I also parallelly look at the Postgres database for the schema and see if action is there about three schemas will be created by the installer and you have to remember to create the extensions for Postgres.
9. If the services are stable I go to OTCS administration under transformation the first page will verify everything and see if you can go to service communications
10. On that page check the URL these are the REST api's for OTIV.
11. if any firewall issue happens loosen it because many times the OTIV process will call the CS rest api to put documents, download documents, etc so developer tools are a great help.
12. If all goes well time to switch our 'lab. demo' user to OTIV, note the installer comes up with a single license and it cannot be transferred
13. If one was using Chrome for OTCS/OTDS try a different browser Edge/Firefox for 'lab. demo' and add a document like DWG or PDF and switch to Smartview.On that page, View should be invoked to bring OTIV
14. You can tail logs of OTDS and you will see 'iv-cs' is now accessing OTDS and some informational messages. expect to see 'iv-publisher' also in that.
15. If you get OTIV messages like "unable to download" this is cause for joy because your CS has called a REST api of OTIV.If you just get a spinner with no apparent errors time to call OT or cross-check all install stuff.