Zentitle SDK and Library
PLM (Passive License Manager):

PLM is a command line tool built for cross-platform testing without the need for a UI or an application. We recommend PLM command line testing for your initial quick testing to understand how all the parts work and to quickly see results from client to the server.

Licensing Commands

Command Description
NSLValidateLibrary Validate library against your data
PSLGetVersion Library version
PSLGetComputerID Retrieve computer ID
PSLImportLicense Import a license into passive library
PSLGetLeaseExpDate Get Lease expiration date
PSLGetLeaseExpSec Get seconds until Lease expiration
PSLGetMaintExpDate Get Maintenance expiration date
PSLGetMaintExpSec Get seconds until Maintenance expiration
NSLGetLicenseCode Current license code on system
PSLGetAvailProcesses Get number of processes allowed to run
PSLGetFeatureStatus Get the current status of a feature
PSLGetUDF Get the value of an Application Agility field
GetErrorMessage Get error message corresponding to error code

Parameters

Command Type Description
Auth1, Auth2, Auth3 uint The authentication values you picked at lib creation
noLoops uint Number of times to test loop (where applicable)
Pause1 and Pause3 uint in seconds For testing (pause1 is after NalpLibOpen,
pause2 is just before NalpLibClose)
CustomerID uint Last 5 digits of your customer ID number
FeatureCode string A feature code OR udf code OR element pool code
Library string /path/to/library.so
LicenseCode string Client ID for passive license
ProductID number uint Last 5 digits of your product ID number
NalpErrorNo int Nalpeiron library error number
PSLLicense string a passive license or filepath to a file
containing a passive license
LogSize uint Max size of log file in bytes
WorkDir string /workdir/path
LogLevel 0,1,2,3,4 0 is off, 4 is full debug
LogQLen uint length (in number of messages) of log queue
ProxyIP string IP address of intervening proxy
ProxyPort uint Port number of intervening proxy
ProxyPass string Password for intervening proxy
ProxyUser string Username for intervening proxy
WorkGroup string Group name for WorkDir ownership

plm Examples

The following are examples of plm usage. In the examples, auth1 is 10, auth2 20, and auth3 30. The values should be replaced with the values selected when you created your libaries. Likewise, the "license code" clientID should be replaced with a valid clientID associated with your passive license.