Skip to end of metadata
Go to start of metadata


How to get started troubleshooting CMS?


CMS, troubleshooting, NWDI.


Step 1: Analyzing the CMS Server Log

1. Start the Visual Administrator tool and connect to the Web AS Java on which CMS is running.
2. Choose Server <XXX> > Services > Log Viewer.
3. Choose Cluster <XXX> > Server <XXX> > applications > cms.log.
The CMS Server Log shows you all CMS errors. Double-click an error message to display details about the cause of the error.
If this does not provide you with enough information to identify the error, you can find further details in the CMS trace.
You can also display the log files directly from the file system, under the installation directory for Web AS Java:
<installation directory>/.../usr/sap/<SID>/JC<instance number>/j2ee/cluster/server<X>/log/applications/cms.X.log

Step 2: Default Trace

AS Java records all errors in the running application in the default trace. This trace is the most detailed log that you can examine. In its default setting, however, it only records errors in the categories Warning and Error. If you want more details, you need to change this setting manually.
Note that raising the trace level can have a negative effect on the performance of your system. Only raise the trace level to reproduce errors. Change it back to its default setting afterwards.
For information about raising the trace level, see Filtering Log Records. Use as the location for your trace recording.