If you are running a demo of the whole Prime Collaboration product (provisioning and assurance) and it is converged, then then licenses for provisioning and assurance are loaded through the Administration/License Management UI.
If you are running a demo of Prime Collaboration Provisioning 9.x as a standalone server then the licenses must be added through the CLI into the /opt/cupm/licenses directory. The product will read the licenses within a couple of minutes and then act on them. A license audit will force this to happen as well.
Starting in PC Provisioning 10.0, the provisioning server has a UI license mechanism so the licenses are added and deleted from this UI.
Make sure you have a license that matches the MAC of the VM and that there is a base license and a scale license or it will not come out of eval mode. You did not say what exactly the license is or is expected to do, so I cannot provide any more advice.
I have a similiar issue. Is the MAC of the VM the MAC address of the VM's network Adaptor? Or is there a CLI command to get the VM's MAC address ? Also, can you tell me what are the part numbers for the base license and scale license ?
The Base licenses really do matter, especially in the Provisioning app, so make sure you get the needed ones. An important note about all UPM revisions and all PCP revs up to 9.5, the base license controls much more than just the number of clusters, users and logins. It also enables the Web services, NICE and JBOSS. If these are disabled, the product will appear to be dead.
Starting in PCP 10.0, the base licesne only controls user related features, and the system related services are turned on permanently.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.