Utilities
We can export system data. Support personnel can then import and view the data as a simulated system to troubleshoot problems.
The import and export features are compatible with later versions, so if we have a recent version of IBM WebSphere Portal use themes from previous versions. For example, an exported Portal 7002 them can be viewed on a WebSphere Portal 8.0 system.
- Export
- Export the data to share with IBM support or the local support organization.
- Import
- Import data from an external system to create a simulated system to aid in troubleshooting. When we import display data, the portlet enters a simulation mode. When the portlet is in simulation mode, page browsing is disabled and resource contributions cannot be clicked or viewed.
- Control Center
- Provide some short cuts for changing settings, which can help with theme analysis and debugging. These shortcuts are explained in detail on the Control Center page. Tools in the control center only affect the node on which we are currently working.
- Invalidate Cache
- Clear theme optimization-related caches so that changes made locally to a theme's modules and profiles can be made available immediately, without restarting the server. Modify your theme then click the Click to invalidate link.
- Remote Debugging
- View each module contribution as an individual request. If there is a debug uncompressed version of the contribution it uses that resource. The same as setting the trace string to...
com.ibm.wps.resourceaggregator.CombinerDataSource.RemoteDebug=all
- Development Mode
- Disable all caches of the theme optimization framework. Equivalent to setting resourceaggregation.development.mode to true within the ConfigService resource environment provider.
- Reports
- View further information about the theme optimization framework, which is written to the trace log. There are three types of reports, profiles, modules, and meta-modules. Click the link in each section to turn on the reports, and click again to turn them off.
- Client tracing
- Enable traces for JavaScript code. The difference between client tracing and enabling tracing with the administration portlet is the administration portlet enables Java tracing. Add multiple strings by adding strings with a pipe. When we click add, the trace is persisted immediately. We can choose to enable the trace scope for the current browser or all users on the server. If we set the trace scope to Server, any client accessing the server will have JavaScript traces on that server only. If we set it to current browser, we can remotely debug a server. We must have uncompressed Java resources enabled.
- Advanced Utilities
- Provide an option to export all titles and descriptions of all known modules in the system to a .CSV file.
Parent Theme Optimization Analyzer