baui wrote:

Hi,

I'm having a bit of a problem with displaying feeds inside the client.
When i try to open a feed, it points me to https://VPS428:9443/jazz/.
This presents 2 issues - localhost used as a url and port, which is
set in tomcat/conf/server.xml to 8443, not 9443 (due to firewall
restriction).

I have RTC/Tomcat installed on a virtual server and I'm pointing to it
from outside (DNS entry on my hosting).

teamserver.properties file goes like this:

com.ibm.team.repository.user.registry.type=TOMCAT
com.ibm.team.repository.db.jdbc.location=C\:/jazz/server/repositoryDB
com.ibm.team.repository.server.repourl.hostname=jazz.myhostname.com
com.ibm.team.repository.changeEvent.expirationDefault=1209600
com.ibm.team.repository.notification.mail.from_name=Jazz Team Server
com.ibm.team.repository.server.webapp.url=jazz.myhostname.com
com.ibm.team.repository.notification.mail.smtp.user=user@myhostname.com
com.ibm.team.repository.ws.allow.admin.access=false
com.ibm.team.repository.web.suppressedPages={"com.ibm.team.repository.web.admin"\:
}
com.ibm.team.repository.db.vendor=DERBY
com.ibm.team.repository.notification.mail.from=rtc@myhostname.com
com.ibm.team.repository.changeEvent.expirationByType=com.ibm.team.workitem.WorkItem\:5184000
com.ibm.team.build.BuildResult\:172800
com.ibm.team.repository.web.helpuri=http\://publib.boulder.ibm.com/infocenter/rtc/v1r0m0/index.jsp
com.ibm.team.repository.notification.mail.smtp.server=mail.myhostname.com
com.ibm.team.repository.notification.mail.smtp.password=**************
com.ibm.team.repository.web.logouturi=
com.ibm.team.fulltext.indexLocation=workitemindex
com.ibm.team.repository.web.homeuri=jazz.myhostname.com
com.ibm.team.repository.notification.mail.enabled=true
com.ibm.team.repository.web.pageorder={"com.ibm.team.repository.web.admin"\:
,
"com.ibm.team.process.web.projectArea"\:
,"com.ibm.team.process.web.projectAreaList"\:
}
com.ibm.team.repository.ws.allow.identity.assertion=false
com.ibm.team.repository.server.repourl.port.https=8443
com.ibm.team.repository.changeEvent.expirationByCategory=SystemLog\:259200

I also tried to set some URL related entries in advanced properties
after reading a bunch of forum posts about similar problems, but with
no succes :(

Anyone solved this issue before?

Forgot to mention the server version:
Rational Jazz Team Server - Express-C 1.0 (I20080618-1642)

There could be a number of things going on here.

The entry link text for workitems is not affected by the publicUriRoot
property (although setting that property correctly is important for any
URIs that may be embedded in comments, the WebUI, e-mail, etc.).

It is however, influenced by a combination of Servlet and Jazz properties.

Hostname:

The lookup for hostname for Jazz URIs (non-publicUriRoot) in our servlet
is to first look to see if a host name has been configured in Jazz, via
the admin WebUI (look for "Host Name" property under
com.ibm.team.repository.servlet.internal.ServletConfigurationService).
If it has been configured (and I suggest you do that if you haven't),
that's used, else, the server name in the HttpServletRequest is used.
The spec says that this will be the value of the "Host" header, the
server IP, or the resolved hostname. So depending upon that value is
probably not what you want in your environment.

Port Number:

Again, the port number specified in our ServletConfigurationService is
preferred, or the value as returned by the incoming HttpServletRequest
is used.

Based on your properties file above, it looks like the hostname/port
that will be returned in entry link elements is "jazz.myhostname.com:8443".

Caching:

Finally (and this may be your problem), once FeedEntries are created on
the server, they're cached and only purged based on an LRU scheme. So
if you change any of the values above, you'll want to cycle the server
to clear that cache containing the old values (even though the setting
of those properties don't require a server restart).

But before restarting the server, you can validate that your changes
made a difference by taking the feed URI in question, popping it into a
browser, appending the query parameters
"cacheEntryOff=true&cacheOff=true", and grab your feed that way. Take a
look at the XML output, and confirm that your "href=" text in your link
elements contain the expected hostname and port.

Don't place those query parameters in any production clients - they're
unsupported, for diagnostic purposes only, and could significantly
impact server performance if left in place.

If you've set those properties, bounced the server, and *still* see the
hostname problems, we need to investigate further.

-- Todd

--
Todd Lainhart
Jazz Repository/Foundation Team

Thanks for the clarification Todd. But isn't the link for entries created in FeedUtils#createLink using IServerDescriptionService#getPublicUriRoot?