|
|
Web NMS is customized using the Eclipseplugin. The customized product is packaged and tested before being shipped. The set of documents here provides guidelines to maintain the development environment viz. your customizations, the build environment and finally packaging the product.
The different stages in the life cycle of a customized product are shown in the image below:
Summary: Links to Other Documents
Given below are the general steps to be executed in the development environment (as shown in the diagram above) for customizing Web NMS:
Perform Web NMS server-side and client-side customization using Eclipseplugin.
Create a directory structure in the versioned repository for checking in your customized source files.
Generate an automated build using a build script.
Release the Customized Product (as Complete Package or Service Pack).
Base Product: It is the platform version of the product over which customizations are performed.
Build: It is a packaged file (EXE, ZIP BIN) comprising all customizations applied over the base product.
Build Script: It is a script file, which automates the creation of the build. It is usually an ANT or a Shell script file.
Complete Package: It is a mode of packaging the customized product as EXE or ZIP or BIN. It is usually considered for major releases of the product.
Service Pack (SP): It is a mode of packaging the product updates as ".ppm" file. These product updates can be deployed over the previously released product.
|
|