Overview#This page provides lists of NAM customized file for YOUR ORGANIZATION on the various NAM devices.
Changes should be managed and backups be maintained for Contingency Planning
These files need replicated to each node of the same device when changed.
Upgrades may overwrite these file and/or cause them to need to be upgraded.
Recommendations #Comments with the date and changes made should be done in each file, every time it is modified. This would be helpful to determine changes required when upgrades are done and is certainly a "Best Practice".
Server Side Comments#A JSP file or fragment file begins with a server side style comment:
<%-- - Author(s): - Date: - Copyright Notice: - @(#) - Description: --%>
This comment is visible only on the server side because it is removed during JSP page translation. Within this comment are the author(s), the date, and the copyright notice of the revision, an identifier and a description about the JSP page for web developers. The combination of characters "@(#)" is recognized by certain programs as indicating the start of an identifier. While such programs are seldom used, the use of this string does no harm. In addition, this combination is sometimes appended by "$Id$" for the identification information to be automatically inserted into the JSP page by some version control programs. The Description part provides concise information about the purpose of the JSP page. It does not span more than one paragraph.
JSP page Visible Comments#In some situations, the opening comments need to be retained during translation and propagated to the client side (visible to a browser) for authenticity and legal purposes. This can be achieved by splitting the comment block into two parts; first, the client-side style comment:
<!-- - Author(s): - Date: - Copyright Notice: -->
and then a shorter server side style comment:
<%-- - @(#) - Description: --%>