OAuth Domain Issue?
Application: there is no Oauth domain in the discovery resource at "https://test.mycompany.com:9443/rm/rootservices" for "/rm" that is a prefix of the discovery resource URI.
This could be caused by changing the public URI setting in the application or friend. Oauth domains from the discovery resource: [https://test.mycompany.com:9443/jts, https://test.mycompany.com:9443/rdm]
2 answers
Comments
I currently have it re-registered https://test.mycompany.com:9443/rm/scr from the registered applications list.
I don't know what app server you deployed in (Tomcat or WAS), or how you did the install (unzip or Installation Manager), but somehow you have an inconsistency in how the RRC application is deployed vs how it is configured. If it is deployed with the context path /rm (e.g. it is deployed in Tomcat, and the war file name is rm.war), then it will only respond to /rm URLs. But since it is reporting that it thinks it's URL is using /rdm, then I suspect that the server/conf/rm/fronting.properties file contains such URLs (that's how it ships out-of-the-box). The URLs in that file must match how the application is deployed.
I cannot answer your question without knowing what you've done, and how your CLM applications are deployed.
This was a fresh brand new installation, no upgrade. Fresh install of Win2k8 Server also. I used the IBM installation manager and had the repo files stored locally. I pointed the IBM install manager to the directory of the files and deployed from there. I'm using TomCat and I'm using SQL and setup Databases for jts, ccm, qm along with Databases for the warehouses. After that, I ran the custom setup and set my public URI which is not an actual URI. I put in all the settings for each application to ensure it made a JDBC connection to the databases. I let the custom install create the DB tables, everything has been successful, including getting passed the RM config. Finally after I finalized the server settings, I went to create a life cycle project for requirements composer and received the errors in my first post. If there is anything additional that you need, please advise. I'm still getting up to speed on this product as it is my first time.
What do you mean by "set my public URI which is not an actual URI"?
I mean it is a stand alone server, not on a network but just local laptops and the computer hosting the instance. The public uri I set is an actual .xxx domain suffix, does that have anything to do with it?
If the hostname you used is resolvable on all the machines in your standalone network, then it shouldn't be a problem.
1 vote