Configuring Your Machine for Trusted Storage
Before starting the license activation and support exercises, configure your machine to use trusted storage. The configuration type depends on your machine’s platform:
| • | Installing the Licensing Service (on Windows) |
| • | Initializing the Trusted Storage Directory (on UNIX) |
Normally, for a licensed product, configuration occurs as part of product installation and is performed only once on a given machine.
Installing the Licensing Service (on Windows)
On a Windows machine, configuration for trusted storage requires installing the FlexNet Publisher Licensing Service and registering the product that is using the service. This procedure uses the example executable installanchorservice.exe.
To install FlexNet Publisher Licensing Service
| 1. | On the Start Menu of your machine, right-click the Windows Command Prompt and select Run as administrator. |
| 2. | To install the FlexNet Publisher Licensing Service and register product PhotoPrint-client that is supplied by publisher demo, at a command prompt in the <platform_dir>, enter |
installanchorservice demo PhotoPrint-client
The output is
Successfully installed anchor service for publisher demo, product PhotoPrint-client
For product PhotoPrint-server that is supplied by publisher demo, at a command prompt in the <platform_dir>, enter
installanchorservice demo PhotoPrint-server
The output is
Successfully installed anchor service for publisher demo, product PhotoPrint-server
Initializing the Trusted Storage Directory (on UNIX)
On a UNIX machine, configuration for trusted storage requires initializing the trusted storage directory. Additionally, for OS X and Linux machines, configuration also requires installing the FlexNet Publisher Licensing Service. This procedure uses the example script installfnp.sh.
Note:On OS X platforms, your user account must have sudo privileges to perform this procedure. On all other UNIX platforms, you must have root permission to perform this procedure.
To initialize the trusted storage directory (and install the FlexNet Publisher Licensing Service, if required)
Perform the appropriate step at a command prompt in the <publisher> directory:
| • | On a UNIX machine, enter the command: |
sh install_fnp.sh
| • | On an OS X machine, enter the command: |
sudo sh install_fnp.sh
The output is
Configuration completed successfully.
If this is your first time through the trusted storage exercises, proceed to Starting the FlexNet License Server. Otherwise, use this procedure to remove any client-side and server-side trusted storage files from previous exercises.
Important:The utilities tsreset_app and tsreset_svr are provided for use with exercises and are not intended to be shipped to an end-user site.
| 1. | To shut down all license servers that might be running, in the <platform_dir>, enter |
lmdown -all
| 2. | To delete any client-side trusted-storage files, at a command prompt in the <platform_dir>, enter |
tsreset_app -delete all
The output is
Performing reset operation, please wait...
Trusted Storage Contents have been reset...
| 3. | To delete any server-side trusted-storage files, at a command prompt in the <platform_dir>, enter |
tsreset_svr -delete all
The output is
Performing reset operation, please wait...
Trusted Storage Contents have been reset...
Starting the FlexNet License Server
Use this procedure to import the vendor daemon demo and start the license server that uses it.
To start the license server and import the vendor daemon demo
| 1. | Copy files <platform_dir>\demo.exe and <platform_dir>\demo_libFNP.dll to the <platform_dir>\lmadmin\demo directory. |
Note:On UNIX platforms, copy files <platform_dir>/demo and <platform_dir>/demo_libFNP.so to the <platform_dir>/lmadmin/demo directory. On AIX, copy demo and demo_server_libFNP_notr.so.
| 2. | To import the vendor daemon demo and use the demo.lic license file, at a command prompt in the <platform_dir>\lmadmin directory, enter |
lmadmin -import demo\demo.lic -force
The output is
Configured new vendor daemon, demo.
| 3. | To start the license server in the background, from a command prompt in the <platform_dir>\lmadmin directory, enter |
lmadmin -allowRemoteStopServer yes