Configuring feed settings on the server

You can use the administrative web interface to configure feeds from the Jazz® Team Server or an application that is registered with the server. While the Atom 1.0 feed rendering scheme is set by default, you can also use RSS 2.0.

About this task

Team members can subscribe to feeds to learn about changes to their project areas. When a client connects to a repository, the feeds are generated based on the settings in Jazz administrative web interface. Atom 1.0 and RSS 2.0 feed rendering schemes are supported. Use the feed rendering scheme that is preferred by your feed reader.

Note: In the Eclipse client, you can override some of the server feed settings by updating the client properties for the feed.


  1. Log in to the Administration page of the Jazz Team Server or an application that is registered with the server.
    • For the Jazz Team Server:
      1. Point your web browser to https://fully qualified hostname:9443/jts/admin
        Remember: The fully qualified hostname is the host name along with the DNS domain reference of the computer on which the Jazz Team Server is installed.
      2. On the Administration page, click the Server tab.
    • For an application registered with the server:
      1. Open a web browser and go to to access the application, where application is one of the following values:
        • ccm for Change and Configuration Management
        • dcc for Data Collection Component
        • gc for Global Configuration Management
        • qm for Quality Management
        • relm for IBM® Engineering Lifecycle Optimization - Engineering Insights
        • rm for Requirements Management
      2. On the Server Administration page, click the Server tab.
  2. In the Configuration pane, click Feed Settings.
  3. Click Edit to change any of the properties in Table 1.
    Table 1. Server feed properties
    Property Default value Description
    Feed Rendering Scheme atom1.0 The syndication format that is used by the feed service when it returns feed entries. You can also use rss2.0.
    Feed Cache Document Lifetime 120 seconds Feed documents that are composed on behalf of a client request are cached and reused across multiple calls for that document. This value, which is recorded in seconds, specifies how long a shared document is cached before it is cleared. While higher document cache lifetimes reduce the server load, the information returned might not be current.
    Feed Entry Cache Size 4096 entries The entries that comprise a feed document, after it is composed, are retained in a cache and shared across multiple requests for those entries. This value specifies the maximum number of entries that are cached for reuse. The greater the cache size, the quicker the response and greater the memory consumption on the server.
    Feed Query Maximum Entries 1000 entries The maximum number of feed entries that are returned by a service to a client.
    Feed Query Maximum Size 1048576 bytes The maximum size, in bytes, of feed entries that are returned by the service to a client.
  4. Click Save.