Jazz Server Counters (INTERNAL)

Some additional internal Jazz tools are available by adding a parameter to your administration URL as follows:

https://localhost:9443/jazz/admin?internal=true


Counters

Invoking this menu option brings up a screen showing detailed invocation counts and elapsed time data (minimum, maximum, average, total) for functions such as caching, database queries, web service calls, etc. It can be useful to help pinpoint areas causing performance and scalability problems, and is of great value to IBM Support.

Reload Log Settings

In the $JAZZROOT/server/conf/jazz directory is a file called log4j.properties. This file controls what and where the RTC server logs. For example, the size, location, etc. of the traditional jazz.log file is controlled there.

Sometimes it is helpful to change a logging attribute, such as changing the level of messages logged from the default of WARN to a more verbose level of DEBUG. Typically a server restart is required to make such changes take effect; the Reload Log Settings feature allows you to make logging configuration changes take effect without a server restart. Simply make your desired change(s) to log4j.properties and invoke the Reload Log Settings function. Your changes should be used immediately.

Provision Status

The management of user extensions, as well as many built-in functions, is handled by the provisioning services of Jazz. These are built using the Eclipse methodology (see my previous article Rational Team Concert - Creating Custom Operation Advisors to get more information).

The Provision Status page shows what features have been installed onto the server, and the actual jars that comprise those features. This information is helpful not only to determine whether your custom extension was properly provisioned, but also to glean more information about built-in functions (for example, understanding what jars implement which RTC features). It's also a valuable place to go to understand what version of a given jar file is active in the server.

Server Reset

You would use the Server Reset option to force the Jazz server to "reprovision itself" the next time it is restarted. This is used, for example, to get the server to load a new feature that has been specified in an .ini file located in the $JAZZROOT/server/conf/jazz/provision_profiles directory. It is also used when changing the underlying application server from Tomcat to WebSphere.