devices targeted for assessment. It expects the Flexera service to already be running. It can be found
in the following location:
C:\Program Files (x86)\ HP JetAdvantage Security Manager\HP Print License Service\HPQ.exe
It looks for license file(s) in the following directory:
C:\ProgramData\HP\HP Print License Service\LicenseFiles
Ports officially used by the HP Print License service include: TCP Port 8888
PORTS
The architecture of the licensing service was built such that many products could share the same
licensing service, and those licensing components could exist on separate machines if desired. It just
so happens that today, Security Manager, HPPLS, and Flexera all reside on the same machine.
HPPLS runs as a separate service and exposes WCF endpoints. Security Manager makes calls to
HPPLS from an outside process, which is why a port is required, even though they reside on the same
machine. TCP Port 27000 is used by Flexera and TCP Port 8888 is used by HP Print License
Service. Nothing traverses outside the company firewall, much less outside of the Security Manager
server, for managing licenses, even though ports are checked.
FLEXERA HEARTBEAT
Flexera Heartbeat is a mechanism by which HPPLS checks whether Flexera Server is up and running.
HPPLS pings the Flexera Server every 2 hours to check whether Flexera is up and running. If Flexera
has not been responding for more than 6 hours (maximum heartbeat time) or more than 2 hours
(heartbeat interval), it is inferred that the Flexera Server is not available or not responding.
The main purpose of having the Flexera Heartbeat is for the HPPLS to be in constant sync with
Flexera. If the Flexera Server is down, HPPLS also shouldn’t service the clients.
If Flexera is not responding within the 2 hours ping of HPPLS, HPPLS won’t be aware that Flexera is
down, hence it will still service the clients. Once it pings Flexera at the next 2 hour interval, it will
come to know it is not responding, and will stop servicing the clients. After 6 hours, if Flexera still
hasn’t been responding, HPPLS will continue to not service the clients and will inform them that
Flexera is down.
Error codes will be returned to the client in these cases when Flexera is down. For example, for
Server not available, the error code -108 is returned. For Server not responding, the error code -109
is returned.
If Flexera is down or not responding, look in the Flexera Log for further details on why it is down.
Stop HPPLS, restart the Flexera Service. Once Flexera is running, HPPLS can be restarted.
When reading the Flexera log file, the sequence in which the licensing is set-up or configured to be
used by Flexnet enabled appsis as follows:
Install Flexnet Licensing Service
Configure the Demo License Server as a Windows Service
Start the Demo License Server
Checking the Status of the Demo License Server
Using a Floating License – demonstrates check-out /check-in of a feature
Attempt to Check out an Unlicensed Feature
Stop the Demo License Server
Comentários a estes Manuais