You use configuration files in NAS to describe metadata about the individual components (servlets and EJBs) that make up your application. The information in each configuration file is stored in a registry internal to NAS.
Each application component must have a configuration file associated with it. Servlets use a plain-text format called NTV, Additionally, each application component must be associated with a globally unique identifier, or GUID.
The NAS Registry
The NAS registry is a collection of application metadata, organized in a tree, that is continually available in active memory or on a readily-accessible directory server. The process by which NAS gains access to servlets, EJBs, and other application resources is called registration, because it involves placing entries in the NAS registry for each item.
You can change some of the information in the registry at run-time using the NAS Administration Tool. For more information about the registry, and the Administration Tool, see the Administration Guide.
In particular, see Deploying Application Files Manually in the Administration Guide. This section describes how to register servlets, EJBs, and JDBC datasources manually using provided utilities.
GUIDs
A GUID is a 128-bit hexadecimal number in the following format:
{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
GUIDs are guaranteed to be globally unique, which makes them ideal for identifying components in a large-scale heterogeneous system such as a NAS application.
GUIDs are normally assigned automatically by the deployment tool, or by Netscape Application Builder (NAB). You can generate a GUID manually by using a utility named kguidgen. kguidgen is installed by default into the directory BasePath/bin. That directory must be listed in your search path (your PATH environment variable) in order to generate a GUID.
To generate a new GUID, simply run kguidgen from a command line or window.
|