Overview

 This article provides the steps to update the Master License Key on the hub. 

Process

 Follow the steps below:

1. Stop all Telescope applications using WebObjects Monitor.
2. Within the WebObjects Monitor, turn off Auto Recover for the Telescope application.
3. Stop the NPS Broker services (as applicable to your installation) in the following order:
   1. Any Broker not listed in the list below (for example, InDesign Broker, Zoom Builder, Zoom Broker, Distribution Broker, Child Indexing Broker, Indexing Broker).
   2. Ingest Broker.
   3. Graphics Broker.
   4. Lookup Broker.
   5. Message Broker.
   6. NTFS File Broker.
   7. Authentication Broker.
   8. Connection Broker.
   9. State Broker.
   10. Session Broker.
   11. Name Server.

   Note: You must stop all NPS brokers on all computers.

4. Open a command window (DOS window) with Administrator privileges (Run as Administrator) on the machine on which Telescope hub is installed and navigate to the Telescope directory (where the sesb.exe file is located. This is usually located in the Telescope installation directory by default - C:\ Telescope).
5. Delete the sesb.dat file in this directory.
6. Run the following command from this directory:
   sesb -remaster <new master key>
   where <new master key> is the new master key string in the license text file. Insert only characters without the braces "[]".
7. Start the following NPS services in the sequential order:
   1. Name Broker
   2. Session Broker
   3. State Broker
   4. Connection Broker
   5. Authentication Broker.
8. Enter the license keys in either of the following ways:
   • Manually
     1. From WebObjects Monitor (or a saved bookmark), start TSAdmin.
     2. Log in to Telescope Administrator as a sysadmin.
     3. Enter all the subkeys in the license text file.
   • Programmatically
     1. Locate the JLicApp.jar file under C:\Telescope\ on the Telescope hub.
     2. Execute the jar file.
     3. Enter the Hub IP address in the licensing tool.
     4. Locate the License Key file.
     5. Click Parse Subkeys button.
     6. Click Apply Licenses button.
9. Start the remaining NPS services in the sequential order:
   1. File Broker.
   2. Message Broker.
   3. Lookup Broker.
   4. Graphics Broker.
   5. Ingest Broker.
   6. Any other broker not listed above. (For example, Indexing Broker, Child Indexing Broker, Distribution Broker, Zoom Broker, Zoom Builder, InDesign Broker).
   7. If the LDAP license was entered above, then you need to restart the Authentication Broker to apply the LDAP license to the Authentication Broker.
10. Review the gb.log file. Ensure the IPieces are loaded correctly. License sub-keys for IPieces that are incorrectly applied will have an error message displayed in this file.
11. Start all the Telescope applications using WebObjects Monitor.
12. Within the WebObjects Monitor, turn Auto Recover back ON for the Telescope application.
13. Test all licensed components in the application to ensure availability.

Back to top