"); gbWndPopupLinks.document.close(); if (!s_bNS3 && gbWndTemp != null) { gbWndTemp.close(); }else { gbWndPopupLinks.focus(); } return true; } return false; } onload = BSSCOnLoad; document.onclick = BSSCOnClick; onunload = BSSCOnUnload; onerror = BSSCOnError; function reDo() { if (innerWidth != origWidth || innerHeight != origHeight) location.reload(); } if ((parseInt(navigator.appVersion) >= 4) && (navigator.appName == "Netscape")) { origWidth = innerWidth; origHeight = innerHeight; onresize = reDo; } //-->

Setting NIAKWA_RUNTIME vs. Copying License File

Step 8. In order for the client portion of the NPLSecure Service to function properly, it must be able to 'see' the server properly. The information it requires is encrypted in the NIAKSER.DAT license file, found in the directory on the server into which you installed NPL security.

There are two methods of making the license file available to the client. The advantages and disadvantages of each are discussed below.

Note: It is very important to choose the best method for your installation. Please contact your Authorized NPL Distributor for assistance.

Copy the License File

One way to give the NPLSecure Client access to the information in the license file is to simply copy this file into the directory on the workstation where NPL is installed.


The workstation does not need to map a drive to the server for security purposes (however this may still be required by your application), and does not need to set the NIAKWA_RUNTIME variable. This is especially advantageous in multiple-tier environments, where some of the workstations are particularly remote, and where controlling the desktop environment is difficult.


If the server name changes, or the NPL security on the server is re-installed for any reason, the file must be recopied to all workstations. Running a local copy of the RunTime, and using a copy of the license file, some network features, such as #TERM, TERMINAL.TBL, NETID.TBL, $USER, #INSTALL, and #INSTALLID may yield unexpected results or may not work at all.


The other way to give the NPLSecure Client access to the license file is to set the NIAKWA_RUNTIME environment variable to the location where it was installed. See the section titled How to Set NIAKWA_RUNTIME for information on how to set NIAKWA_RUNTIME for specific platforms.


Since the license file is not distributed to the workstations, it does not ever have to be redistributed for any reason. All previously available network features, such as #TERM, TERMINAL.TBL, NETID.TBL, $USER, #INSTALL, and #INSTALLID should behave as expected.


The NIAKWA_RUNTIME environment variable is set to either a mapped network drive or a network share. Thus each workstation must be configured and maintained with these settings.

Choose one of these two options and implement it.

Note that both of these options assume that the local copy of the RunTime will be executed. If desired, a server based copy of the RunTime can be executed. If the server copy is in the same directory as the executable, neither option is necessary, as the RunTime will look for the license file in the execution directory.

This completes the installation for the workstation. Note that only the 32-bit version of the RunTime is installed. Repeat this process for each workstation.

In order to uninstall the RunTime from a workstation, see the section titled Uninstallation from Workstations.