Why sometime the name for a registered application on JTS admin page shown as "undefined title" or "untitiled"
The product version I use is 4.0.3
Adding some jazz applications like dm, rm, qm to JTS which is running on different server. I mean JTS itself is running on server 1 and some registered applications are running on server 2, server 1 and server 2 are physical on different machines.
restarting server 1 before server 2 is started, go to JTS admin page, found entries for dm, rm and qm haven't been listed in application section which is reasonable to me.
Next start server 2 so dm, rm and qm service are available now.
refreshing the JTS admin page on server 1, entries to dm, rm and qm are listed this time. but the name to each application running on server 2 couldn't be displayed properly and shown as sth like "endefined title".
Also I found no matter server 2 is running or not, the consumer key info related to dm, rm and qm could be confirmed from JTS page.
My questions are
(1) during what stage, JTS would go to retrieve the registered application info to admin page. Why the remote application is running, the name for the application couldn't be displayed on page properly?
(2) consumer key to registered application would always be shown on JTS inbound relation page no matter the registered application is running or not. Does it mean application section info on JTS admin page need check each application status synchronisely?
Any ideas?
Thanks
Accepted answer
When you check the folder, <JazzTeamServer>/server/conf. These are locations that JTS inspects (or try to provision). For example, if you copy "ccm" and create new directory "ccm2", then it will be displayed if it is on the same server when jts/setup is run again.
Another server must be registered by the URL exposed by Service Contribution Resource (SCR). Normally, it is https://<server>:<port>/<app>/scr. This URL must exist, and must return resource information. Otherwise, it becomes "Unknown".
Does this answer to your question ?
Another server must be registered by the URL exposed by Service Contribution Resource (SCR). Normally, it is https://<server>:<port>/<app>/scr. This URL must exist, and must return resource information. Otherwise, it becomes "Unknown".
Does this answer to your question ?