After the V200R005B01D052 is installed with the SP10 patch, the interface display after DSLManager login is abnormal
After login, for querying the devices and cards, the IE generates Nullpoint error (similar to the error of opening DSLManager with IE6.0); for querying port and user information, there is the prompt of connection the database failure.
After diabling the tomcat process, delete the %N2000/tomcat/work directory manually and then restar the tomcat. Use IE to log in to the DSLManager. At this time, the interface is the new one and the operations are normal. For the first time, the inerface is opened slowly. Therefore, the problem can be located as before the SP10 patch is installed, the DSLManager was operated, and so, the editing is taken. After the patch is installed, tomcat should taks editing again; as the patch does not delete the initial .class file, the DSLManager adopts the initial resource to access the daemon. Before the patch is installed, if the DSLManager is not operated, there will not be this problem.
The failure of connecting database may be caused by the error of the DSLManager configuration file. In fact, the IP address and the passwords in the %N2000ROOT%/tomcat/conf/DBDeviceDef.xml file are correct. Thus, this cause can be removed. Before the patch is installed, the DSLManager can be operated normally, thus, the IE version is correct.
The interface of DSLManager is the same as the one before the patch is installed (after the patch installation, the interface should contain the device tree). Thus, the patch may be not installed successfully or the DSLManager is not updated successfully. The patch installation log proves that the patch is installed successfully. Therefore, the DSLManager invocating resources may be incorrect. The DSLManager may do not edit the new .jsp file.
List all probable failures according to the phenomenon and then remove the probable failures one by one to locate the real cause.