A JSP file for the UI

The JSP file contains both HTML and Java tag library calls that are run on the server. This file is created in SDK_HOME/tomcat/webapps/nps/portal/modules/custom/skins/default/devices/default. A copy of the file is also added to the Custom.npm file.

This file can be modified to make custom enhancements that are not possible through the Plug-In Studio. For example, you could add an image that displays your company's logo. However, if you later use the Modify Plug-In feature of the Plug-In Studio, you lose any manual modification you have made to the JSP file.

A registration file

For property pages, an XML file is created and written to the SDK_HOME/tomcat/webapps/nps/portal/modules/custom/plug-ins/plug-ins.xml file. This contains information such as the page name and the object class it is used to manage. For tasks, the registration file is installed into eDirectory, and the information is stored in an RBSTask object. For both pages and tasks, a copy of the registration file is added to Custom.npm.

An updated Custom.npm file

The Custom.npm file is ZIP-compressed file that contains all of the custom plug-ins created by the Plug-In Studio. This file is used for two purposes. First, it is used to automatically synchronize plug-ins with other iManager servers in the same tree. Second, it moves the custom plug-ins to another tree. For example, you can take this one file from a test environment to a production environment and simply deploy the NPM and then run the Configure iManager task. The Deploy and Configure tasks are found in the iManager Configure view.