Implementing a Proxy on the Notifylink Enterprise Server
Posted by - NA - on 07 August 2009 10:18 AM
NotifyLink Enterprise Server:
When implementing a proxy environment into the NotifyLink Enterprise Server Configuration.
First it is best to confirm what proxy information is being used. You can do so by going into your servers Internet Explorer Browser. Are you able to reach a webpage successfully? If so, then select Tools à Internet Options à Connections Tab à Lan Settings Button.
Does any proxy information exist? If so, you will want to retrieve this information,
If using NLES v 4.6
After retrieving this information we now need to go into the NotifyLink Web directory.
By Default: C:\Program Files\NotifyLink Enterprise Server\Web\Includes
Inside the Helpers.inc you will want to locate the proxy server configuration location.
(in most cases if you select to do a Find: then type< proxy > the 2nd instance down from the top)
$proxyServer = "";
$proxyPort = 80;
From here we will populate the Proxy information that had been taken from the Proxy Server LAN Settings.
$proxyServer = "proxy.ntfy.net";
$proxyPort = 8081;
Confirming Validation of License/Connection:
You will need to confirm if you are able to validate the license successfully periodically through the steps. Depending on what portion of the configuration you are at in your NotifyLink installation/implementation of the proxy.
**New Installation: You can attempt to add your license. Or, you will want to go into the NotifyLink Administrative Web Console and go to License Manager à select a license à License Details à select the Update License button. When the license updates, does it validate successfully, showing the appropriate about of ‘seats’?
**Upgrade/Implementation of Proxy: You will want to go into the NotifyLink Administrative Web Console and go to License Manager à select a license à License Details à select the Update License button. When the license updates, does it validate successfully, showing the appropriate about of ‘seats’?
-You can also verify if the license updated successfully by going to the ValidateLease.html (log). This log can be located by default C:\Program Files\NotifyLink Enterprise Server\Logs
Within the log you will want to see the Key is Valid as it shows below:
ValidateAllLeases: validating key: xxxxxxxxxxxxxxxxxxx-1409
ValidateAllLeases: Key is VALID
The example below is a failed attempt:
ValidateAllLeases: validating key: xxxxxxxxxxxxxxxxxxxx-1176
ValidateAllLeases: Key is INVALID
You now will need to configure Windows to allow the proxy connection for NotifyLink.
Windows Server 2003:
You can configure the proxy settings by running the Window’s Component proxycfg.exe . The file itself may already exist on your Windows Server as you may want to attempt a search to locate the file.
If not, you can retrieve this file from Microsoft’s Knowledge Base or from a NotifyLink Support Representative.
Once the file is located, we now need to open up a Command Prompt to execute the file. First go to the appropriate directory the file is located. (Example below, the file is in the root of C: ) We will then run the file itself by running proxycfg –u then selecting <Enter>.
If you are forcing authentication through the proxy (using NLES x4.6) and none of the above steps are successful, you will want to then add your proxy authentication information within the NotifyLink Web Administrative Console.
Once logged into the console, select Server Administration. You will see the Proxy Settings information at the bottom of the page.
In the Proxy Settings , you may need to populate your server name and authentication information. Once populated click the ‘Apply Changes’ button on the right.
Note: After following the above steps, if you are still experiencing further issues validating your license with NotifyLink, you may want to speak with your network administrator regarding any form of exceptions needing to be made on the proxy.
If no exceptions need to be made, you will want to contact NotifyLink Support for further assistance.