Perofrmance issues using file-based repo in distributed topology
Francis Kemp (72●1●30●44)
| asked Mar 06 '13, 3:01 p.m.
retagged Mar 25 '13, 3:39 p.m. by Tory Jaskoviak (520●1●5) Due to issues at my current customer, we are using a Federated file-based repository to authenticate users in an Enterprise Topology CLM configuration. This is a stopgap solution as we are waiting on paperwork to complete to allow us to connect to the corporate authentication service. In our current situation, all users are complaining that it can take up to a minute after logging in for all of the Jazz applications to be available, and some are complaining that they are timed out after as little as 5 minutes of non-activity. Are there any WAS settings that can be configured to alleviate these issues while we wait to move to the corporate authentication service? Thanks in advance. |
One answer
Hi Francis,
Since your setup is as per the enterprise topology, the cause of the performance issues may not be due to the File based federated repository. I would suggest you test this with Firebug and see where the delay is coming from. By default, the http session timeout should be 30 mins in WAS. Are the users getting prompted when they traverse from one application to another ? Have you enabled SSO ? |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.