The next blog will explain how to change the behavior of the Common Event Console with respect to the cache in the TEP JWS client
The ITM Common Event Console displays several events each time the tep view is changed. For example, when the Common Event Console is called once in the physical view and then in a logical view, the events are displayed twice. The same behavior is shown with each change. The number of events is equal to the number of changes to the views multiplied by the number of events of the first view
The Common Event Console uses a cache that is not refreshed when switching from one view to the other. This behavior can be controlled by the parameter cnp.commonevent.cache.timeout
Number of minutes to retain the cache for the common event console when the user has switched to a workspace that does not contain the common event console view. If this time ends before the cache is used again, the cache is cleared. The cache is then rebuilt when it is needed by a common event console view. The parameter needs to set to 0
TEP JWS client:
1) Edit the tep.jnlpt file found in the following directory on the machine where the TEPS is installed:
2) In the tep.jnlpt file, there are two comment marker statements between which user-provided custom properties should be added. Scan the file for the following statements:
<!-- Custom parameters -->
<!-- /Custom parameters -->
3) Between these 2 marker statements, add the following statement exactly as shown (best to copy-and-paste to avoid typing errors):
<property name="jnlp.cnp.commonevent.cache.timeout" value="0"/>
4) Save the changes to the tep.jnlpt file.
5) Perform a reconfiguration of the TEP browser client:
e.g., <itm_install_dir>/bin/itmcmd config -A cw
6) On the machine where the TEP JWS client is executed, clear the jar cache:
7) On the machine where the TEP JWS client is executed, if the JWS client is being launched via the browser, the clear the browser's cache as well to ensure that the most recent tep.jnlp file will be downloaded with the changes.
8) Launch the TEP JWS client. If the changes were successful, then the JWS trace log(s) will contain a reference to the jnlp.cnp.commonevent.cache.timeout system property. You can scan the JWS trace logs for that string.
Reference: csdnkrue 2018
Subscribe and follow us for all the latest information directly on your social feeds: