Open the browser and navigate to the Selftest page of ICXT (Note: Only accessible for ICXT administrative users)
Verify, if all features and functions are working as expected:
The first thing to check when running into issues with the ICXT application (or the PDF Export and Tailored experience community templating feature) is whether server the applications are installed on started OK and whether the individual applications were able to start up and are in a running state.
ICXT server status
Navigate to Servers > Application servers
ICXT applications status
Navigate to Applications > Application Types > WebSphere enterprise applications
If server/applications are not in running status that means something went wrong . We can add Log setting to further investigate issue either from ic360/ui or WebSphere console
Following trace settings should be applied in order to trace down server-side errors:
*=info: com.ibm.ess.ic.ic360.rest.impl.*=fine: com.ibm.ess.ic.ic360.ui.api.*=all: com.ibm.ess.ic.ic360.mod.backupstore.api.*=all: com.ibm.ess.ic.ic360.mod.profiles.api.*=all: com.ibm.ess.ic.icxt.contentmanagement.tasks.*=all
ICXT provides an admin user interface that allows to adjust trace settings of the runtime configuration and download the most recent log files for the server. It can be found by navigating to Tools > ICXT Maintenance
Alternatively, trace logs can be enabled via WebSphere console via the following steps:
Note: If debugging during server/app initialization is necessary, check the checkbox to Save runtime changes to configuration as well in the General Properties section. This will keep trace settings enabled throughout a server restart. The logs need to actively be removed after debugging, whereas runtime traces will be cleaned up during next server restart.
A trace.log file will then be generated in the server’s logfile directory. This can be found by navigating to APPSERVER_PROFILE/logs/ICXT_SERVERNAME/trace.log on the respective application server’s file system. * APPSERVER_PROFILE example path: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 * ICXT_SERVERNAME example name: server1, ICCluster_server1 or ICXTCluster_server1
Following URL parameters can be used in order to enable client-side logging. This can be used in combination with the browser’s developer tools like the network activity inspector or javascript debugger.
jsdebug=true
This parameter activates the console logger.
jscomponents=componentA,componentB
This URL parameter allows to enable certain components. It is useful to trace-down an error within a certain component (directive or controller)
combined=false
This parameter deactivates the JS combination feature. If this parameter is set, all JS files will be served separately.
angulardebug=true
This parameter renders unminified angular files. If an angular error occurred this parameter could be used to get more accurate JS stack traces.
If you experience an error or malicious behavior of ICXT, please report it to us. In order to ease error analysis, we need as much information as you can provide.
Following information are interesting:
or