Quite recently we have released the NWDI troubleshooting guide (which is part of the Java Development Wiki). Its idea is to provide a fast solution to known problems by merging two well established ways of NWDI support.
On the one hand side, a notes search provides quick help. When you find a note that describes your problem, it is often a matter of minutes until your system is back up and running. However, it is not always easy to find the right note, be it because you (or the note J) are using inappropriate keywords, or simply because there is no note for your problem. On the other hand, there is the option to open an OSS ticket. SAP support provides individual help by asking specific questions, but in many cases it takes time to find the right processor, to exchange log files, screenshots, to open a connection to your system, etc.
The troubleshooting guide tries to find a note for you, by asking ‘individual’ questions about your NWDI problem. On the start page, it lists some of the most frequently encountered problems.
Once you have identified your issue among these, you will be asked a couple of questions about your use case, your system configuration, log entries etc. that help encircle the root cause.
Ideally, the last page you look at will contain a brief problem description together with a description of the solution.
In general, it will also state a note that provides more details about the issue. However, in some cases this will not be possible, and the last page will kindly ask you to open an OSS ticket, and to provide information about your concern.