Missing Friend ?
One of our JTS/QM/RM configurations isn't allowing connection to RM projects. From QM application visiting the Requirements menu gives this:
The proxy is not configured to allow the request to https://jts05:9445/rm/discovery/_GHp9dJKCEeGjXbwNCL2tGQ/services.xml. There may be a missing friend entry for this server.) has been forbidden.
But the https://jts05:9445/jts/friends contains the 2 QM and 1 RM application. I found 3 other mentions
of "missing friend entry" that is shown in the error dialog.
I can open the said services.xml from REST client.
Suggestions welcome !
The proxy is not configured to allow the request to https://jts05:9445/rm/discovery/_GHp9dJKCEeGjXbwNCL2tGQ/services.xml. There may be a missing friend entry for this server.) has been forbidden.
But the https://jts05:9445/jts/friends contains the 2 QM and 1 RM application. I found 3 other mentions
of "missing friend entry" that is shown in the error dialog.
I can open the said services.xml from REST client.
Suggestions welcome !
Accepted answer
The "missing friend" is in QM - in order for QM to be able to access RM resources, the RM application must be added as a friend to QM. You should see it in the Friends section the QM admin web UI.
Normally the LPA (/admin) application takes care of "cross-friending" all the registered CLM applications during setup. Did you not execute setup that way, or could someone have deleted friend relationships after creating them in setup?
Normally the LPA (/admin) application takes care of "cross-friending" all the registered CLM applications during setup. Did you not execute setup that way, or could someone have deleted friend relationships after creating them in setup?
2 other answers
I would check the registrations of the applications. I would also check if friends fit the opposite entries. I have seen cases where minimal typos caused issues. Check the server/conf/app/*.rdf files.
Since we are now at version 4 it also becomes more and more critical to provide version Infos in posts.
Version is 3.0.1.3
Registrations check out fine. There are no friends*.rdf files under any server/conf/* except jts.
$ cd /CLM.3
$ ls -F
jts03/ jts04/ jts05/ rqmmax/ rtp-rqm1/ tcbdb-1/ tcbdb-2/ tdsrqm1/ tdsrqm2/
$ find . -name "friends*"
./jts03/server/conf/admin/friends-1335618876845backup.rdf
./jts03/server/conf/admin/friends.rdf
./jts03/server/conf/rm/friendsconfig-1335619329947backup.rdf
./jts03/server/conf/rm/friendsconfig-1335619420140backup.rdf
./jts03/server/conf/rm/friendsconfig.rdf
./jts04/server/conf/admin/friends-1335619752916backup.rdf
./jts04/server/conf/admin/friends.rdf
./jts04/server/conf/rm/friendsconfig-1335619911010backup.rdf
./jts04/server/conf/rm/friendsconfig.rdf
./jts05/server/conf/admin/friends.rdf
./jts05/server/conf/rm/friendsconfig.rdf
./rtp-rqm1/server/conf/jazz/friendsconfig.rdf-saved
./tdsrqm2/server/conf/jazz/friendsconfig.rdf-saved
The consumer key in ./jts05/conf/rm/friendsconfig.rdf matches what is shown on the "Friends" page of the jts for the RM application. Each QM application has the JTS in Friends list and consumer key matches the approved key in JTS.
Registrations check out fine. There are no friends*.rdf files under any server/conf/* except jts.
$ cd /CLM.3
$ ls -F
jts03/ jts04/ jts05/ rqmmax/ rtp-rqm1/ tcbdb-1/ tcbdb-2/ tdsrqm1/ tdsrqm2/
$ find . -name "friends*"
./jts03/server/conf/admin/friends-1335618876845backup.rdf
./jts03/server/conf/admin/friends.rdf
./jts03/server/conf/rm/friendsconfig-1335619329947backup.rdf
./jts03/server/conf/rm/friendsconfig-1335619420140backup.rdf
./jts03/server/conf/rm/friendsconfig.rdf
./jts04/server/conf/admin/friends-1335619752916backup.rdf
./jts04/server/conf/admin/friends.rdf
./jts04/server/conf/rm/friendsconfig-1335619911010backup.rdf
./jts04/server/conf/rm/friendsconfig.rdf
./jts05/server/conf/admin/friends.rdf
./jts05/server/conf/rm/friendsconfig.rdf
./rtp-rqm1/server/conf/jazz/friendsconfig.rdf-saved
./tdsrqm2/server/conf/jazz/friendsconfig.rdf-saved
The consumer key in ./jts05/conf/rm/friendsconfig.rdf matches what is shown on the "Friends" page of the jts for the RM application. Each QM application has the JTS in Friends list and consumer key matches the approved key in JTS.