Using KeyServer on OS X
The version of KeyServer and KeyAccess that are included with MacVector 7.1.x work fine on OS 9.x, but may not be stable on Mac OS X.
Problems may be encountered using KeyServer 5.1 on servers running Mac OS X. Similarly, problems may occur while trying to connect to a KeyServer with a client Mac using KeyAccess 5.1 on Mac OS X.
Download and install KeyServer 5.2 or KeyAccess 5.2, as appropriate. You may also need a new license file for KeyServer 5.2.
If you have MacVector 7.2.x, the KeyServer 5.2 (KSServer.sea) and KeyAccess client (KSClient.sea) installers are available on the MacVector program CD in the Network Licensing / KeyServer folder.
Alternatively, the KeyServer 5.2 and the KeyAccess client installers can be obtained from the following Sassafras web site:
http://www.sassafras.com/revisions/downloads.html
One option is to download the complete image that includes KeyServer 5.2, KeyAccess for Mac OS X (now called KeyClient), and several updated components for both Windows and Macintosh. A README file is included in the image that points to crucial documentation (e.g. the component history document and the OS details Appendix). Alternatively, you could download just the KeyServer (KSServer.pkg.tar) or KeyClient (KSClient.sea) installers for Mac OS X, depending on which component you need.
Note: KeyServer 5.2 requires a different license file than was used for KeyServer 5.1. Please contact Accelrys Customer Support if you need a new license file. Consult our web site at www.accelrys.com for contact information.
Use the following general instructions to install KeyServer 5.2 and KeyAccess for Mac OS X.
1. Install KeyServer 5.2 on a networked Mac server.
2. Copy the MacVector license file to the KeyServer 5.2 Data folder.
3. Launch KeyServer 5.2.
4. Install MacVector on a Mac client
5. Install KeyAccess 5.2 on the client
6. Configure KeyAccess on the client to log onto the KeyServer. You'll need the IP address of the machine running KeyServer for this step.
Steps 1-3 are described in detail in the Administrator Guide which is present as a PDF file in the Network Licensing | KeyServer folder on the MacVector program CD.
Steps 4-6 are described in the Network User Guide which is present as a PDF file in the Network Licensing folder on the MacVector program CD.
Install KeyServer 5.2 and KeyAccess 5.2 from the MacVector 7.2 program CD
A KeyAccess 5.2 installer and two KeyServer 5.2 installers are included on the MacVector 7.2 program CD. The KeyAccess installer is a "carbonized" application that runs on OS 9 and OS X, whereas the KeyServer installers are OS-specific. The KeyServer installer labeled for use with OS X should be used if you wish to install KeyServer on a OS X server.
Installation of KeyAccess is quite straight-forward and requires knowledge of the IP address of the machine running the KeyServer. The following discussion describes the installation and configuration of KeyServer 5.2 on OS X.
Note: The KeyServer installer will update any previously installed KeyServer components to the latest version while preserving your custom configuration information.
Installing KeyServer
1. Login to an Admin account.
2. Double-click on the KSServer.pkg.tar file to extract the installer (KSServer.pkg). This step can be omitted if you plan to use the KeyServer installer already extracted on the MacVector program CD.
3. Double-click on the icon for KeyServer.pkg (in the Network Licensing folder on the MacVector program CD). This launches the graphical Installer program which will install the KeyServer. All KeyServer files are installed into the /Library/KeyServer directory.
Installing the MacVector License File
Copy the license file (MacVector n-users.lic) from the MacVector license CD to the KeyServer Data folder located in the /Library/KeyServer folder.
Launching KeyServer
Two approaches are available to launch KeyServer on OS X after the installation:
A. Restart the server machine. KeyServer will automatically launch when the server boots.
Note: By default, the KeyServer program is configured to start up automatically each time your Mac OS X Server is started. This is done using a file named KeyServer in the /Library/StartupItems folder. To temporarily disable KeyServer without uninstalling it (if you are upgrading KeyServer, for example), rename this file to KeyServer-Disabled then kill the ks process from the Process Viewer or reboot the server.
Tip: If you do not want to restart the server machine while updating KeyServer, then you should first stop the running KeyServer process and run the /Library/StartupItems/KeyServer script from a Terminal window while logged in as root, as described below.
B. Use the following commands as "root" in the OS X terminal window to launch KeyServer as a native daemon process:
% cd /Library/KeyServer
% ./ks -d
Stopping KeyServer
To stop a running KeyServer process, use the Process Viewer program from within the Mac OS X Server graphical environment. Alternatively, you can use the kill command at the command line in the OS X terminal window. You can obtain the process id for the 'ks' process by typing ps aux | grep ks at the command line.
KeyServer command line options
The KeyServer program recognizes a few command line options that can be used to control how it runs. The most useful options are listed below.
b [dir]
By default, KeyServer looks for its data folder (KeyServer Data Folder) in the current working directory. If you want to store the data folder in a different location, use this option to specify the directory in which the data folder is stored.
d
By default, when you launch KeyServer it runs as a simple console program, and writes basic status information to the terminal in which it was started. If the terminal is closed, the KeyServer will stop running. To run KeyServer as a “daemon” process, use the d option. When running as a daemon, KeyServer does not write status information to the terminal, and continues to run even after the originating terminal is closed. Note that the startup script, KeyServer, in /Library/StartupItems uses this option.
e [file]
KeyServer can optionally write some status messages to a separate log file, other than the KeyServer log (where program usage information is stored) and the system log (where startup and shutdown information is written). If you want a simple log of KeyServer's startups and shutdowns, specify the log's location using this option.
n [host]
When KeyServer is running on a multi-homed host (a host with more than one IP address assigned to it), it will open its service port on the default IP address. Use this option to force KeyServer to open its service port on a specific IP address.
z [zone]
When KeyServer is running on a multi-homed AppleTalk host (a host with more than one AppleTalk address assigned to it), it will open its service port in the default AppleTalk Zone. Use this option to force KeyServer to open its service port in a specific AppleTalk Zone.
|
