WEF testing
WEF's Model Action Tracing allows WEF specialists to test their code with tracing to look at the application flow, find problem, and execute some level of debugging. It helps them identify slow methods and code response. Besides, it also performs the following:
It looks at actions and subactions for every portlet request
It looks at time spent in each subaction for every portlet request
It is triggered with a property or within WEF designer perspective using the
RuncommandIt is recommended for use only during development
It looks at a single-user test case executed manually or automatically
It is saved in the
Web Experience Factory WARfolder for each WAR file, for examplemodelActions.txtin text format atWEB-INF/logs
WEF performance best practices are as follows:
Use runtime and schema caching whenever plausible and cache across users.
Consider the scope of variables (request, read-only, read/write) while avoiding the use of request scope for large XML variables with high usage...
