[. . . ] Licence Server User Guide
Edition 5. 1 November 2007 Booklet written by Daniel Spreadbury, Andrew Pearson and Richard Payne.
Sibelius Licence Server copyright © 20012007 Sibelius Software, a division of Avid Technology, Inc. The Sibelius Licence Server constitutes part of the Sibelius Product and is subject to the Sibelius licence agreement, supplied with Sibelius or available on request. You are not licenced to install or use the Sibelius Licence Server unless you are a registered Sibelius network version user.
Contents
Introduction to network site licences . 16
Configuring and using the Licence Server
19
Configuring the Licence Server . [. . . ] * If all else fails, refer to the further troubleshooting steps in Troubleshooting on page 37.
Registering the Licence Server
To register the Licence Server, click Register. The following dialog appears:
* Type your Sibelius serial number into the Serial number edit box. Once you have typed it in
correctly, the Generate Computer Number will become enabled. Now you should contact Sibelius registration with your serial number and Computer Number. 25
Sibelius Licence Server User Guide
* When you receive your Registration Number from Sibelius registration, type it into the Regis-
tration Number edit box. Once you have typed it in correctly, the OK button will become enabled. * Click OK to complete the registration: after a few moments you will be told that your registration was successful. You will now see the following status messages at the bottom of the Server Status page:
Congratulations!Notice that you are told the total number of copies in your license (in the above example, 25 clients), and how many clients are connected at the moment (in the above example, none). The next step is to test client-server communication with the Licence Server using the built-in testing feature.
26
Testing the Licence Server
Testing the Licence Server
Once you have registered the Licence Server, you can test client connections to the server using the Licence Server Control Panel. Choose the Server Options page:
To test client connections, simply set the Number of clients to simulate, then click Run Test Now. The Licence Server Control Panel will spawn the specified number of windows (so be careful not to set too high a number!), each of which pretends to be a running client copy of Sibelius. Each window has a colored background:
A green background means that the test client is running successfully. You can see a log of the communication the client has received from the server in the pane at the bottom of the test client window.
27
Sibelius Licence Server User Guide If a test client fails to connect for whatever reason, it shows a red background:
Again, you can see the reason why the test client failed to connect in the pane at the bottom of the window. In the above example, the Licence Server already had the maximum number of allowed clients connected, so it refused authorisation (hence the message not enough licences). To close all the test client windows, click Close All Test Clients.
If no test clients can connect
If no test clients are able to connect to the Licence Server, consider the following:
* Is the Licence Server running, and if so, is it correctly registered?Check the read-out under
Server Status on the Status page of the control panel. * Is your firewall blocking communication between the Licence Server and the test clients?Make sure that the correct port (7312 by default) is open for both the TCP and UDP protocols. * Is the Licence Server prevented from accepting client connections from the IP address of the computer you are using to test the connection?If all else fails, consult Troubleshooting on page 37.
28
Access Control
Access Control
On the Access Control page of the Licence Server Control Panel, you can set up rules about which computers on your network can connect to the Licence Server in order to authorize client copies of Sibelius or change settings for the Licence Server itself.
Clients and Managers
By now you will be familiar with the term client, meaning a computer on which Sibelius is installed, and which will be connecting to the Licence Server for authorization. A manager is a computer from which it is possible to change settings for the Licence Server. [. . . ] So to allow localhost (127. 0. 0. 1) and all machines on the subnet 172. 24. 170. * access to the Licence Server, on Windows type:
LicenceServerV5 -setvar ALLOWED_CLIENTS "127. 0. 0. 1, 172. 24. 170. *"
On Mac, type:
. /LicenceServer -setvar ALLOWED_CLIENTS "127. 0. 0. 1, 172. 24. 170. *"
46
Appendix B: Manually configuring the Licence Server to which the response will be: Set variable ALLOWED_CLIENTS = 127. 0. 0. 1, 172. 24. 170. * To check your access control settings, use the -getvar command. On Windows, type:
LicenceServerV5 -getvar ALLOWED_MANAGERS
On Mac, type:
. /LicenceServer -getvar ALLOWED_MANAGERS
to which the response will be something like: Got variable ALLOWED_MANAGERS = 127. 0. 0. 1 To check which machines are allowed as clients, on Windows type:
LicenceServerV5 -getvar ALLOWED_CLIENTS
On Mac, type:
. /LicenceServer -getvar ALLOWED_CLIENTS
to which the response will be something like: Got variable ALLOWED_CLIENTS = 127. 0. 0. 1, 172. 24. 170. *
47
Sibelius Licence Server User Guide
Appendix C: Manually locating Licence Server logs
Normally you should view the Licence Server's logs using the Licence Server Control Panel, but should you need to do this manually, do so as follows.
Logging on Windows
The Licence Server creates a log file called LicenceServerV5. log. The log file is normally located in:
* Windows 2003 Server: C:\Documents and Settings\Default User\Application Data\Sibel-
ius Software\Logs * Windows XP: C:\Documents and Settings\LocalService\Application Data\Sibelius Software\Logs * Windows Vista: C:\Users\LocalService\AppData\Roaming\Sibelius Software\Logs The exact location depends on your computer's settings, so it may be necessary to search for the folder. The logs are updated with every event.
Logging on Mac OS X
The Licence Server creates a log file in /var/log called LicenceServer. log (unless you have changed its name and location in the start_licence_server script). [. . . ]